Digital Strategy & Product Planning
The technical roadmap for long-term success. Turning rough concepts into sequenced, fundable, buildable product plans.
Build the right thing in the right order.
Sequence is most of the strategy
Most product plans fail on sequence rather than substance. This engagement decides what ships first, what waits, and what gets cut, before anyone writes code against the wrong assumption.
Deliverables
- Product Strategy Document - goals, constraints, success metrics
- MVP feature prioritisation matrix
- Technical roadmap - phased, with dependencies mapped
- Competitor analysis with UX benchmarking
- Market positioning brief
- Discovery Workshop report (first engagement)
Common questions
It starts with a Discovery Workshop - a structured two-to-three hour session that interrogates the concept from a user and technical perspective. It documents assumptions, identifies the riskiest ones, and defines the smallest version of the product that would prove or disprove those assumptions. You leave with a clear problem statement, a user hypothesis, and a scope for phase one. No concept is too rough - rough is actually preferable, because there's less to unlearn.
Prioritisation uses a modified MoSCoW framework (Must Have / Should Have / Could Have / Won't Have) combined with a user value vs. build effort matrix. Every proposed feature is assessed against two questions: does this directly address the primary user problem, and can the core hypothesis be tested without it? Features that fail the first question are deferred. Features that pass the second are deferred too - the MVP should be minimal, not comprehensive.
Yes. The roadmap is structured in phases with defined inputs, outputs, and dependencies for each. It specifies which design deliverables are required before each development phase starts, which third-party integrations need to be scoped early, and which decisions can be deferred. It's written to be read by both technical and non-technical stakeholders - no jargon without explanation.
Competitor analysis goes beyond feature lists. It runs a UX audit of the top three to five competitors - documenting their information architecture, onboarding flow, primary CTA placement, and any identified friction points. That produces a map of what the market expects (table stakes) and where there's differentiation opportunity. Market research informs positioning; the UX audit informs design decisions.
The Discovery Session is a structured conversation - not a sales call. The questions are about the problem, the user, the constraints, and what you have already tried. You should expect to leave with a clearer articulation of your own problem than when you arrived. If there is alignment on scope and approach, a fixed-price proposal follows within 48 hours. If there is not, you still leave with a clearer brief at zero cost.
The engagement
The same four steps apply to every service. There is no hourly billing and no open-ended scope.
- 01You reach out with the problem, not the solution. A brief description of what is not working is more useful than a specification.
- 02A 30-minute discovery call covers goals, constraints and timelines.
- 03A fixed-price, line-item proposal follows within 48 hours. Every line is something you can question or remove.
- 04A deposit starts the work, and the schedule is agreed in writing before anything begins.