The core demo: nine minutes, fixed order

Rule

Until the fictional demo workspace exists, demos are run only by Alex or John Cooper, on a Maktura internal workspace using consenting colleagues' profiles, never real client data. Steps 4 and 5 use a consenting colleague's profile cleared by Alex and John; if none is cleared, skip them and offer a follow-up. Never approve or publish a demo post on a connected profile: point at Approve, do not press it. After every demo, run the reset. Never leave a demo post scheduled.

Finished artefact first, then the shortest path, then let their questions choose what you peel back. Nine minutes (closed-deal decks averaged 9.1 minutes against 11.4 in lost deals; vendor data). Their questions, not features. Speak in "you"; avoid "if", "or" and "also". Start each step with an instruction to Holly where you can. Hand over the keyboard only after the reset.

The finished artefact (30 seconds)#

Open next week's team calendar, coloured by person, with the pre-run drafts waiting in the approvals queue.

Say (recruitment owner)

"Before we spoke I looked at your team. Of your fourteen consultants, three posted last month. On Tuesday [the story] broke and nobody at the firm said a word. This is what next week looks like when a team does." [Pause.] "These are demo voices from our own team, used with their permission; yours would come from your consultants' own posts. Every one is waiting for a person to approve it. Nobody wrote from a blank page, and the rule you'd want caught a line in this one. Let me show you how it got there."

Say (law head of BD): "This week's [ruling or report]. Three practice areas, each drafted in a demo partner's voice, each checked against 'nothing that reads as advice to an individual'. One line flagged and rewritten, all in the approvals queue. Your partners' job on Monday is to approve, not to write. Let me show you how it got there."

Step 1: one sentence to Holly (about 2.5 minutes)#

Type one new instruction, using the Q7 target's story if you have one (Test first if you use a pasted link or headline; manual route: start the post from the story in the feed):

Say

"Write [demo name]'s post on this story from the [sector] feed: [headline]. Shorter and less formal than the one in the calendar, for Thursday morning."

Say while it works: "That's Holly. You tell it what you want in plain English and it does the work across the platform: the news, the voice, the drafting, the calendar, the reports. It's set to Suggest: it drafts and asks. It doesn't act on its own."

Let them read in silence. Then: "Would you actually post that?" Whatever they say: "We lead the horse to water; you decide what it drinks." Ask Holly for one change, ideally theirs. If they change a lot: "Good. You control what it learns from." Only if they raise ChatGPT: "Everybody has the writing now. The difference is this one sounds like a person, it's checked against your rules, and it lands in a calendar your whole team shares." If asked the model: "It runs on Anthropic's Claude. The value isn't the model; it's the voices, your rules and Holly doing the work around them." Do not lead with it.

Step 2: the rules check, then approval (about 2 minutes)#

1. Type into the new draft a line that breaks your rule, for example: "We guarantee you'll find the right hire within two weeks."
2. Show the rules check flag it and the one-click rewrite. (Test first when the check runs; if only at submission, do 3 first and show the flag in the queue.)
3. "Send this to me for approval." (Test first; manual route: the editor's submit-for-approval control.)
4. Open the approvals queue: the new post and the pre-run posts, a note pinned on a line, Approve (not pressed).

Say

"Two things just happened. Your firm's rules checked the post, flagged that line, and rewrote it to fit your rule in one click. And now it's waiting for a person. You decide who approves what: the whole workspace, particular people, or a chain. We recommend a person approves every LinkedIn post."

Regulated buyer: "Right now, compliance is probably the reason nobody at the firm posts. Here it's the reason they can." Drafting attribution reads "Holly, in [name]'s voice".

Step 3: the team calendar and campaigns (about 1.5 minutes)#

"Schedule this for Thursday at the suggested best time." (Test first; manual route: pick the time in the calendar.) Show the calendar by week, coloured by person; drag one draft to another day. Open a campaign only if its view shows no "leads" label.

Say

"This is what fixes the fortnight problem. Everyone's posts in one calendar. Maktura suggests a best time from when your audience engages, and quiet hours block the window you choose. Colleagues connect their own LinkedIn by a link; nobody shares a password. Monday stops being 'why haven't you posted?' and becomes a look at one screen."

Say their number back: "That's [n] people, not one."

Step 4: who's engaging (about 1 minute)#

Never connect a prospect's LinkedIn. Use the consented colleague's profile, comment inbox only, names not readable on the shared window (zoom out, or skip). Do not open the warmth list or any person. Never show engagers' names until Karl Foster confirms (D1).

Say

"This is where comments on the posts land, in one place, and you can reply from here, so nothing sits unanswered. On your own account you'd see who's engaging with your posts, and reply from one place."

Then stop and let them read. Dormant account, big following: "You're basically creating a football stadium and then sitting there silently in the middle of it." If the buyer spots a name they know, do not point at it, and never search the list for their target company.

Rule

Never say: "leads", "prospects", "candidates", "everyone who's reacted", "every like becomes a named lead", "by the next morning", "the name, role and company behind every like", or anything about exporting or pushing people to a CRM. Warmth scores are AMBER: never describe them in writing as leads.

Say (where does the engagement data come from, word for word): "Publishing runs through LinkedIn's own connection: we don't ask for your password and we don't hold one. On the engagement side, I'll get you a written answer from our legal team rather than paraphrase it, because your compliance people will want it exactly right."

Log it.

Step 5: the report a managing partner would read (about 1.5 minutes)#

Show the measure home page (this week against the previous 16 weeks, best recent posts), then results by person with the plain-English verdict on each post. Reports, share links and scheduled emails are AMBER until D1: do not build, send or mention them. Skip the audience panel.

Say

"This is what you'd show [the managing partner] each month without anyone losing an afternoon to it. What went out, who it reached, what landed, by person. It doesn't claim revenue, and neither will I. It shows whether the team is turning up, and what works when they do."

Proof, matched to the buyer. Owners and partners: "We're the customer. It's used every working day inside the recruitment business one of the founders owns." Marketers, agencies and freelancers only, as a pilot user's words: "You end up with logins for so many pieces of software and you don't end up using them. This replaces the lot. And it does my least favourite job, end-of-month analytics, in a click."

Stop and ask#

At nine minutes: "That's the core of it. What would you want to see more of?" If nothing: "Which part of that matters most for the problem you described?" Then, every time: "Did you find the scale of it overwhelming, or did it make sense?" Write the answer down.