Research
Scope, evidence and direction before anyone builds.
Most projects that fail were mis-scoped, not badly built. We define what the work must do, whether it can be done that way, and what delivery requires.
The problem
A vague brief transfers uncertainty into every later decision.
Teams compare tools or estimate builds before agreeing on users, workflows, evidence and constraints. Proposals become hard to compare and expensive questions return during delivery.
What is included
Requirements & scope
Users, workflows, data, constraints and definition of done.
Feasibility & risks
Unknowns, blockers and a response to each risk.
Technology comparison
Options weighed against actual requirements.
Delivery roadmap
Phases, priorities, dependencies and decisions.
Reports & editing
Evidence-based reports or detailed draft review.
How the work moves
- 01
Brief
Review what already exists.
- 02
Questions
Close gaps and agree on criteria.
- 03
Work
Research, compare and record the method.
- 04
Handover
Deliver and explain the recommendation.
Useful outcomes
A buildable scope
Requirements describe users, constraints and success.
Fewer changes
Risks surface before implementation.
A checkable decision
Recommendations show criteria and trade-offs.
Handover and fit
What you receive
- A written brief, report or review
- Reasoning behind recommendations
- Sources and method
- A walkthrough call
A strong fit when the idea is real but direction is unsettled.
Best when a project lacks a specification or a study needs defensible structure.
- Stakeholders describe the project differently
- Technology is chosen before requirements
- A study needs traceable evidence