Compare a product and a service model, expose their assumptions and design a small evidence-gathering experiment.
A fictional repair club considers selling a printed maintenance kit or providing a monthly workshop. Neither option has been tested with customers. The figures below are hypotheses for one month, not forecasts or investment recommendations.
| Model | Units | Price | Variable cost per unit | Fixed cost |
|---|---|---|---|---|
| Kit | 40 | 20 | 8 | 300 |
| Workshop | 20 | 35 | 10 | 400 |
Start with the situation a customer wants to improve. A proposed solution is not the same as an observed need. Keep the customer, beneficiary and payer separate when they differ. In this case no interview has happened, so write hypotheses rather than invented customer quotations.
Write two customer situations and label every unverified claim.
Customer hypothesis sheet
Record your result and evidence here or in a separate file.
The sheet contains no fictional quotation presented as research.
Rewrite assumed preferences as questions to investigate.
Compare what each model delivers, the activities required and the relationship after purchase. A product model may still require service and a service model may use products. Avoid choosing a label first and forcing the case into it. The comparison should help explain operating differences.
Map the kit and workshop against delivery, support, resources and payment.
Two-model comparison
Record your result and evidence here or in a separate file.
Each model has a distinct delivery process and a named payer.
Describe actual activities instead of repeating model labels.
Contribution is revenue minus variable cost; it must still cover fixed costs. Compare the models at the supplied volume and test a lower volume. This simple calculation excludes tax, financing and many real-world costs. Its purpose is to reveal which assumptions matter, not to predict a business outcome.
Calculate monthly contribution and surplus, then reduce each volume by 25%.
Scenario calculation
Record your result and evidence here or in a separate file.
Base surpluses are 180 and 100; reduced-volume surpluses are 60 and -25.
Keep unit costs separate from monthly fixed costs.
A useful experiment can change a decision. Define the uncertainty, the observation needed and the stopping rule before collecting evidence. Avoid treating polite interest as a purchase. A no-cost interview or mock offer can test understanding, while actual willingness to pay would require a carefully designed later test.
Plan five voluntary interviews with neutral questions and a decision rule. Do not contact anyone for this exercise.
Experiment protocol
Record your result and evidence here or in a separate file.
The protocol says what result would weaken each model.
Replace questions that praise your idea with questions about recent behavior.
A recommendation should distinguish known arithmetic from unknown demand. State what you would test first and why, and identify conditions under which the other model becomes preferable. Keep a versioned assumption register so new evidence can change the model without hiding the earlier reasoning.
Write a one-page comparison and prioritize the three riskiest assumptions.
Decision memo and assumption register
Record your result and evidence here or in a separate file.
The recommendation is conditional and includes an explicit next evidence step.
Remove certainty words unsupported by the case.
Deliver the customer hypotheses, two-model map, base and downside calculations, interview protocol and conditional memo. Add a third scenario with a higher support cost and explain how the recommendation changes.
All demand and cost assumptions are labeled; no hypothetical revenue is presented as earned.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The kit generates 40 × (20 − 8) − 300 = 180. The workshop generates 20 × (35 − 10) − 400 = 100. At 75% of those volumes, the results are 60 and −25. The kit looks stronger under these assumptions; the arithmetic does not establish demand, quality or long-term viability.
This is a fictional model-design exercise, not financial advice or validation of a real venture.