Decide what to build before anyone builds it.
A short engagement that ends in a written first-release scope and roadmap, so the budget goes to the version worth shipping.
Sound familiar?
The expensive decisions are made before any code exists. A roadmap built on assumption is difficult and slow to unwind once a team has built against it.
Before · how it feels now
- 01Competing ideas with no way to choose between them
- 02A roadmap based on opinion
- 03Scope that grows faster than the budget
- 04No agreed definition of a first release
- 05Research that never reaches a decision
After · what changes
- A defined audience and problem
- A first release the team agrees on
- Evidence behind the roadmap
What we do
The work,itemised.
This can run as a short standalone engagement. There is no obligation for Arctos to build what it recommends.
- 01Discovery workshops
- 02Customer and stakeholder interviews
- 03Problem and opportunity definition
- 04Competitive review
- 05Product roadmap
- 06Scope and release planning
- 07Prototype validation
- 08Success measures and reporting
How it runs
Laid one plankat a time.
Five steps, in order. Each one rests on the one before it.
- 01Agree the decision the work has to inform
- 02Interview customers and the people who serve them
- 03Define the problem and who has it
- 04Shape a first release and what it must prove
- 05Set the measures that tell you it worked
Honest about fit
When we’re thewrong choice.
Saying so early saves both of us time. If none of these sound like you, we should talk.
- Not a fit · 01
You already know the audience, the problem, and the first release. Go straight to a build service instead.
- Not a fit · 02
You need an answer this week. Most engagements run two to six weeks because they involve real customer interviews.
- Not a fit · 03
You want research that confirms a decision already made, not one that could change it.
Related work
The same work,in real projects.
Questions
Askedoften.
Q01How long does a strategy engagement take?
Most run between two and six weeks, depending on how many customers and internal stakeholders need to be spoken to.
Q02Do we have to build with Arctos afterwards?
No. The output is yours, and it is written so another team could pick it up and build from it.
Q03What if we already know what we want to build?
Then the work is shorter and focuses on validating the plan and defining the first release rather than exploring the problem.
Often paired with
Start here
Test the plan before it becomes a build.
Tell us where the work gets stuck. You don’t need a technical brief, and the reply comes from the people who would do the work, within two business days.



