business-baseline
Map, diagnose, and optimize business operations through progressive visual analysis.
Inputs
- kpi-registry — Canonical KPI definitions and thresholds.
- process-definitions — Documented processes — the maps being diagnosed.
- client-kpi-registry — Client KPI registry when scoped to a client.
- client-id — Client folder name under
- business-type — Business archetype for inference patterns (auto-detected if omitted) (agency | coach | course-creator | creator | ecommerce | enterprise-b2b | franchise | local | manufacturing | multi-channel-retail | nonprofit | real-estate | saas | service-provider | technical-services)
- profile — Company or client profile — identity and stage.
- icp — ICP — target customer the strategy is for.
- offerings — Offerings catalogue — what is being strategised.
- marketing-context — Positioning, narrative, and competitive frame.
- process — Process name to expand (e.g. 'Lead Gen', 'Onboarding', 'Fulfillment')
- process-note — Path to the `type: process` source note (client or company scope)
- orientation — Layout direction (default horizontal, unchanged behavior). horizontal = lanes are rows, steps flow left→right. vertical = lanes are columns with a top label, steps flow top→bottom — use for LONG processes (e.g. 16 steps) that run off the right edge horizontally; the canvas gets tall (expected). Two-way arrow binding holds identically in both. Vertical writes a distinct {process-id}-swimlane-vertical.excalidraw.md so it never clobbers the horizontal diagram. (horizontal | vertical)
- no-archive — Skip archiving an existing diagram before regeneration (default false — archive first)
- no-bands — Suppress stage bands (default false). When steps carry a `stage:` field and orientation is vertical, consecutive same-stage steps are grouped into labelled full-width bands behind the lanes; --no-bands renders the plain sequence. Bands are vertical-only — horizontal ignores stage regardless.
- business-type — One of the 15 archetype slugs (auto-detected from baseline if a session exists) (agency | coach | course-creator | creator | ecommerce | enterprise-b2b | franchise | local | manufacturing | multi-channel-retail | nonprofit | real-estate | saas | service-provider | technical-services)
- scope — 'company' (default — this vault's own business) or a client-id for a client-scoped registry
- chains — One or more journey value-chain ids to score, e.g. `service-to-renew`, `deliver-to-satisfaction`. The two meta-chains (infrastructure, operating-controls) have no journey stages and cannot be scored.
- business-type — Archetype packs supplying the stage→evidence mapping; repeatable. Stages with no row in the selected packs fall back to the all-archetype union and are flagged as such in the report. (agency | coach | course-creator | creator | ecommerce | enterprise-b2b | franchise | local | manufacturing | multi-channel-retail | nonprofit | real-estate | saas | service-provider | technical-services)
- kpi-packs — Archetype KPI packs — the `Computed from` column is the stated stage→evidence-entity mapping this route reads.
How you ask
- Run a business baseline on my operations" · "Map my business and identify bottlenecks" · "Create a bow-tie funnel for my SaaS product" · "Give me an Excalidraw swimlane I can drag around
Outputs
- (Action Roadmap page)
- (client scope, horizontal) or (company scope, horizontal); vertical orientation appends -vertical before the extension ({process-id}-swimlane-vertical.excalidraw.md)
- (company scope) or (client scope)
- (new page)
- Each swimlane migrated into a structured `type: process` note — the source of truth (drawio-only baselines liberated into queryable data)
- Excalidraw swimlane rendered from the process note — derived view, not the source of truth; prior version archived to diagrams/_archive/. Horizontal and vertical are separate files that can coexist for the same process.
- Optional swimlane render of the process note
- Optional visual export rendered from the process notes — not the source of truth
- Per-stage verdict table with the evidence each verdict rests on, plus the vault-visible-only caveat
- Registry with domain tables + Value-Chain Mapping section, same contract as the company registry (parsed by list_value_chains.py and consumed by owner-priority-system kpi_refresh.py/kpi_verify.py)
- Source-of-truth process note with steps[], owners, state, and opportunity flags
- Structured `type: process` note(s) — the source of truth (steps, owners, state, flags)
- continued_baseline (drawio)
- roadmap_page (drawio-page)
- scan_summary (markdown)
- session_state (yaml)
Levelbeginner
Inputconversation
Outputdocument
Setup[none]
Roles[CEO / Founder, Operations Manager]
