01
Decision document
The written case for what to build first — and what to leave alone. Read it in an hour. Defend it to a board.
DESIGN · STAGE 01 / 04
Are we building the right thing?
Discovery separates appetite from opportunity. Before anyone commits to a build, we map the people, systems, constraints, and value around the work — and put the case in writing.
- TYPICAL LENGTH
- 2–4 weeks
- WHO SHOWS UP
- Strategist · principal engineer · designer
- STARTS WITH
- A goal, a hunch, or a stalled initiative
WHAT YOU WALK AWAY WITH
Artifacts, not impressions.
Reproduced from real engagements and redacted where they must be. The redaction is part of the discipline you are buying.
02
Opportunity map
Every candidate bet plotted against customer value, business expectation, and technical risk. One usually dies here. That is the point.
03
Stakeholder map
Who decides, who blocks, who has to run this after launch — mapped before they surprise the project.
04
Maturity snapshot
An honest read on what your organization can absorb: capacity, readiness, and where change management will matter.
We will tell you when a project should not be built.
HOW IT RUNS
Week two of a discovery sprint, as it actually runs.
One real week beats any methodology diagram. This is the rhythm, not the highlight reel.
-
MON
Stakeholder interviews — three of them, recorded and transcribed.
-
TUE
Systems walkthrough with your engineers. The architecture goes up on the wall.
-
WED
Opportunity mapping session — every bet priced for value and risk.
-
THU
Technical spike on the riskiest assumption. Code, not opinion.
-
FRI
Findings in writing. Decision review booked with your sponsors.
ENGAGEMENTS AT THIS STAGE
What’s on the menu.
The workshops, sprints and engagements we run at this stage — scoped to where you are, not a fixed package.
The three perspectives we align
01
Customer experience
02
Technology
03
Business expectations
- Strategy Sprint
- Value Proposition Design
- Business Design Sprint
- Applied Innovation
- Design Sprints
- Business Case Development
- Lean Product Development
- Service Design
- UX & Prototyping
- Information Architecture
- Data Management
- Technical Analysis
PROOF, NOT PROMISES
Discover inside one engagement.
9 → 2
initiatives after discovery
A European energy group · ENERGY · IOT
- THE ASK
- Nine candidate initiatives, board pressure to start all of them, and no shared view of which ones could carry their own weight.
- THE TURN
- Three weeks of discovery priced every initiative for customer value, business case, and technical risk. The evidence supported two.
- SHIPPED
- One of the two became a data platform our team still operates today. The other seven were retired in writing — before they cost anything.
WHO SHOWS UP
Named people. One accountable team.
The team you meet is the team that does the work — cross-border, senior, and accountable by name. This is who discover brings into the room:
- Product strategist — lead
- Principal engineer
- Service designer
Vasil Gocevski
Co-Founder & CEO
“A founder sits in every discovery sprint. The honesty is structural.”
THE HANDOFF → STAGE 02
What exactly do we build first?
Discover ends in a decision. Define turns it into a shape — scope, prototype, and plan built directly on the discovery artifacts, not re-derived from scratch.
Related capabilities
ENTRY OFFER
Discovery Sprint
- 2–4 weeks
- Fixed price
- Senior team only
A focused engagement that turns ambition into a written, evidence-backed decision: what to build first, what it must prove, and what to leave alone.
The decision document is yours — whoever you build with.
The questions procurement asks first.
- What do you need from us?
- Access to around six stakeholders, two engineers, and whoever owns the budget. Roughly four hours of your team’s time per week.
- Do we need a master agreement first?
- No. A sprint runs under a simple fixed-price agreement and an NDA. The MSA conversation happens only if we both want to continue.
- Who owns the output?
- You do — the report, the maps, the spike code. Contractually, all of it.
- What if the answer is “don’t build it”?
- Then you saved a seven-figure mistake for the price of a sprint. You’ll know why, in writing.