Selling for Non-Salespeople: Demos, Objections, Case Studies

If the word "sales" makes you slightly ill, good news: what closes clients at your scale is not persuasion technique. It is a prepared demo, calm answers to five predictable objections, and proof from clients like them. All three are preparation, not personality — which means a non-salesperson who prepares beats a natural talker who wings it. This lesson builds the three assets.

The demo: fifteen minutes, their material, one question

The demo structure from the first-client week deserves its full form, because you will give this demo for the life of the business.

Minutes 0–2 — their problem, said back to them. Open with what you know: "You're printing QR stickers per menu change, and you can't tell whether anyone scans them." A prospect who hears their situation described accurately relaxes; you have already differentiated from every generic pitch they've seen. This is your positioning line doing its job.

Minutes 2–10 — their brand, live. Do not tour features. Perform their Tuesday: shorten their actual URL on your branded domain, make the QR code of their actual menu, open the analytics on your seeded demo workspace to show what their numbers will look like. The moment their logo appears on a working link is worth more than any slide — it moves the product from "a tool" to "my thing, almost set up".

Minutes 10–14 — the money and the next step. Show your plans, recommend one ("for a single location, the $19 plan is right"), state the trial. Prescribing a plan is a service, not pressure — menus with a recommendation convert better than menus alone.

Minute 15 — one question, then silence. "Want me to set this up for you?" And stop talking. The silence after the ask is the only genuinely uncomfortable sales skill you need, and it is learnable in one week of practice. Any answer is progress: yes starts concierge onboarding; hesitation surfaces the real objection, which is the next section's material.

The five objections, and the answers that are actually true

You will hear the same five objections in an endless loop. Scripted, honest answers turn them from ambushes into routine. Never argue; agree with the kernel, then reframe.

1. "There's a free tool for this." — "There is, and for occasional personal links it's fine. You're printing codes and running campaigns: on the free tier you get someone else's domain on your table stickers, and if you ever need to change where a code points, you reprint. With me it's your domain, editable destinations, scan stats — and me on the phone." The white-label brand story is the emotional half of this answer; say it in their nouns.
2. "Too expensive." — First, diagnose: too expensive versus what? Versus free (see above), versus a competitor (rare, ask which), or versus zero budget (a qualification miss, not an objection). The reframe that works for real businesses: price against their spend, not against zero — "$19 is under one table's lunch; the reprint you did last month cost more." If a pattern of price objections appears, that is data for your pricing, not something to solve per-call with discounts — remember the first-month rule: no panic discounts.
3. "I don't have time to set this up." — The easiest one, because your answer is structural: "You won't. Fifteen minutes together and it's live — I do the setup while you watch." Concierge onboarding as a sales argument. For the DNS-wary, mention that the guides exist under your brand for their IT person.
4. "What if you disappear?" — Fair question for a small provider; answer it with structure, not protest: their links run on their domain, so the asset is theirs; the platform behind you is built for uptime; and their data exports. Confidence here comes from knowing the machinery — which you do.
5. "I need to think about it." — Usually one of the four above, unnamed. Make thinking concrete: "Of course — what's the main open question?" If none surfaces, schedule the follow-up on the call and start the trial now: "Think while it runs — I'll set up the domain today so you're deciding on your own numbers." A trial with a connected domain decides in your favour far more often than a bookmark does.

Case studies: proof that sells while you sleep

After a few clients succeed, you hold the strongest sales asset in existence: specific results for businesses exactly like the prospect. A usable case study is one page and one afternoon:

• Numbers, small and true. "1,340 scans in March across 12 tables; menu updated 4 times without reprinting; ~$85 of reprint cost avoided" beats any adjective. Pull them from the client's own reports — with permission.
• The client's voice. Two sentences of quote, asked for at the moment of visible success (the same moment the retention lesson has you forwarding reports — one email, two purposes).
• The shape: before (the fumble), after (the numbers), how long setup took (honesty about "one evening" is itself persuasive). Look at this site's customer stories for the pattern at full scale.

Deploy everywhere: the demo's minute 12 ("here's a restaurant two districts over"), objection answers (nothing dissolves "too expensive" like a peer's math), outreach openers, your homepage. One case study per client segment is the goal — a restaurateur is moved by restaurants, not by an affiliate team's CTR.

Practice, the unskippable part

None of this works as reading. The demo needs five out-loud runs before it feels like yours — record one and listen; painful and worth it. Objection answers need to be written, in your words, then said until smooth. The first case study needs to be asked for, which is its own small courage. Schedule all three this week; the weekly metrics lesson that closes the track will show you, in numbers, whether the practice moved the demo→client rate — which is the only review that matters.

Checklist

• [ ] Write your 15-minute demo script in the four-block structure, with your niche's nouns throughout. Rehearse aloud five times; record once.
• [ ] Prepare the seeded demo workspace: realistic links, styled QR, live-looking analytics — refreshed from whatever it was on launch week.
• [ ] Write your five objection answers in your own words. Read them before every call until you stop needing to.
• [ ] Ask your best client for the first case study today: numbers from their report, two sentences of quote, permission.
• [ ] After each of the next five demos, log: which objections came up, and did you ask the closing question and hold the silence? Honest logging fixes more demos than any technique.