Onboarding delays come from the handoffs, not the work
Customer-onboarding swimlane - 5 lanes x 5 phases + handoffs, Security bottleneck
Try in PlaygroundExample brief
A board cross-functional swimlane: enterprise SaaS customer onboarding. Lanes: Sales, Customer Success, Legal, Security (bottleneck, emphasized), Platform Ops. Phases: Contract signed, Kickoff, Security review, Technical setup, Go-live. Sales confirms scope and sends the order package; Legal validates non-standard terms; CS runs kickoff and captures success criteria; Platform Ops confirms tenant + integration assumptions; Security sends questionnaire and risk classification; Legal reviews DPA exceptions; Platform Ops provisions the tenant, SSO and sandbox; Security signs off controls; CS runs enablement and success-plan handover; Platform Ops monitors first-week incidents; Sales transitions sponsor ownership. Handoffs: order package -> kickoff -> security questionnaire -> tenant setup -> go-live handover. Takeaway: standardize the security handoff and tenant-readiness checklist to cut onboarding by two weeks.
Render it
Brief path
curl -X POST https://api.slideforge.dev/v1/render/auto \
-H "Authorization: Bearer sf_live_..." \
-H "Content-Type: application/json" \
-d '{ "brief": "A board cross-functional swimlane: enterprise SaaS customer onboarding. Lanes: Sales, Customer Success, Legal, Security " }'Structured intent (this template)
{
"pattern": "swimlane_flow",
"title": "Onboarding delays come from the handoffs, not the work",
"subtitle": "Enterprise customer onboarding - who does what, by phase",
"phases": [
{
"id": "contract",
"label": "Contract signed"
},
{
"id": "kickoff",
"label": "Kickoff"
},
{
"id": "security",
"label": "Security review"
},
{
"id": "setup",
"label": "Technical setup"
},
{
"id": "golive",
"label": "Go-live"
}
],
"lanes": [
{
"id": "sales",
"label": "Sales"
},
{
"id": "cs",
"label": "Customer Success"
},
{
"id": "legal",
"label": "Legal"
},
{
"id": "security",
"label": "Security",
"emphasis": "primary"
},
{
"id": "platform",
"label": "Platform Ops"
}
],
"activities": [
{
"id": "a1",
"lane_id": "sales",
"phase_id": "contract",
"title": "Send order package",
"detail": "Scope + sponsor notes"
},
{
"id": "a2",
"lane_id": "legal",
"phase_id": "contract",
"title": "Validate terms",
"detail": "Non-standard clauses"
},
{
"id": "a3",
"lane_id": "cs",
"phase_id": "kickoff",
"title": "Run kickoff",
"detail": "Capture success criteria"
},
{
"id": "a4",
"lane_id": "platform",
"phase_id": "kickoff",
"title": "Confirm tenant",
"detail": "Integration assumptions"
},
{
"id": "a5",
"lane_id": "security",
"phase_id": "security",
"title": "Risk questionnaire",
"detail": "Classify + send"
},
{
"id": "a6",
"lane_id": "legal",
"phase_id": "security",
"title": "DPA exceptions"
},
{
"id": "a7",
"lane_id": "cs",
"phase_id": "security",
"title": "Keep customer aligned"
},
{
"id": "a8",
"lane_id": "platform",
"phase_id": "setup",
"title": "Provision tenant",
"detail": "SSO + sandbox"
},
{
"id": "a9",
"lane_id": "security",
"phase_id": "setup",
"title": "Sign off controls",
"detail": "SSO + audit logging"
},
{
"id": "a10",
"lane_id": "cs",
"phase_id": "golive",
"title": "Enablement handover",
"detail": "Success plan"
},
{
"id": "a11",
"lane_id": "platform",
"phase_id": "golive",
"title": "Monitor week one"
},
{
"id": "a12",
"lane_id": "sales",
"phase_id": "golive",
"title": "Transition sponsor"
}
],
"handoffs": [
{
"from": "a1",
"to": "a3",
"label": "order package"
},
{
"from": "a3",
"to": "a5",
"label": "kickoff notes"
},
{
"from": "a5",
"to": "a8",
"label": "cleared"
},
{
"from": "a8",
"to": "a10",
"label": "tenant ready"
}
],
"takeaway": "Standardize the security handoff and tenant-readiness checklist to cut onboarding by two weeks."
}Related templates
Bars vs target marker
Margin recovery is visible but three units are below target
Diverging variance bars
Cloud hosting and contractor spend offset hiring delay savings
Ranked magnitude bars
Three offer families drive 68% of FY25 growth
Stacked composition bars
Compare media mix for FY25 and FY26
Frequently asked questions
How do I render the Onboarding delays come from the handoffs, not the work template?
Send a POST to /v1/render/auto with a brief, or call create_slide via MCP with the structured intent shown below. The response includes an editable .pptx, a PDF, and a PNG. $0.05 per slide.
Does an AI write the slide?
No. SlideForge renders deterministically from a structured intent — no LLM draws the slide, so text is never mangled or fabricated. The optional brief path uses a router to pick the pattern, then renders deterministically.
Can I customize the colors and fonts?
Yes. Pass a theme_id to apply a built-in or custom brand theme; the layout stays the same.
Try this template
Render Onboarding delays come from the handoffs, not the work deterministically — editable PowerPoint in under a second.