Operate stage · Module 12 of 15
Outcome for this lesson
Estimate setup, recurring, usage, maintenance, support, failure, and owner-time costs before committing to delivery.
Bring forward: Bring the tested product, operating requirements, dependencies, and support expectations.
Produce: A low, base, and high monthly cost worksheet with assumptions and review dates.
0 of 15 core modules complete
Progress is saved on this browser. Create a free membership to sync across devices.
Recommended prerequisite: complete Module 11, “Test, Debug, and Prove the Important Journeys,” and bring its artifact. You may still use this page as a reference.
Operate stage
Build the next result
A working product can still be an unsustainable offer. Count all resources needed to deliver, maintain, support, recover, and review it before choosing a price or launch commitment.
Your result for this module
A low, base, and high monthly cost worksheet with assumptions and review dates.
Continuous case study
Worked example: Three tracker cost scenarios
The base case includes hosting, email, monitoring, payment fees, two support hours, monthly access review, backup testing, and expected usage. The high case adds incident time and higher API volume. Each assumption has a date and recalculation trigger.
Do the work
Separate cost types
Record one-time setup, fixed recurring, per-customer or usage-based, maintenance, support, failure, and owner-time costs.
Choose a cost unit
Calculate per month, per delivery, or per active customer so the result can inform pricing.
Create three scenarios
Use low, base, and high volume or failure assumptions rather than one precise-looking forecast.
Set review triggers
Record provider-price dates, capacity thresholds, time overruns, refund levels, and events that require recalculation.
Copy-and-complete template
Create your module artifact
Cost unit: One-time setup: Fixed monthly costs: Variable cost per unit: Maintenance and security time: Support and failure allowance: Low/base/high totals: Assumptions and source dates: Recalculation triggers:
Keep sensitive information, passwords, API keys, payment data, and private customer details out of course notes and AI prompts.
Quality gate
Check the result before the quiz
- Owner time is not treated as free.
- Free tools include scale and replacement risk.
- Variable costs use a named volume assumption.
- The worksheet can be updated when evidence changes.
How this moves the project forward
Module 13 uses the tested system and cost boundaries to prepare a release and recovery packet.
Evidence checkpoint and lesson summary
Confirm the artifact, then answer the key questions
The questions cover a core idea, a realistic decision, and evidence from the lesson. Incorrect answers identify concepts to review; they are not a complete measure of your experience or ability.
Confirm the artifact and answer all three questions correctly to unlock the recommended next step.
Continue to Module 13: Prepare a Reliable Deployment and Recovery Path