How we work
From thesis to traction, in four phases.
The shape holds whether the engagement is a commercialization sprint, a market entry, or a workflow pilot. What changes is the evidence, the scoring criteria, and what gets installed at the end.
The method
Week 1
Frame
Establish what is actually being decided
Interviews, pipeline and product review, and the existing evidence. The output is a written problem statement the leadership team agrees with, which is more often the hard part than the analysis that follows.
- Written problem statement
- Evidence inventory
- Decision list
Weeks 1 to 2
Decide
Score the options and make the cuts
Markets, buyers, use cases, workflows, or partners are scored against criteria agreed in advance. Scoring happens with your team in the room, because the argument is where alignment forms.
- Scoring criteria
- Ranked shortlist
- Explicit deprioritizations
Weeks 2 to 3
Plan
Turn the decision into sequenced work
Narrative, roadmap, partner sequence, operating model, or workflow design, with owners, dependencies, and the small number of metrics that will confirm or break the thesis inside a quarter.
- Roadmap with owners
- Dependency and risk map
- Metric set
Weeks 3 to 4 and beyond
Install
Run it once with the team, then hand it over
A plan that has never been run is a hypothesis. The last phase runs the cadence, the workflow, or the first partner conversations with your team, adjusts what breaks, and hands over documentation your team maintains.
- Working cadence or workflow
- Handover documentation
- 90-day plan
How the work runs with your team
Engagements are designed to consume as little of your team's week as the work allows, while still producing decisions rather than documents.
Senior ownership
The person in the discovery call does the work. No handoff to a junior team after the engagement starts.
Written before verbal
Decisions, scope, and reasoning are written down. Meetings review documents rather than generating them.
Your tools, your artifacts
Work lives in your workspace from week one. Nothing important sits in an outside folder you lose access to at the end.
One weekly working session
A fixed slot for decisions, not status. Written updates handle the rest so the engagement does not tax the team calendar.
What this is not
Stating the boundaries early saves a discovery call later.
No legal, compliance, or regulatory advice
Regulatory dependencies are identified and sequenced into the plan. Questions that need qualified counsel are referred to qualified counsel.
No fully autonomous systems
Agentic workflows are built with approval gates, escalation paths, and audit trails. Anything consequential keeps a human in the loop.
No staffing by the seat
Engagements are scoped to outcomes and artifacts. If the real need is headcount, the honest answer is to hire.
No borrowed proof
Client names, metrics, and case studies are never published without permission. Credibility here comes from method and specificity.
Two ways to engage
- Fixed scope
- A defined question, a defined output list, and a written scope and fee before work starts. Best when a specific decision is blocked. See all six.
- Ongoing mandate
- Monthly, with the decisions in scope, the cadence, and what has to be true at 90 days written down. Best when senior capacity is needed without a full-time hire.
Next step
Bring the decision that is currently stuck.
Most engagements start with one blocked question rather than a service selection. Describe it and you will get a straight answer about scope and sequence.
Or write directly to