Demo-request follow-up without a sales team: the two-nudge sequence and when to stop

For an inbound demo request, send one complete reply the same day, then at most two nudges, then stop and record why. The reply answers the buyer's question and offers two real times. Nudge 1, about two days later, adds something new. Nudge 2, about a week after the reply, says when the held time expires and makes "no" easy. One email is too few: Belkins' 2026 study of 7.53 million B2B emails found 58.6% of replies came after the first message¹. Eight to twelve touches is a playbook for outbound reps, not for a founder answering people who asked.

We cap follow-up at two by default in Valet. This post explains why, gives the sequence we would hand any founder, and is plain about what we do not yet know.

Why does demo-request follow-up need its own rule?#

A demo request is an inbound inquiry with a sales label on it. The buyer chose to write. That changes the economics of every message after the first one.

Most published advice for this query comes from outbound sales. Prospeo's 2026 playbook for demo-request follow-up recommends "eight to twelve touchpoints over 17-21 days across email, phone, and LinkedIn," and cites "RAIN Group research" that "meetings require 8 touches on average"⁴. That is a reasonable plan for a team with reps, a dialler and a sequencing tool, working a list of people who never asked to hear from them.

A seed-stage founder has none of that. The headcount is one or two people. The opportunity cost of every hour is product work. And the person on the other end already raised their hand. The question is not how to wear down resistance, but how to finish a conversation the buyer started.

What the eight-touch playbook gets right#

The eight-touch playbooks are right about one thing: a single message forfeits most replies. The data behind that is reasonably solid.

Belkins analysed 7.53 million B2B emails in 2026. The first email drew 41.4% of replies; steps two through six drew 58.6%; step three alone drove 35.6% of email-sourced meetings¹. That is outbound email, and Belkins publishes no spam-complaint or unsubscribe data alongside it. The direction is still clear. Stopping after one message leaves most of the outcome on the table.

The failure most founders have is zero follow-up, not too much. Pied Piper's 2026 mystery shop of 3,211 home-services inquiries found 72% got no follow-up at all⁵. Leadferno's 2024 test of 225 small-business contact forms found 42.6% got no reply of any kind⁶. Neither study covers SaaS, but both describe what happens when follow-up depends on somebody remembering.

Why we cap it at two, not eight#

We cap follow-up at two because the third, fourth and eighth messages in an inbound thread cost more than they return. That is a judgement, not a measured optimum, and the reasoning matters more than the number.

First, the eight-touch figures come from a different activity. A request for a demo is not a cold prospect, and the trust you spend on a fourth "just bumping this" is trust you may need when the buyer does come back. Second, the louder sales statistics that justify heavy cadences are weak. Prospeo's playbook states that "78% of buyers purchase from the first company that responds," attributed to its own benchmarks⁴; versions of that figure have circulated for more than a decade with shifting sources. VentureBeat showed in 2014 that the widely quoted "80% of sales need 5–12 follow-ups" figure traced to an organisation that does not exist⁸.

Third, founders already feel the cost of empty nudges. A thread in r/sales (50+ comments, about a year old) puts it plainly: "I know I sound super desperate when I send a quick email a few days later after hearing nothing from a lead." The fix for that feeling is not more messages or none. It is a message that carries something the buyer needs.

The trade-off is real. Some buyers would have replied to a third or fourth nudge, and a cap of two gives them up by default. We accepted that cost because the alternative, a tool that keeps writing to people who have stopped reading, damages the one asset a small company cannot buy back: its reputation with people who asked.

The demo-request sequence#

The sequence has three messages and a close. Each message has a job, and none of them may introduce a price, a discount or a term you have not already set.

REPLY - same day (within the hour in working hours)
Subject: Re: Demo request - [their question, in their words]
Hi [name], thanks for reaching out.
[Direct answer to what they asked, from your pricing page,
docs or security notes. If you don't know yet, say when you will.]
I can show you [the specific thing they care about] on a 25-minute
call. I'm holding two times for you:
- [Tue 14 Oct, 10:00 ET]
- [Wed 15 Oct, 15:30 ET]
Reply with one and I'll send the invite. One question so I can
prepare: [e.g. which tool are you replacing?]

NUDGE 1 - about 2 days later, only something new
Hi [name], one thing that may help before you decide:
[a doc, a short recording or an answer to the next question
buyers like them usually ask]. Still holding [time] for you.

NUDGE 2 - about 5-7 days after the reply, expiry and an easy no
Hi [name], I'll release the time I'm holding on [date].
If a demo is still useful, pick any slot here: [link].
If the timing's wrong or you've gone another way, a one-line
reply is fine and I'll close this out.

CLOSE - same day as the stop condition
Record one reason (see the rubric below). No further messages
unless they write again or named a later date.

Two rules sit behind the template. The reply answers before it schedules: Techstars mentor Nora Khalili notes that "If an objection (concern, obstacle, hesitation, etc.) exists, it will only get larger in their minds when they walk away"⁷. And a calendar link goes in nudge 2 as a fallback, not in place of real times in the reply. For the operating setup behind this (who owns sales@, the facts sheet, the weekly review), see why inbound leads don't convert at a tiny startup.

What should you send when a demo is booked, or missed?#

Once a demo is booked, the goal changes from getting a reply to getting attendance. Andrew Schafer's 2023 advice on demo-request flows sets out a sensible pattern: a confirmation with product details, a follow-up two days later with a relevant customer example, and a reminder the day before the call³. Schafer's subtitle is the reason: "There are no spare customers."³

Show rate is where the money moves. One founder reported on Indie Hackers in May 2026 that demo show rate rose from 38% to 79% for prospects who first went through a five-minute product tour; the test ran 30 days with 340 tour visitors². That was cold outbound, not inbound, and one founder's experiment. The founder's lesson still travels: "The tour doesn't replace the conversation. It earns the right to have a better one."²

For a no-show, send one message the same day. No guilt, two new specific times, an easy way to say the timing is wrong. If the buyer misses a second booked demo without a word, close the request. A third chase costs your calendar and teaches the buyer that your time is free.

What is a better demo-request flow worth?#

The value is extra demos held, times your close rate, times contract value. The inputs below are an illustration with stated assumptions.

Compare that with your burn rate rather than with a sales hire. The sequence above costs no headcount. Its unit economics are a few minutes of founder time per request, against contract values in the thousands.

What we do not know yet#

Reply rates by nudge number for inbound demo requests have not been published by anyone we can find. The Belkins figures are outbound¹, and the cadence above is a convention built from them and from inbound practice, not a measured optimum.

How we are measuring this: reply and booking rates for the first reply, nudge 1 and nudge 2 could be measured as inquiries move through Valet; no figure is published yet, together with how often a capped thread is reopened by the buyer later. No figures are published yet.

The unresolved question for the industry is the one this post cannot settle: whether a third nudge with real news (a new feature, a changed price, an integration the buyer asked about) earns its place on inbound. Our default says no unless something changed. For the general version of this rule, see how many times to follow up with a lead. For why follow-through matters more than first-reply speed, see the first reply is free; follow-up is where leads die.

Where Valet fits#

Valet runs this sequence for written inbound, including demo forms and sales@. It answers from your own facts (pricing, plans, integrations, security notes), offers and holds real times from your calendar, books the demo and sends the invite. The Valet follow-up cap sends two nudges by default, each with something useful, then stops and tells you why. Discounts, custom terms and contracts come to you with one-tap replies, and the buyer is told when you will reply. Every message has a Valet receipt and is signed as your AI assistant.

The free lead check reviews 10–20 recent demo requests and shows what went unanswered, what stopped after one reply, and what it was worth.