Growth Architecture Sprint
Turn the diagnosis into an operating system.
A focused 90-day engagement to redesign the growth system around the constraint — installing the strategy, ownership, metrics, decision rights and operating cadence required to scale.
90 days · three phases · one owner per layer
The 90-day architecture
Days 01–30
Architect
Output · Growth Blueprint
Days 31–60
Install
Output · Operating System
Days 61–90
Run
Output · Working Growth System
Each phase ends in something the company keeps and uses — not a document it files.
01 · When a sprint is needed
Knowing the problem is not the same as fixing the system.
A sprint is the right move when the constraint is already named and what is missing is structure — owners, cadence, decision rights.
01
Audit identified the constraint
The diagnosis exists. Nothing structural has changed yet.
02
GTM needs redesign
The motion that got you here will not carry the next stage.
03
Teams are misaligned
Capable functions optimising against different definitions of success.
04
Ownership is unclear
Several people contribute to a number nobody is accountable for.
05
Channels operate independently
Each partner optimises its own layer; the joins belong to no one.
06
Data does not drive decisions
Reporting happens. Decisions still wait for a meeting and an opinion.
07
Founder is still the approval layer
Decision rights never moved as the company grew.
08
Strategy exists but execution is fragmented
The plan is sound and the operating system to run it is missing.
02 · What the sprint changes
Seven structural shifts, one per row.
Nothing on the right is new activity. Each is the same work, held by a different structure.
Fragmented strategy
A single thesis every function can point its work at.
Unclear ownership
One person per layer, on the record, reviewed weekly.
Channel-led execution
Channels serve defined roles inside one revenue model.
Multiple dashboards
One source of truth, and an agreed rule for who acts on it.
Founder escalation
Decisions resolve at the level that holds the metric.
Reactive reviews
A fixed weekly and monthly rhythm with decisions attached.
Disconnected AI initiatives
Deployed where it removes a measured bottleneck, with an owner.
04 · What gets installed
Ten layers. Each one gets a name against it.
This table is the system. When every row is filled and agreed, the sprint has done its job.
Core rule
A layer with two owners has none. Names go on the record in phase one.
Core rule
Each owner is judged on a single defined number, with its baseline stated.
Core rule
A fixed day and a standing agenda. The cadence is what makes it a system.
01
Founder / CEO
Revenue vs plan
Monthly
Where to play, what to refuse
02
Founder + growth lead
Win rate vs alternative
Quarterly
Category claim and pricing logic
03
Growth / marketing lead
Qualified pipeline created
Weekly
Channel mix and spend shifts
04
Sales lead
Stage-to-stage conversion
Weekly
Process, qualification and SLA changes
05
Lifecycle / CS owner
Repeat and expansion revenue
Monthly
Retention and expansion priorities
06
Analytics owner
Metric definition coverage
Monthly
Source of truth and tracking changes
07
Named function owner
Cycle time or cost removed
Monthly
What to deploy, pause or retire
08
Founder + function leads
Capacity vs plan
Monthly
Hiring, agency and capability calls
09
Growth lead
Planned vs shipped
Weekly
Prioritisation and work in progress
10
Growth lead + analytics
Decisions per review
Weekly
Targets, baselines and escalation
Owners shown are roles · filled with real names in phase one
05 · Who owns what
I hold the architecture. Your team holds the work.
Two columns, drawn on day one, reviewed weekly. Nothing sits in the middle unassigned.
Dheeraj owns
Architecture
Strategic priorities
Decision rights
Operating model
Leadership alignment
Measurement design
Review cadence
Your team owns
Execution
Channel operations
Sales follow-up
Content
Campaigns
CRM activity
Day-to-day delivery
06 · Sample sprint
Strong demand, weak conversion — and what was installed.
Anonymised by sector and stage. No performance numbers are claimed — the change is structural.
Problem
Pipeline creation was healthy and had been for three quarters. Closed revenue was not moving with it, and each function blamed the other.
Audit found
Marketing measured leads. Sales measured meetings. Nobody owned the transition between them, and no written definition of a qualified lead existed on either side.
Result
The argument about lead quality ended, because both functions were finally measuring the same thing on the same day of the week.
Sprint installed
One set of stages both functions use, with entry and exit criteria written down.
An agreed definition of qualified, applied before handoff rather than argued after.
A committed first-contact window, instrumented and visible to both teams.
One view, one set of definitions, reviewed on the same day every week.
A standing meeting with named owners where the numbers produce decisions.
07 · What you leave with
Ten artefacts. All of them already in use by day 90.
Every item below is live in the business before the engagement closes. Nothing is delivered for future consideration.
Phase one
Growth Architecture Blueprint
The agreed system on one page: thesis, priorities, layers and owners.
Phase one
90-Day Operating Plan
What changes in which week, and who is responsible for each move.
Phase two
Decision Rights Map
Who decides, who is consulted, what escalates and to whom.
Phase two
KPI Architecture
Every metric defined, owned, baselined and tied to a review.
Phase two
Growth Dashboard Structure
The views, their definitions and the day each one gets read.
Phase one
Team Roles
Accountabilities per layer, and the gaps that need hiring or training.
Phase two
Agency and Partner Roles
What each partner owns inside the architecture, and how it is judged.
Phase two
AI Opportunity Map
Where AI removes a measured bottleneck, with owner and expected effect.
Phase three
Operating Cadence
The weekly and monthly rhythm, with agendas and decision rules.
Phase three
System Documentation
The whole system written down, so the next hire can be onboarded into it.
08 · Where the sprint sits
Five engagements. One job each.
The sprint is the only one that designs and installs. If the system already works, you do not need it.
Audit
A structured diagnostic across nine layers, ending in one constraint and a sequence.
Strategic Consulting
One high-stakes call examined properly, with a clear recommendation.
Growth Sprint
Design and install the system
The operating system built and running with your team, not handed over as a plan.
Fractional CMO
Operate the system over time
Executive ownership of growth, week after week, once the system exists.
Founder Advisory
Standing counsel on the calls only the founder can make.
09 · Fit
A sprint needs a team to install into.
Best for
Founder-led companies
Growth-stage businesses
Teams with internal execution capability
Companies after an Audit
Businesses preparing to scale
GTM resets
New market expansion
Leadership transitions
Not for
Idea-stage founders
Execution-only buyers
Companies without internal ownership
Teams unwilling to change operating rhythm
10 · Engagement
Ninety days, and the calendar it runs on.
The cadence is the deliverable. If the reviews do not happen, nothing installs.
Duration
Three equal phases of thirty days. The end date is fixed at the start.
Investment
Scoped once the constraint and the team shape are known. Fixed before work begins.
Founder time
One standing session per week, plus the leadership workshops and monthly review.
Weekly
One hour with the founder on decisions, trade-offs and what is blocked.
Per phase
Half-day with the leadership team to agree architecture and ownership.
Ongoing
Working sessions with the operators who will run each layer.
Weekly
The standing review, run with me until the owners run it themselves.
Monthly
Progress against the 90-day plan, with the decisions it produced.
11 · At day 90
Handover is the default outcome.
The sprint is designed to end. Anything beyond it is a separate decision, made after day 90 and never assumed in the scope.
System can run internally
The default and the intended outcome. The team owns it from day 91.
Needs ongoing executive ownership
The system exists but has no senior owner inside the business.
Founder needs ongoing counsel
The system holds; the founder decisions around it keep compounding.
12 · Questions
What founders ask before applying.
If your question is not here, put it in the application — the first conversation covers it before any scope is agreed.
13 · Apply
You do not need more activity.
Selective
One or two sprints run at a time, because each needs my weekly presence for ninety days.
Diagnosis first
If the constraint is not yet named, I will route you to the audit rather than start here.
Response
I read every application personally and reply within two working days.
Sprint application · 8 fields
Name
Company
Website
Revenue / stage
Constraint
Current team
Desired 90-day outcome
Apply for a Growth Sprint
Commercial details stay between us. Under NDA on request.