Real Estate · Demo Call

Real Estate Product Demo Script: Running the Demo for Principals Who Interrupt

You already had the pitch call. The Principal said yes to a demo, which means they are not dialling in to find out what it does — they're dialling in to find where it breaks. They've been cold-called by three proptech startups this week. They've bought AI copywriting that got used twice, a digital appraisal tool that never talked to VaultRE, and a callback product that nobody was accountable for. So they arrive with a list: what does this hook into, who owns it when you're gone, what happens on a Saturday at 9am when it calls a buyer and says something stupid, and how long before it's actually producing anything they can show a vendor.

They will interrupt. Every interruption is either a buying question or a disqualification test. The one thing that loses this call is the standard tour — the login screen, the settings tab, the dashboard with the pretty graph. Do that and you'll hear typing, then "yeah, no, that makes sense," said flat, and the deal dies four weeks later without anyone saying no.

This script is built around the moments a principal actually feels: Saturday morning portal enquiries landing while every agent is running opens back to back; the Sunday-night vendor report that gets copy-pasted from last week; the week-four price conversation with no documented buyer feedback to stand on. Show three of those completely and you'll beat any demo that covers twelve features partially. The numbers this room is judged on — lead response time in minutes to first contact, enquiry-to-inspection conversion, appraisal-to-listing conversion, days on market, market share of listings by postcode — belong inside the demo, not in a slide at the end.

The demo call script

Say it in your own words. The structure is the part that matters.

  1. 1

    Before the call: confirm the stack in writing

    Send this in the confirmation email, 48 hours out: "Quick one so I don't waste Thursday showing you things that don't apply — three questions: 1. What CRM are you running? VaultRE, Agentbox, Rex, MyDesktop, Box+Dice, something else — and who administers it in the office? 2. When a realestate.com.au or Domain enquiry comes in, where does it actually land — straight to the listing agent's inbox, into the CRM lead pool, or to a shared sales admin address? 3. Who's on the call with you and what do they need to walk away with? I'll build the demo around your listings, not a sandbox." Then do the homework: pull three of their current listings off the portal — real street names, real price guides, real open home times. If they carry an auction book, note the clearance rate they'd be quoting in a listo. Load those into the demo environment. A demo running on '123 Test Street, Sample Suburb' tells a Principal you didn't prepare, and they will discount everything that follows.

  2. 2

    Before the call: decide what you will NOT show

    Write the not-list before you open the laptop. Do not show: the user admin screen, the billing tab, the AI listing-copy module they didn't ask about, the mobile app if nobody raised mobile, the settings page for call scripts. Every feature you demo that they didn't ask about is a feature they now have to evaluate, question, and price in their head — and a Principal with proptech fatigue counts unrequested features as future abandoned modules. Pre-build exactly three screens, tied to what they said on the pitch call: 1. The Saturday 9:14am portal enquiry, called and booked. 2. The post-open vendor report that writes itself Sunday morning. 3. The listing presentation evidence page — buyer numbers, enquiry source, price feedback on a comparable campaign. If they only get through two, that's a good demo.

  3. 3

    Opening: 90 seconds, set the contract

    "Last time we spoke you said Saturday's the problem — enquiries land while all eight agents are running opens back to back, and by the time someone calls Monday the buyer's already inspected three other properties. You said you can see the enquiry count in the portal dashboard and you can see the inspection numbers, but you can't prove which agent dropped which lead. Still the case?" (Let them answer. Then:) "Anything shifted since we spoke — new listings, someone resigned, a vendor giving you grief?" (Then the contract:) "Two things before I share my screen. One — please interrupt me. If you're sitting there thinking 'that won't work here, my agents won't touch it,' say it in the moment. That's the useful part of this call, not the polite part. Two — what's the one thing that, if this can't do it, we don't need to keep talking? Tell me now and I'll show you that first." Whatever they name, that becomes screen one. Reorder live. Say it out loud: "Right, then I'm skipping the front end entirely and going straight to that."

  4. 4

    Core loop 1: the Saturday enquiry

    PROBLEM — "It's Saturday, 9:14am. Deb's at the 9:00 open at [their real listing address], she's got another at 9:45 and a third at 10:30. An enquiry comes through on that listing from a buyer who's sitting in the car outside." SCREEN — Narrate as the buyer and the agent, never as the software. "The enquiry hits the CRM lead record. Eight minutes later this buyer's phone rings. Listen to it — [play the call, 30 seconds, not three minutes]. It qualifies: are you looking in this pocket, are you pre-approved, have you sold. Then it books him onto the 10:30 open and texts him the address." CONSEQUENCE — "Deb finishes her 9:45, opens her phone, and there's a name on the 10:30 list with three lines of qualification underneath it. She didn't do anything. Her lead response time on that enquiry was eight minutes instead of Monday." CHECK — "Is that how your Saturdays actually run, or am I making that up? Where do your enquiries land right now — agent's inbox or the lead pool?" Then shut up. Their answer reshapes the next ten minutes.

  5. 5

    Core loop 2: the Sunday-night vendor report

    PROBLEM — "Week two of a six-week campaign. Vendor at [address] rang you on Tuesday because he hadn't heard from his agent since the open. And when you get to the price conversation at week four, there's nothing written down — no record of what buyers actually said about the price." SCREEN — "Open closes 10:30. By 11:15 this exists: eleven groups through, seven of them came from realestate.com.au, two from the board, two repeat. Four gave price feedback — three of them said the same thing about the guide. Agent reviews it, adds a line, hits send." CONSEQUENCE — "Vendor gets a report Saturday lunchtime instead of Monday night. And at week four, when the agent sits down for the price conversation, there are four weeks of documented buyer feedback in front of them instead of 'the market's telling us.' That's a completely different conversation." CHECK — "How are your agents doing vendor reports now — is it a template in the CRM, or is it whatever they type at 9pm Sunday?"

  6. 6

    Core loop 3: the evidence in the listo

    Use this if they've raised stock shortage — and most Principals will. PROBLEM — "You're up against two other agencies on a listing presentation in [their farm suburb]. All three of you will say you get more buyers through. Two of you will say it." SCREEN — "This is the page that prints into the listo. Last four campaigns in that postcode: groups through per open, enquiry source split, average time from enquiry to first contact, days on market. Real numbers off your own campaigns." CONSEQUENCE — "You're not pitching a promise, you're handing the vendor a page. That's an appraisal-to-listing conversion tool, not a lead tool." CHECK — "What's your appraisal-to-listing sitting at across the office at the moment? And is it even across the team or is it two agents carrying it?"

  7. 7

    Handling 'will it handle X?' — the pattern

    1. SLOW DOWN, GET SPECIFIC. "Will it handle auction campaigns?" is unanswerable. Ask: "Tell me the actual case — is it that you want buyers registered before auction day, or that you don't want it giving a price when there's no price to give?" 2. ANSWER ONE OF THREE WAYS, HONESTLY. - Yes, and here it is — go show it live, right now. Strongest thing that happens on this call. - Yes, but not how you'd expect — "You don't do it from the listing, you do it from the buyer record, and it's two extra clicks." Principals forgive ugly. They don't forgive finding ugly in month three when the vendor's already complaining. - No. Say no. "No. It doesn't call vendors, only buyer enquiries. Not this year either." Then: "How often does that come up — every campaign, or once a quarter?" 3. NEVER say "we can build that" or "that's on the roadmap." To a Principal who's been burned, that is word-for-word the promise the last vendor broke. 4. WRITE IT DOWN OUT LOUD. "Noting that — buyer registration into the auction register. I'll come back to you Thursday with a straight yes or no." Then do it Thursday.

  8. 8

    Pressure line 1: integration (what they're really asking is 'will this talk to my CRM')

    Raise it before they do. It's a credibility move. "Let me do the boring part before you ask, because I know the last thing you bought didn't talk to VaultRE. We read the lead record out of [their CRM] — the enquiry, the listing it came from, the buyer's mobile. We call, and we write back three things: a contact note with the transcript, the inspection booking against the open home, and a qualification tag on the buyer record. That's it. Reads on the enquiry, writes on completion. What we don't touch: your trust account, your rent roll, your property management side, and we don't post anything back to realestate.com.au or Domain. Your data stays where your data is. Setup is an API key from your CRM admin — that's [name the person they gave you], and it's a twenty-minute call, not an IT project." If they're on an older on-prem instance or a heavily customised setup, say what that means now, with the extra step named. Discovering it at contract stage kills the deal.

  9. 9

    Pressure line 2: who owns it once you're gone

    "Here's the honest version of the ongoing work, because 'nobody used it' is what killed the last one. Ongoing it's about thirty minutes a week and it's not IT work — it's adding an agent when someone starts, changing the open home buffer, checking the exception list of calls that didn't connect. Your Operations Manager or sales admin does it. If they're on leave for a fortnight, nothing stops; the exception list just gets longer. On my side: I run the setup, and I'm also the person you call after. Same phone number, not a handover to an account team you've never met. And for the first thirty days, I want one named person owning adoption — not 'the office.' Who would that be here?" Make them name a human out loud. If they can't, that's a real risk and you should say so.

  10. 10

    Pressure line 3: what happens when it breaks

    Never lead with an uptime percentage. Give them the failure mode. "If we fall over on a Saturday morning, the enquiry doesn't disappear. It sits in your CRM lead pool exactly like it does today and the agent works it the way they work it now. You lose the eight-minute callback, you don't lose the lead. If a call goes sideways — buyer says something the system can't handle — it stops, sends the agent an SMS with the buyer's name and number and a one-line reason, and logs it. It doesn't keep going and it doesn't guess a price on an auction listing. Support: Saturday between 8 and 5 is a phone number and a human, because that's when it matters in this business. Weekday evening is email, next business day. I'm not going to pretend it's 24/7." If they ask about the last incident, describe one honestly. Principals trust vendors who can describe an outage more than vendors who claim none.

  11. 11

    Pressure line 4: time to value, in three dates

    Never give one date. Give three, tied to their campaign calendar. "LIVE — enquiries flowing and calls going out: end of week one. We'd switch it on a Thursday so the first real test is the Saturday. USEFUL — one thing stops being done the old way: by the third Saturday, your agents stop doing Monday morning callback chase, because there's nothing left to chase. FULLY ROLLED OUT — every agent, every listing, vendor reports going out automatically: four to six weeks, which is roughly one campaign cycle. What I need from you: an agent list with mobiles, the CRM API key, and forty-five minutes with the team on a Tuesday sales meeting. That's your whole workload. I'd rather tell you that now than have your Operations Manager discover it in week three and stall the rollout. And we wouldn't switch on the week you've got [their auction date / big campaign launch] running." Then one reference in their world, as a sentence, not a logo: "[Agency], two offices, went live on a Thursday, first booked inspection the Saturday morning, vendor reports automated by week three."

  12. 12

    Reading disengagement and recovering

    Signs: shorter answers, 'mm-hm', typing, a beat of delay before responses, 'yeah, no, that makes sense' said flat, camera off. Stop. Do not push through. In order of preference: "I've been talking for a while — is this the part you care about, or should I jump to something else?" "Let me stop the tour. What's the thing you're worried about that I haven't touched yet?" "Do you want to drive? Tell me what to click." (Almost nobody offers this. It works.) "I think I'm showing you the wrong things. Can I stop, take ten minutes to understand what actually matters here, and come back Thursday with a demo built for that?" What does not work: talking faster, adding a feature, or 'one more thing I want to show you.'

  13. 13

    Closing the demo

    1. SUMMARISE THE FIT AND THE GAPS — gaps out loud. "Three things landed: the eight-minute callback, the vendor report writing itself, and the evidence page for the listo. Two open: whether it can push buyer registrations into your auction register, and how it behaves on your off-market listings. I'll have both answered Thursday." 2. TEMPERATURE. "Where does this sit for you now — worth pursuing, or has something already ruled it out?" Let them say no. A clean no today beats four weeks of chasing. 3. WHO ELSE. "Who else needs to see this before it's real — your Director of Sales? Your Operations Manager, since she'd own it? I'd do a fifteen-minute version for her that's just the Monday morning workflow, nothing else." 4. BOOK THE NEXT THING ON THE CALL. Calendar open, date agreed, invite sent before you hang up. Suggest the specific one: "Let's do a two-listing pilot starting the Thursday before the long weekend — those Saturdays are your biggest enquiry days. Can we agree that date now?" 5. SEND WITHIN 24 HOURS: the gap list with your answers, the two call recordings from the demo, the CRM integration one-pager if their admin was on, and the three things you need from them with names next to each. Nothing generic.

How the call actually sounds

Prospect on the left, the rep on the right.

  1. Rep

    Before I share anything — last time you said Saturday's the killer. Enquiries land while all nine agents are running opens, nobody calls back until Monday, and you can't prove which agent dropped which lead. Still the case, or has something shifted?

  2. Buyer

    It's the case but honestly it's not my problem this quarter. We can't get stock. I've got six agents fighting over four listings a week. Selling them isn't the issue — winning them is.

  3. Rep

    Fair, and that's the better conversation. What's your appraisal-to-listing conversion sitting at across the office?

  4. Buyer

    Roughly a third. My top two are better than that, the rest drag it down.

  5. Rep

    Then let me skip the callback stuff entirely and show you the thing that goes into the listo. Vendors pick the agent who turns up with evidence. This page is your last four campaigns in [suburb] — groups through each open, where the enquiry came from, how long from enquiry to first contact, days on market. It prints into your presentation off your own data. That's not a lead tool, that's a listing-winning tool.

  6. Buyer

    Right, but you're describing something my number one writer will never touch. Deb's been doing this nineteen years, she's got her own database in a spreadsheet, her own copywriter, and if I mandate a system she'll walk across the road and take half my appraisal pipeline with her.

  7. Rep

    Then don't ask her. Genuinely. I'd rather you pilot this with two mid-tier agents who want to write more — who are they?

  8. Buyer

    Sam and Priya. Both two years in, both hungry.

  9. Rep

    Run it on Sam and Priya only. Deb never hears about it. If their enquiry-to-inspection numbers move over a campaign cycle, Deb will ask what they're doing. Mandates fail in agencies. Envy doesn't.

  10. Buyer

    Look, I'll be straight with you — we bought an AI callback thing eighteen months ago. It never talked to VaultRE. Leads went into some portal we had to log into separately, nobody logged in, and I paid for it for eleven months. So you'll forgive me if I'm slow on this.

  11. Rep

    That's the most useful thing you've said. Was it the integration or the accountability that killed it?

  12. Buyer

    Both. It sat in a separate system and nobody owned it.

  13. Rep

    Then here's the boring part, and I'd rather do it now than have you find it in month three. We read the lead record out of VaultRE — enquiry, listing, buyer mobile. We write back three things: a contact note with the transcript, the inspection booking against the open home, and a qualification tag. There's no second system for your agents to log into. We don't touch your trust account, we don't touch the rent roll, and we don't post anything back to realestate.com.au. Setup is an API key from whoever administers VaultRE here. Who is that?

  14. Buyer

    Karen, our Operations Manager. And that's the other thing — Karen's got enough on. What's she actually doing with this every week?

  15. Rep

    About thirty minutes. Adding an agent when someone starts, adjusting the open home buffer, and looking at the exception list — calls that didn't connect. It's admin, not IT. And if Karen's on leave for a fortnight, nothing stops; the exception list just gets longer.

  16. Buyer

    And what happens when it rings one of my vendors' buyers on a Saturday morning and says something stupid? Because that call comes back to me, not to you.

  17. Rep

    Two answers. If the buyer says something it can't handle, it stops — it doesn't guess. It SMSs the listing agent the buyer's name, number and a one-line reason, and logs the transcript. And on auction listings it never quotes a price, full stop. Second answer: if we go down entirely, the enquiry sits in your VaultRE lead pool exactly as it does today. You lose the eight-minute callback, you don't lose the lead.

  18. Buyer

    Alright. It's not nothing. But this is a franchise office — I can't sign for something that touches the CRM across the network anyway.

  19. Rep

    What can you do at office level, on your own P&L?

  20. Buyer

    A trial, if it's small. I don't need state's permission to spend a few hundred a month.

  21. Rep

    That's all I want. Two agents, Sam and Priya, four listings, one campaign cycle. If their enquiry-to-inspection conversion doesn't move, we stop and you've lost nothing. If it does, you walk into state office with your own numbers instead of me cold-calling them. Two open items I owe you: whether we push buyer registrations into your auction register, and how we behave on off-market listings. I'll have both by Thursday. Can we start the Thursday before the long weekend — I've got the calendar open now.

  22. Buyer

    Send me something first and I'll look at it.

  23. Rep

    Happy to — but so I send the right thing rather than a brochure: how many listings are you carrying right now, and how many of those vendors are ringing you asking why the numbers are down?

  24. Buyer

    Twenty-eight live. Four vendors have called me directly in the last fortnight.

  25. Rep

    Then I'll send the vendor reporting screens and the VaultRE integration page for Karen, not the general deck. And I'll put fifteen minutes in for Thursday 8:30 — before opens, before it gets away from you. Does 8:30 work?

Objections you will hear

What they say, and what you say back.

ObjectionHow to answer it
Our top agents have their own systems — they won't change."Don't ask them to. Who's your number one writer?" Name them out loud. Then: "This runs underneath what she already does. Her leads still land in her inbox the way they do now — the only difference is nothing sits unanswered while she's at an open." Then ask to pilot with two mid-tier agents who want to write more, never the top biller. When those two lift their enquiry-to-inspection conversion over a campaign cycle, the top agent will ask what they're doing. Mandates fail in agencies; envy works.
We already pay realestate.com.au a fortune. There's no budget left.Agree first, then reframe the spend. "You're right, and you're paying that for enquiry. What percentage of last Saturday's enquiries got a call back before Monday?" If they don't know the number, that's the sale — they're buying enquiry they can't prove they answer. This isn't new spend on top of the portals, it's making the spend they've already committed convert. Then price it per listing per month against a single extra sale at their average commission rate.
We tried something like this and nobody used it.Ask what it was and what killed it — you'll hear either "it didn't talk to our CRM" or "nobody was made accountable." Then be specific, not reassuring: name their CRM, name what you read and what you write back, name the person who owns adoption in the first thirty days and make them say a name out loud. Offer a rollout where they don't pay until a named number of listings are live on it.
Our vendors want a person calling their buyers, not a bot."Vendors want their property sold and they want to know what's happening. Nobody's replacing your agent at the open or in the price conversation at week four." This handles the first response and the inspection booking, so the agent walks into a warm buyer instead of chasing a cold one on Monday. Then ask it straight: "What would your vendor rather have — a personal call from Sam on Tuesday, or a booked inspection eight minutes after the enquiry?"
We're in a stock shortage. The problem is winning listings, not selling them."Fair, and that's the better conversation. What's your appraisal-to-listing conversion?" Then pivot the demo to the evidence page — groups through, enquiry source, price feedback, days on market on their last four campaigns in that postcode, printing straight into the listing presentation. Vendors choose the agent who arrives with evidence. Sell it as a listo tool, not a follow-up tool.
This is a franchise decision. I can't buy at office level."What can you do at office level, on your own P&L?" Most Licensees in Charge can run a small pilot without asking anyone. Get the pilot, get their own numbers over one campaign cycle, then ask them to introduce you to the state or group office holding their own results. A Principal advocating internally beats a cold call to head office every time.
Send me some information and I'll look at it."Happy to — but so I send the right thing rather than a brochure: how many listings are you carrying right now, and how many of those vendors have rung you asking why the numbers are down?" Get one real number before you agree to email anything. Then send the two screens that matter, not the deck, and book the follow-up while you're still on the phone — a specific day and time, before opens, not "sometime next week."

Questions reps ask about this call

How long should a real estate product demo actually run?

Thirty to forty minutes of screen time at most, covering three workflows completely rather than twelve partially. For an agency demo that's usually the Saturday enquiry callback, the post-open vendor report, and the evidence page that goes into the listing presentation. If you're more than ninety seconds into talking without handing the mic back, you've drifted into tour mode. Principals and Directors of Sales are between opens and appraisals — they will forgive a short demo and punish a thorough one.

What do I show first when the buyer opens with an objection instead of a question?

Reorder live and say so out loud. If the Principal opens with "our problem is stock, not selling," don't push through the callback demo — go straight to the listing presentation evidence screen and ask their appraisal-to-listing conversion. If they open with "we tried this and nobody used it," go straight to the CRM integration screen and name what you read and what you write back. The demo you rehearsed is a resource, not a script.

How do I handle the CRM integration question without an IT person on the call?

Raise it before they do, and describe it in traffic, not in the word "integration." Say which CRM — VaultRE, Agentbox, Rex, MyDesktop, Box+Dice — say what you read from it, what you write back, how often, and crucially what you don't touch: no trust account, no rent roll, nothing posted back to the portals. Then name the setup step in real terms: an API key from whoever administers the CRM, usually the Operations Manager, twenty minutes. Vagueness here is what a principal remembers about the last product that never talked to anything.

What's the right answer when a principal asks 'what happens if it goes wrong on a Saturday?'

Give the failure mode, never an uptime percentage. "If we're down, the enquiry sits in your CRM lead pool exactly as it does today — you lose the fast callback, you don't lose the lead." Then describe what happens on a bad individual call: it stops, SMSs the listing agent with the buyer's name, number and reason, and logs the transcript. Then be honest about support hours, and make sure Saturday morning is covered by a phone and a human, because that's the only window that matters in this business.

Should I demo to the Principal alone or get the whole team on?

Demo to the Principal or Licensee in Charge first, alone or with the Director of Sales. Then offer short, tailored versions rather than one big group call: fifteen minutes for the Operations Manager on the Monday morning workflow and weekly admin, fifteen for the Head of Marketing on vendor reporting and campaign evidence. Never demo to the top-billing agent as a group approval step — that's how a pilot turns into a veto.

How do I close a demo without it dying in 'I'll come back to you'?

Summarise the fit and the gaps out loud, including the gaps, with a date on your answers. Ask the temperature question — "worth pursuing, or has something already ruled it out?" — and let them say no. Then propose one specific, small next step on their calendar: a two-agent, four-listing pilot starting on a named Thursday so the first Saturday is the real test. Get the invite sent before you hang up. "I'll follow up next week" is where agency demos go to die.