Our process
Every engagement here runs the same way. Nothing is spent or shipped before it is defined in writing and tested end to end. Work ships weekly and is written down. The monthly meeting is where the record becomes a decision. This page is the sequence: the shape every engagement shares, then the ninety days of Growth Partner week by week, then the three parts of a technical engagement.
The shape
Written before anything is built or spent.
For the growth engagement, one working session produces the customer definition, who you turn away, what a customer is worth, and the two definitions the ninety days run on. For a technical engagement, a written design names the workflow, the systems of record, the corpus, the tools and their side effects, where each class of data sits, which model product is called, and the evaluation set that decides whether a change ships.
Tested before it is live.
Tracking from the click to the CRM, with one test lead from a phone traced end to end before spend. The campaign page is written for the offer as a task inside this step. For a build: instructions versioned, tools allow-listed, the evaluation set run against real questions with known answers. If the test lead cannot be traced, or the set does not pass, launch waits.
Shipped and written down, weekly.
One experiment a week with a decision rule written before the test. Leads read against the definitions, the wrong ones cut, budget moved toward what produces pipeline. For a system in production: the evaluation set rerun on every change to the model, the instructions, or the corpus, and a failed set blocks the change.
Monthly, on the record.
A report finance can read: platform count beside CRM count, cost per qualified lead with the fee inside it, what was cut and why, speed to lead. Then a working session. At day ninety, one question: did the channel work at a cost that works for this company? Continue, add a channel, change, or stop.
Growth Partner, week by week
One working session: what you sell, who buys it, who you turn away, and what a customer is worth. From that we write the definitions the engagement runs on: a qualified lead or qualified signup, opportunity or pipeline, activation, first paid action. Every number after this is counted against them, unchanged, for ninety days.
In the same week we collect access: the ad accounts, or permission to open them in your name; analytics; the CRM; the repo or CMS for the campaign page; and the calendar a demo lands on.
You do
You get
Definitions first, then instrumentation: events, URL parameters, the source field in the CRM, and one test lead from a phone traced end to end. A written note of what the ad platform counts, including view-through, so the dashboard can be read for what it is. The campaign page is a task in this step: written for the offer, instrumented, ready to be changed when an experiment calls for it. The account is structured by audience and offer, with exclusions built from who you do not want.
Nothing is live yet. If a test lead cannot be traced end to end, launch waits.
You do
You get
Campaigns go live. Early numbers move around and we treat them that way. The first weeks are for finding the audiences and terms that bring the wrong people and cutting them, not for scaling. Every lead is read and tagged against the definitions.
The first experiments ship, one at a time, each with its decision rule written first. You get a short written note each week: what came in, what qualified, what we shipped, what we cut.
You do
You get
With enough leads behind it, cost per qualified lead stops swinging and can be set against what a customer is worth to you. Creative, the offer, and the page are tested against the leads they produce, not against click rates. Budget moves toward the audiences and offers that create pipeline.
The first full monthly report and working session fall here: the platform’s count beside the CRM’s, the fee inside the cost, and one question about why the last losses did not buy. Decisions from the meeting are written down and become next month’s plan.
You do
You get
By day ninety there have been live campaigns, a dozen shipped experiments, three reports, and more than one review. The meeting answers one question: did the channel produce qualified pipeline or paid customers at a cost that works for this company?
If yes, we talk about what to press and whether a second channel is earned. If no, we say so, and stopping is one of the options on the table. There is no claim that ninety days fills a pipeline. There is a record of what the channel did.
You do
You get
A technical engagement
The same shape, for a system instead of a channel. The site describes the shape and leaves commercial terms to the conversation.
First
Before anything is built. It names the workflow, the systems of record, the corpus, the tools and their side effects, where each class of data sits, which model product is called, what that product retains, and the evaluation set that will decide whether a change ships.
Then
In your cloud and your source accounts. Instructions are versioned. Tools are allow-listed. The evaluation set runs against real questions with known answers. A short operating note tells your people what the system will do and who to tell when it is wrong.
After launch
A new workflow is new work: specified, designed, and accepted on its own. It is not absorbed into the retainer. You own the system at the end of the build: the account, the index, the instructions, the evaluation set, and the runbook.
The rhythm
The engagement runs on a fixed cadence so you always know when you will hear from us and what it will contain.
Every weekday
Spend, audiences, search terms, new leads, and the tracking checks. A change that cannot wait is made the same day and noted.
Every week
A test ships. A short note says what came in, what qualified, what changed, what is next. No meeting unless something needs one.
Every month
Platform count beside CRM count, cost per qualified lead with the fee inside it, what was cut, what is next. One working session on the work.
How we decide
No campaign goes live until a test lead has been traced from the ad to the CRM with its source intact. If the first week cannot be reconstructed, it did not happen.
A result that exists only inside the ad account does not count. The account is judged by qualified pipeline or paid customers, and nothing else gets the headline.
A second channel is earned by the first one producing qualified leads at a cost you can live with. Spreading a small budget across three platforms produces three sets of noise.
Kill if cost per qualified lead is above this after this many leads. One change at a time. The decision is made against the rule, not the mood.
Each monthly meeting ends with continue, change, or stop. We would rather say the channel is not working than spend another month proving it.
Ad accounts, analytics, CRM, the page, the domain, the record. If the engagement ends, nothing moves and nothing is held back.
What we need from you
Before we start
While it runs
Questions
If yours is not here, ask. We answer plainly, including when the answer is that this is not the right engagement.
One working session in week one, a short reply on each lead’s outcome, one meeting a month, and reading a weekly note. Founders who give us the lead outcomes get a better account; it is the one input we cannot produce ourselves.
If tracking already works end to end and there is a usable page, yes. We will not launch on a page we have not tested from a phone or into a CRM that drops the source.
A short written note: what came in, what qualified, what we shipped, what we cut and why, and what is next. Reply if you want to talk. There is no weekly meeting unless something needs one.
Then pipeline, not closed revenue, is the ninety-day number, and we say so up front. Qualified leads and opportunities created are readable inside the term; revenue follows on your cycle.
Yes. The written design is the definition. The build is tested against an evaluation set before it is live, the way a test lead is traced before spend. The retainer is the cadence after launch. A new workflow is a new design, not an addition to the retainer.
Yes. We own the channel and the record; they own the rest. Clear lines, written in the brief. If they are better at something than we are, we say so.
Tell us what you sell and who buys it. We answer with a time to talk, or with a straight reason this is not the right engagement yet.