Skip to content
GrowthOS.

How we work

Audit the constraint. Sequence the build. Leave the system owned.

A twelve-week build has a visible order because brand, conversion, CRM, and operations depend on one another.

The first 90 days

From ambiguity to an operating rhythm.

Constraint map, baseline metrics, sequenced priorities

  1. Weeks 1–2

    Diagnose

    Constraint map, baseline metrics, sequenced priorities

  2. Weeks 3–4

    Design

    Offer architecture, buyer journey, operating plan

  3. Weeks 5–8

    Install

    Conversion assets, content system, CRM stages, follow-up rules

  4. Weeks 9–12

    Compound

    Dashboard, experiment queue, documentation, handover

Stage by stage

What each stage delivers.

  1. Stage 1 · Week 0–2

    Audit

    Evidence review, interviews, journey mapping, response-time and CRM checks.

    Delivered: Leak map, measurement baseline, and decision brief.

  2. Stage 2 · Week 2

    Roadmap

    Sequence constraints by commercial impact, dependency, and effort.

    Delivered: Prioritised 90-day plan, scope, price, owners, and deliberate exclusions.

  3. Stage 3 · Weeks 3–10

    Build

    Install positioning, pages, proof, content system, CRM, automations, and operating tools in dependency order.

    Delivered: Working assets and workflows tested with the team, not a presentation about them.

  4. Stage 4 · Weeks 11–12 and ongoing

    Operate

    Train owners, monitor leading indicators, close gaps, and set the weekly operating rhythm.

    Delivered: Dashboard, documentation, ownership map, and next experiment queue.

What we need from you

Access and decisions, on time.

  • One accountable decision-maker, not a rotating approval group.
  • Access to current commercial numbers, site, CRM, content, and sales context.
  • A weekly working session and decisions within two working days.
  • Honest feedback from the people who will operate the system after handover.