Professional Services · Demo Call
The Professional Services Product Demo Script: Running the Call for Partners Who Bill by the Hour
The Practice Leader on this call has forty minutes between a client steerco and a go/no-go on a $1.4m transformation bid, and they already sat through your pitch call. They are not dialling in to learn what your product does. They're dialling in to find out where it breaks: whether the output looks like their firm wrote it or like a vendor wrote it, whether their MSA with a top-three client prohibits any of this, who on their team is expected to feed it once you've gone, and whether it survives contact with eleven other partners who don't report to them.
That's the room. Everything in this Professional Services product demo script is built around one assumption: the interruptions are the call. When a Director of Business Development stops you at minute six to ask whether the pricing view pulls from actual realized fees or from standard rates, that isn't a derailment — that's the deal. When the Head of Knowledge Management goes quiet and you hear typing, you've drifted into tour mode and you have about ninety seconds to get out of it.
The numbers these buyers actually carry into a partners' meeting are narrow and well-known: average days from RFP receipt to proposal submitted, win rate on proposals submitted inside five days, unbillable pursuit hours per closed deal, utilization by grade, realization, bench days. If your demo doesn't move one of those out loud, on the call, in their words, it becomes a nice conversation that gets circulated to the partner group and dies there. Build the demo around three of their moments, not twelve of your screens.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Before the call: confirm the stack and the practice, in writing
Send this the day after the pitch call, not the morning of the demo: "Two things so I don't waste your forty minutes showing you screens that don't apply. 1. What are you running for CRM and time & billing? I need the specifics — 'Salesforce' and 'Salesforce with a custom pursuit object and a green sheet approval flow built by a contractor in 2019' are two completely different demos. Same for the finance side: Aderant, Intapp, NetSuite, Workday PSA, something homegrown? 2. Can you send me three sanitized SOWs from the [operations / supply chain / tech] practice — ideally one that priced well, one that got written down, and one you lost? I'll build the demo on your material rather than a sample firm." If they won't send documents — and about half won't before legal's involved — ask for their language instead: practice names, grade titles, the internal name of their go/no-go form, three client industries. A demo running on 'ACME Corp' and 'Sample Engagement 1' after they told you they do supply-chain diagnostics for CPG clients tells them you didn't prepare. Also ask who's dialling in and why. The Practice Leader wants their proposal turnaround fixed. The COO wants to know whether this becomes another rollout that dies of polite non-adoption. The Firm CFO wants to know what it does to realization and lockup. The Head of Knowledge Management wants to know whether you're about to embarrass the platform they championed in 2021. Three or four demos, one hour. Decide the order before you dial.
- 2
Opening: set the interruption contract in ninety seconds
"Before I share anything — last time you told me a client called on a Thursday wanting something 'early next week,' a boutique got a proposal in Friday afternoon, and yours went out the following Wednesday because it needed a partner review, a risk read, and someone to go find the analogous case study. And it got logged in the CRM as a price loss. Still the live problem?" [Let them answer. Then:] "Anything changed since we spoke — headcount, budget, a new practice leader?" "One ground rule and then I'll stop talking. I'd rather you cut me off than sit politely through something irrelevant. If you're thinking 'that won't work here' or 'our MSA prohibits that' — say it in the moment. That's the useful part of this call." "And so I demo in the right order: what's the one thing where, if this can't do it, we don't need to keep talking?" Whatever they name goes first. If they say 'confidentiality,' you do the access-wall screen before you do anything about proposals.
- 3
Loop 1 — Thursday afternoon: the pursuit that has to go out Monday
**Problem:** "So it's Thursday, four o'clock. The client wants something early next week. Right now what happens is a senior manager who's already at seventy-something percent utilization starts opening old folders looking for the diagnostic you did in 2022 that priced well — and the person who ran it left for industry." **Screen:** "This is what your BD manager sees. She types the shape of the work — 'supply chain diagnostic, CPG, eight to ten weeks, three sites.' These four come back. That one's yours, March 2022. It's showing her the scope section, the staffing table, the fee, and — this is the part people care about — what it actually realized versus what it was billed at." **Consequence:** "She's not hunting. She starts from your best prior version of this instead of from a blank page, and Friday afternoon is a draft with a partner review on it instead of a search." **Check:** "Is that how a pursuit actually kicks off in your practice, or am I inventing a process you don't have?"
- 4
Loop 2 — the assembly hours nobody can charge to a client code
**Problem:** "You said partners rebuild the same methodology slide three or four times a quarter. That's the piece that lives in overhead." **Screen:** "Qualifications section, staffing table, rate card, the methodology page. It's pulling from your last twelve SOWs — this is your language, because it came out of your documents. What it does not touch is page three, the client-specific hypothesis. That stays blank on purpose. That's the partner's job and it should be." **Consequence:** "The assembly disappears. The judgment doesn't. If your average pursuit burns — what, thirty, forty unbillable hours before a partner even reads it? — you're looking at where a third of that goes." **Check:** "What's your honest number for unbillable pursuit hours per closed deal? Does anyone track it, or is it just felt?"
- 5
Loop 3 — pricing the next one off the last forty
**Problem:** "Fixed-fee scoping off a partner's gut feel about 'roughly a twelve-week effort.' Half come in over-scoped and get written down at month three, half were under-priced from day one and the team eats it to protect the relationship. Realization tells you afterwards. Nothing tells you beforehand." **Screen:** "Here are the eleven engagements in your firm that look like this one. Scoped weeks against actual weeks. Fee at signature against realized fee. Leverage ratio on each — this one ran two-to-one and got written down, these three ran four-to-one and held above 90% realization." **Consequence:** "The partner still makes the call. They just make it with the last eleven in front of them instead of the last one they personally remember." **Check:** "Where does your realization sit by practice right now? And is under 85% the number that triggers the conversation here, or is your threshold different?"
- 6
Handling 'will it handle X?' — slow down, then answer three ways
**Step one, get the actual case.** 'Does it handle confidentiality?' is unanswerable. Say: "Tell me the real situation — is this a client MSA that prohibits reuse of the deliverable, or a conflicts wall between two practices bidding the same sector?" Those are different builds. **Step two, one of three honest answers:** - **Yes, and here it is.** Stop talking and show it live. "You asked about matter-level walls — watch. I'm logged in as a consultant in the tech practice. That 2022 engagement is invisible to her. Same query, my login, it's there." This is the strongest thing that happens on a demo. - **Yes, but not how you'd expect.** "You don't do it in this screen. You do it here, and it's two extra clicks and a manual approval. It's ugly. I'd rather you see the ugly now than find it in month three." - **No.** "No. We don't generate the green sheet today and it's not on this year's roadmap. How often does that come up — every pursuit, or is that a large-deal-only thing?" Half the time the deal-breaker turns out to be an edge case they raised because it occurred to them. **Never say 'we can build that.'** To a Managing Partner who's already been through one failed rollout, that reads as the exact promise their last vendor broke. **Write it down out loud:** "Noting that — redaction of client names in reused case material, and whether it satisfies your MSA with [client]. I'll come back Thursday with a straight answer, and I'd like your risk partner on that call."
- 7
Pressure line 1 — integration, in their systems
What the COO is really asking: how much of this lands on our two-person IT function, and does it break when Salesforce upgrades? "Three connections, and I'll name the method rather than saying 'we integrate.' One: read-only from your CRM — opportunity, client, sector, pursuit team — over the REST API, every fifteen minutes. We don't write to it unless you switch that on. Two: your document store. If your SOWs live in SharePoint, we index the folders you point us at. Not the whole tenant. You choose the libraries, and you can pull one back out any time. Three: time and billing. This one's a nightly flat file to SFTP — hours by grade, standard rate, billed, realized. That's the file that makes the pricing view worth anything. What we don't touch: your GL, your billing runs, your client-facing portals. We never write a rate into your practice management system. If a partner changes a fee, they change it where they change it today. And if your CRM has a custom pursuit object with a bespoke approval flow — which you said it does — that's a mapping conversation with whoever administers it, not a rebuild. I'd want thirty minutes with that person before we scope anything."
- 8
Pressure lines 2 and 3 — who owns it, and what happens when it falls over
**Who maintains it.** Be brutally concrete, because the real fear is asking billable people to do unbillable filing. "Ongoing, it's about two hours a month and it's admin, not IT. Adding users, changing who sees which practice's material, approving a new template. Your practice operations manager does it — not a senior manager at 68% utilization, and not your Head of Knowledge Management doing it on a Sunday. The whole design principle is that capture happens as a byproduct of work already being done: when a proposal goes out through this, it's captured. Nobody files anything." "If that person leaves — handover is a two-hour session and a four-page runbook. I'll send you the runbook before you sign, not after." **When it breaks.** Don't quote uptime. Describe the Thursday. "If we're down, nothing in your operation stops — you're not billing through us and you're not delivering through us. What you lose is retrieval. The documents are still in your SharePoint, exactly where they were; you're back to hunting for an afternoon. That's the worst case, and I'd rather tell you that than quote you a percentage." "Support: P1 is a phone number, someone answers. P3 is email and it's next business day — I'm not going to pretend otherwise. Your named contact is [role], and above that is [role]. If you want, I'll describe our last significant incident and what we told customers. I'd rather you hear it from me."
- 9
Pressure line 4 — time to value, in three dates against their calendar
"Three dates, not one. **Live** — we're reading your CRM and we've indexed the first practice's SOWs. Two to three weeks, and it depends almost entirely on how fast we get the document libraries pointed at us. **Useful** — one practice stops hunting. That's when your first pursuit goes out through this. Call it week five or six, and it's the week that produces the number you take to the partners' meeting. **Fully rolled out** — every practice. That's not a technical question, that's twelve partners. I'd deliberately not do that until one practice leader can stand up and say what happened to their RFP-to-submission days. What you have to do, and I'd rather over-state it: someone gives us the document library paths, someone gives us the user list and who can see which practice, and your practice ops manager sits in two ninety-minute sessions. That's the workload. Projects like this stall in week three when the firm realizes nobody was resourced for it. And you said your year-end close is the first three weeks of the month — we wouldn't cut over into that."
- 10
Recovering the room when you've lost it
The signs: shorter answers, 'mm-hm,' a beat of delay, typing, 'yeah no that makes sense' said flat, camera off. Stop. Do not add features and do not talk faster. In order of preference: "I've been talking for a while — is this the part you care about, or should I jump somewhere else?" "Let me stop the tour. What's the thing you're worried about that I haven't touched? If it's whether your partners will actually use this, say so and we'll spend the rest of the call there." "Do you want to drive? Tell me what to click." Almost nobody does this. It works. "I think I'm showing you the wrong things. Can I stop, take ten minutes to understand what actually matters in your practice, and come back with a demo built on your three SOWs?" Giving up twenty minutes of a demo to save a pursuit is a good trade.
- 11
Closing: gaps out loud, one practice, next date on the calendar
"Let me summarise, including the parts that didn't land. Three things worked for you: the retrieval on Thursday afternoon, the fact that the output is built from your own SOWs, and the realized-fee comparables on pricing. Two open: whether matter-level walls satisfy your MSA with [client] — that's a question for your General Counsel, not for me — and whether we can map to your custom pursuit object. Both answered by Thursday." "Where does this sit for you now — worth pursuing, or is there something that's already ruled it out?" Let them say no. A clean no beats four weeks of chasing a Managing Partner's inbox. "Who else needs to see it? I'd run a twenty-minute version for your risk partner that's nothing but access walls and redaction — no proposal screens at all. And a separate one for your Firm CFO that's realization and pursuit cost, twenty minutes, no product tour." "Rather than a firm-wide review — which practice leader has the worst proposal turnaround right now? I'd like twenty minutes with them. One practice with a real before-and-after number is worth more in a partners' meeting than anything I can send you." Book it live, calendar open, invite sent before you hang up. Then within 24 hours: the two open questions answered, the four screens that mattered, the security and tenanting doc if risk was on the call, and a one-line list of what you need from them.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share anything — last time you said a CPG client called on a Thursday, wanted something early next week, and a three-person boutique had a proposal in Friday afternoon while yours went out the following Wednesday. Still the live problem, or has something else jumped the queue?
Buyer
That's still it. Though I'll tell you now, I've got about thirty-five minutes and I've sat through two of these this quarter. Both of them showed me a dashboard first. Please don't.
Rep
No dashboard. Cut me off whenever. And so I go in the right order — what's the one thing where, if this can't do it, we stop?
Buyer
Two things. Our MSA with our largest client says deliverables are their property and can't be reused. And second — my managers are running at sixty-eight percent. I'm not asking them to spend Sunday feeding a system so it can spit out a proposal later.
Rep
Then I'll do the walls first and the drafting second. On the MSA — is it prohibition on reuse of the deliverable itself, or on identifying the client in any derivative material? Those are different builds and I don't want to answer the wrong one.
Buyer
Honestly? I'd have to read it again. Our risk partner would know.
Rep
Then I'd rather get him on the second call than pretend I can clear it. Here's what I can show you today — I'm logged in as a consultant in your tech practice. That 2022 diagnostic is invisible to her, matter-level. Same query as a principal, it's there. And here's the redaction view: sector, scope shape, week count, fee band, no client name anywhere in the retrieved text.
Buyer
Fine. But that's the same promise the KM platform we bought in 2021 made. We paid for two years. Nobody uploaded anything. What percentage of engagements do you think actually got a closeout deck filed?
Rep
You tell me — what was it here?
Buyer
Low. Very low. Which is my point.
Rep
That's the strongest argument for this, not against it. Every KM system fails the same way — it asks billable people to do unbillable filing. Nothing in what I'm showing you asks your managers to upload. Capture happens because the proposal went out through this. The document your manager was writing anyway is the record.
Buyer
And what comes out the other end? Because if it reads like it came out of a machine, my clients will smell it in a paragraph. Our differentiation is judgment, not paperwork.
Rep
Look at page three of this draft. It's blank. It stays blank. The client-specific hypothesis is the partner's job and it's the part that wins the work. What's assembled is the qualifications section, the staffing table, the rate card, the methodology page — the pieces your partners rebuild for the fourth time each quarter. The judgment isn't in reformatting a staffing table.
Buyer
Alright. Say I believe that. I've got eleven other practice leaders who all bill north of eight hundred an hour and none of them report to me. Every firm-wide thing we've tried has died of everyone nodding and then doing nothing.
Rep
Then don't sell it firm-wide. Do it in your practice only, measure two things — average days from RFP receipt to submission, and unbillable pursuit hours per closed deal — and you walk that into the partners' meeting yourself. What are those two numbers in your practice today?
Buyer
Turnaround's somewhere between eight and twelve days. Pursuit hours nobody tracks, which I suspect is deliberate.
Rep
Then the first thing we'd do together is baseline it for one quarter, before you change anything. If turnaround doesn't move and pursuit hours don't drop, you've got a clean number to kill it with. Can I get twenty minutes with your risk partner on the MSA question, and then a session with your practice ops manager on what the two hours a month actually look like?
Buyer
Risk partner yes. Send me times. Don't send me a deck for the partner group — that's where these things go to die.
Rep
Agreed, I won't. Thursday or Friday for the risk call — my calendar's open now, which works?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “If it doesn't drive billable hours, partners won't fund it.” | Agree with the frame and then use it. "You're right, and that's exactly why I'd sell it as a utilization tool rather than an overhead tool. The hours your seniors spend rebuilding a methodology slide are hours that can't go to a client code." Then ask the question rather than asserting the answer: "How many unbillable hours went into pursuits in your practice last quarter, and what would recovering a third of them be worth at your blended rate?" Finish by making it one partner's number, not a firm number — pick one practice, baseline pursuit hours before, measure after, and let that Practice Leader carry it into the partners' meeting themselves. |
| “We built our own templates and our consultants like doing it their way.” | Don't argue with the templates. "Good — I'm not replacing them, I'm feeding them. The problem isn't your template, it's that a manager burns four hours hunting for the right prior engagement to drop into it." Then make it concrete on the call: "Send me three sanitized SOWs from this practice and I'll rebuild this demo on them for the next session. What comes out will look like your firm wrote it, because your firm did." Retrievable, not replaced. |
| “We already have a knowledge management system. Nobody uses it.” | "That's the strongest argument for this, not against it." Then ask them for the number rather than quoting one: "What percentage of engagements actually get a closeout deliverable uploaded?" Whatever they say, the diagnosis is the same — KM fails because it asks billable people to do unbillable filing. Your pitch is capture as a byproduct of work already happening, and retrieval that shows up inside the proposal moment on a Thursday afternoon, not a portal someone has to remember to go browse. |
| “Client confidentiality — some of our MSAs prohibit reuse of deliverables.” | Take it seriously; this is a real conflicts and NDA question, not a stall. Get the specific first: prohibition on the deliverable itself, or on identifying the client in derivative material? Then show tenanting, redaction of client-identifying content, and practice-level and matter-level access walls, live. Point out — carefully — that most firms already reuse sanitized case material today, just manually and inconsistently. Then stop selling and offer the right meeting: "I'd rather get your General Counsel or risk partner on the next call than have either of us guess at this." |
| “We're in a budget freeze — utilization is down, we're not adding spend.” | "Then the freeze is the reason to have this conversation, not the reason to skip it. Bench time is capacity you're already paying for. The question is whether it's going into pursuits that close faster." Reframe from new spend to reallocated spend: what's the fully loaded cost of unbillable pursuit hours in one practice this quarter? Then ask the qualifying question straight out: "What has to be true in the numbers for the freeze to lift — utilization back to target, or a specific revenue month?" Now you know what you're actually selling against and when. |
| “Send me something and I'll circulate it to the partner group.” | Name it kindly. "I'll send you the two open answers, but I'll be honest — a deck to twelve partners is where these go to die, and you know that better than I do." Then ask for one thing instead: "Which single practice leader has the worst proposal turnaround right now? Twenty minutes with them, not a firm-wide review." A pilot inside one practice that produces a real before-and-after on RFP-to-submission days is worth more in a partners' meeting than anything you can email. |
| “Automating proposals commoditizes the judgment we sell.” | Meet it head-on, on the screen. "The judgment isn't in the qualifications section or the staffing table. It's in the client-specific hypothesis on page three — and look, page three is blank in this draft and stays blank." Then land the argument: every hour a partner spends on assembly is an hour not spent on the part that wins the work. This pushes more partner time toward judgment, not less. If they push again, ask which section of their last winning proposal actually won it. |
Questions reps ask about this call
- How do I structure a Professional Services product demo script when several buyer types are on the same call?
Order the demo by whoever named the deal-breaker, then cover the rest in short blocks. A Practice Leader wants Thursday afternoon fixed — retrieval and drafting. The COO wants to know who owns it after go-live and whether it dies of polite non-adoption. The Firm CFO wants realization, pursuit cost and lockup, not screens. The Head of Knowledge Management wants to know whether you're about to embarrass the platform they championed. Ask at the top which of those is the blocker and demo in that order. Then offer separate short sessions afterwards — twenty minutes of access walls and redaction for the risk partner, twenty minutes of numbers for the CFO — rather than trying to satisfy everyone in one hour.
- What data should I load before demoing to a consulting or advisory firm?
Their own sanitized SOWs if you can get them — ideally one that priced well, one that got written down, and one they lost. Ask in the confirmation email, not the morning of. If legal blocks it, use their vocabulary at minimum: real practice names, their grade titles, their sectors, the internal name of their go/no-go form. Running a demo on 'ACME Corp' and 'Sample Engagement 1' after they've told you they do supply-chain diagnostics for CPG clients signals you didn't prepare, and in this industry that's read as a proxy for how the implementation will go.
- Which metrics should appear inside the demo script itself?
Two or three, spoken out loud, and asked as questions rather than claimed as results. Average days from RFP receipt to proposal submitted is the one Practice Leaders and Directors of Business Development feel weekly. Unbillable pursuit hours per closed deal is the one that reframes the tool as a utilization play rather than overhead. Realization rate — with the under-85% partner conversation — is the one the Firm CFO carries. Utilization by grade and bench days per consultant per quarter matter to the COO and the Director of Resource Management. Pick the two that belong to the person who invited you and build the loops around them.
- How should I answer confidentiality and MSA objections live in the demo?
Get the specific case before you answer anything: is the MSA prohibiting reuse of the deliverable itself, or prohibiting client identification in derivative material, or is this a conflicts wall between two practices bidding the same sector? Then show what you actually have — tenanting, redaction of client-identifying content, practice-level and matter-level access — live, as two logins on screen. Do not try to clear the legal question yourself. Write it down visibly, commit to a date, and offer to bring their General Counsel or risk partner into the next call. Buyers trust a vendor who escalates a legal question more than one who answers it confidently.
- What's the right closing ask on a demo with a professional services firm?
Not a firm-wide review, and not 'I'll send something for the partner group.' Ask which single Practice Leader has the worst proposal turnaround right now and request twenty minutes with them. Pair it with a baseline: agree to measure average RFP-to-submission days and pursuit hours in one practice for a quarter before anything changes, so there's a number either way. Then book the actual date on the call with the calendar open. Partner autonomy means firm-wide rollouts die of polite non-adoption — one practice with a real before-and-after is the only thing that survives a partners' meeting.
- The buyer went quiet halfway through the demo. What do I do?
Stop the tour immediately. Do not talk faster and do not add a feature. Say: "I've been talking for a while — is this the part you care about, or should I jump somewhere else?" If that doesn't reopen it, hand over control: "Do you want to drive? Tell me what to click." If you've genuinely built the wrong demo, say so — "I think I'm showing you the wrong things. Can I stop, take ten minutes on what actually matters in your practice, and come back built on your three SOWs?" Losing twenty minutes of a demo to save the pursuit is a good trade; a polite silent ending is not.