---
name: solutionlink-business-planning
description: Prepare and verify native Solutionlink TIPS relationships, phased deployment and illustrative ROI in explicitly configured owned projects.
---

Read [business specifications](../../docs/business-specifications.md) before authoring. Start with context list, native business state and business options. Use native categories/currencies and typed IDs. Create actual Trend -> Challenge -> Possibility -> Solution relationships rather than descriptive links alone. A possibility-to-scenario association is not exposed as a working tool.

Use solutionlink_prepare_change for a local baseline/preview. Review scope and assumptions, then solutionlink_apply_change for an authorized write with enableWrites true. It guards against changed baselines and records evidence. A failed or interrupted plan is inspect-only; do not replay blindly. Completed replay independently checks current state without duplicating rows.

Define implementation phases with dates, gates, dependency descriptions, proposed owners and linked solution rollouts. Verify native dates and relationships. Keep assumptions illustrative unless finance supplies evidence. Use a low/base/high population range and explicitly scale cost/benefit drivers; distinguish capacity value, cash savings, eligibility and adoption.

Reconcile native timed cashflows and actual stored discount rate with independent monthly end-period NPV. solutionlink_evaluate_roi provides a separate dated arithmetic reference. Native monthly rate precision may prevent the exact desired annual hurdle. Disclose the stored value and mismatch; never change benefits to force NPV agreement.

solutionlink_prepare_billboard builds a local TIPS content blueprint; native UI creation and persistence are separate, described in [eXplore](../../docs/explore.md).
