Foundry Academy · Founder Business Fundamentals · Lesson 6 of 6

Founder narrative and evidence room

Create a concise venture narrative whose claims can be traced to organized, current, permissioned evidence.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Founder narrative and evidence room

Objective: Create a concise venture narrative whose claims can be traced to organized, current, permissioned evidence.

A founder narrative should explain the customer problem, current alternatives, offer, proof, model, economics, team, risks, milestones, and use of resources in a sequence a skeptical reader can follow. Lead with what is known, not adjectives. Distinguish historical facts, current measures, forecasts, and goals. Define the period and denominator behind traction metrics. If a customer name, quote, logo, or result is used, confirm permission and preserve the approval. Tailor the depth to the audience without changing the underlying facts. Never imply a commitment, partnership, patent status, approval, or funding relationship that does not exist.

The evidence room is an indexed set of controlled records, not a dump of every file. Organize folders by corporate, market, product, financial, commercial, team, legal, and risk categories as applicable. Maintain an index with owner, date, version, source, access class, and expiration or review date. Restrict confidential files to people with a legitimate need, and do not place trade secrets or personal financial data in public links. Qualified counsel and accountants should determine which legal, tax, securities, and financial records are appropriate for a specific transaction. Before sharing, perform a claim-to-source check and remove stale, duplicated, or unauthorized material.

Before you begin

  • Confirm interview count, redacted logs and nonbinding letter, provisional offer, bench-only evidence, unknown requirements, IP conflict, unsupported claims, and provisional funding timing.
  • Define the audience and permitted evidence-room access before drafting narrative sections.
  • Classify each statement as fact, estimate, forecast, goal, conflicting, or unknown.

Original overview module anchor →

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

Section or slide
Prototype evidence boundary
Purpose
Explain what has and has not been demonstrated before discussing product readiness.
Supported content
The prototype has only been exercised on a bench, not on an operating vehicle lift.
Source input ID
M06-I04 (F07, confirmed)
Accessibility or format note
Field-validation evidence: not supplied. Place the limitation adjacent to any prototype description; do not imply field validation.
Reviewer
Founder and qualified technical reviewer
Status
Sourced draft — technical review pending

A well-handled evidence gap

Section or slide
Safety and installation requirements
Purpose
Disclose the readiness question without offering a technical conclusion.
Supported content
Applicable safety, electrical, insurance, installation, and certification requirements are undetermined.
Source input ID
M06-I05 (F08, unknown)
Accessibility or format note
Label unknown prominently; requirements and approved public wording are not supplied.
Reviewer
Qualified technical, safety, insurance, installation, and certification reviewers
Status
Gap open — external readiness claim blocked

Flawed approach — do not copy

Marking this two-page founder-brief outline “approved and complete” without the required evidence or reviewer is a flawed submission. Stop external release when any material claim lacks a source, permission, accurate confidence label, or qualified review.

Repair: Rework the two-page founder-brief outline as an evidence-backed draft, not an approved result. Inventory every proposed founder-brief statement and link it to its module source input before writing prose. Separate customer evidence, offer, prototype state, requirements, IP, claims, and funding goals into distinct sections. Remove prevention and savings language unless a source supports it; preserve bench-only limitations prominently. Check the revision against this requirement: Every material statement is classified and traceable to an input or explicitly marked not supplied. 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 →

03 · Bounded practice

Build the two-page founder-brief outline.

Rewrite the pitch so a skeptical reader can trace every material statement and unresolved risk.

Deliverable: A two-page founder brief, claim-to-source matrix, and redacted evidence-room index.

Complete a bounded starter and gap analysis using only CB01, F01, F03, F04, F07, F08, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M06-I01 · F01 — Nine shop-manager interviews were completed from one shared discussion guide.
  • M06-I02 · F03 — Two shops supplied redacted maintenance logs and only one signed a nonbinding pilot-interest letter.
  • M06-I03 · F04 — The working offer is a $149 monthly subscription plus a $420 installation charge.
  • M06-I04 · F07 — The prototype has only been exercised on a bench, not on an operating vehicle lift.
  • M06-I05 · F08 — Applicable safety, electrical, insurance, installation, and certification requirements are undetermined.
  • M06-I06 · F10 — A collaborator calls the algorithm proprietary while the repository contains an unreviewed open-source dependency.
  • M06-I07 · F11 — Draft marketing says the product prevents failures and saves thousands without supporting test evidence.
  • M06-I08 · F12 — The founder wants outside funding within eight weeks but has not defined a funded milestone.
  • M06-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M06-S01 · F01, F03, F04, F07, F08, F10, F11, F12 — Build a starter version of “A two-page founder brief, claim-to-source matrix, and redacted evidence-room index.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Inventory every proposed founder-brief statement and link it to its module source input before writing prose.
  2. Separate customer evidence, offer, prototype state, requirements, IP, claims, and funding goals into distinct sections.
  3. Remove prevention and savings language unless a source supports it; preserve bench-only limitations prominently.
  4. Label the working offer and funding timing provisional, the requirements unknown, and the IP statement conflicting.
  5. Add permission, access class, version, owner, and review-date fields in the companion claim and evidence-room records.
  6. Route public claims, IP, safety, technical, and investment language to the appropriate authorized reviewers.
  7. Perform a claim-to-source back-check and a redaction/access check before any external release.
Field-by-field guidance
Section or slide
Name the founder-brief section, such as Customer evidence, Prototype boundary, Offer, Risks, or Funded milestone.
Purpose
State the decision the section helps a reader understand, not a promotional slogan.
Supported content
Use only supplied facts and preserve confidence, limitation, and contradictory evidence.
Source input ID
Cite the matching M06-Ixx input for every material statement.
Accessibility or format note
Specify plain-language limitation, readable heading, and redaction or access requirement where applicable.
Reviewer
Name the authorized content owner and qualified technical, IP, safety, or funding reviewer as required.
Status
Use Draft sourced, Gap open, Specialist review required, Permission pending, or Release blocked.
Two-page founder-brief outline · learning draft
Section or slidePurposeSupported contentSource input IDAccessibility or format noteReviewerStatus

Start with 6 rows; the complete workbook specifies 6 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 6 · 2-item formative check

Founder narrative and evidence room

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 6 · knowledgeWhich treatment belongs in a responsible founder narrative and evidence room?
Question 2 of 2 · MODULE 6 · scenarioHow should MesaLift address the conflict between a proprietary-algorithm claim and an unreviewed open-source dependency?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Every material statement is classified and traceable to an input or explicitly marked not supplied.
  • Unsupported prevention and savings claims are removed or clearly identified as prohibited.
  • Permission, access, version, owner, and review status are represented in the companion controls.

Stop: Stop external release when any material claim lacks a source, permission, accurate confidence label, or qualified review.

Go: Go to internal review when every section is source-linked and all limitations, permissions, and access classes are visible.

Escalate: Escalate IP, safety, technical, legal, investment, savings, and prevention statements to qualified owners before public use.

04 · Evidence to keep

Leave with usable work.

Versioned narrative, claim-to-source matrix, permission log, evidence-room index, access classification, and missing-evidence list.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Founders mapping a business plan together around a conference table.
Learn the standard. Practice the work.
Business team testing a venture plan during a modern office presentation.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

sba-plan-your-business · Official guidance

Plan your business

Current SBA consolidated guidance containing the market-research, business-plan, and startup-cost sections used in Modules 1–3.

Open reviewed external source ↗

nist-privacy-framework · Official guidance

NIST Privacy Framework

Primary voluntary framework for governing privacy risk in data collection, use, communication, and protection.

Open reviewed external source ↗

irs-starting-a-business · Official guidance

Starting a business

Official IRS starting-business overview used to identify federal tax, entity, EIN, and recordkeeping dependencies; it is a planning boundary and not individualized tax or legal advice.

Open reviewed external source ↗

ws-founder-operating-standard · Academy internal operating standard

Wealth Synergy founder evidence and decision-gate internal operating standard

Academy-selected milestone, responsibility, scorecard, evidence-room, and review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.