create-existing-solutions

Evaluating existing solutions involves cataloging candidates from internal code, open-source libraries, SaaS products, and standards, then mapping them to your functional requirements. This process assesses licensing, maturity, integration effort, and alignment to determine whether to adopt, extend, or build.

Surveying open-source and SaaS candidates requires applying internal search and reference materials to map options against project requirements. The evaluation generates a structured report detailing the strongest candidates, trade-offs, licensing implications, and a recommended adoption direction.

Comparing build versus buy trade-offs involves analyzing candidate solutions against functional and non-functional requirements. The evaluation produces a decision plan highlighting integration effort, maturity, licensing constraints, and open questions to guide whether to adopt, extend, or build.

Yes, you can assess integration effort and licensing by providing feature requirements and context. The evaluation catalogs candidates from internal code, open-source, and SaaS, producing a concise report comparing licensing, maturity, and alignment to guide your decision.

You should extend an existing solution when candidates map closely to your requirements but require modification. The evaluation identifies this by assessing integration effort, maturity, and alignment, recommending an extension approach with documented trade-offs and open questions over a full build.