Most companies start here
Growth.
Growth Partner runs one acquisition system for ninety days and produces the record: qualified pipeline or paid customers, in your CRM, with the source still on it.
Services
Growth runs the acquisition system and produces the record. AI integration puts a model to work inside one workflow. Tech integration and data keeps the records under it authoritative and in your account. Technical support keeps the named system true after launch. Each is scoped on its own, with what is excluded written down.
The four
One acquisition system: the customer definition, one channel, the offer, the creative, and measurement through to the CRM. Judged on qualified pipeline or paid customers, not on the ad account. Run as Growth Partner.
View serviceA model put to work inside one existing workflow. It answers from your records with the source attached, calls a short list of tools, and stops where a person has to decide. Built in accounts you own, with the tests that show when it is wrong.
View serviceThe records under the model. One home for each fact, an explicit corpus with explicit exclusions, an index that keeps the permission of the source and lives in your account, and a knowledge graph only when the question is about relationships.
View serviceAfter the system is in use, someone has to notice when the model changes, the index goes quiet, or a tool reaches further than it should. A retainer for the behavior of a named system, measured by its evaluation set and its data rule.
View serviceHow they fit
The technical services are not part of the Growth Partner definition. They are the tech that carries the system when the record, or a workflow that already costs time every week, calls for them.
Most companies start here
Growth Partner runs one acquisition system for ninety days and produces the record: qualified pipeline or paid customers, in your CRM, with the source still on it.
When a workflow is named
A written design first. Then one system, in your cloud and your source accounts, with an evaluation set that decides whether a change ships. The records under it are named, permissioned, and indexed in an account you own.
After launch
Care of the named system: the model vendor’s changes, retrieval quality, the index, permissions, tool behavior, access. Measured by the evaluation set and the data rule in its design.
Pricing
Every scope is written before work starts and lists what is excluded. If a request does not fit, we say so and point to who does it well.
Questions
If yours is not here, ask. We answer plainly, including when the answer is that this is not the right engagement.
No. Each service is scoped on its own. Most companies start with Growth Partner, because it produces the record. The technical services start with a written design, and a company can come to us for that alone.
Against the written design: the workflow, the systems it touches, and the evaluation set that decides whether it ships. Support is priced against the named system, the hours, and the response window. We do not print a number here until we have one we intend to keep.
The people you meet on the first call. There is no handoff to a delivery team, and no account manager between you and the person changing the bids or the instruction set.
Yes. We work in accounts in your name. For an ad account, its history is useful even if its campaigns were not. For a system we did not build, the first step is a formal acceptance against an evaluation set and a data rule, so the retainer has something to measure.
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.