Growth Systems Audit
A written map of your growth stack, a ranked list of what's holding it back, and a build plan, before you commit to a build.
Seven steps, each with something you keep.
-
Audit and mapping
Map how growth work and data move across tools, people and decisions.
You receive: A written map of your growth stack and workflows.
Illustrative example. Not a client result. Channels + customers↓Data warehouse↓Knowledge + workflows -
Diagnosis
Find where data breaks, context gets lost and work waits.
You receive: A ranked list of diagnoses, with the evidence for each.
Illustrative example. Not a client result. - PriorityPlatform-reported revenue 30% above Shopify for prospecting; attribution windows differ by channel.
- NextCampaign naming and source definitions need review before comparison.
- LaterRecord the reporting definitions in the knowledge index.
-
Scoping
Agree priorities, dependencies and ownership before work starts.
You receive: A written build plan.
Illustrative example. Not a client result. Illustrative scoped plan Work Planned work Warehouse Meta, Google, TikTok, Shopify, Klaviyo → modelled daily Knowledge Reporting definitions, brand rules and decision records Workflows Reporting workflow with growth-lead review before action -
Build
Build the warehouse, knowledge index, AI agents and workflows in your accounts.
You receive: Working systems in your stack.
Illustrative example. Not a client result. -
Iteration and QA
Test against your data and workflows, fix edge cases and set review points.
You receive: A QA record and defined review points.
Illustrative example. Not a client result. - ✓ Source data reconciled
- ✓ Access reviewed
- ✓ Edge cases tested
- ✓ Human review confirmed
-
Launch
Roll out to the team with training and documentation.
You receive: Live systems and handover documentation.
Illustrative example. Not a client result. System handoverAccount ownershipOperating guideTeam trainingReview points -
Follow-up
Review performance, extend the system or train your team to run it.
You receive: Ongoing operation, or a trained handover.
Illustrative example. Not a client result. Review calendarReviewDecideFollow upEvidenceNext changeOwnership
What your team provides.
Account access and a few working sessions help us map your stack and workflows. Your team identifies priorities and dependencies during those sessions.
Your accounts. Your records.
Your team owns the data, configurations and records. Actions are logged, and people review at defined decision points. Launch includes training and documentation, followed by ongoing operation or a trained handover.
Where teams start
A qualitative framework for discussing the starting point. It is not a score or a performance forecast.
Disconnected tools
Reports and context are spread across tools.
Shared reporting
The team agrees how to report on its work.
Unified data
Channel and customer data use one model.
Indexed knowledge
People and AI can find the team context and decisions.
Compounding operations
The team reuses recorded evidence in its next decisions.
Before your audit.
What account access is needed?
We review access and provider permissions before connecting sources. The audit maps your growth stack and workflows, with data handling reviewed before sources are connected.
What does our team provide?
Your team provides account access and working sessions to map the stack, workflows and decisions. Your team identifies priorities and dependencies during those sessions.
What happens after the audit?
You receive a written map, a ranked diagnosis and a build plan. If you proceed, the engagement moves through scoping, build, iteration and QA, launch and follow-up.
How is the build scoped?
The build plan covers tools, priorities, dependencies and ownership, with scope agreed before build. Access, third-party tools, ongoing operation and handover are set out in writing.
Map the work before you build.
Discuss your growth stack, workflows and priorities in an audit conversation.