Final Recommendation

What this activity covers

Choose the next step based on repeatability, readiness, evidence, architecture, and investment confidence.

Why it matters

Do not recommend platform or SaaS direction just because the idea sounds reusable; use evidence.

Typical output

Final recommendation and decision rationale.

Questions this activity helps answer

• Is this custom only, client first reuse friendly, internal platform, SaaS first, pilot first, or no-go?
• Which evidence supports the decision?
• What must happen before product investment?

Proceed as SaaS-first product

• Repeatable problem is validated.
• Target market, buyer, and user segments are clear.
• Existing alternatives leave a meaningful gap.
• Configuration needs are manageable.
• Pricing and packaging assumptions are promising.
• Technical architecture can support multi tenant growth.

Discovery indicates that the problem is repeatable, the target buyer and user segments are clear, and the product can be built as a configurable, reusable SaaS offering. Proceed with SaaS MVP, pilot, pricing validation, onboarding model, and scalable architecture.

Proceed as client-first, reuse-friendly product

• Current client need is strong.
• Immediate delivery is important.
• Future reuse is possible but not fully validated.
• Some client specific customization is acceptable.
• Architecture should still preserve future productization options.

Prioritize the immediate client or unit need, but design selected parts for future reuse and configurability. Proceed with the first delivery while protecting the product core, tenant model, role model, governance approach, and backend structure needed for future scaling.

Proceed as internal platform

• External commercial case is unclear.
• Multiple internal teams or departments can use it.
• Reuse is valuable internally.
• Standardization will reduce duplicate development.
• Pricing is less important than governance, configuration, and adoption.

Discovery indicates strong internal reuse potential, but the external SaaS case is not yet validated. Proceed with reusable architecture, configurable setup, internal pilot, governance model, and future SaaS validation if demand grows.

Build as custom project only

• Problem is specific to one client.
• Other customers do not show similar needs.
• Configuration would create unnecessary complexity.
• Productization cost is not justified.
• Future reuse is weak or unlikely.

Discovery indicates that the problem is specific to the current client or context and does not justify scaled-solution investment at this stage. Proceed as a scoped custom project and avoid unnecessary productization complexity.

Pilot before product investment

• Opportunity seems promising.
• Evidence is incomplete.
• Buyer or user adoption is uncertain.
• Configuration model is unclear.
• Technical or support model needs testing.

Discovery indicates potential, but key assumptions around repeatability, adoption, configuration, technical readiness, support, governance, or commercial value remain unresolved. Run a controlled pilot before committing to full scaled-solution development.

Do not proceed now

• Problem is weak.
• Buyer is unclear.
• Existing alternatives are good enough.
• Product complexity is too high.
• Support or implementation cost is not justified.

Discovery does not provide enough evidence to justify SaaS, platform, or custom development at this stage. Revisit only if stronger demand, clearer ownership, or better commercial value emerges.

Related outputs

These outputs usually sit beside this activity when the team reviews the evidence together.

• Discovery summary.
• Key risks and assumptions.
• Onboarding, setup, support, and training notes.
• Support and maintainability model.
• Pricing and packaging hypothesis, if SaaS is a priority.
• Pilot plan, if validation is still needed.
• Final recommendation.