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.

Before

Before

After · day 90

Fragmented strategy

→

One growth architecture

One growth architecture

A single thesis every function can point its work at.

Unclear ownership

→

Named owners

Named owners

One person per layer, on the record, reviewed weekly.

Channel-led execution

→

Shared metrics

Shared metrics

Channels serve defined roles inside one revenue model.

Multiple dashboards

→

Clear decision rights

Clear decision rights

One source of truth, and an agreed rule for who acts on it.

Founder escalation

→

Integrated execution

Integrated execution

Decisions resolve at the level that holds the metric.

Reactive reviews

→

Operating cadence

Operating cadence

A fixed weekly and monthly rhythm with decisions attached.

Disconnected AI initiatives

→

AI tied to real workflows

AI tied to real workflows

Deployed where it removes a measured bottleneck, with an owner.

03 · The 90-day system

Architect. Install. Run.

Three equal phases of thirty days. Select a phase to see what is defined, built and handed over.

Days 01–30

Architect

Design the growth system on paper, with the leadership team in the room.

Days 31–60

Install

Turn the blueprint into the machinery the team uses every week.

Days 61–90

Run

Run the system with the team until it holds without me.

Days 01–30 · Define

Decide the model before anyone builds against it.

Four to six working sessions establish the thesis, what the company will refuse, and which layer each channel and team actually serves.

Output

Growth Blueprint

The agreed architecture: thesis, priorities, channel roles, owners and the metric each one carries.

Defined in phase one

01

Growth thesis

How this business will grow for the next four quarters, in one page.

02

Positioning

The claim, the ICP and the reason to choose you, sharpened to survive sales.

03

Priorities

Three to five moves that matter, and the long list being explicitly refused.

04

Channel roles

What each channel is for — create, capture or convert — and what it is not.

05

Ownership

One named owner per layer, agreed in the room, not assigned afterwards.

06

Metrics

The metric each owner is measured on, with its definition and baseline.

03 · The 90-day system

Architect. Install. Run.

Three equal phases of thirty days. Select a phase to see what is defined, built and handed over.

Days 01–30

Architect

Design the growth system on paper, with the leadership team in the room.

Days 31–60

Install

Turn the blueprint into the machinery the team uses every week.

Days 61–90

Run

Run the system with the team until it holds without me.

Days 01–30 · Define

Decide the model before anyone builds against it.

Four to six working sessions establish the thesis, what the company will refuse, and which layer each channel and team actually serves.

Output

Growth Blueprint

The agreed architecture: thesis, priorities, channel roles, owners and the metric each one carries.

Defined in phase one

01

Growth thesis

How this business will grow for the next four quarters, in one page.

02

Positioning

The claim, the ICP and the reason to choose you, sharpened to survive sales.

03

Priorities

Three to five moves that matter, and the long list being explicitly refused.

04

Channel roles

What each channel is for — create, capture or convert — and what it is not.

05

Ownership

One named owner per layer, agreed in the room, not assigned afterwards.

06

Metrics

The metric each owner is measured on, with its definition and baseline.

03 · The 90-day system

Architect. Install. Run.

Three equal phases of thirty days. Select a phase to see what is defined, built and handed over.

Days 01–30

Architect

Design the growth system on paper, with the leadership team in the room.

Days 31–60

Install

Turn the blueprint into the machinery the team uses every week.

Days 61–90

Run

Run the system with the team until it holds without me.

Days 01–30 · Define

Decide the model before anyone builds against it.

Four to six working sessions establish the thesis, what the company will refuse, and which layer each channel and team actually serves.

Output

Growth Blueprint

The agreed architecture: thesis, priorities, channel roles, owners and the metric each one carries.

Defined in phase one

01

Growth thesis

How this business will grow for the next four quarters, in one page.

02

Positioning

The claim, the ICP and the reason to choose you, sharpened to survive sales.

03

Priorities

Three to five moves that matter, and the long list being explicitly refused.

04

Channel roles

What each channel is for — create, capture or convert — and what it is not.

05

Ownership

One named owner per layer, agreed in the room, not assigned afterwards.

06

Metrics

The metric each owner is measured on, with its definition and baseline.

03 · The 90-day system

Architect. Install. Run.

Three equal phases of thirty days. Select a phase to see what is defined, built and handed over.

Days 01–30

Architect

Design the growth system on paper, with the leadership team in the room.

Days 31–60

Install

Turn the blueprint into the machinery the team uses every week.

Days 61–90

Run

Run the system with the team until it holds without me.

Days 01–30 · Define

Decide the model before anyone builds against it.

Four to six working sessions establish the thesis, what the company will refuse, and which layer each channel and team actually serves.

Output

Growth Blueprint

The agreed architecture: thesis, priorities, channel roles, owners and the metric each one carries.

Defined in phase one

01

Growth thesis

How this business will grow for the next four quarters, in one page.

02

Positioning

The claim, the ICP and the reason to choose you, sharpened to survive sales.

03

Priorities

Three to five moves that matter, and the long list being explicitly refused.

04

Channel roles

What each channel is for — create, capture or convert — and what it is not.

05

Ownership

One named owner per layer, agreed in the room, not assigned afterwards.

06

Metrics

The metric each owner is measured on, with its definition and baseline.

03 · The 90-day system

Architect. Install. Run.

Three equal phases of thirty days. Select a phase to see what is defined, built and handed over.

Days 01–30

Architect

Design the growth system on paper, with the leadership team in the room.

Days 31–60

Install

Turn the blueprint into the machinery the team uses every week.

Days 61–90

Run

Run the system with the team until it holds without me.

Days 01–30 · Define

Decide the model before anyone builds against it.

Four to six working sessions establish the thesis, what the company will refuse, and which layer each channel and team actually serves.

Output

Growth Blueprint

The agreed architecture: thesis, priorities, channel roles, owners and the metric each one carries.

Defined in phase one

01

Growth thesis

How this business will grow for the next four quarters, in one page.

02

Positioning

The claim, the ICP and the reason to choose you, sharpened to survive sales.

03

Priorities

Three to five moves that matter, and the long list being explicitly refused.

04

Channel roles

What each channel is for — create, capture or convert — and what it is not.

05

Ownership

One named owner per layer, agreed in the room, not assigned afterwards.

06

Metrics

The metric each owner is measured on, with its definition and baseline.

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

One owner

One owner

A layer with two owners has none. Names go on the record in phase one.

Core rule

One metric

One metric

Each owner is judged on a single defined number, with its baseline stated.

Core rule

One review cadence

One review cadence

A fixed day and a standing agenda. The cadence is what makes it a system.

Layer

Layer

Owner

Owner

Metric

Metric

Cadence

Cadence

Decision

01

Strategy

Strategy

Owner

Owner

Founder / CEO

Metric

Metric

Revenue vs plan

Cadence

Cadence

Monthly

Decision

Decision

Where to play, what to refuse

02

Positioning

Positioning

Owner

Owner

Founder + growth lead

Metric

Metric

Win rate vs alternative

Cadence

Cadence

Quarterly

Decision

Decision

Category claim and pricing logic

03

Demand

Demand

Owner

Owner

Growth / marketing lead

Metric

Metric

Qualified pipeline created

Cadence

Cadence

Weekly

Decision

Decision

Channel mix and spend shifts

04

Conversion

Conversion

Owner

Owner

Sales lead

Metric

Metric

Stage-to-stage conversion

Cadence

Cadence

Weekly

Decision

Decision

Process, qualification and SLA changes

05

Customer Growth

Customer Growth

Owner

Owner

Lifecycle / CS owner

Metric

Metric

Repeat and expansion revenue

Cadence

Cadence

Monthly

Decision

Decision

Retention and expansion priorities

06

Data

Data

Owner

Owner

Analytics owner

Metric

Metric

Metric definition coverage

Cadence

Cadence

Monthly

Decision

Decision

Source of truth and tracking changes

07

AI

AI

Owner

Owner

Named function owner

Metric

Metric

Cycle time or cost removed

Cadence

Cadence

Monthly

Decision

Decision

What to deploy, pause or retire

08

People

People

Owner

Owner

Founder + function leads

Metric

Metric

Capacity vs plan

Cadence

Cadence

Monthly

Decision

Decision

Hiring, agency and capability calls

09

Execution

Execution

Owner

Owner

Growth lead

Metric

Metric

Planned vs shipped

Cadence

Cadence

Weekly

Decision

Decision

Prioritisation and work in progress

10

Measurement

Measurement

Owner

Owner

Growth lead + analytics

Metric

Metric

Decisions per review

Cadence

Cadence

Weekly

Decision

Decision

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

The Sprint does not replace the team. It changes how the team operates.

The Sprint does not replace the team. It changes how the team operates.

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

Strong demand, weak conversion

Strong demand, weak conversion

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

Sales qualification and follow-up had no common ownership

Sales qualification and follow-up had no common ownership

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

A system where demand and sales operate against the same definition.

A system where demand and sales operate against the same definition.

The argument about lead quality ended, because both functions were finally measuring the same thing on the same day of the week.

Sprint installed

Shared lifecycle stages

Shared lifecycle stages

One set of stages both functions use, with entry and exit criteria written down.

Lead scoring

Lead scoring

An agreed definition of qualified, applied before handoff rather than argued after.

Response SLA

Response SLA

A committed first-contact window, instrumented and visible to both teams.

Revenue dashboard

Revenue dashboard

One view, one set of definitions, reviewed on the same day every week.

Weekly growth review

Weekly growth review

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.

The goal is not a deck. The goal is a system your team is already running.

The goal is not a deck. The goal is a system your team is already running.

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

90 days

90 days

Three equal phases of thirty days. The end date is fixed at the start.

Investment

Discussed after diagnosis

Discussed after diagnosis

Scoped once the constraint and the team shape are known. Fixed before work begins.

Founder time

Weekly

Weekly

One standing session per week, plus the leadership workshops and monthly review.

Weekly

Founder / CEO session

Founder / CEO session

One hour with the founder on decisions, trade-offs and what is blocked.

Per phase

Leadership workshop

Leadership workshop

Half-day with the leadership team to agree architecture and ownership.

Ongoing

Team implementation

Team implementation

Working sessions with the operators who will run each layer.

Weekly

Growth review

Growth review

The standing review, run with me until the owners run it themselves.

Monthly

Executive review

Executive review

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

Handover

Handover

The default and the intended outcome. The team owns it from day 91.

Needs ongoing executive ownership

Fractional CMO

Fractional CMO

The system exists but has no senior owner inside the business.

Founder needs ongoing counsel

Founder Advisory

Founder Advisory

The system holds; the founder decisions around it keep compounding.

Another narrow decision

Strategic Consulting

Strategic Consulting

One bounded call remains — a market, a price, an AI bet.

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.

Does every Sprint require an Audit first?

−

No, but the constraint has to be named before day one. If you already have a credible diagnosis — internal or from prior work — we start from it. If the constraint is still contested inside the company, the audit comes first; a sprint built on the wrong constraint installs the wrong system very efficiently.

Who needs to participate?

+

Does Dheeraj manage execution?

+

Can you work with our agencies?

+

What if the team is missing capability?

+

What happens after 90 days?

+

Can the Sprint lead into Fractional CMO?

+

Does every Sprint require an Audit first?

−

No, but the constraint has to be named before day one. If you already have a credible diagnosis — internal or from prior work — we start from it. If the constraint is still contested inside the company, the audit comes first; a sprint built on the wrong constraint installs the wrong system very efficiently.

Who needs to participate?

+

Does Dheeraj manage execution?

+

Can you work with our agencies?

+

What if the team is missing capability?

+

What happens after 90 days?

+

Can the Sprint lead into Fractional CMO?

+

Does every Sprint require an Audit first?

−

No, but the constraint has to be named before day one. If you already have a credible diagnosis — internal or from prior work — we start from it. If the constraint is still contested inside the company, the audit comes first; a sprint built on the wrong constraint installs the wrong system very efficiently.

Who needs to participate?

+

Does Dheeraj manage execution?

+

Can you work with our agencies?

+

What if the team is missing capability?

+

What happens after 90 days?

+

Can the Sprint lead into Fractional CMO?

+

Does every Sprint require an Audit first?

−

No, but the constraint has to be named before day one. If you already have a credible diagnosis — internal or from prior work — we start from it. If the constraint is still contested inside the company, the audit comes first; a sprint built on the wrong constraint installs the wrong system very efficiently.

Who needs to participate?

+

Does Dheeraj manage execution?

+

Can you work with our agencies?

+

What if the team is missing capability?

+

What happens after 90 days?

+

Can the Sprint lead into Fractional CMO?

+

13 · Apply

You do not need more activity.

You need the system activity belongs inside.

You need the system activity belongs inside.

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

Email

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.