Business stage · Module 14 of 15
Outcome for this lesson
Set a price using complete costs, defined scope, willingness-to-pay evidence, and a tightly bounded paid pilot.
Bring forward: Bring the validation record, cost worksheet, release scope, and support boundary.
Produce: A pricing decision record with unit, scope, floor, scenarios, pilot price, evidence threshold, and revision rule.
0 of 15 core modules complete
Progress is saved on this browser. Create a free membership to sync across devices.
Recommended prerequisite: complete Module 13, “Prepare a Reliable Deployment and Recovery Path,” and bring its artifact. You may still use this page as a reference.
Business stage
Build the next result
Price is a hypothesis about a defined unit, not a reward for effort. It must cover the complete cost boundary and be tested with a specific customer under honest pilot terms.
Your result for this module
A pricing decision record with unit, scope, floor, scenarios, pilot price, evidence threshold, and revision rule.
Continuous case study
Worked example: A bounded paid pilot
The pilot includes setup for one freelancer, one workflow, 30 days, and a stated support limit. The cost floor is calculated from delivery and support. Five qualified buyers are offered the same price; results and actual service time determine the revision.
Do the work
Define the priced unit
State deliverable, customer, time period, limits, support, revisions, exclusions, refund terms, and third-party costs.
Calculate the floor and scenarios
Use the cost worksheet to model contribution and break-even without treating forecasts as results.
Test willingness to pay
Use conversations, a consistent offer, checkout behavior, deposits, or paid pilots; keep attention separate from payment.
Write the revision rule
Decide what purchase, delivery-time, support, refund, and retention evidence will change the price or scope.
Copy-and-complete template
Create your module artifact
Priced unit and customer: Included: Excluded: Delivery and support limits: Cost floor and scenarios: Pilot price and sample: Success/change/stop threshold: Observed behavior: Revision date and rule:
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
- Scope prevents an unlimited obligation.
- The price is tested against complete cost.
- The pilot is disclosed as a pilot.
- Actual payment and delivery evidence remain separate from interest.
How this moves the project forward
Module 15 combines every artifact into a launch system and a traceable continue, change, or stop decision.
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 15: Launch Responsibly and Present the Course Capstone