Stakeholder workshops
Two structured days with the people who decide. Scope drafted live, disagreements listed and resolved in the room. The brief is signed before everyone leaves.
Turn a vague mandate into a costed plan.
Discovery workshops, a technical audit, and a sequenced roadmap. Two to eight weeks, ending in a plan your CTO and CFO both sign.
What you walk away with
Six artifacts, one signed plan.
Strategy is not a deck. It is the documents your team still opens six months later.
Scope, written down
In scope, out of scope, deferred. Each exclusion carries its reason, so it stays excluded.
InOutDeferred
Success criteria
The numbers that say the work succeeded. Quantified and agreed before the first bet is ranked.
MetricBaselineTarget
Systems and team audit
Code, data, infrastructure, and team capacity. We read what exists before planning what comes next.
SystemsDataCapacity
Sequenced bet list
The roadmap as an ordered list of bets. Each has effort, impact, and confidence attached. Your team pulls from the top and re-ranks without breaking the plan.
Every bet costed
Engineering days, vendor spend, and run cost for each bet. Finance and engineering read the same number.
The hard part
Bets ranked by effort × impact, not by who spoke loudest.
Most strategy work fails at prioritization. The loudest voice in the workshop takes the top slot. We score every bet the same way, in writing, against goals agreed before anyone pitched an idea.
- Effort sized in engineering days — the unit finance already budgets in.
- Impact scored against the three goals your leadership agreed in week one.
- Confidence rated low, medium, or high — low-confidence bets get more discovery, not a slot.
- Final order is impact × confidence ÷ effort. Changes happen in writing, with a reason.
How it runs
Interviews, workshops, a signed plan — then checkpoints.
Week one is listening and reading. Workshops come once we know the systems. The plan is signed at the end, and the review dates go in the calendar before we leave.
- Week 1: stakeholder interviews and a read of code, data, and infrastructure.
- Week 2: two days of workshops, ending in a signed brief.
- Weeks 3+: bets costed, sequenced, and stress-tested with engineering leads.
- Quarterly: the bet list is re-ranked against what shipped and what changed.
2–8 wk
Kickoff to signed plan, scoped in writing up front
2 days
Of stakeholder workshops, ending in a signed brief
Every bet
Costed in engineering days and vendor spend
Quarterly
Review checkpoints booked before the plan is signed
The brief ended a scope argument that had run for two months. The bet list is still the first thing we open in planning.
Questions
What buyers ask us first.
How long does it take?
Two weeks for a focused discovery on one product. Up to eight when the plan spans several teams and needs a full systems audit. Scope and dates are fixed in writing before kickoff.
What do you need from our side?
A sponsor who can make decisions, two days of time from the key stakeholders, and read access to repositories, cloud billing, and internal docs.
Who owns the plan at the end?
You do. The brief, bet list, cost model, and architecture notes live in your docs tool, in formats your team can edit.
Do we have to hire you to build it?
No. The plan is written so your team, us, or any other vendor can execute it. If a bet should not be built at all, the plan says so.
How is it priced?
A fixed fee per phase, quoted after a scoping call. You know the cost before you commit.
Ready when you are
Tell us the mandate that’s keeping you up.
A 30-minute call. You leave knowing whether discovery, an architecture review, or neither is the right next step.