Demo Requests and Sales-Assisted Paths for Small SaaS

A demo path converts on three things: a request form short enough to finish in a minute, a reply fast enough to catch the evaluation while it is warm (same working day at the outside), and a demo run on the prospect's own scenario, data shape and questions - not a generic tour. The page's job is to set those expectations and to qualify kindly: who the demo suits, how long it takes, what happens with the details given. Sales-assisted conversion is still conversion; all this site's rules about honesty, totals and follow-through apply with a human attached.

State plainly who the demo is for ('Teams of five or more migrating from spreadsheets') so the solo self-serve visitor routes themselves to the trial instead - a misqualified demo wastes both calendars. State the format and length, what the prospect should bring, and what they leave with. One or two specifics about the person or team who runs demos (role, experience) outperform a stock-photo sales team. If a calendar booking tool is embedded, test it monthly as a stranger: booking widgets break silently and the failure mode is a quarter of lost pipeline blamed on demand.

The form needs: contact details, company or team size band, the job they are evaluating the product for, and anything that changes the demo's content (current tool, deadline). Everything else can be learned in conversation. Routing questions should visibly benefit the requester ('So we can show your migration path, what do you use today?'), which is the difference between qualification and interrogation. The forms bench's justification test applies unchanged; the fact that a human follows up does not raise the visitor's budget for fields.

An evaluation has a temperature, and it falls by the day. Set a public internal standard - reply within a few working hours, offer times within two working days - and measure against it like a step rate: requests, replies within standard, demos held, trials or contracts started. Where volume is low, the founder or a senior hand replying personally is a genuine advantage over enterprise competitors' queues; use it while it lasts. The follow-up guide on the services bench covers the same mechanics for service businesses.

Open with their scenario: their data shape, their current tool's pain, their deadline. Show the activation moment from the onboarding guide happening on screen. Leave behind a trial configured with what the demo showed, so the evaluation continues without a cold start. Record the objections verbatim in the log; demo objections are the highest-grade copy research a SaaS can get, and the pricing page's FAQ should be rebuilt from them quarterly.

Some requests never become meetings. One reminder before, one short note after a no-show offering two new times, and one final message closing the loop politely; then stop. The chase sequence is a trust surface: aggressive pursuit of a cold trail teaches the market that your demo form is a trap, and the lesson spreads further than the trail was worth. Log no-show rates by source; a source that books and vanishes is telling you something about its quality that its click prices will not.

The demo's afterlife decides close rates as much as the call. Send, the same day: the recording or a short summary in the prospect's own terms, the trial configured as demonstrated, the pricing for their tier with its arithmetic shown, and the migration outline if one was discussed. Each asset answers one of the internal questions the prospect must now argue to colleagues who were not on the call - which makes your follow-up the actual sales document, written for readers you will never meet. Date and version these assets like pricing pages; last quarter's summary quoting last quarter's price is the assisted path's version of a broken message match.

Some demo requests come from visitors the product cannot serve: too small for the assisted tier, outside the segment, needing a capability that does not exist. The conversion-minded response is a fast, honest redirect - the trial if it fits, a named alternative if it does not, a clear 'we do not do X' where that is the fact - sent within the same reply-speed standard as a qualified request. A slow, evasive answer to an unqualified request costs the same reputation as a slow answer to a qualified one, and the redirected visitor talks to exactly the peers you will sell to next year. Qualification is a routing decision; kindness is the routing done at full speed.