By David Bartas · Updated
What this work helps you decide.
Product strategy consulting helps a team choose what to build, for whom and in what order. I work with founders and product leaders to connect a business goal to a focused product brief, explicit MVP boundaries and a roadmap the team can explain and use.
What is the smallest useful next step that moves the product towards its business goal?
What to bring.
- The customer problem and the outcome you want to change
- The current product, roadmap or prototype
- Existing evidence, open assumptions and competing requests
- Team capacity, dependencies, timing and budget
Typical deliverables.
- A product brief with the goal, audience and key assumptions
- MVP scope with explicit inclusions and deferrals
- A prioritised roadmap connected to business goals and delivery constraints
The scope depends on your question and available context. A consultation frames the decision; a complete review, workshop or delivery engagement is scoped and quoted separately.
How I approach the work.
01
Frame the goal
Name the customer, the problem and the decision facing the team. Identify the evidence already available and the assumptions that still need testing.
02
Compare priorities
Make the trade-offs between requests visible. Consider the expected value, uncertainty, dependencies and delivery effort rather than treating every request as equally urgent.
03
Draw the boundaries
Define what an initial release must do, what it can defer and which questions require a separate experiment. Give the team a reason for each boundary.
04
Sequence the work
Turn the chosen direction into a practical roadmap. Record ownership, dependencies and review points so the plan can change when new evidence arrives.
Related project evidence.
These cases describe project scope and personal contributions. Each links to a public product, profile or source record.
BuildPortfolio.ai
Oct 2026 – present
An Investboard product for shaping editable portfolio proposals around an investor’s objectives and rules.
Read the case study →Investboard
2025 – present
Bringing portfolio data, a personal mandate and decision history into one product.
Read the case study →George Business
Aug 2022 – Jun 2025
Payment lifecycle, transaction history and card reservations for Česká spořitelna’s corporate banking.
Read the case study →David Bartas is the founder of Investboard and creator of InvestingStack. His own products and ecosystem work are identified in the case studies.
Common questions.
What is the difference between a product strategy and a roadmap?
The strategy explains the audience, problem, goals and choices that guide the product. The roadmap sequences the work intended to advance those choices. A roadmap is easier to review when each priority has a clear reason and the assumptions behind it are visible.
Can you review an existing roadmap?
Yes. Bring the current roadmap, the goal it should support and the main constraints. We can compare priorities, identify unclear assumptions and dependencies, and agree which decisions need more evidence before the team commits.