Method
Four stages. No surprises.
We work in an explicit order. Every stage ends with a deliverable you can read, argue with and use, even if you decide to stop there.
- 01
Find the signal
Before proposing anything, we look for where growth is leaking. It is rarely where it hurts most; it is where the journey breaks.
- Interviews with leadership and with whoever sells
- Review of data, campaigns, website and CRM
- Market, competition and real objection analysis
- A read of the full journey, from first impression to close
Deliverable
Diagnosis document with findings, priorities and proposed decisions.
- 02
Design the path
We turn the diagnosis into a plan with order, owners and success criteria. What stays out of the plan gets written down too.
- Positioning, offer and message system
- Channel selection by function, not by habit
- Metric definitions and the decision each one changes
- 90-day plan with sequence and dependencies
Deliverable
Prioritized path with scope, timeline and associated budget.
- 03
Activate the system
We build and connect. Nothing ships without instrumentation: if it cannot be read, it cannot be corrected.
- Website, landing pages and content
- Campaigns, creative and account structure
- CRM, routing, automations and alerts
- Events, dashboards and data quality control
Deliverable
A system in production, documented, with access handed over.
- 04
Learn and expand
A review cycle with recorded decisions. What shows signal gets scaled; what does not gets retired, with the same ease.
- Recurring review against business metrics
- Experiments with a hypothesis and a closing criterion
- Budget reallocation
- Documented, accumulated learnings
Deliverable
Decision log and the next prioritized cycle.
Working rhythm
One review meeting with an agenda and written decisions. Asynchronous communication the rest of the time, so the project does not depend on matching calendars.
If something is not working, you say it or we say it at the next review. Not next quarter.
Questions about the method
Do we have to start with the diagnosis?
We recommend it almost always, because it avoids building on a wrong assumption. If the problem is already isolated and the data backs it, we can go straight to execution.
What if we stop after the diagnosis?
You keep the document and the priorities. It is written to be useful even if another team executes it.
Do you work per project or on retainer?
Both. Diagnosis and build are usually projects. Campaign operation and the learning cycle work better as an ongoing engagement.
Next step