The listing is still on the market. The landlord thinks you are working it. The tenant at the other property left a voicemail about a leak that is not a leak until someone sees it. A buyer who toured last Thursday asked a question that did not make it into the file. You open the CRM.
The contact is there. Name, phone, email, company, last meeting. A note that says "good conversation." A stage that someone set in January and never touched again.
What is next on this deal?
The screen does not know.
That is the whole problem, and it is not a data-entry problem. Most CRMs store people. The work in commercial real estate is what happens after the last conversation.
A rolodex can be full and the week can still be empty
A 40-person shop in this business can look organized from the parking lot. Brokers have books. Property managers have stacks. The front desk can find a phone number. Leadership can pull a list of "active" contacts that looks like a pipeline if you do not ask what active means.
Ask.
Active as in we spoke this month, or active as in there is a live listing, a live tour, a live lease, a live work order? A contact list will answer the first kind of question. It will not answer the only question that moves rent, a sale, or a repair: what is the next step on this property, who owns it by name, and when it goes stale.
You can have thousands of contacts and still miss the landlord who expected a call after the second showing. The record stored the landlord. The deal did not have a home.
What the work actually is
Walk a brokerage morning without the software story.
A listing comes in. Someone said yes. Photos are promised. A flyer is "in progress." The owner wants weekly updates. A colleague has a buyer who might fit, but that colleague is in a tour across town and the fit lives in a text. The listing record, if there is one, is a property address and a price. The next step is a feeling.
A tour happens. The buyer liked the dock height and hated the office. Someone was supposed to send comps. Someone was supposed to ask the landlord about a shorter term. Those "supposed tos" are the deal. They are not fields next to the phone number.
An offer shows up in email. It is a PDF. It is also a phone call that contradicts the PDF. The version the team discusses at lunch is the phone call. The version in the file is the PDF. The landlord has a third version from a conversation on Saturday.
Now walk a property management morning.
A tenant reports something. It hits a shared inbox, or a portal that emails the shared inbox. A tech is assigned in a text. The work order, if you can call it that, is a thread. The next step is "waiting," which is a polite word for "not in a system."
A lease is 90 days from end. The contact is in the CRM. The renewal conversation is not. It is on a to-do list that belongs to a person who also has 40 other to-dos that are not attached to properties. When that person has a sick day, the date does not get less real.
This is how the business runs when the official system is a directory and the unofficial system is memory plus email.
People are not the unit of work
This is where generic CRM thinking fails a CRE floor.
A CRM that thinks like sales software wants a person, a company, a stage, a close date. That is a bad map of a listing, a lease, a work order, or a tenant relationship that lasts longer than the broker who logged the cell.
The unit of work is the deal, the property, the unit, the job on the property. People attach to those. A landlord, a tenant, a buyer, an attorney, a contractor. If you only store the people, you force every next step to live in a note, and notes do not chase anyone.
"Called Jim" is not a next step. "Send Jim the revised rent schedule and ask for a decision by Thursday, and if he does not answer, call the other contact on the ownership" is a next step. The first one fits in a contact timeline. The second one needs a place that is not a biography.
Same for a property. "123 Industrial is listed" is a status. "Need the landlord to approve the dock repair before the Tuesday tour, and the repair quote is sitting with the PM who is out" is the week. If your system can store the address and not the Tuesday problem, you have a catalog. Catalogs do not collect fees.
Follow-up is the product
In this business, follow-up is not a courtesy. It is the work.
The listing that dies quietly usually does not die from price on day one. It dies from a week where nobody told the owner what happened, then another week, then a conversation that starts with "we thought you were on it." The CRM still has the owner. The owner still has a phone number. The next step expired in someone's head.
The tenant who leaves often told you, just not in a field you report on. They told a tech. They told the office in a tone. They asked about a renewal and got a "we'll get back to you" that never became a task on the property. You can run a contact report and look healthy while the building is emptying.
Brokers are not lazy. They are overbooked, and overbooked people do the thing in front of them. A system that only stores contacts makes the next step optional. Optional work loses to the tour that is already on the calendar.
If you want to know whether you have an operating system or a rolodex, do not look at how many fields you capture. Look at a deal that went quiet. Ask the system what should have happened after the last touch. If the answer is a blank timeline and a human saying "I was going to," you have a list.
The Friday question has a CRE accent
Owners and partners already have the question. They ask it in the hall, in the car, in a Sunday text. What's next on this listing. This tenant. This buyer. What slipped that still has our name on it.
A contact list answers "who." The Friday question is "what" and "by when" and "is it still true." When the answer requires pulling three people into a room, you do not have a reporting gap. You have a system that does not hold the work. The meeting is the query.
That meeting gets romanticized. "We are a relationship business." You are. Relationships are not the opposite of a next step. A landlord does not experience your culture. They experience whether you called after the showing with the thing you promised. Charm still matters. Charm does not run a book of listings and tenants when the only shared truth is a contact record and a spreadsheet someone updates when they have time.
Duct tape looks like a stack
Email is where the deal actually moves. The CRM gets a note if someone has a virtuous hour. A shared workbook is the real pipeline because leadership already opens it. A drive folder per property, if you are lucky. If you are not, the photos are in a text and the old survey is in an email from a person who left.
A generic CRM sits on top of that and asks the team to log activity. Logging activity is not the same as advancing a deal. It is theater that produces a timeline. Comforting in a review. Useless at 7:50 a.m. when a tenant is in the parking lot.
People then buy AI seats and summarize the email they are about to forget to turn into a next step. Faster notes. Same hole.
Replacing duct-taped workflows does not mean buying a bigger rolodex. It means the listing, the lease, the work order, and the follow-up have a home built around how the business actually runs.
What "what's next" looks like when it is real
You do not need a science project. You need the object the floor already talks about.
A listing should carry the next action, who owns it, when it goes stale, and the last thing the landlord was told. If those are empty, the listing is not in the system. The address is. A deal should survive a broker being in a car. A property should hold the open tenant issues and the lease dates that create work. The contact still matters. It is not a substitute for the issue.
When something changes, the record should change. If it takes a data-entry mood, people will stop using it, and they will be right.
This is not a claim that a packaged CRE product is sitting on a shelf. The shops that get this right do not contort the floor to fit a generic pipeline. They build the broken process as software: the follow-up, the listing cadence, the tenant issue, the Friday question. One process is enough to start. The contact list can stay. It just stops pretending it is the company.
Frozen custom is how you get a second rolodex
A lot of firms already tried "our system." It matched the process of the year it was scoped. Then the team added a step. Then the person who could change it left. Custom software often freezes the day it ships. The floor does not. The live list moves back to the sheet.
That is not an argument against custom. It is an argument against custom that cannot take a correction. If the next-step language on a listing changes and the software cannot, you will get a column called "real status." You already have that column.
Do not start with a data cleanup
The tempting project is to clean the contacts. Deduplicate. Add titles. Force everyone to log calls for 30 days.
You will spend the quarter on hygiene and still not know what is next on the deal.
Clean data is good. It is not the work. The work is the promised follow-up that has no owner. Start there, even if the phone numbers are messy. A messy contact with a live next step beats a perfect contact with a dead stage.
If you need a picture of the mess, sit with one broker or one PM for an hour and watch what they open after a call. That second screen is your current operating system. The CRM is the archive.
Ten records, one afternoon
This week, pick ten live things. Mix them. Listings, tenant issues, deals that are supposed to be warm.
For each one, write a single sentence: what is next, who owns it, when it goes stale. Do it on paper if you have to.
Then try to find that sentence in the official system without asking a person.
Count the misses. Do not dress them up. A miss is a record that stores a human and not a next step.
If most of the ten fail, you do not have a CRM problem in the way vendors mean it. You have an operating-system problem. The contact list is doing contact-list work. The company is trying to run a book of properties on top of it.
If you want that book built as a system, not another SaaS subscription you have to feed, tell Mantum what is broken. The listing that goes quiet. The tenant issue that lives in a thread. The Friday question you cannot ask without a meeting.