# Runwise product planning toolkit

Choose tools around a workflow, owner, and output. This guide is a selection framework; it does not endorse a vendor or promise current pricing.

| Job | Required output | Selection questions |
| --- | --- | --- |
| Customer research | Evidence log and problem hypotheses | Can you export notes? Who can access recordings? What consent and retention are needed? |
| Product discovery | Brief, workflow map, prioritized stories | Are decisions and assumptions visible? Can the whole team review and export them? |
| Prototyping | Testable primary journey | Can users complete the test task? What data and interactions are simulated? |
| Delivery planning | Milestones, owners, acceptance checks | Can you trace a requirement to working behavior and a reviewer? |
| Product measurement | Baseline and outcome signals | Is the event necessary? Does it collect personal information? Who reviews the results? |
| Operations | Monitoring, recovery, support ownership | Can you restore data, rotate access, and identify incidents without one person's memory? |

## Keep the toolchain small
Write the job first. Select a tool only if it improves a real handoff or decision. Check integration costs, exportability, permissions, licensing, and ongoing administration before adopting it.

## Runwise tools
- Readiness check: https://runwise.agency/resources.html#readiness
- Brief builder: https://runwise.agency/resources.html#brief-builder
- Cost planner: https://runwise.agency/calculator.html
- Editable scope and prototype: https://developer.runwise.agency/

Review your release boundary before choosing a production stack.