Growth metric

Demos. The earliest actionable leading indicator — two numbers, not three.

Demos Scheduled and Demos Completed are the earliest signals a SaaS leadership team can act on inside a quarter. They sit one layer before pipeline coverage and 30 days before closed-won — which means demos completed this week are MRR next month, with enough lag to actually intervene. Most SaaS metric content over-engineers this measurement with pre-demo qualification scores and conversion-to-opportunity attribution. The honest version is two clean numbers: how many demos got on the calendar, and how many actually happened. The gap between them is the diagnostic. Everything else is process, not metric.

What it is

Two cells on the scorecard. Demos Scheduled — total demo meetings on the calendar this week. Demos Completed — meetings that actually happened. Cancellations don't count toward either. No-shows count as scheduled but not completed — that's the diagnostic.

Measurement period

Weekly.

Demos are counted against the week the meeting occurred (or was scheduled to occur). Weekly is the operating cadence; monthly gives the trend view. Anything longer loses the leading-indicator value.

Formula

Demos Completed

Demos Scheduled

= Show-up %

Derived diagnostic. 80%+ is healthy. Below that is a process problem, not a funnel problem.

When to review

Weekly.

The earliest scorecard cell where leadership can still act inside the period. Monthly review gives the bigger picture. Don't watch quarterly — by then it's already in pipeline coverage and 60 days from MRR impact.

Why it matters

Demos completed this week are MRR in 30 days.

At PipelineCRM, demo-to-close was typically about 30 days at most. That window is what makes demos completed such a useful leading indicator — earlier than pipeline coverage, with enough room to intervene before the consequence lands in MRR. A drop in demos this week shows up in MRR roughly four weeks later. That's enough lead time to fire a campaign, tighten the SDR motion, or adjust qualification before the quarter slips.

At $3-5M ARR we ran about 40 demos per week, roughly 10-12 per AE. The motion was simple by design — primarily AE-led discovery-plus-product calls, with a meaningful share coming through self-serve "Book a Demo" links on the marketing site. We only ran one demo type: showing the product to the business user, usually a director or VP of Sales. Not three demo types segmented by buyer or stage. One type means one playbook to refine, one structure to study, one conversation to optimize. The more demo types you run, the more your team's execution dilutes across them.

The hardest part of this metric isn't the math. It's resisting the urge to over-engineer it. Most modern SaaS playbooks insist on hard pre-demo qualification — BANT scores, MEDDIC discovery calls, gatekeeping demos to "qualified" prospects only. At PipelineCRM, we took everyone who showed up. Honestly, that probably wasn't optimal. Over time we started sending pre-demo questions, but I'm not sure we ever actually turned anyone away. The downstream check we did watch carefully was the demo-to-close rate — that's where the qualification math actually lives. If the close rate from demos is healthy, qualification was good enough. If it isn't, that's where to tighten — not by gatekeeping the demo, but by sharpening what happens during and after.

Demos completed this week are MRR in 30 days. Pipeline coverage tells you 60-90 days out; demos tell you 30. That's the earliest leading indicator a leadership team can actually act on.

Worked example

Three teams. Same 40 demos completed. Very different motions.

Each team finishes the week with 40 completed demos — the headline that hits the scorecard. The scheduled-vs-completed split tells you which team has a clean motion and which is wasting AE time chasing phantom meetings.

Clean motion

40 done

Demos scheduled45
Demos completed40
No-shows5
Show-up rate89%

Healthy show-up rate. SDR motion is producing real demos, confirmation cadence is working, qualification is tight enough that prospects who book actually show up. The team is executing well — every additional scheduled demo converts to a completed one at a high rate.

Watchable

40 done

Demos scheduled55
Demos completed40
No-shows15
Show-up rate73%

Same completed count, but 27% of scheduled demos didn't happen. That's 15 AE hours wasted weekly chasing phantom meetings. The fix is in the confirmation cadence, not in scheduling more — booking 15 more next week just produces 4 more no-shows.

Phantom funnel

40 done

Demos scheduled75
Demos completed40
No-shows35
Show-up rate53%

Half the calendar is fiction. Forty real demos, thirty-five wasted slots. Pipeline math built from "scheduled" overstates real top-of-funnel by 47%. This is what a phantom funnel looks like — and why scheduled volume in isolation is the metric most SaaS teams misread.

Benchmarks

Demo volume by team size.

Demo volume scales roughly with AE headcount, with significant variance by sales motion. PipelineCRM ran about 10-12 demos per AE per week with an inside-sales motion at $2,500 ACV. PLG-heavy motions or SMB self-serve can run much higher; enterprise field motions much lower. These are typical bands at $1M-$10M SaaS scale.

Per-AE demo volume

8-15 completed demos per AE per week is the typical band for inside-sales motions at $2,500-$10,000 ACV. Lower is fine if deal complexity is higher; higher is fine if the motion is more transactional. PipelineCRM ran 10-12/rep at $2,500 ACV.

Team total at $1M-$5M ARR

20-60 demos completed per week across the team. Where most $1M-$10M SaaS companies live. Heavily dependent on AE count and motion type. PipelineCRM ran about 40 per week at $3-5M ARR with 4 AEs.

Show-up rate

80% or better is healthy. 70-80% is a watchable band where confirmation cadence and qualification should be reviewed. Below 70% is a structural process problem — every quarter of dropped demos is AE capacity destroyed, not pipeline issues.

Demo-to-close rate

The downstream quality check. Typical ranges run 15-35% from demo to closed-won within 60 days, heavily dependent on ACV and segment. Track it monthly. If demos are flat but close rate is dropping, the demo execution itself is the problem — not the funnel.

When demos are trending wrong

Three plays — and the right one depends on which number is dropping.

If scheduled is dropping, that's a top-of-funnel volume problem. If completed is dropping but scheduled is steady, that's a no-show problem. If both numbers look healthy but the downstream close rate is dragging, the demo execution itself is the issue. The diagnostic is in the gap; the play follows the diagnostic.

— 01 If Demos Scheduled is dropping: add demo paths everywhere

More routes to the calendar, not more outbound.

The first instinct when scheduled demos drop is to push the SDR team harder. That's a slow lever. The faster move is to multiply the surfaces where a prospect can book — and most SaaS teams under-invest in this. At PipelineCRM, every employee email had a "Book a Demo" link in the signature. Customer support replies routinely included "Schedule a Demo" links when prospects asked product questions. We optimized placement of demo CTAs across marketing site pages. We also discovered, later than we should have, that international prospects wanted demos at 24×7 hours — and lost meetings because we hadn't optimized for that. Optimize the scheduling surface, not just the outbound motion. It compounds for years.

— 02 If Demos Completed is dropping: tighten the confirmation cadence

No-shows are a process problem, not a volume problem.

If scheduled is healthy but completed is dropping, the answer is not more outbound. It's discipline in the 24-72 hours before the meeting. Confirmation emails. Calendar invites with clear agenda and value. A reminder the day before. A reminder the morning of. Personalized confirmation from the AE for higher-value prospects. The other axis is friction reduction — make rescheduling trivial so a prospect with a conflict moves the meeting rather than ghosts it. PipelineCRM's no-show rate got materially better once we started tracking it weekly and tightening the process around it. It wasn't one big fix; it was a half-dozen small ones, applied consistently.

— 03 Volume is fine, close rate is dragging: record and study

The demo motion is itself a thing to optimize.

If demo volume and show-up rate are healthy but the downstream close rate is dropping, the metric isn't telling you about the funnel — it's telling you about the demo motion itself. The highest-leverage move here is recording demos and studying them. At PipelineCRM, recording demos and reviewing them as a team materially improved our close rate. You see what stories land. You see where prospects light up versus tune out. You see where AEs talk too long or miss the question that was actually being asked. The demo is a craft. Treating it as a craft — recording, reviewing, refining — is the single highest-return process investment in this whole metric.

Common mistakes operators make with demos.

Putting only one demo number on the scorecard.

Many teams track "demos completed" and call it done. That hides the no-show problem entirely. A 40-completed week from 45 scheduled is a completely different motion than a 40-completed week from 75 scheduled — but both look identical on a one-cell scorecard. Put both numbers in adjacent cells. The gap between them is one of the highest-signal diagnostics on the scorecard.

Adding Demos → Opportunity conversion as a third cell.

Tempting, but it usually adds confusion rather than insight. Different companies create opportunities at very different funnel positions — some before the demo, some during, some after. That makes the "demos to opportunity" ratio non-comparable internally over time (CRM hygiene changes) and definitely non-comparable across companies. Use demo-to-closed-won rate, tracked monthly, as the downstream quality check. Opportunity creation is mostly a measure of CRM discipline.

Gating demos too hard with pre-demo qualification.

The current orthodoxy in B2B SaaS is hard pre-demo qualification — BANT scores, mandatory discovery calls, gatekeeping based on company size or use-case fit. There's a real risk of going too far. At PipelineCRM, we took essentially everyone who showed up for years. Over time we started sending pre-demo questions to filter, but I'm not sure we ever actually turned anyone away. That probably wasn't optimal. But tight pre-demo gating trades top-of-funnel volume for AE efficiency, and at $1M-$10M scale that trade often costs more than it saves. Let the qualification happen in the conversation; let the demo-to-close rate tell you if the gate is loose enough or too loose.

Running multiple demo types when one would do.

Teams often build intro-demo / technical-demo / proof-of-value progressions. At PipelineCRM, we ran one demo type — product walkthrough for the business user — and that simplicity helped us optimize execution. One demo type means one playbook to refine, one structure to study, one set of recordings to learn from. Multiple demo types means each one is less polished than it could be. Consolidate where you can; segment only when ACV or technical complexity genuinely requires it.

Ignoring international scheduling.

A real lesson learned later than it should have been. If you have international prospects, they're booking demos at hours that don't match your local business day. Time-zone-aware scheduling pages, calendar slots covering more hours, ability to book without back-and-forth email — all of this matters more than most US-centric SaaS founders realize. If a prospect can't book a slot that works for them in two clicks, they don't book. They disappear.

Not recording demos to improve execution.

Demo recording is one of the highest-leverage process investments a SaaS team can make. Watching successful demos versus unsuccessful ones surfaces the story structure that works, the questions prospects keep asking, where AEs are talking past objections, where attention is dropping. PipelineCRM's demo-to-close rate improved meaningfully as we used recordings to refine the structure and study what landed. If you're tracking demo volume but not investing in execution quality, you're leaving close rate on the table — and demo volume alone won't tell you that's what's happening.

Read alongside

Demos are the earliest signal. Pipeline Coverage is the next.

Demos tell you what's happening in the funnel this week. Pipeline Coverage tells you whether the quarter will hold up 60-90 days out. Read them together — demos catch issues 30 days before coverage does.

Pipeline Coverage guide →

How Upbeat helps

Demos belong on the scorecard as two cells, not one.

Most teams either don't track demos on the leadership scorecard, or they track them as a single combined number that hides the no-show problem. Upbeat puts Demos Scheduled and Demos Completed on adjacent rows of your Monday scorecard — so the gap between them surfaces as the diagnostic it actually is.

See how it works → See pricing

Related metrics

Demos are upstream. Read what they predict.

Demos are the funnel's earliest scorecard signal. Two numbers, not three.

Upbeat puts Demos Scheduled and Demos Completed on adjacent rows of your weekly scorecard — so the no-show gap surfaces as the diagnostic it actually is.

Email Nick directly →