I help companies understand what is holding the product back and decide what to do first.

I look at where the ideas come from, what customer or business evidence supports them, how product decisions are made today, and where the cycle from signal to action slows down.

Which customer problem or risky assumption deserves attention first, what evidence would change the decision, and what the company should consciously leave out for now.

We choose the smallest reliable way to test the assumption. That may be focused customer research, a working prototype, or a small product change with a clear result the team can learn from.

I then turn the result into clearer scope, a product specification, an engineering decision, or a reason not to proceed.

The team has one clear priority, a shared reason for choosing it, an explicit “not now” list, and a more repeatable way to make the next product decision.

I compare what the company says with why customers buy, what they try to accomplish, where they get stuck, and what they use instead.

Depending on the situation, I may look at active, inactive, churned, and non-converted customers separately, alongside sales conversations, support themes, pricing, onboarding, product usage, and the journey from first interest to first value.

Whether the main problem sits in the target segment, product promise, packaging, onboarding, activation, existing experience, or a genuine product gap.

From there, the company can decide which customer, problem, and use case should lead the product story.

We test one focused intervention instead of automatically adding another feature.

That may become a clearer positioning direction, a messaging test, a revised package structure, a simplified product flow, a prototype, or a focused product improvement. I stay involved as the decision moves into the experience and the way the company takes it to market.

The company has a clearer segment choice and one shared explanation of why the product matters. Product, sales, and marketing can use the same customer language and work toward the same priority.

I look at the backlog, user journeys, unresolved product decisions, technical constraints, edge cases, deadlines, and the outcome the release is expected to create.

What belongs in the release, what can wait, which trade-offs are acceptable, and what order gives the team the clearest path to a usable product.

I turn the decision into the form the team needs: user flows, screens, a working prototype, a scoped backlog, or a product specification.

I remain involved as development surfaces new constraints, helping the team make trade-offs without losing the intended customer outcome.

The team has a shared definition of the release, a prioritized backlog, and a clearer way to make new scope and engineering trade-offs as development continues.

I look at who the launch is for, the core use case, the promise being made, the actual release scope, readiness gaps, dependencies, the first-use experience, and how the company plans to collect useful feedback.

What must be true at launch, what can wait, which message should lead, and what the company needs to learn from its first real users.

The decision may become a focused launch scope, a pre-launch page, a messaging test, a readiness checklist, or a plan for collecting and reviewing feedback.

I help product, engineering, marketing, sales, and customer-facing work stay aligned around the same audience, promise, and release.

The company has one clear launch message, a realistic view of readiness, and a shared plan for what to learn and improve after release.

I look at the customer problem, existing evidence, alternative ways customers solve it, strategic fit, technical cost, and the assumptions that would cause the current direction to fail.

Whether the problem deserves further investment, whether the proposed product is the right response, and what evidence is still missing before the company commits.

We choose the smallest test that could change the decision instead of immediately investing in a polished build.

I synthesize the evidence and turn it into a scoped build direction, a redirected approach, or a documented stop decision.

The company can move forward with a decision it can explain and stand behind, whether that means building, changing direction, or stopping. The evidence, accepted risks, and next step are clear to the team.