Business Operating System

01 — Operating system for a service firm

Run the business from Git. Use Twenty, n8n, and Metabase as tools — not as the operating system.

YAML and Markdown define how you sell and deliver. CRM, automation, and dashboards stay replaceable.

Example GmbH · CHF · Europe/Zurich · stack health-checks optional

02 — Problem

Five products, one unanswered question.

Spreadsheets, a SaaS CRM, and a wiki drift apart. Nobody can answer “what is the pipeline, and what does won mean?” without clicking five products. Custom apps make it worse.

03 — Solution

One Git repository is the operating system.

  1. business.yml Offer, CHF, pipeline, integrations.
  2. processes/ Inputs, outputs, and KPI for how you actually work.
  3. crm/*.yml Applied in Twenty by hand — runtime optional.
  4. automation/ n8n examples: New Lead, Qualified Lead, Won Deal — runtime optional.
  5. kpi/ Metabase reads a warehouse, not tribal Slack lore — runtime optional.

04 — How it works

From visitor to CHF dashboard.

  1. Visitor submits the lead form. The website is the product. Docker is not required to read or send it.
  2. n8n creates Twenty records at stage New — when that optional stack is running. If it is not, the request is still captured on the page.
  3. You qualify against the ICP in business.yml.
  4. Won deals start onboarding tasks.
  5. Snapshots land in PostgreSQL so Metabase can show CHF and funnel KPIs.

05 — Offer

Two packages. Prices in Swiss francs.

bos-setup

BOS Setup

4 900 CHF

One-off project

Processes mapped, Twenty configured, n8n imported, first dashboards.

Request a setup

bos-retainer

BOS Retainer

1 900 CHF

Monthly

Weekly operating review, pipeline hygiene, KPI snapshots.

Talk about a retainer

Prices come from business.yml. Update both together.

06 — Proof

Replace the tools. Keep the definition.

Replace this section with real customer quotes when you have them.

07 — Lead form

Request a setup.

Tell us who you are. If the optional n8n webhook is up, the payload becomes a New opportunity in Twenty. If it is not, you still get a confirmation — nothing is stored in Git.

Privacy: when the CRM stack is connected, this data lands in Twenty. It is never committed to Git.