Question 1

What does a growth operator actually do?

Accepted Answer

A growth operator builds the systems your growth runs on and then keeps running them. Growth operations is the practice of treating marketing as infrastructure rather than as projects: your website, SEO, email, content, ads and outbound each become a system with an owner, a budget and monitoring, instead of a task that gets done when someone has time. The distinction from a consultant is that an operator is measured on whether the thing runs, not on whether the advice was good.

Question 2

How fast do we see results?

Accepted Answer

The first system is live within seven days of a signed brief, and what it returns depends entirely on which one you start with. Email and outbound usually show a number inside the first month because the audience already exists. SEO and content are slower by nature — expect movement in a quarter, not a fortnight. The Diagnose phase tells you which of these is the fastest lever for your business before you commit to any of it.

Question 3

Who is this for?

Accepted Answer

Founders doing roughly $500K to $5M whose marketing is scattered across freelancers, a VA and their own evenings. Big enough that the work genuinely needs an owner, too small to justify hiring a growth team. If you have an in-house marketing function already, you probably want a contractor for a specific gap rather than an operator.

Question 4

How is this different from hiring an agency?

Accepted Answer

An agency gives you a roster; this gives you one person who owns the outcome. With an agency the work is split across specialists who each own a slice, none of whom owns whether it worked, which is why you end up project-managing them. Here the person who builds your systems is the person who runs them, and there is nobody to hand the problem to.

Question 5

How is this different from a fractional CMO?

Accepted Answer

A fractional CMO decides what should happen; an operator makes it happen. A CMO brings strategy, hiring plans and oversight, and still needs people underneath them to execute. If your problem is that you do not know what to do, hire the CMO. If your problem is that you know exactly what to do and none of it is getting done, that is this.

Question 6

Why not just hire someone in-house?

Accepted Answer

Eventually you should, and we are built to be replaced. A capable in-house growth hire costs more than this once you count recruitment, salary, tooling and the months before they are productive — and at your size you would be hiring one generalist to cover six disciplines. When the volume justifies a full-time team, everything we built goes with you.

Question 7

What if I only need one thing done?

Accepted Answer

That is the normal starting point — everyone begins with a single operation. The Diagnose phase decides which one, and you are not committed to the other five. Expansion only comes up once the first system is demonstrably paying for itself, and it is a conversation rather than an automatic upgrade.

Question 8

What happens if it breaks?

Accepted Answer

It pages us, not you. Every operation ships with monitoring and alerting wired up before it goes live, and a failure falls back to a safe state — paused, queued, or routed to a human — rather than doing something irreversible or expensive. You get a written account of what broke and what changed in that week's pulse.

Question 9

How do you keep spend under control?

Accepted Answer

The ceiling is set by you and enforced in code. It is not a policy document or a calendar reminder to check the dashboard — the system stops when it hits the number. This applies to ad spend and to the cost of running the automation itself.

Question 10

How much of my time does this take?

Accepted Answer

Roughly two weeks of real involvement at Diagnose, then very little. After that it is a written pulse each week that you can read in two minutes and a monthly review call. The entire point is to stop growth being something that needs your evenings.

Question 11

Who owns the systems you build?

Accepted Answer

You do, outright. Every account is in your name — ad platforms, email, analytics, hosting, domains — and the code lives in your repository. There is no per-seat licence, no proprietary runtime, and nothing that stops working if you stop paying us. If you want to take all of it in-house on day eight, it is yours to take.

Question 12

What happens if we stop working together?

Accepted Answer

The systems keep running and you keep everything. Documentation and runbooks are part of the deliverable rather than an exit negotiation, specifically so that leaving is not a project. Nothing is structured to make it difficult.

Question 13

Where does our data live?

Accepted Answer

In your accounts, not ours. We build inside your infrastructure by default and document exactly what leaves the boundary where a third-party service is involved.

	OPERATIONS REVIEW	FIRST SYSTEM	OPERATE
Funnel teardown	Included	—	—
Operations built	—	1	Ongoing
Live in 7 days	—	Included	Included
Spend ceiling in code	—	Included	Included
Weekly written pulse	—	—	Included
On the pager	—	—	Included
You own every account	Yours	Yours	Yours

	OPERATIONS REVIEW	FIRST SYSTEM	OPERATE
Funnel teardown	Included	—	—
Operations built	—	1	Ongoing
Live in 7 days	—	Included	Included
Spend ceiling in code	—	Included	Included
Weekly written pulse	—	—	Included
On the pager	—	—	Included
You own every account	Yours	Yours	Yours

Published, so you don’t have to book a call to find out.

Compare

Questions we get before the first call.

Still deciding which slice to start with?

Published, so you don’t have to book a call to find out.

Compare

Questions we get before the first call.

Still deciding which slice to start with?