The 15-minute walkthrough

Internal script for the partner working session. Goal: leave with two pilot builders named. Links: the demo · the leave-behind.

MIN 0–2 · The problem, in their language

"Builders pay for photography, listings, and websites — and then their social channels go quiet, because posting is a daily chore no one owns. Marketing coordinators drown, agencies are expensive, and the AI tools guess — which in this industry is a liability, not a feature. I built something that fixes all three at once, and it's live. Let me show you, not tell you."

MIN 2–7 · The live demo (the machine, running)

Do: open /demo/builders/ on a phone (or narrow browser window) — the phone-ness is the point. Walk one card: photo, text, channels, time. Tap Approve. Tap Edit on the second, change one word, approve. Skip the third and pick a reason — say: "every skip teaches it."

Do: scroll to the held card. This is the moment. Say the line below slowly.

"Look at this one — the engine wanted to post a price, couldn't verify it from the listing source, and locked the post. Nobody can approve it, including me. Every fact in every post traces to the listing. In a world of AI that makes things up, this machine structurally can't. That's the difference."

Do: now prove the pipe is real. On the laptop, run:
ssh root@64.227.29.192 python3 /opt/postiz/demo-fire.py --fire
…then open the two URLs it prints — a post appearing on X and on Bluesky, live, during the meeting.

"That just published to two real networks from the same machine. Facebook, Instagram, and LinkedIn connect the identical way — those apps are in review now."

Do (the closer of the demo section): after the live-fire, open the REAL portal on the phone — postiz.wholetech.com/portal/app/?c=demo&t=… (bookmarked) — and approve one genuine engine-generated post. Say: “The mockup you just saw is the design; this one is the working product — real database, real scheduler, built last week. Your builders would be using this on day one.”

MIN 7–10 · What the builder's team actually experiences

Under a minute a day, from a phone. No logins, no tools to learn — the hub is our back-of-house, never their problem.
If a channel doesn't exist or isn't business-grade, a real person sets it up properly under the builder's own identity. We do the annoying parts.
Weekly digest; monthly five-number report: posts, reach, engagement, site clicks, top post. The report is the product.

MIN 10–13 · The ask

"Here's what I want: pick two builders. We run their social for 60 days, free, instrumented from day one — baseline before the first post, weekly snapshots, honest reviews at day 30 and day 60. If the numbers are good, we price it together from the evidence and talk about how you want to be involved — referral, revenue share, or under your brand. If they're not, the review will say so plainly. Which two builders should we start with?"

Then stop talking. The next voice should be theirs. If they hesitate, the fallback ask: "Would you introduce me to one builder marketing director who'd give me honest feedback?"

MIN 13–15 · Questions — honest answers ready

"What does it cost?" — "The pilot, nothing. After that we price from pilot data — normal builder marketing money, month to month, no lock-in, and their accounts stay theirs."
"Is this ChatGPT?" — "No. The drumbeat posts are assembled deterministically from listing facts — that's why it can't hallucinate. Nothing publishes without a human approval."
"What about Facebook/Instagram?" — "Same pipe, their apps are in review now; the pilot starts on the open networks and adds channels as approvals land — you'll see them appear in the weekly digest."
"Who runs this?" — "The machine runs itself and is monitored around the clock; a human owns every approval gate and answers the phone."
"Why you?" — "Because I built it, it's already posting, you've watched it work for five years' worth of projects — and because it's the only one in this space that structurally cannot make things up."

Prep checklist (before the session)

Phone charged, demo page loaded and reset (button at the bottom).
Laptop SSH tested; run demo-fire.py without --fire once to preview.
Leave-behind printed (2 copies) or link ready to send on the spot.
Have day-30/60 dates in mind so scheduling happens in the room.