The Holly demo
On this page
Holly-first, about nine minutes, finished artefact first: a draft for someone in the prospect's role before any tour. Discovery happens first (see Discovery and demo). The demo is not a tour.
Say (first-call offer)"Thirty minutes. We'll show you Holly drafting for someone in your role, on a demo workspace, and you can judge it for yourself."
Rules for every demo.
- Only Alex or John Cooper demo, on the Maktura internal workspace, with consenting colleagues' profiles, never real client data.
- NDA first. Until D3 is decided, an NDA is signed before any demo unless John Cooper waives it in writing at booking.
- Never build a prospect's voice before the call, never prepare a draft from their public posts, and never connect, log into or publish to their LinkedIn.
- Reset after every demo. Never leave a demo post scheduled.
Before the call.
- Ask their role and what their clients ask them. Nothing more.
- Pick the demo voice closest to their role, built with a colleague's permission, and say so on the call. If they want their own voice, they may paste posts on the call; build it only with consent given then, mark it TEST FIRST, delete it in the reset (consent wording pending Karl Foster, D27). If pasted text reads as heavily AI-edited, ask which pieces are most "you".
- Seed the feed with their sector and one story from this week. No client names as watched subjects.
- Workspace: Holly on Suggest, approvals on, a short set of firm rules, quiet hours set, no live LinkedIn connection, no links in demo posts (a past link bug is not confirmed fixed).
- For a regulated prospect, add one demo person on Observe.
- Rehearse the exact prompts that morning on the current build. Ask Dom what changed since yesterday.
- Keep a backup: one draft in the demo voice on their sector's story, made beforehand and never from the prospect's posts. Say when it was made if you use it.
- If a screen still says Pulse, know the line (see the name section).
The nine minutes#
Every typed instruction is TEST FIRST on today's build.
| Time | You type to Holly | You say |
|---|---|---|
| 0 to 1 | Nothing | "I'm going to ask Holly to do a real piece of work for someone in your role. Then you tell me honestly whether you'd post it. If you wouldn't, that's useful too." Then: "You're probably thinking this will post generic stuff under your name and embarrass you with clients." Pause. "Let's find out." |
| 1 to 3 | "Write me three LinkedIn posts in [demo voice name]'s voice about [the story or issue they raised in discovery]." | Nothing. Let them read. Then: "Which of those would you actually post?" |
| 3 to 5 | Their changes, e.g. "Make the second one shorter, cut the question at the end, keep the line about [x]." Or mark up lines to keep, cut and change | "Every change you just made is the judgement Holly can't have. That's the job we leave with you." Hand over the keyboard only on Suggest with no live LinkedIn connection |
| 5 to 6 | "Schedule that one for the best time next week." | "It's on the calendar, and your firm's rules check it before it goes out. Approve or Dismiss: that's the decision you make." |
| 6 to 7 | Nothing: show the person's Holly level | "This is the part that decides how much control you keep. Holly is on Suggest: it proposes, you decide what goes ahead. You can start on Observe if you'd rather watch first. You move each person up only when Holly has earned it." |
| 7 to 8 | "Plan a four-week campaign for [their event or theme], two posts a week in [demo voice name]'s voice. Show me before you schedule anything." | "You said [their pain]. That's a month of it, done in a minute, and nothing scheduled until you say." |
| 8 to 9 | Nothing: back to the draft they liked | "Is that something you'd actually post?" If yes, the risk-off close. If no: "What would it need to do differently?" |
Hold back in a first demo: Auto-publish, Watch alert numbers (fault under investigation, D12), any engager's name or list, reports, share links, scheduled emails and the daily digest (AMBER until D1; never show the digest heading), testing, bulk import, the full feature list.
Optional modules (longer call, TEST FIRST). Meetings to posts, only with a demo calendar and one staged meeting with no real client content. The team ("Draft one post for each of these three people, in their own voices, for approval"), only with three consenting-colleague demo voices. Rules ("Check this draft against our social media policy"), only with demo rules loaded.
Observe-first version (law, financial services, accountancy, any firm that asks, anyone nervous). Same nine minutes, but at 6 to 7 spend about 60 seconds on a demo person set to Observe. Show what Holly would do as designed (if the build does not show it, describe the level and move on). Say: "This is where I'd start your partners. Holly watches and shows you what it would do. Nothing more until you decide." Move that person to Suggest live: "And this is the first small win: when you're comfortable, one click, one person." Close with Observe for partners, approvals on with your compliance step, onboarding booked, 30-day review.
If they quote our website at you#
| Site says | You say |
|---|---|
| "Four settings, per surface" | "The site's being updated. Today the levels are set per person, and you choose them." |
| "Every action is logged and explained" | "Every action is logged. I'll only show you what you can see working today." |
| "While you sleep, Pulse keeps working..." | "Pulse was Holly's working name. Holly works on the levels you set; we recommend a person approves every post." |
| "Take a photo and Pulse can turn it into a post" | "That's older copy and it's coming off. Today you type to Holly." |
| "Nothing goes out that you have not allowed" | "You decide what Holly can do on its own and what needs approval. Nothing you've set to need approval goes out without it." |
When it goes wrong#
Name it, do not fight it, move on, follow up. Never troubleshoot live for more than a minute. Never pretend a fault is a feature.
A poor draft live (this will happen). Say it first: "That one's not good enough, and I'm not going to pretend it is." Diagnose in one honest sentence ("It's had only a few posts to learn from, and it's playing safe" or "I gave it a vague instruction"). Fix it once, in front of them, with a specific instruction or by marking up lines. Then make the point: "And that's exactly why we recommend a person approves every post. Holly does the heavy lifting; you keep the judgement. A bad draft costs you ten seconds. A bad post costs you a client." If the second try is poor, stop and show the backup, saying when it was made. Never blame the prospect's writing, rerun the prompt hoping, or schedule a draft you would be embarrassed by. Afterwards send Dom the prompt, voice material and result.
| What goes wrong | You say | You do |
|---|---|---|
| Holly is slow or stuck | "It's working through it. While it does: [a saved discovery question]." | After about a minute, use the backup. Report it |
| Holly misreads | "Fair enough, I wasn't clear." | Rephrase: who, what, how long, what to avoid |
| A draft states something wrong | "That's wrong, and it's exactly why we recommend someone reads every post before it goes out. Set up the way we recommend, it can't go out without that." | Correct it. Never let a wrong fact pass |
| A screen says Pulse | "Pulse was Holly's working name; you'll see it disappear as screens update." | Carry on |
| An error or failure | "That's broken, and I'll tell you straight: this is an early release and you'll see rough edges. You'd also have a direct line to the people who fix them." | Follow up within one working day |
| (Unconfirmed) a Holly fault flag appears | "That's Holly flagging a fault. It raises those with our team itself." | Do not speculate. Report it |
| Asked for something Holly cannot do | "No, it doesn't do that." Then the reason from the claims rules | No roadmap, no date |
| Odd number on a Watch screen | "This is the trend and the risk level; the alert figures are being checked." | Do not read numbers out |
| Voice sounds like someone else or like AI | "That tells me the material it learned from wasn't really you." | Ask for writing that is more them, or offer the five-minute interview |
After the demo. Send the draft they liked as email text, if they want it. Reset straight away: unschedule and delete every demo post; delete the prospect's voice and pasted text (if they signed up, move it to their own workspace first); remove watched subjects, feeds, sites and names added for them; disconnect any prospect connection and delete data it pulled in; clear Holly's conversation. Record what Holly did well and badly in the deal notes, and report every fault to Dom the same day.