Scope the real problem
We start with the actual bottleneck: what is blocked, who is affected, what good looks like, and what can realistically move in the next 1-2 weeks.
Consulting
Product help for teams that need clarity and execution.
I work with early-stage teams on short, focused engagements: clarify scope, shape workflows, and ship useful products.
Best fit when something is clearly stuck: a feature needs shape, a workflow needs structure, or the team wants a working artifact before making a bigger commitment.
- Diagnostics
- Build sprints
- Fractional support
Ways To Work
Ways to work together.
The engagement should match the problem.
-
Diagnostic
Product Diagnostic
Fast clarity in 3-5 days
A short engagement for founders or product leads who want help clarifying what to build next, what to simplify, and where the real product risk sits.
- One working session to understand the product, team, and bottleneck
- Written memo with scope, risks, sequencing, and recommended next step
- Best for teams with too many open questions and not enough product clarity
-
Sprint
Scoped Build Sprint
Usually 1-2 weeks
A focused push to prototype, spec, or ship a feature, workflow, or internal tool without committing to a longer engagement.
- Product framing, UX, implementation, and iteration loop in one package
- Can end in a prototype, working demo, spec, or production-ready feature slice
- Best for startups that need momentum this month, not just advice
-
Fractional
Fractional Product + Engineering
Usually 1-2 days / week
Ongoing support for teams that need senior product judgment and hands-on execution in the same person, but do not need a full-time hire yet.
- Useful when product, UX, and implementation are all bottlenecked at once
- Can cover roadmap shaping, workflow design, execution, and launch decisions
- Best for seed to Series B teams in health tech, developer tools, and product-heavy software
How It Works
A simple working model
Short engagements work best when the problem is clear and the expected output is concrete.
Pick the right engagement shape
Sometimes this is a memo. Sometimes it is a prototype. Sometimes it is an execution sprint. The point is to match the work shape to the risk.
Leave behind something useful
The output should outlast the meeting: a clearer roadmap, a working demo, a shipped slice, or a decision-ready artifact the team can keep using.
Signal Check
Best when
These are the situations where I can usually create value quickly.
- You have a real product or workflow bottleneck, not just broad interest or exploration
- The team needs scope, UX, and execution to move together
- You want something shipped, tested, or clarified quickly
What You Get
The output should be useful even if we only work together briefly.
Even a short engagement should leave behind something the team can use immediately.
Clear scope
A sharper definition of the user problem, the release boundary, and the real tradeoffs.
Working artifact
A prototype, demo, or feature slice that makes the decision concrete instead of hypothetical.
Workflow judgment
A more trustworthy operating flow with clearer failure handling, structure, and human control.
Execution momentum
Less ambiguity sitting between PM, design, and engineering, and more movement toward a shipped result.
Next Step
A short note is enough.
If you want to explore a project, a few lines of context is plenty. It does not need to be polished.
If you already have a product, workflow, or feature in mind, it helps to include the team stage, what feels blocked right now, and what a good next step would look like.
Subject: Consulting inquiry
Company + stage:
What you are building:
Current bottleneck:
What needs to happen next:
Preferred engagement shape:
Timeline: