02 · Compare the artifacts
Supported work. Visible uncertainty.
This is a fictional, sanitized training case. It contains no real personal, customer, supplier, financial, or confidential data and does not provide legal, accounting, engineering, investment, or regulatory advice.
MesaLift predictive-maintenance venture
MesaLift is a fictional Utah founder project exploring a retrofit sensor and monthly monitoring service for independent automotive repair shops. The founder believes unexpected lift downtime is costly, but the current evidence is mixed. Nine shop managers were interviewed using a common question guide. Six recalled at least one lift-related interruption during the prior year, three described downtime as routine maintenance rather than an urgent business problem, and only two shared redacted maintenance logs. One five-bay shop signed a nonbinding letter to consider a paid pilot after a qualified safety review; another wants a free trial but refuses to install unproven hardware. The founder estimates a $149 monthly subscription and a $420 installation charge. A preliminary supplier email quotes $118 per sensor at 100 units, excluding enclosure, calibration, freight, installation, returns, and warranty. A competing preventive-maintenance contract costs roughly $900 per lift each year but includes inspections the proposed service cannot replace. The prototype currently detects vibration patterns on a bench; it has not been validated on an operating lift and no safety, electrical, insurance, or certification determination has been made. The founder has $28,000 available, wants to order 250 sensors, and hopes to raise capital within eight weeks. A collaborator says the algorithm is proprietary, yet the code repository contains an unreviewed open-source component with license obligations. The founder also drafted a pitch stating that MesaLift prevents failures and saves shops thousands, although neither claim is supported. Learners must turn this incomplete record into a staged, evidence-led venture plan. The goal is not to approve the product or predict success. It is to show how disciplined customer discovery, model design, economics, gates, responsibility, and claim control change the next decision.
Supported example — reference only
- Step or milestone
- Remove or substantiate prevention and savings claims before public release
- Trigger or date
- Before any marketing publication; calendar date not supplied
- Evidence and source ID
- M04-I06 (F11, confirmed)
- Owner
- Founder and authorized commercial reviewer
- Gate or threshold
- Proceed only when claims are removed or traceably supported and approved; otherwise revise, pause, or stop release.
- Dependency or gap
- Supporting test evidence and approval record: not supplied.
- Status
- Gate pending — public claim blocked
A well-handled evidence gap
- Step or milestone
- Define a funded milestone
- Trigger or date
- Founder seeks outside funding within eight weeks; start date and funded milestone not supplied.
- Evidence and source ID
- M04-I07 (F12, provisional)
- Owner
- Founder and authorized funding/commercial reviewer
- Gate or threshold
- Do not present a funding request until use of funds, measurable milestone, evidence, and approval are defined.
- Dependency or gap
- Milestone outcome, amount, use-of-funds schedule, and approval: not supplied.
- Status
- Gap open — funding representation blocked
Flawed approach — do not copy
Marking this ninety-day milestone plan “approved and complete” without the required evidence or reviewer is a flawed submission. Stop purchase, field use, unsupported claims, or funding representation when the corresponding evidence gate lacks qualified approval.
Repair: Rework the ninety-day milestone plan as an evidence-backed draft, not an approved result. List the irreversible commitments and place a separate evidence gate before each one. Build milestone rows backward from purchase, field, claim, and funding decisions rather than from desired activity dates. Attach supplied evidence and preserve bench-only, unknown, conflicting, confirmed, and provisional statuses exactly. Check the revision against this requirement: Every milestone produces evidence tied to a named irreversible decision. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.
Full case record, ambiguities and all assignments →