Tools · Startup & strategy
Systemization
Name a task you personally do — get a documented SOP and a score for whether the business can run without you.
How it works
Corpus-grounded systemization (Gerber's E-Myth via the start-a-company corpus): applies the Three-Step Process Documenter (Innovate the best current way → Quantify standards/metrics per step → Orchestrate it as the one written way) to draft a step-by-step SOP (each step with owner, standard, metric, citation), then applies the Franchise Prototype lens — would this run without you? — flagging founder-dependency hotspots and missing standards and scoring delegability 0–100. Complements EOS (MF-176): EOS is the operating cadence; this systemizes the work the company runs on.
You bring
{ task, context? }
You get
{ task_summary, sop{steps[] (action · owner · standard · metric · grounded_in)}, franchise_prototype{founder_dependency_hotspots[], missing_standards[], delegability_score, score_rationale}, grounded_in, provenance }
Use it for
- →Founder-as-bottleneck: name a recurring task → a documented, delegable SOP with a founder-dependency score
- →Find what only lives in your head: the Franchise Prototype lens flags the steps that still depend on you
- →Systemize before you scale: document the core processes, then run them on the EOS cadence (MF-176)
See it work
example outputTask: "onboard a new bookkeeping client," described by a solo bookkeeper who currently does every step herself.
Systemization & SOP — Onboarding a New Bookkeeping Client
Task: The end-to-end process the founder runs each time a new small-business client signs: collect access, set up the books, reconcile the opening balances, and hand off a first monthly close.
Standard operating procedure
- Send the intake + access checklist. Owner: Client Coordinator. Standard: every system (bank, payroll, POS, prior software) requested in one message with read-only roles named. Metric: < 1 business day from signed engagement to checklist sent.
- Verify access is live before any work starts. Owner: Bookkeeper. Standard: each connection test-loads one statement. Metric: 100% of accounts confirmed before step 3.
- Set up the chart of accounts from the template. Owner: Bookkeeper. Standard: start from the industry template, customize only documented exceptions. Metric: ≤ 5 custom accounts added without a written reason.
- Reconcile the opening period. Owner: Bookkeeper. Standard: every account ties to a source statement to the penny. Metric: 0 unreconciled items at handoff.
- Run and review the first monthly close. Owner: Reviewer. Standard: second-eyes review against the close checklist. Metric: client sign-off within 5 days of period end.
Franchise Prototype — would this run without you?
Delegability score: 52 / 100. A real process exists, but two steps still live in the founder's head.
- Founder-dependency hotspots: judgment calls on chart-of-accounts exceptions; the "is this client a fit" read during intake; reconciliation of messy prior-bookkeeper data.
- Missing standards: no written rule for when a custom account is justified; no defined escalation path when access stalls; no documented review checklist for step 5.
Score rationale: the mechanical steps (1, 2, 4) are delegable today; the score is held down by undocumented judgment in steps 3 and 5. Write those two standards and delegability clears 75.
Grounded in The E-Myth Revisited (Gerber) — Innovate → Quantify → Orchestrate, and the Franchise Prototype lens.
Run it now
Systemize a task into an SOP
Turn a recurring task into the one written way to do it — a drafted standard operating procedure, plus the Franchise-Prototype read on whether it runs without you.
Prefer code? Call it over the API or hand it to your AI agent via MCP — POST /api/bicycle/systemization · document_business_process. API & agent access →