Own
The handoff. Your accounts, your data, your models, and your team running the loop on a rhythm it keeps without us. The engagement ends. The loop doesn't.
Wave 7
Own.
Own is the handoff wave, and it's the one that makes the other six worth paying for. Everything the method builds, the baseline instruments, the ground, the answer-layer position, the test discipline, the retention models, the routing policy, ends up in your hands: your accounts, your data, your contracts, your team running it. Not as a gesture at the end, but as a design constraint from the first day.
It gets a whole wave because ownership fails quietly and by default. The agency's login ends up on the ad account, the model retrains on the vendor's schedule in the vendor's cloud, the dashboard goes dark when the retainer does, and the content system turns out to live in one contractor's head. None of it is malicious. It's just what accumulates when nobody makes ownership someone's job, and then the engagement ends and the brand discovers it was renting its own growth machine.
We build the other way around, on purpose. The people who pitch you are the people who build, and what they build is made from kickoff to run without them. That isn't generosity, it's the honest shape of the deal: a consultancy you have to keep re-hiring to keep your own systems running isn't a partner.
The handoff isn't the end of the method. It's the seventh wave of it, and we design for it on day one.
Own versus the waves next to it
Own is the receiving end of every seam in the method. Each wave builds something, and this wave makes sure it's yours and stays alive.
| The wave built it | Own makes it yours |
|---|---|
| Truth: the baseline and its definitions | A page your team re-runs and keeps current |
| Ground: catalog, inventory truth, customer record | Named owners and cadences, inside your org |
| Found: the answer-layer position and content system | A cadence your team runs after the first cycle |
| Chosen: the test discipline | A rhythm your team keeps: frame, test, pick by the number |
| Grow: the flows and the models | Your platform, your data, your accounts |
| Deliver: the routing policy and the forecast | Levers ops changes without a ticket |
What good looks like.
Own ships five things, and together they answer the question a founder should ask any consultancy: what's left when you leave?
1. Everything in your name, from day one
Accounts, data, code, content, contracts: created in your name or transferred before the work starts, never parked with us for convenience, and that includes model weights and training data. The ownership audit should be boring and short. If listing what you'd keep after firing us takes longer than a coffee, ownership has already drifted.
2. A handoff designed at kickoff
Every workstream carries its handoff artifact from the start: the runbook written while the system gets built, the definitions filed back into the Truth page, the notes on why it's set up this way that save your next hire a month of archaeology. A handoff improvised in the last two weeks of an engagement is how knowledge evaporates. One accumulated across the whole engagement is how it compounds.
3. An operating rhythm your team keeps
The method leaves behind a cadence, not just systems: a weekly read of the numbers that reviews decisions rather than activity, what did we decide, what did it do, what's still open, plus the regular re-read of the baseline and a named owner and review cycle per domain. Rhythm is the part of an engagement that dies first after a handoff, so we treat it as a deliverable. Your team runs the meeting while we're still in the room, then keeps running it when we're not.
4. The right amount of platform
Stack decisions sized to your stage, with the incentive said out loud: we don't resell licenses and we don't earn more when the migration gets bigger, so we have no reason to sell you architecture. Most growth-stage brands do well with a solid engine and a flexible front rather than a full re-architecture, and recommending less than you expected to buy is how you end up owning a stack your team can actually operate.
5. What stays with us, if you want it
Some brands keep us around for the calls that matter: the baseline re-read, the pricing decision, the replatform question, the "is this tool real" gut check. That's advisory, and it's the right shape for the relationship after a handoff, partner-level judgment on demand, sitting on top of a machine your team runs. The wrong shape is us operating your systems forever, and we'll say so if an engagement starts drifting that way, because it means wave seven didn't finish.
How it runs, on us. This wave is also why our own house runs the way it does. Our engagement margins are visible while the work is happening, not reconstructed at year-end, which is what lets us plan the next engagement on real numbers instead of instinct. And every client artifact lives in client-owned accounts from the first week, because we've sat on the brand side of the table when it wasn't done that way, and we remember exactly how that felt.
The threads, in this wave.
Woven in.
The models keep learning after we step back, on your data, in your accounts, on a retraining schedule that's written down and owned. A model that quietly goes stale is this wave's version of the dead dashboard, so the handoff includes the instructions for keeping the machine smart, not just keeping it on.
Your team.
This whole wave is the thread at full size. The measure of the method isn't what we built, it's what your team runs a year later without calling us. When the lifecycle lead owns the churn score, the ops lead edits the routing policy, and the founder reads the baseline page in the Monday meeting, the method did what it said it would.
The coda.
The engagement ends. The loop doesn't. Your team runs the machine, and it keeps compounding after we're gone.
Let's talk.
Tell us where you're trying to grow. We'll tell you the truth about how to get there.