Composer OS Layer Map
A six-layer view of Brand, Experience, Workflow, Knowledge, AI, and Trust with the weakest layer made visible.
Founder’s Audit
Five days. One map. One decision.
A fixed-scope Composer OS diagnostic for founder-led businesses that have accumulated tools, workflows, knowledge, and AI experiments faster than they have composed a system.
Duration
5 business days
Price anchor
EUR 1,000 starting point
Sessions
60-min intake + 45-min walkthrough
Deliverables
Plain-English Gap Report
A written diagnosis of what is strong, weak, missing, and what should not be fixed yet.
90-Day Roadmap
A prioritised sequence of fixes with owner, dependency, effort, and success signal.
Week-1 Quick Win
One dependency-light action your team can ship in seven days to create immediate commercial clarity.
Scope
A diagnosis, not a disguised implementation pitch.
The audit inspects how the business actually runs across the six Composer OS layers, identifies the bottleneck under the symptoms, and turns it into a practical commercial decision.
Brand and positioning
Website and sales experience
Workflow and automation
Knowledge and documentation
AI readiness and placement
Trust, data, and governance
Timeline
Five business days from intake to decision.
Day 1
Founder intake
A 60-minute session to understand the business model, constraints, bottlenecks, and what has already been tried.
Day 2
Evidence review
We review the website, sales material, tools, workflows, knowledge sources, AI experiments, and trust surface.
Day 3
Layer diagnosis
The business is scored across the six Composer OS layers so the root bottleneck is separated from symptoms.
Day 4
Roadmap composition
Findings are sequenced into a practical order: build, remove, defer, handle internally, or scope next.
Day 5
Walkthrough and decision
A 45-minute walkthrough turns the report into a decision: build with us, build internally, wait, or cut tools first.
Sample artifacts
Concrete outputs your team can inspect.
These thumbnails show the shape of the audit artifacts. Client examples are anonymized or blurred unless a client approves public use.
Layer Map
Brand
Experience
Workflow
Knowledge
AI
Trust
Layer Map
AI Placement Map
Human decision
Tool
Data touched
Guardrail
Outcome
AI Placement Map
90-Day Roadmap
Week 1
Weeks 2-4
Weeks 5-8
Weeks 9-12
Metric
90-Day Roadmap
For
Founder-led B2B businesses around EUR 1M-EUR 20M revenue
Teams with tool sprawl, workflow drag, scattered knowledge, or unclear AI experiments
Operators who want a diagnosis before buying more software or commissioning a rebuild
Not for
Pre-revenue founders still looking for product-market fit
Teams looking for a prompt workshop, AI theatre, or SaaS reseller recommendation
Enterprise change programmes where procurement and org design are the main problem
Current proof
Honest evidence, not inflated case-study theatre.
Public Composer OS framework documented across six layers.
Current founder-led engagements being converted into honest case studies.
No invented metrics: proof is limited to approved names, public artifacts, and anonymized patterns until clients approve more.
Request the audit
Start with context before the calendar handoff.
Use this page to understand fit and scope before choosing a time. Do not include passwords, exports, or sensitive client data in the initial booking context.
What happens after booking
- 1. We review fit and reply with any clarification questions.
- 2. You receive the intake checklist and data-sharing instructions.
- 3. We confirm the sharing route before any audit material is exchanged.
- 4. Day 1 starts with the founder intake session.
Booking
Book the audit conversation.
The calendar is the handoff after you have reviewed the audit scope, inputs, deliverables, and data-handling baseline.
Length
30 minutes
Timezone
Shown in your local time
After booking
Calendar invite + focused audit conversation
Choose a time for the audit conversation. You’ll get a calendar confirmation and a simple expectation-setting note before we meet.
No pitch theatre. No AI hype. First we look at the system. If the calendar ever fails, email fallback keeps the path open.
Inputs required
Bring the real operating evidence.
Website, deck, proposal, onboarding material, or current sales assets
Current tool stack and recurring SaaS or AI costs where available
Two or three workflows that repeatedly create delay, manual effort, or mistakes
Knowledge sources such as docs, Notion, Drive, SOPs, FAQs, or training material
Known trust constraints: GDPR, client security requirements, AI policies, contracts, or DPAs
Data handling and trust
The trust layer is part of the audit.
These notes are the public baseline. Client-specific DPA, subprocessor, security, and AI governance requirements are confirmed during intake.
Privacy
We only ask for the context needed to qualify and run the audit. Sensitive documents should be shared through agreed client channels, not through the public form.
Data handling
Audit inputs are used to diagnose your operating system and prepare the report. We do not publish client material, train public models on it, or reuse it as proof without written approval.
AI governance
AI may support synthesis, summarisation, and drafting, but final diagnosis and recommendations remain human-reviewed. AI is recommended only where workflow, knowledge, and trust layers can support it.
Subprocessors
Typical audit work may touch Google Workspace, Microsoft 365, Notion, Make, n8n, Vercel, Cloudflare, OpenAI, Anthropic, or similar tools depending on the client stack. The exact list is confirmed during intake.
Security baseline
Access is kept to the smallest practical scope, shared links are time-limited where possible, and the audit report flags missing MFA, ownership, logging, backup, vendor, and data-flow controls.