HandoverKit — client handbooks for AI automation deployments

1. The idea

In March 2026 an automation builder asks r/n8n how anyone documents workflows for clients: "every time I need to hand one off or get approval on a flow, it turns into a whole thing — Loom videos, manual Notion pages that go stale, or just screensharing. Is there a clean system people use for this? Or is everyone just winging it?" The answers confirm the winging: sticky notes on the canvas, Microsoft Visio, an hour of Loom per workflow, one operator who built himself a Notion template system to get it down to 15 minutes. Meanwhile the client who paid €3K for the build gets a video they won't watch, no answer to "what do I do when it breaks," and — if they touch the EU — new AI Act transparency obligations that started being enforced August 2, 2026.

HandoverKit generates the handover pack automatically. The agency pastes the workflow export (n8n/Make JSON) plus the SOW; out comes a branded client handbook: what each automation does in plain English, what triggers it, what it costs to run, what to do when it breaks and who to call, staff instructions for the tools involved, and an EU AI Act transparency annex (where AI is used, what data it touches, required disclosures). Delivered as a hosted page the agency white-labels, kept in sync when the workflow changes. Agencies pay $79/month; the handbook ships with every build as their professionalism upgrade.

2. Fact strip

3. The numbers

4. Why now

Two clocks, one real and dated, one softer.

The dated one: the EU AI Act's Article 50 transparency obligations became enforceable on August 2, 2026 — the European Commission confirmed on July 31, 2026 that enforcement begins on that date. Deployers (the agency's clients) must inform users when they interact with an AI system and mark AI-generated content; the AI Omnibus agreement of May 2026 gives systems already on the market until December 2, 2026 for machine-readable marking. Every agency deploying chatbots, AI email responders, or content automations into businesses with EU exposure now hands the client a compliance question along with the workflow — and almost none of them deliver documentation that answers it.

The softer clock: the AI-automation-agency wave is young and professionalizing fast. r/n8n has 254K members; beginners ask "what documents do you send?" (r/AiAutomations, Jul 2026) with no standard answer; and the first purpose-built competitor (flospect) appeared in these same threads in March 2026 — a sign the gap is real and open, and won't stay open long.

Sources: Data Protection Report, Jul 2026 · DLA Piper, 2026 · Article 50 practical guide

5. The receipts

"Every time I need to hand one off or get approval on a flow, it turns into a whole thing — Loom videos, manual Notion pages that go stale, or just screensharing. Is there a clean system people use for this? Or is everyone just winging it?" — r/n8n · kellyjames436 · Mar 2026 · thread (25 comments)

"I stopped fighting this and built a simple template system in Notion with screenshots auto-embedded at key decision points. […] Takes me 15 minutes per workflow now instead of an hour of Loom recording." — r/n8n · axpinto · Mar 2026 · comment

"I also produce a bunch of videos for the client showing them how everything works and how to troubleshoot, it helps in 6 months when they've forgotten the handover" — r/n8n · rekt_by_inflation · Mar 2026 · comment

"Especially if you're handing this to a client. They will find the one wrong number, and 'the AI did it' is not an answer." — r/n8n · easybits_ai · Jul 2026 · post

"I realized I'm not entirely sure what the standard client onboarding process looks like. […] What documents do you typically send?" — r/AiAutomations · Prisik_45 · Jul 2026 · thread

6. Whitespace

The gap: every documentation tool documents processes for teams (Scribe, Trainual) or workflows for builders (n8n sticky notes, flospect's canvas). Nobody generates the client-facing deliverable — the plain-English handbook the SMB owner and their staff actually need, with the what-if-it-breaks playbook and the compliance annex.

The wedge: import the workflow JSON the agency already has. Zero authoring. The incumbent (Notion + Loom) costs the agency an hour per workflow and goes stale; HandoverKit regenerates on every workflow change. Generic SOP tools can't read an n8n export; flospect reads it but points the output at the builder's own catalog, not at the client.

7. Proof & signals

• A €3K n8n build's scope explicitly included "1:1 delivery & documentation" — documentation is already a paid line item (r/n8n, Jun 2025, 116 upvotes).
• Implementation, training, and change management make up 60–70% of SMB AI project cost; small-org AI implementations run $5K–$50K (BayTech Consulting, 2026).
• 73% of small businesses say they need additional training to fully leverage AI (SMB survey, Carrier Management, Jul 2026).
• A competitor self-launched in the researched threads: flospect — "Catalog, share and document your automation flows," AI doc generation from the actual flow, n8n import added by user request (flospect.io, founder comment, Mar 2026).

8. Who you're up against

• Notion + Loom + screensharing — INCUMBENT. Free, universal, and named verbatim in the receipts. Costs the agency ~1 hour per workflow and "goes stale."
• flospect — the closest purpose-built player: visual canvas catalog of automation flows, AI-generated docs, test protocols, version control; n8n + Copilot Studio import; free signup, "Library plan" (pricing page thin). Builder-facing, not client-facing. Early and unproven.
• Scribe — screen-capture SOP generator, free tier, Pro Team from ~$13–17/seat/mo. Documents clicks, not workflow logic; client would have to author it.
• Trainual — SMB training/SOP platform, Build plan $249/mo for 10 seats. For the client's whole company, not the agency's deliverable; manual authoring.
• iorad — external-facing tutorial builder, ~$200/mo for teams. Tutorials, not system handbooks.
• Tango / Guidde — capture-based step guides, freemium. Same authoring problem as Scribe.
• n8n sticky notes / "have Claude document it" — the DIY route, named in the thread: "Just build everything with claude code… Just have AI document the entire process."

9. The verdict

Reasons to build

• The pain is receipts-real and recurring: a 25-comment thread of operators comparing hacks, one of whom built his own internal tooling to cut doc time from 60 to 15 minutes per workflow — people are already paying in time, and documentation already appears as a paid scope line in a €3K build.
• The buyer channel is one Rui already operates: his LinkedIn pipeline targets agency founders — the exact ICP — so the first 20 demos cost outreach he is doing anyway.
• A dated forcing function exists: Article 50 enforcement began Aug 2, 2026, and no documentation tool ships a deployer-transparency annex; the compliance angle is unclaimed positioning.
• Import-don't-author is a real wedge: every adjacent tool (Scribe, Trainual, Tango) requires manual authoring; the workflow JSON already contains the structure, and generating prose from it is exactly the kind of LLM product Rui builds at production quality.

Reasons to not build

• Demand signal is loud in words, weak in numbers: the anchor thread has a score of 4 (25 comments, 84% upvoted) and the onboarding thread scored 2. No keyword data surfaced showing meaningful search volume for "client handbook" / "workflow documentation for clients" — this is category-creation against a free incumbent.
• The DIY threat is structural, not hypothetical: a top-visible comment in the anchor thread is "just have AI document the entire process" with Claude Code. The technical half of the ICP can replicate the core output with one prompt; only branding, hosting, sync, and the compliance annex are defensible.
• Buyers are cheap and churny: solo automation agencies are price-sensitive, die young, and per-seat expansion is near zero. At $79/mo, 100 paying agencies — a strong outcome in this niche — is $95K ARR.
• One counter-receipt cuts at the premise: "the biggest mistake is to show the workflow to the client. They don't care about it, they want the final result and the real ROI" (r/n8n comment) — part of the market believes less client documentation, not better, is the answer.
• flospect has a head start on the import problem and is actively marketing in the exact threads where customers gather.

10. Founder fit

The idea demands: distribution 8/10 · domain 7/10 · sales 6/10 · technical 6/10 · capital 2/10

Best for: a founder already selling to automation agencies with an existing channel into them, who can ship an LLM product solo and use compliance positioning credibly.

Wrong for: anyone who'd have to build the agency audience from zero — distribution is the whole game here, and the product is too thin to pull its own demand.

The Rui check: unusually strong on paper. Rui is systems-led with recurring-revenue temperament (Innovator), ships production AI solo (technical 9), and — decisively — his Aether pipeline already DMs the exact ICP weekly. The two flags: his archetype says avoid businesses that depend on constant audience attention, and a $79/mo tool for a churny niche needs exactly that kind of feeding; and distribution demand (8) still exceeds his current distribution strength (5) outside his warm pipeline.

11. Value ladder

12. The plan

Days 1–14: build the generator as an internal AgentForge tool — n8n JSON + SOW in, branded handbook out — and use it on real client deliveries. Days 15–45: turn the outputs into the lead magnet and post before/after teardowns; offer the free one-workflow handbook in every Aether conversation that mentions delivery or docs. Days 45–90: convert free users to the $79/mo agency plan; answer the standing Reddit questions (the two receipt threads still have no accepted answer) with the checklist, not the pitch. Hardest part: making the generated prose trustworthy enough that an agency puts its brand on it unedited — the same "one wrong number" problem easybits_ai describes; solve with a review-diff step, not blind generation.

13. Napkin math — year one

Weakest assumption: the 20% free→paid conversion. Cheapest test: offer the free handbook in 30 Aether conversations and count who asks for a second one — before writing any SaaS code.

14. The ceiling

$300K–$800K ARR: ~300–800 paying agencies at ~$80–100/mo blended. Requires the n8n/Make agency ecosystem to keep growing and HandoverKit to become the category default before flospect or n8n itself ships client-facing docs. This is a niche-tool ceiling, not a venture one — appropriate only as a cash-flowing side asset next to AgentForge.

15. Playbook prompts

• Build plan: "Read reports/2026-08-29-handoverkit.md. Give me the MVP scope for the P1 internal version only (n8n JSON + SOW → branded handbook markdown/HTML): stack, week-one ship list, and the review-diff step from section 12."
• Roast: "Read reports/2026-08-29-handoverkit.md and roast it as (a) a skeptical n8n agency owner who already uses Notion+Loom, (b) flospect's founder, (c) an investor who thinks the ceiling is too low. No mercy."
• Money model: "Read reports/2026-08-29-handoverkit.md. Stress-test the value ladder: is $79/mo right for this buyer? Model $49/$99/$149 against the napkin funnel and the per-client continuity rung."

16. Verdict & next move

PIVOT · medium confidence

As stated — "AI onboarding handbook generator" sold as standalone SaaS — this is a PASS-leaning idea: category creation, near-zero search demand, a free incumbent, and a one-prompt DIY threat. But pivoted one step — an internal AgentForge deliverable first, productized only after it proves itself in Rui's own engagements — it fits his profile almost perfectly: built solo in days, immediately billable inside existing consulting scope (documentation is already a paid line item), distributed through a pipeline he already runs, and differentiated by an AI Act annex no competitor ships. The SaaS decision gets made later, on evidence: if agencies in his pipeline ask for the tool after seeing the output, build the $79/mo plan; if they don't, he still keeps a margin-raising deliverable. Next move: generate one handover pack for a real AgentForge client build this week — cost: ~2 days, $0.