Product discovery and opportunity shaping
Covers Conceive plus Should we / Shouldn't we.
What clients buy: clarity, decision confidence, and a grounded business case.
Detailed service architecture
Eight billable phases. One coherent product lifecycle offer.
Every phase answers a different business question, creates a defined output, and can be sold as a standalone engagement or combined into a broader product programme.
Service families
How the offer is packaged for clients.
These categories simplify buying while the underlying phase model keeps the work scoped, measurable, and commercially sensible.
Product strategy and delivery planning
Covers Plan.
What clients buy: scope definition, roadmap logic, governance structure, and execution readiness.
Product leadership during build
Covers Develop.
What clients buy: delivery control, requirements clarity, and stronger decision-making through build.
Launch support and product improvement
Covers Iterate plus Launch.
What clients buy: adoption readiness, feedback loops, and practical improvements after release.
Product governance and value management
Covers Steady State plus Maintain or Kill.
What clients buy: governance routines, KPI ownership, and disciplined product investment decisions.
Remote and founder-led
All services are designed for remote delivery through workshops, working sessions, artefacts, governance packs, and asynchronous stakeholder review.
Phase detail
The Inside-Out lifecycle, phase by phase.
Each phase below includes the objective, the work involved, the deliverables, and what the client is actually buying at that point in the lifecycle.
01 Conceive
Define the opportunity.
Objective: Define a worthwhile product opportunity linked to a real business problem, operational gap, or growth opportunity.
- Understand business context, users, pain points, and system constraints.
- Identify process leakage, friction, blind spots, and possible digital interventions.
- Frame a clear product concept with value hypothesis and target use cases.
Deliverables: Problem statement, opportunity statement, concept summary, target users, value hypothesis, initial risk view.
02 Should we / Shouldn't we
Test whether it is worth doing.
Objective: Help the client make a disciplined investment decision before major spend begins.
- Assess strategic fit, operational fit, likely cost, expected benefit, and core risks.
- Compare options, including doing nothing or redesigning the concept.
- Use business-case thinking and value-versus-complexity logic to recommend proceed, pause, redesign, or stop.
Deliverables: Business case, options analysis, feasibility view, risk assessment, recommendation pack.
03 Plan
Translate concept into delivery structure.
Objective: Create a realistic and business-aligned plan for building the right thing in the right order.
- Define goals, success measures, scope, MVP, user journeys, and prioritised backlog.
- Surface process changes, integrations, reporting needs, and stakeholder roles.
- Set roadmap logic, delivery approach, governance cadence, and key decision points.
Deliverables: Product vision, scope document, user stories, process maps, roadmap, KPI framework, delivery plan.
04 Develop
Provide product leadership during build.
Objective: Keep the build aligned to business value, user needs, and agreed priorities while execution is underway.
- Act as product lead between business stakeholders and technical teams or agency partners.
- Clarify requirements, acceptance criteria, priorities, and trade-offs.
- Maintain decision logs, resolve ambiguity, and protect focus on intended outcomes.
Deliverables: Refined backlog, priority packs, decision logs, build oversight notes, requirement clarifications, stakeholder reviews.
05 Iterate
Improve the product based on real evidence.
Objective: Strengthen fit, usability, adoption, and value realisation after initial delivery.
- Review feedback, early usage, friction points, defects, and missed assumptions.
- Identify the changes most likely to improve adoption and operating performance.
- Refine workflows, feature priorities, reporting, and the next iteration plan.
Deliverables: Feedback summary, issue log, enhancement priorities, revised backlog, iteration plan.
06 Launch
Prepare the business to release successfully.
Objective: Launch in a controlled way that supports adoption and minimises operational disruption.
- Coordinate readiness across training, support, communications, process changes, and reporting.
- Define rollout structure, escalation routes, and adoption tracking.
- Make sure the business is ready, not only the software.
Deliverables: Launch plan, readiness checklist, communications plan, support model, adoption tracking plan.
07 Steady State
Move from project mode to managed product mode.
Objective: Establish a sustainable operating model for the product in business-as-usual conditions.
- Define ownership, KPI reporting, governance routines, and prioritisation rules.
- Set ongoing backlog management and decision-making cadence.
- Make product performance visible commercially and operationally.
Deliverables: Product operating model, governance framework, KPI dashboard definition, reporting cadence, ownership map.
08 Maintain or Kill
Review whether ongoing investment still makes sense.
Objective: Support disciplined portfolio decisions about whether to maintain, improve, reposition, consolidate, or retire a product.
- Review performance against original objectives and current strategic relevance.
- Assess adoption, support burden, revenue or cost impact, and operating complexity.
- Recommend continue, optimise, redesign, integrate, or retire.
Deliverables: Performance review, value realisation review, recommendation pack, transition or retirement plan where required.
How we engage
Flexible structures without losing discipline.
Pricing can be structured around phases, workshops, short advisory sprints, or ongoing monthly product leadership depending on the situation.
Phase-based engagement
Best when the business needs a specific outcome such as an opportunity assessment, business case, plan, or governance pack.
Product sprint or workshop series
Best when rapid alignment is needed across stakeholders, especially in early concept or planning stages.
Fractional product leadership
Best when a business has delivery teams but needs an experienced product lead to shape decisions through build and beyond launch.
Next step
Start with the phase that answers the most important business question first.
For some clients that is opportunity shaping. For others it is a business case, a roadmap, launch readiness, or a steady-state governance review. The work is modular, but the method stays coherent.