Iteration, Growth & Scaling

Iteration, Growth & Scaling

Once customers start using your product, the quality of the evidence changes completely. Before launch, you were working with research, prototypes, assumptions and forecasts. After launch, you can see what customers actually do: where they arrive, whether they activate, how quickly they reach value, which workflows they adopt, where they drop off, what brings them back, which segments stay, and whether the behaviours you expected to create value are really happening.

That should change how the roadmap is built. The next phase is not about shipping more features as fast as possible. It is about understanding what is driving growth, where the product is leaking value, and which bets deserve the next round of investment.

If you are a founder, CEO or CPO with a live product, this is usually the point where the pressure peaks. Investors want to see traction. Sales, support, big customers and your own instincts all want something different built next. And without a senior product and data team, it is very hard to tell which of those signals deserve your engineering budget.

Iteration, Growth & Scaling is how we help you answer that. We combine product analytics, customer behaviour and customer feedback into one growth system, find the single constraint holding the product back, test the changes most likely to move it, and prepare the product, technology and economics for growth that compounds rather than breaks.

Three ways teams try to grow after launch

Build what people ask for

Once a product is live, requests arrive from every direction. Sales wants something for a prospect. Support hears the same complaint several times. A large account asks for a new workflow. A competitor launches something. The founder has another idea. Each signal matters, but if every request becomes a feature, the product grows wider without growing stronger. Every feature adds interface complexity, code to maintain, edge cases and surface area for future teams to support.

Buy more traffic

The second instinct is to add acquisition: more ads, more outbound, more content, more partnerships. Sometimes that is exactly what the business needs. Often it simply pours more customers into a funnel that is already leaking. If customers are not activating or not staying, more traffic makes the numbers bigger and the economics worse.

Run growth as an evidence system

We chose a third path. We treat the product and the funnel around it as one connected system, find the one constraint that is limiting growth right now, turn every roadmap item into a testable bet, test it in the cheapest credible way, and invest only behind what the evidence supports. Then we repeat the loop, continuously.

It asks more discipline of everyone, including us. But it is the only approach we know of that turns early traction into growth that compounds, instead of growth that has to be bought every month.

Is this for you?

You arrive with a live product, real customers, analytics and early product behaviour. You leave with a clear view of product performance, prioritised growth opportunities, tested hypotheses, stronger activation and retention, better unit economics, and a roadmap for scaling.

The job it does: "When my product is live but I need to understand what is driving or limiting growth, help me combine product analytics, customer behaviour and user feedback into better product decisions, so we can strengthen product-market fit and scale with evidence."

You are likely a good fit if you are:

It is not the right fit if the product has not launched, has too little usage data, or the core customer and problem are still unclear. It is also not for teams that want feature development only, have a fixed backlog that cannot be questioned, cannot give us access to users or feedback, have no analytics and are unwilling to add them, or refuse to test assumptions.

Not launched yet? Start with MVP Build & Launch. Opportunity still unclear? Start with Product Ideation & Discovery.

The growth system and the six-stage framework

Everything we do in this phase is organised around one connected growth system:

Acquisition → Activation → Engagement → Retention → Revenue → Referral / Expansion

It is supported underneath by customer satisfaction, revenue quality, unit economics and product reliability. If one part weakens, the rest eventually feels it. The goal is not to maximise every metric on its own. It is to find the current constraint and improve the system as a whole.

Once a product is live, there are eight uncertainties this work is designed to reduce:

To answer them, we run a six-stage loop: Measure → Diagnose → Hypothesise → Experiment → Optimise → Scale, and then repeat. Unlike Discovery or MVP, this is not a one-off project. Every cycle starts from better evidence than the last.


Stage

The question it answers

The methods we use

What you get

1. Measure

What is happening across the product and growth funnel?

Analytics audit, product funnel mapping, metrics library, PMF scorecard

A trustworthy view of what customers actually do

2. Diagnose

What is currently holding the product back?

Funnel diagnosis, cohort and segment analysis, behaviour analysis, AI-assisted feedback synthesis

Growth Constraint Analysis, PMF Gap Analysis, Prioritised Problem List

3. Hypothesise

What do we believe could materially improve the product?

Hypothesis format, opportunity scoring, the roadmap rule

Product Hypothesis Pipeline, Growth Roadmap

4. Experiment

What is the cheapest credible way to test this?

Experiment briefs, guardrail metrics, decision rules

Experiment results with a clear Scale / Iterate / Test Again / Stop call

5. Optimise

Where should product and engineering investment go now?

Activation, retention, monetisation, satisfaction, referral and reliability work

Shipped improvements and an updated Growth Scorecard

6. Scale

Can this system keep working if growth accelerates materially?

Product, technical, operational, economic and distribution scaling; 12 PMF quality gates

Scaling plan and Hyperscale Readiness Scorecard

Stage 1 - Measure

What is happening across the product and growth funnel?

Before we optimise anything, we confirm the data can be trusted. Many teams find their analytics are incomplete, inconsistent or measuring the wrong things, and every decision built on them inherits the problem.

The methods we use

Metric family

The question it answers

Examples of what we track

Acquisition

Are the right customers coming in?

Qualified traffic, visitor-to-sign-up conversion, customer acquisition cost (CAC), cost per lead, acquisition by channel, organic vs paid, win rate, sales cycle

Activation

How many customers reach real value, and how quickly?

Sign-up and onboarding completion, activation rate, time to first value, drop-off by onboarding step, activation by segment and channel

Engagement

Is the product becoming part of how customers work?

DAU, WAU, MAU, DAU/MAU, WAU/MAU, core actions per customer, feature adoption, depth of usage, users per account

Retention

Do customers keep coming back?

Day 1, 7 and 30 retention, cohort retention, logo retention, voluntary and involuntary churn, retention by segment, channel and activation behaviour

Revenue & monetisation

Is customer value turning into business value?

MRR, ARR, ARPU, ARPA, contract value, free-to-paid and trial-to-paid conversion, upgrades, downgrades, expansion, GRR, NRR, gross margin, LTV, LTV:CAC, CAC payback

Revenue quality

Is the revenue durable?

Refund rate, cancellation rate, downgrades, failed payments, chargebacks and disputes, refund and cancellation reasons

Customer satisfaction

How do customers feel about the experience?

NPS, CSAT, support contact rate, response and resolution time, tickets per 100 active customers, reviews, sentiment

Referral & expansion

Is growth starting to compound?

Invite and referral rates, invited-user activation, seats added, account expansion, organic sign-ups, product-generated leads, upsell and cross-sell

The terms that matter most, in plain words

Why it matters to you: every growth decision, and every investor conversation about traction, rests on these numbers. If they are wrong or incomplete, you are steering blind. If they are right, you can show exactly where the business is strong and where it is not.

Stage 2 - Diagnose

What is currently holding the product back?

When companies want to grow faster, the instinct is to add acquisition. Sometimes that is right. Often it just puts more customers into a funnel that is already leaking. The most important question is usually where the constraint sits, and the rule is simple: do not optimise everything at once. Find the constraint.

At different stages, the constraint might be traffic quality, acquisition, sign-up conversion, onboarding, activation, time to value, engagement, retention, pricing, monetisation, refunds, cancellations, expansion, referral, reliability, customer support, infrastructure or distribution.

The methods we use

What you get

Why it matters to you: the highest-leverage decision is usually the one that fixes the current constraint, not the most visible opportunity. Finding it can be worth more than a whole quarter of feature development.

Stage 3 - Hypothesise

What do we believe could materially improve the product?

A roadmap should be a set of bets, not a collection of requests. The question is not "what are customers asking us to build?" but "what do we believe will improve the product, what evidence supports that belief, and how will we know if we were right?"

The methods we use

What you get

Why it matters to you: this is how you say no, or "not yet", to a large customer, your sales team or your own instincts, with a reason everyone can accept. It also gives your board a roadmap tied to measurable outcomes instead of a list of features.

Stage 4 - Experiment

What is the cheapest credible way to test this hypothesis?

Experiments should answer questions, not create activity. Not every idea needs an elaborate A/B test. Sometimes five customer interviews are enough to disprove an assumption before any engineering begins. Sometimes a prototype is enough, or a landing page can test demand, or a manual process can stand in for a feature before automation is justified. The method should fit the question.

The methods we use

What you get: a running experimentation system, typically 2–5 meaningful hypotheses tested every month, each with a written brief, results, and a clear decision.

Why it matters to you: experiments let you learn before committing serious design and engineering effort. Every "stop" is money you did not spend building the wrong thing; every "scale" is an investment backed by evidence.

Stage 5 - Optimise

Where should product and engineering investment go now?

This is where the evidence turns into shipped product. We do not just recommend changes; our designers and engineers implement the ones the evidence supports.

The methods we use

What you get

Why it matters to you: you get one team that diagnoses, decides and delivers, so insight does not get lost in a hand-off between a strategy consultant and a development shop.

Stage 6 - Scale

Can this system keep working if growth accelerates materially?

Scaling is different from growing. Growth asks whether you can create more customer and business value. Scaling asks whether the product, technology, team and economics can keep doing that at a much larger level. A product that works for 500 customers may not work for 50,000. Manual processes break, support volume changes, infrastructure costs behave differently, database decisions that made sense at MVP stage become constraints, permissions get complex, security expectations rise, enterprise customers bring new requirements, and compliance can expand with every new market.

The challenge is timing. Scale too early and you waste money and slow product development. Scale too late and reliability breaks exactly when growth starts accelerating. The right time is when the evidence shows a constraint becoming material.

The methods we use

What you get

Why it matters to you: the bigger questions arrive here. Should you move upmarket? Introduce self-serve? Expand into a new country? Build an API? Change pricing? Rework the infrastructure now? The quality of those decisions decides whether early traction becomes durable growth. Scale should amplify what already works, not what is already broken.

The numbers we steer by

The right numbers depend on your product, business model, price point, customer segment and sales motion. The targets below are aggressive internal operating targets, not universal benchmarks and not guarantees. We calibrate them for every client.

What aggressive success can look like

Area

Metric

Aggressive target

Acquisition

Visitor → sign-up

8–15%+

Activation

Sign-up → activation

60–80%+

Onboarding

Completion

75–90%+

Value

Time to first value

As close to immediate as the product allows

Core usage

Core action completion

70%+

Engagement

DAU / MAU

20–40%+ where daily use matters

Engagement

WAU / MAU

50–70%+ where weekly use matters

Retention

Day 7

35–50%+ for high-frequency products

Retention

Day 30

25–40%+ for high-frequency products

Churn

Monthly logo churn

Below 2–3%

Revenue

Gross revenue retention (GRR)

90–95%+

Revenue

Net revenue retention (NRR)

110–130%+

Monetisation

Trial → paid

20–40%+

Economics

LTV:CAC

3:1 minimum, 4:1+ strong

Economics

CAC payback

Under 12 months

Revenue quality

Refund rate

Below 2%, ideally below 1%

Advocacy

NPS

50+

Satisfaction

CSAT

85–90%+ satisfied

Distribution

Organic / referral share

20–30%+ as the product matures

Learning

Hypotheses tested

2–5 meaningful tests a month

When a major funnel constraint is addressed, we look for a 10–20% relative uplift where realistic. For example, activation moving from 40% to 48% is a 20% relative uplift.

The point is not to chase every number at once. It is to find the metric currently limiting the system, and move it far enough to change the economics of the business.

How we read refunds and NPS

Refund rate, as an internal watchlist: below 1% is very strong; 1–2% is healthy; 2–3% means monitor closely; above 3% we investigate immediately; above 5% signals a material product, positioning, billing or customer-quality problem. The pattern underneath matters more than the headline. A rising dispute or chargeback rate is a product and customer-experience signal, not just a finance issue.

NPS, as a practical guide: below 0 is a serious customer-experience problem; 0–30 is weak to moderate; 30–50 is healthy; 50+ is strong advocacy; 70+ is exceptional. We segment NPS by customer type, plan, tenure, geography, channel, activated versus non-activated, retained versus churned, and power versus light users, because the overall number often hides where advocacy really sits.

The traffic-light model

To make the numbers actionable, we rate the key metrics green, amber or red, calibrated per client:


Metric

Green

Amber

Red

Activation

60%+

40–59%

Below 40%

Monthly logo churn

Below 2%

2–4%

Above 4%

NPS

50+

20–49

Below 20

Refund rate

Below 1%

1–3%

Above 3%

LTV:CAC

3:1+

2:1 to 3:1

Below 2:1

Green means healthy enough to keep investing. Amber means improvement is needed before aggressive scaling. Red means a likely constraint or a material risk.

Earning the right to scale

Hyperscale is not just a technical architecture problem, and it should never be judged on revenue alone. Strong activation, durable retention, low refunds, high customer advocacy, healthy unit economics, efficient acquisition and expansion all need to reinforce one another before aggressive scaling makes sense. Scale before that point simply magnifies whatever is already broken.

The 12 product-market-fit quality gates

Before we recommend aggressive scale, the product must pass all twelve:

  1. Acquisition: can you repeatedly acquire the right customers?

  2. Activation: do enough customers reach value?

  3. Retention: do enough continue receiving value?

  4. Customer segment: is there a clear ideal customer where performance is strongest?

  5. Satisfaction: are NPS, CSAT, support and feedback consistent with a healthy product?

  6. Revenue quality: are refunds, cancellations, chargebacks and downgrades low enough?

  7. Monetisation: does customer value convert into economic value?

  8. Unit economics: are CAC, LTV, margin and payback healthy?

  9. Expansion: do retained customers generate additional value?

  10. Product quality: can the product handle much greater usage reliably?

  11. Operations: can the organisation support many more customers?

  12. Infrastructure: can the technology support substantially more demand?

What a hyperscale-ready business looks like

When the fundamentals start reinforcing each other, the picture looks something like this: 60–80%+ activation where realistic, fast time to value, durable cohort retention, a low refund rate, strong NPS, healthy GRR, 110%+ NRR where expansion exists, LTV:CAC of 3:1 or better, acceptable CAC payback, growing organic and referral acquisition, strong reliability, scalable operations and healthy margins.

At that point, the conversation changes. The question is no longer "does the product work?" It becomes: how aggressively can we invest in distribution, product, infrastructure and team without breaking the economics that made the product work in the first place? That is the transition from finding product-market fit to building a system capable of hyperscale growth.

How we work

A fixed operating rhythm

Growth work needs a cadence, not occasional bursts. Every engagement runs on the same rhythm:


Cadence

What happens

Weekly

Metric review, customer evidence review, experiment review, roadmap decisions, product and engineering prioritisation

Every two weeks

Experiments launched, product improvements released, funnel review, cohort review

Monthly

Activation, retention, NPS, refund rate, revenue, GRR and NRR, CAC and LTV, hypotheses tested, scaling risks

Quarterly

Product strategy, ideal-customer review, pricing, expansion, distribution, technical scaling, operating model, growth investment allocation

The team

Role

What they own

Growth Product Lead

The growth system, constraint diagnosis, the hypothesis pipeline and the roadmap

Product / Data Analyst

Analytics audit, funnels, cohorts, segments, experiment measurement

Product Designer

Onboarding, activation and retention experiences, prototypes and usability testing

Technical Lead

Engineering decisions, reliability and technical scaling

Software Engineers

Shipping the improvements the evidence supports

Specialists, when needed

Growth engineer, data engineer, AI engineer, UX researcher, lifecycle/CRM specialist, performance marketer, DevOps or platform engineer

Scope control

Every engagement defines up front the product area, metrics, funnels, customer segments, analytics sources, platforms, experiments per month, design, engineering and research capacity, growth channels and scaling work. The one brief we never accept is "optimise everything".

What you leave with: the Growth & Scaling Blueprint

A strong engagement should leave you with more than a bigger backlog. Everything comes together in one master document, the Growth & Scaling Blueprint, which connects every stage of continuous work.


#

Section

What it tells you

01

Executive Growth Assessment

Where the business stands and what matters most, on one page

02

Product Performance

What customers actually do inside the product

03

Growth Funnel

Where value is created and where it leaks

04

Acquisition

Whether the right customers are coming in, and at what cost

05

Activation

How many customers reach value, and how fast

06

Engagement

Whether the product is becoming part of customers' routines

07

Retention

Who stays, who leaves, and why

08

Revenue

How customer value is turning into business value

09

Refunds & Cancellations

Whether revenue is durable

10

NPS & Customer Satisfaction

How customers feel, by segment

11

Referral & Expansion

Where growth is starting to compound

12

Cohort Analysis

Whether the product is getting better over time

13

Segment Analysis

Where product-market fit is strongest

14

Product-Market-Fit Assessment

How close you are, measured across the whole system

15

Growth Constraints

The single biggest thing holding growth back

16

Customer Evidence

What customers are telling you, synthesised

17

Product Hypothesis Pipeline

Every opportunity, written as a testable bet

18

Experiment Results

What was tested, what was learned, what was decided

19

Growth Roadmap

What to build next, and why

20

Activation Strategy

How more customers will reach value faster

21

Retention Strategy

How more customers will keep coming back

22

Monetisation Strategy

How value converts into revenue

23

Growth Loops

How usage creates more growth

24

Technical Scaling Plan

What the technology needs as you grow

25

Operational Scaling Plan

What the organisation needs as you grow

26

Unit Economics

Whether growth is profitable to buy

27

Hyperscale Readiness

How you score against the 12 quality gates

28

Next Investment Priorities

Where the next dollar should go

By the end, you have a clear view of product performance, a fully instrumented funnel, a defined activation event, cohort and retention analysis, engagement metrics, NPS and CSAT visibility, refund and churn analysis, deeper customer insight, a prioritised hypothesis pipeline, a working experimentation system, improved activation, retention and monetisation, stronger revenue quality and expansion, a product-market-fit measurement system, an evidence-based roadmap, and a technical and operational scaling plan with clear hyperscale-readiness criteria.

Three ways to work with us

All three packages use the same six-stage loop. What changes is how much of it we run, and for how long.


Growth Diagnostic

Product Growth Sprint

Growth & Scaling Partnership

Length

5–7 days

4–6 weeks

3–12+ months, ongoing

Best for

Teams that know growth is constrained but do not know where

Teams ready to diagnose, test and ship improvements in one focused push

Funded startups moving from product-market fit toward scale

Measure

Full

Full

Continuous

Diagnose

Full

Full

Continuous

Hypothesise

Prioritised

Full

Continuous

Experiment

Recommended

Executed

Continuous

Optimise

Roadmap

Executed

Continuous

Scale

Assessment

Where relevant

Full

Includes

Analytics audit, funnel review, activation, retention, cohorts, NPS, refunds and cancellations, customer feedback, growth constraints, prioritised hypotheses

Everything in the Diagnostic, plus customer research, experiments, activation, retention and monetisation work, refund and churn reduction, product iteration, engineering support and a scaling assessment

Continuous analytics and experimentation, AI-assisted feedback synthesis, roadmap leadership, engineering delivery, technical and operational scaling, growth planning and quarterly strategy

You receive

A Growth Diagnostic and a 90-day roadmap

Measured improvement plus the Blueprint

A continuous growth operating system

Our flagship is the Product Growth Sprint.

How we price

You are buying better growth decisions and measurable product improvement, not developer hours.

Our guarantee. We will never promise "we will achieve hyperscale" or "we will increase retention by 30%". We promise that you will have a measurable growth system connecting product analytics, customer evidence, experimentation, roadmap decisions and scaling priorities.

What is not included

Unless explicitly scoped: paid media management, full marketing execution, sales team management, full customer-success operations, PR, 24/7 support, unlimited engineering, enterprise-wide replatforming, large-scale data migration, legal or compliance advice, and a full brand redesign.

The roadmap gets better as the evidence gets better

Your first roadmap is usually built from what the team believes. A mature roadmap should increasingly be built from what the company has learned.

That does not mean product strategy becomes a spreadsheet. Data cannot tell you what future to create. Customers cannot design the product for you. Experiments cannot replace conviction. The best product decisions still require judgement, but judgement becomes far more valuable when it is informed by real customer behaviour, strong qualitative insight, revenue quality, customer satisfaction and a clear sense of what the company is trying to become.

Underneath everything we do in this phase sit six questions, asked again and again: Where is the constraint? Why is it happening? Which customers are affected? What hypothesis explains it? What should we test? How will we know if it worked?

That is the loop that takes a product from its first release toward product-market fit. And once the fundamentals are strong enough, it is the same loop that carries a company toward hyperscale growth, without losing sight of the customer value that created the opportunity in the first place.

The objective is not an endless stream of features, dashboards for their own sake, or growth at any cost. It is a product that becomes more valuable, more loved, more efficient and more capable of compounding as it grows.

View All

FAQS

Common Questions
Answered

We’ve answered some of the most common questions we receive from founders and product teams. If you don’t see your question here, feel free to contact us for personalized assistance.

01

Working with us

Who do you typically work with?

We work with founders, product leaders, and technology teams building new products, improving existing ones, or solving complex product and engineering challenges.

When should we work with you?

We can join from early discovery through MVP delivery, growth, scaling, or enterprise engineering, depending on what has already been validated and what needs to happen next.

02

Services

What services do you offer?

We cover Product Ideation & Discovery, MVP Build & Launch, Iteration, Growth & Scaling, and Enterprise Engineering across the full product lifecycle.

Can you work on existing products?

Yes. We can improve product performance, build new capabilities, solve technical constraints, modernise systems, or add specialist engineering capacity to your existing team.

03

Technology

What technologies do you work with?

We work across web, mobile, AI, cloud, data, and infrastructure, including React, Next.js, React Native, Node.js, Python, AWS, Vercel, OpenAI, Anthropic, Terraform, Stripe, and more.

How do you use AI in development?

We use AI to accelerate research, design, development, testing, and delivery, with senior engineers and designers responsible for architecture, security, user experience, and production decisions.

04

Pricing & engagement

How much does a project cost?

Pricing depends on scope, complexity, team requirements, and product stage. We define the work and expected outcomes before recommending the right engagement model.

Engagement models we offer

We offer fixed-scope projects, focused product and engineering sprints, and longer-term partnerships depending on the work, timeline, and level of support required.

05

Process & timeline

What does your process look like?

We start with the problem, customer, business objective, and technical context, then define scope, milestones, success metrics, delivery plan, and the team required.

How long does a project take?

Discovery can take days, focused product sprints can take weeks, and larger engineering or scaling engagements can run for several months

06

Collaboration & security

How do we work together?

We run regular development and stakeholder reviews with real-time communication so priorities, progress, risks, and decisions remain visible throughout the project.

How do you handle security?

We consider security from the start, including access, infrastructure, data handling, integrations, and AI usage based on the requirements and risk profile of the product.

Let’s Talk.

Tell us what you’re building

Engineering & AI

From SaaS and mobile products to AI, cloud, data, and enterprise systems, we bring the technical capability needed to build and scale.

Product strategy & delivery

From discovery and MVP build to growth and scaling, we help you define the right product direction and move it into execution.

READY TO BUILD?

Tell us about your idea and we’ll get back to you shortly.