How I work
One clear decision at every stage.
Diagnose
A sales problem can turn out to be a product problem, and a product problem an operating-cost problem. I look at the business and the system together.
- Trace the customer problem, buying decision, usage and lost deals. Separate evidence from internal assumptions.
- Review revenue, delivery effort and running costs to see where value is lost.
- Inspect architecture, code, integrations and infrastructure with agreed access. If a live service is at risk, stabilize it first.
A diagnostic brief: the main constraints, reusable assets, urgent risks and open questions.
Reframe
The answer isn’t always more features. It may be a narrower market, different packaging or a new use for technology you already own.
- Compare the options: improve the current offer, reposition it, reuse custom-built technology or stop investing.
- Define the buyer, the user, the problem worth paying for and the boundaries of the offer.
- Spell out pricing, delivery costs, dependencies and trade-offs. Name the assumptions that could break the plan.
A recommended direction, alternatives and a focused scope to test, rather than a speculative feature backlog.
Validate
Before major development, test the assumptions that could sink the direction. Agree up front what counts as success and what means stop.
- Use targeted customer conversations, an offer, a prototype or a technical spike to test the highest-risk assumptions.
- Where it makes sense, scope a pilot around a real buyer, a specific use case and measurable acceptance criteria.
- Check demand and delivery feasibility together. Interest is not revenue; a pilot is not proven profitability.
A short evidence record, open risks and a recommendation to proceed, adapt or stop.
Deliver
I turn the commercial plan into a working implementation, anywhere from an operational prototype to a production release.
- Design the architecture and build with AI-assisted coding. Review and test the code against the agreed requirements.
- Set up deployment, infrastructure, access controls, secrets handling and observability to suit the product.
- Plan integration, migration and rollback where needed. Work with your existing team and specialist partners when the scope calls for it.
A working increment, release evidence and the documentation needed to run it or hand it over.
Measure
Launch is only a milestone. Compare what changed against the baseline and let that decide what comes next.
- Track the signals that matter for this product: activation, repeat use, paid demand, revenue or contribution margin.
- Include delivery effort, support load, infrastructure cost and reliability. Growth without workable economics is not a recovery.
- Review results with the owner on an agreed schedule. Keep, adjust or stop the next increment based on the data.
An outcome scorecard, remaining risks and a clear next decision. Revenue, profit and early traction are reported separately.