01
18+
Years of cross-disciplinary experience across strategy, design, and technology.
Product Strategy
Features ship without a clear strategy behind them. The roadmap has become a list of stakeholder requests, and nobody is connecting the decisions across product, design, and engineering. You are seeing the cost in rework, conflicting priorities, and features that do not move the business forward.
That usually means there is no one with the cross-disciplinary experience to set product vision and hold the course across the team. I define the product strategy with you, drawing on what you already know about your market, your customers, and your business. Then I turn that into direction, roadmap, and scoped features the team can execute.
What this covers
I work with what you already know about your business and customers to define where the product needs to go, plan how to get there, and build the frameworks so the team can sustain the direction.
Planning
Product vision and direction
Defining what the product should become, its position in the market, and how it connects to business goals.Roadmap planning
Building a prioritised plan based on objectives, user needs, and technical feasibility.Feature prioritisation
Establishing criteria for deciding what gets built, what gets deferred, and what gets cut.
Delivery
Feature scoping
Turning roadmap priorities into specifications that design and engineering can act on.Cross-team coordination
Working across product, design, and engineering to keep decisions connected as work progresses.Working-level involvement
Joining the team in planning and review sessions to shape decisions as they happen.
Handover
Decision frameworks
Prioritisation and scoping models the team can apply independently after handover.Objective-driven planning
Moving from reactive feature requests to structured, goal-driven roadmap cycles.Documentation and handover
Recording decision rationale so the product thinking outlives the engagement.
Process
How I work
I work embedded with the product, design, and engineering teams for the duration. I join regular working sessions, contribute to planning, and shape decisions as they happen. This is hands-on involvement at the working level. For businesses building digital products, this work often runs alongside UX strategy or broader web engagements. I adjust the scope based on what capability the team already has.
I work embedded with the product, design, and engineering teams for the duration. I join regular working sessions, contribute to planning, and shape decisions as they happen. I draw on whatever the business already has, whether that is customer data, sales insight, internal research, or institutional knowledge. I do not conduct market research or primary user research. If that work is needed, I help you find the right people for it. For businesses building digital products, this often runs alongside UX strategy or broader web engagements. I adjust the scope based on what capability the team already has.
02
100%Client return rate. Every client that needed further work came back.
Who this is for
For businesses whose product needs direction, not just more features.
Has builders, no product direction
You have developers and designers, but nobody connecting what gets built to business outcomes.
Roadmap is a wish list
Features ship based on whoever asks loudest. There is no structured way to decide what matters most.
Growing faster than the product
The business has evolved but the product still reflects decisions made a year or two ago.
No product lead on the team
You know the product needs strategic direction but a full-time hire for the role is not justified yet.
FAQ
Frequently Asked Questions
How long does a product strategy engagement typically run?
Most run two to four months, depending on the complexity of the product and how much groundwork already exists. If the team has some product discipline in place, the engagement focuses on direction and frameworks. If everything needs building, it takes longer.
Do you do market research or user research as part of this?
I do not conduct primary market research or user research. I work with what the business already knows, customer insight, sales data, usage patterns, and internal knowledge. If research gaps exist that need filling, I help identify what is needed and who should do it. The product strategy builds on real information the business already has.
Do you replace our product manager or work alongside them?
Both, depending on the situation. If there is nobody in the role, I fill the gap. If there is, I work alongside them. The goal is to set direction, build frameworks, and hand over cleanly. For businesses considering a permanent product hire, I can help define the role and support the transition.
What if we need UX or technical work alongside product strategy?
Product strategy often runs in parallel with UX strategy or broader web and technical work. I adjust scope to cover what is needed across disciplines, structured as a single engagement or through a retained consulting arrangement.
Not sure where to start?
If you know something needs to change but aren't sure which service fits, that's normal. Most engagements start with a conversation. Tell me what's going on and I'll tell you what I think would help.