Selling Into Real Estate Agencies: The Principal Signs, and He's Been Pitched Three Proptechs This Week

An agency principal is the cleanest buyer in software and the hardest one to get thirty seconds from. He owns the business. He signs the contract. There is no procurement, no security questionnaire, no IT director who needs to "take a look at it," no committee that meets on Thursdays. If he likes you on Tuesday you can be live on Friday.

He is also the guy who has taken three proptech calls this week, sat through two demos that looked identical, and is currently standing in a hallway between an appraisal and a team meeting while you talk. He is deciding whether you are worth the rest of the call inside the first ninety seconds, and he is deciding it on tone before he decides it on product.

That trade is the whole game. One signature, no patience. Everything below is about earning the patience.

What he is actually protecting

Before you write a word of your pitch, get straight on what the man is defending. Almost every rep I have watched sell into agencies pitches efficiency at a buyer who is not primarily worried about efficiency.

The listing pipeline

Listings are the business. Not sales, not settlements, not the CRM — listings. A principal who is short on stock has a problem that compounds: fewer boards in the ground means fewer buyer enquiries, which means fewer future vendors calling his office instead of the agency two streets over, which means his best agents start wondering whether the desk is worth the split. Everything in his head runs back to appraisals booked and listings won.

So when your product touches lead capture, portal enquiry response, appraisal follow-up, or vendor reporting, you are near the artery and you should say so plainly. When it does not — when you sell trust accounting or compliance or document management — do not pretend. Pretending is how you get the "send me some info" brush-off. Sell the second-order version honestly: this takes an hour a week off your property managers so they stop asking your sales team for help.

Agent retention

The second thing he protects is his people, and he protects them nervously. Good agents leave. They leave for a better split, for a franchise brand, for their own shingle, and they take their database with them when they go. A principal who has lost a top writer knows exactly what that quarter looked like.

This is why he flinches at anything that adds work to an agent's day. He is not being lazy on their behalf. He is calculating whether the thing you are selling gives an agent one more reason to feel like the office is making their life harder. If your product makes his best writer's life visibly easier, say that early and in their language, not yours.

The economics of the split

The principal thinks in margin per desk. Whatever his split arrangement is, he knows what a desk costs him and what it has to produce. Every software subscription he signs is a fixed cost sitting against a variable revenue line that swings with the market.

That means a per-seat product is a scarier purchase to him than it is to a VP of Ops at a company with a software budget. A seat is a person. A person is a split. If you price per agent you are asking him to do arithmetic he does not enjoy in a market he cannot forecast. We will come back to this.

"My agents won't use it" is not an objection

It is the decision criterion. Treat it as an objection and you will spend the call arguing. Treat it as the actual question on the table and the call gets easy.

He has bought software before. Someone sold him a platform, he paid for it, and three weeks later he walked the floor and found two of his agents still working out of a spreadsheet and one still working out of his own head. He paid for that for a year. The scar is real and it is recent, because the proptech category has been throwing product at this buyer for a long time.

So he is not asking whether your software works. He assumes it works. He is asking whether adoption will happen in his office, with his people, without him having to become the enforcement mechanism. That last part matters most. A principal does not want to spend his Monday meeting nagging adults about logging activity.

Which means your job in discovery is not to prove capability. It is to prove that adoption is a solved problem and that you, not he, are the one solving it. Some ways to do that which do not sound like marketing:

Name the failure mode before he does. "Half the agencies that buy this get it live with the admin team and the sales team never touches it. That is the thing I want to avoid, so can I ask how the last rollout went here?"

Ask who the hold-out will be. Every office has one. He will name him instantly, usually with a laugh, and often the name is the top writer. Now you are both looking at the same problem from the same side of the table.

Ask what happened to the last tool. Not "what are you using now" — what happened to the thing before it. The answer tells you the shape of the resistance and gives you the language he will use with himself when he decides.

I have written the longer version of this conversation as a twenty-five minute discovery structure for agency principals, because twenty-five minutes is genuinely all you get and the sequencing matters more than the questions.

The first ninety seconds

He answers his own mobile. That is the first thing to understand. There is no gatekeeper, which sounds like a gift and is actually a trap, because it means he is answering while driving, while walking into an open home, while a vendor waits. You have caught him mid-something, always.

So lead with the acknowledgment and get to the point faster than feels comfortable:

"Tim from [company], I know this is a cold call and I know you have had a few of these this week. Thirty seconds and you can tell me to go away."

Then one sentence on what you do, framed as a problem he has, not a category you belong to. "We handle the portal enquiries that come in after six at night so your agents are not answering them at ten the next morning." Not "we are an AI-powered engagement platform." He has heard that sentence three times this week and it means nothing to him, because it means nothing.

Then a real question. Not "is that something you'd be interested in" — a question about his office. "How are those getting handled at the moment, is that on the agents or does the front desk pick them up?"

If he engages, you are in. If he says send me an email, ask one clarifying question first so the email has a reason to exist, because an email with no reason gets deleted. The full call structure, including the openers that survive a principal who is clearly in a car, is in the real estate cold call script.

One more thing on timing. He is busiest when his agents are busiest, and his agents are busiest on Saturdays and on the evenings around open home follow-up. Mid-morning midweek, after the sales meeting, is when he is at a desk. Not a statistic, just the shape of the week in that industry — ask any principal and he will tell you the same.

The demo where he interrupts on slide two

He will. Assume it. You are two minutes in, still on the setup slide, and he says "yeah, we looked at something like this" or "how is this different from [competitor]" or just "can you show me the actual thing."

Almost every rep I have watched handles this badly in one of two ways. Either they apologise and skip ahead in a panic, losing all structure and ending up clicking around a product with no story. Or they say "I'll get to that in a moment" and keep going, which to an owner-operator reads as: this person is running a script and does not care what I asked.

The right move is to stop, take the interruption as the new agenda, and say so out loud.

"Good — then let me not waste your time on the intro. What did you look at, and what stopped you?"

That question is worth more than the next ten slides. He will tell you the actual objection, the actual price he was quoted, and usually the actual reason the last thing failed. Now you demo against that instead of against your standard flow.

The discipline is to keep one thread rather than showing everything. Pick the single workflow that maps to what he just told you, run it end to end, and narrate it from the agent's chair, not the admin's. "Your agent is at an open home. Enquiry comes in on the portal. Here is what lands on his phone. Here is the one tap." A principal watching a demo is not evaluating features; he is imagining his hold-out agent doing the thing on a Saturday afternoon and deciding whether it will happen.

Then check the imagining out loud. "Is that a thing you can see Dave doing?" If he hesitates, that hesitation is the deal. Chase it rather than moving on. I have laid out the full flow for running a demo when the principal interrupts, including how to re-open structure after you have abandoned it, which is the part people get wrong.

One small thing that matters more than it should: do not demo on a laptop screen turned sideways in his office while he stands. Either sit down properly or send a short recording and book fifteen minutes to talk about it. Half-demos in hallways lose deals that would otherwise close.

Pricing against a man who thinks in per-listing and per-agent

Here is where a lot of proptech deals go sideways. Your pricing page says per seat per month. His brain says per desk per month, and his desks are not all equal. He has a couple of writers who bill, a couple who are building, an assistant or two, a property management side that may or may not be in scope, and a principal who lists himself and does not consider himself a seat.

So when you quote per agent, three things happen at once. He counts heads. He counts the heads he is not sure about. And he starts sandbagging — telling you he only needs four licences when he has eight people, because he wants a smaller number to say yes to.

Two ways through this that I would use.

First, anchor on the unit he already values. If your product touches listings, price the conversation in listings before you price it in seats: "across the office, if this brings in one extra listing a quarter it has paid for itself several times over — do you want to walk through whether that is realistic?" You are not making up a number, you are asking him to supply his own. He knows his average commission better than you ever will. Let him do the maths in his head and land on his own answer. It sticks harder than anything on your slide.

Second, sell the office, not the seat, whenever your pricing lets you. An office price removes the head-counting problem entirely and it removes the adoption tax — because the moment a principal is paying per seat, he has a financial incentive to limit rollout to the agents he is confident about, which is exactly the wrong incentive. You want everyone in from day one. Say that out loud: "I would rather price the office so you are not deciding who gets it. Partial rollouts are how these things die."

If you must price per seat, at minimum give him a floor and a glide path. He needs to know what happens when he hires two agents in March and what happens when someone leaves in June. An owner-operator's real fear about subscription pricing is not the price, it is being locked into a shape of business that changes.

Holding the number

The principal will ask for a discount. It is not personal and it is not usually a real objection — it is a reflex from a man who negotiates for a living. He negotiates commission with vendors every single week. He is very good at it and you are not going to out-negotiate him, so do not try.

What works is being boring and consistent. State the number, explain what is in it, and then do not fill the silence. If he pushes, trade rather than cut: a longer term, a case study, an introduction to two other principals in his network, a payment up front. Never give a number away for nothing, because the moment you do, he knows the first number was soft and everything you say afterwards is a starting bid.

Watch also for the reverse trap. Sometimes the discount ask is a tell that he has already chosen you and is just collecting his win before signing. If the conversation has moved to implementation dates and who gets access first, he is buying. Hold the number and give him a small non-price concession so he still gets to feel like he negotiated. I have written the specific language for holding your price with a principal who has already decided, including the three trades I would make before I moved on price.

What actually separates the reps who win this buyer

It is not product knowledge. Everyone selling into this market has roughly the same demo. It is the ability to stay composed and useful in the first ninety seconds of a call with someone who is busy, sceptical, and slightly rude by accident. That is a performance skill, and performance skills do not improve by reading about them.

The reps who are good at this have simply had the conversation four hundred times. They have heard "we looked at something like this" so often that it lands as a gift instead of a threat. They have a next sentence ready for every version of the brush-off, and the sentence comes out flat and calm rather than fast and defensive.

The uncomfortable truth is that most reps get those four hundred reps by burning through live pipeline, which is an expensive way to learn. If I were building this skill from scratch for a proptech team today, I would take the three moments in this post that decide deals — the ninety-second open on a principal's mobile, the demo interruption on slide two, and the discount reflex at the end — and drill each of them out loud until the response is automatic, before anyone touches a real list. That is exactly what we built DrillCall for: an AI buyer who plays the impatient owner-operator so your first hundred bad attempts happen somewhere that does not cost you a territory.

The agency principal is one of the best buyers in software once you get past his front door. One person, one signature, fast decisions, and if you do right by him he will tell every principal he knows. You just have to survive the first ninety seconds, and that part you can practise.