The Growth Operating System

Find the constraint. Align the company. Build the fix.

The work begins with the customer journey, connects evidence across departments, and ends with accountable execution.

Most growth problems do not belong to one function.

A weak trial conversion rate may begin with an acquisition promise aimed at the wrong customer, continue through onboarding designed for a different level of expertise, and end with a sales handoff that arrives too early—or never arrives at all.

An NRR problem may reflect poor customer fit, product complexity, pricing, an undifferentiated service model, or a roadmap shaped around a small number of influential accounts.

That is why I do not begin with a departmental audit or a favorite playbook.

I begin by building one evidence-based view of the customer journey and identifying the constraint that best explains the pattern.

Four moves

01 · EXPERIENCE THE CUSTOMER JOURNEY

Leadership teams often know the journey through dashboards—not direct experience.

We examine the journey from the customer's perspective:

—What promise brought them in?
—What are they trying to accomplish?
—What must they understand before they can begin?
—Where do they encounter friction?
—When do they experience meaningful value?
—When would human help change the outcome?
—What causes them to expand, stall, or leave?

The goal is not performative empathy. It is a shared reference point for the decisions that follow.

02 · CONNECT THE EVIDENCE

I synthesize the evidence no single department owns.

—Customer interviews and Jobs-to-be-Done research
—Product usage and behavioral data
—Firmographic and segment performance
—Acquisition and conversion patterns
—Sales conversations, wins, losses, and objections
—Support interactions and recurring friction
—Onboarding, adoption, retention, and expansion
—Revenue, cost-to-serve, and customer economics
A coherent answer to three questions
—Which customers succeed?
—Why do others fail to realize value?
—What should the company do differently because of that evidence?
03 · MAP THE GROWTH CONSTRAINT

Specific enough to act on. Broad enough to explain the pattern.

A useful constraint is specific enough to act on and broad enough to explain the cross-functional pattern. Examples include:

—Acquisition is attracting customers whose jobs do not match the product's strongest value.
—The product requires too much expertise before customers reach a meaningful outcome.
—High-potential self-serve customers are not offered human help at the moment it would change conversion.
—Large-account feedback is dominating the roadmap and suppressing scalable innovation.
—Expensive human service is compensating for problems that should be addressed through product or AI.
—Leadership lacks a recurring process for converting customer evidence into priorities.

We prioritize the small number of constraints with the greatest effect on growth rather than producing a long list of disconnected ideas.

04 · BUILD AND TRANSFER

The diagnosis becomes a sequenced operating plan.

When I continue as a fractional leader, I work with the existing team in short execution cycles, inside the existing stack, with one accountable growth outcome and explicit measures.

The engagement is designed for transfer from day one. Decisions, experiment logic, operating rhythms, and ownership are documented so the organization can continue running the system without me.

AI

AI is a leverage decision, not a feature checklist.

The wrong question

Where can we use AI?

The useful question

Where can AI improve a measurable customer or business outcome without degrading trust, quality, or strategic learning?

ACCELERATE HUMANS

Help employees synthesize evidence, identify patterns, and make better decisions.

GUIDE CUSTOMERS

Help customers understand the product, complete difficult tasks, or reach value faster.

AUTOMATE OPERATIONS

Remove repetitive work where the process is stable, measurable, and suitable for automation.

CREATE NEW VALUE

Enable product outcomes or business models that were not previously practical.

Each opportunity is evaluated against customer value, business value, readiness, effort, risk, trust, and measurable return.

The diagnostic

What a diagnostic looks like.

Before kickoff
Read-only access to agreed data and systems
Existing strategy, ICP, research, and board materials
One internal point of contact
Executive and customer-facing interviews scheduled
Week 1 · Evidence and journey
Executive and functional interviews
Customer journey immersion
Funnel and instrumentation review
Customer, product, revenue, and service synthesis
Initial hypotheses and evidence gaps
Week 2 · Constraint and decisions
Segment and cohort analysis
Win, loss, churn, friction, and success-pattern synthesis
Growth constraint map
AI opportunity assessment
Executive working session
Prioritized 90-day roadmap with owners and measures
You do not need another list of ideas. You need to know which constraint matters most.

Discuss a diagnostic.

A first conversation is a practical working discussion, not a sales presentation.

Start a conversation