Founder & Finance School · Learning track
Build a venture around evidence, economics, and a manageable operating cadence.
Start Lesson 1No 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.
A different tab changed this track. Nothing was overwritten. Export your current draft first if needed, then load the saved version before editing and saving again.
01 Learning plan
Public foundation 2026.10.08-learning-paths-1 · published 2026-10-08. Independent subject-matter review is pending; paid delivery and credential issuance remain closed. This track is organized around inspectable work, not attendance alone.
Workload
No validated completion time is published. Read the six modules, then complete the six case assignments and self-review across as many sessions as needed. This release has not yet been timed with learners; no facilitated capstone is included.
Prerequisites
Outputs
Working vocabulary
02 Public foundation curriculum
Each module states what to understand, what to practice, what evidence to retain, and the criteria for moving forward. The case lab turns those standards into six realistic assignments.
Module 1
Objective: Define a narrow buyer, user, problem, and current alternative, then distinguish observed evidence from founder interpretation.
Open Lesson 1: examples, worksheet & feedback →Begin with a situation, not a product description. Name who experiences the problem, when it occurs, what they do today, and what the current approach costs in money, time, risk, or missed opportunity. Separate the buyer from the user when they are different. A useful segment is specific enough that its members share a buying context and a reason to act. Broad labels such as small businesses or consumers hide important differences. Record the source and date of every market fact, and mark estimates as estimates. Secondary research helps size and structure the field; it does not prove that a particular person will buy.
Use customer conversations to investigate past behavior rather than request praise for the idea. Ask for a recent example, the trigger, the workaround, who approved spending, and what made the issue urgent or tolerable. Do not lead with a pitch or count polite interest as demand. After each conversation, capture direct observations, your interpretation, contradictory evidence, and the next question. Evidence strength rises when independent sources converge, a customer commits scarce time or money, or a test reproduces the result. It falls when the sample is convenient, the question is leading, or the claim cannot be traced. Protect interviewees' privacy and obtain permission before recording or quoting them.
Practice
Conduct three neutral discovery conversations and build a one-page evidence table that includes at least one contradiction to the original idea.
Evidence to keep
Interview notes with consent status, source links, dated observations, and a written problem statement naming buyer, user, trigger, alternative, and consequence.
Ready to move on when
Module provenance
Mapped sections or criteria: Market research and competitive analysis
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 2
Objective: Map how the venture creates, delivers, and captures value and identify the dependencies most likely to break the model.
Open Lesson 2: examples, worksheet & feedback →A business model is a connected set of choices, not a poster filled with slogans. Describe the customer, problem, offer, channel, revenue mechanism, major activities, key resources, partners, and cost structure in operational language. Then trace one order from awareness through purchase, delivery, support, payment, and renewal or replacement. This reveals handoffs and costs that a high-level model can hide. For each element, identify the evidence already available and the person responsible for keeping the information current. Do not treat a partner, supplier, or channel as secured unless the relationship and terms have been confirmed.
Stress-test the connections. A model can have real demand and still fail because acquisition cost is too high, cash arrives after suppliers must be paid, delivery capacity is constrained, or a regulated activity requires qualified support. Build a dependency map showing what must happen before the next step can occur. Rank assumptions by business impact and evidence strength, then design the cheapest responsible test for the high-impact, low-evidence items. The purpose is not to predict every detail. It is to expose where one attractive assumption is carrying several downstream promises and to prevent a planning document from disguising that concentration of risk.
Practice
Trace a single representative order through the full model and identify the five dependencies with the greatest combined impact and uncertainty.
Evidence to keep
A dated business-model map, order-flow diagram, dependency register, and ranked assumption backlog with owners.
Ready to move on when
Module provenance
Mapped sections or criteria: Write your business plan · What new business owners need to know about federal taxes
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 3
Objective: Construct an offer and price hypothesis that reflects customer value, delivery reality, and a transparent preliminary margin model.
Open Lesson 3: examples, worksheet & feedback →An offer combines a defined result, scope, conditions, price, and credible reason to believe. State what the customer receives, what is excluded, how delivery works, and what the customer must contribute. Compare direct competitors, substitutes, internal workarounds, and doing nothing. Their prices are reference points, not instructions. Test the language and package with relevant buyers before assuming that a feature creates value. Avoid unsupported savings or performance claims. If a claim depends on future testing, label it as a hypothesis and identify the evidence required before it can appear in marketing or sales material.
Build unit economics from explicit inputs. For a product, include selling price, discounts, materials, conversion, packaging, freight, duties, payment fees, expected returns, warranty, and variable support. For a service, include delivery labor, contractor cost, tools, payment fees, rework, and other costs that change with the engagement. Calculate contribution dollars and contribution margin, then test low, base, and high cases for price, cost, volume, and returns. Do not present preliminary economics as audited financial information. Taxes, revenue recognition, accounting classification, and financing decisions require review by qualified accounting, tax, or financial professionals when applicable.
Practice
Create three offer packages and a low-base-high unit-economics model; test the packages with at least two relevant buyers without offering a false deadline.
Evidence to keep
Offer sheet, source-backed reference-price table, documented cost assumptions, sensitivity model, and buyer feedback notes.
Ready to move on when
Module provenance
Mapped sections or criteria: Calculate your startup costs · Write your business plan
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 4
Objective: Turn the venture thesis into a staged plan in which spending and commitments follow evidence rather than optimism.
Open Lesson 4: examples, worksheet & feedback →A milestone should demonstrate a changed state, not merely that activity occurred. Replace tasks such as finish research with outcomes such as eight target buyers confirm the same costly workflow and two accept a paid pilot under defined terms. For each milestone, specify the evidence, due window, accountable owner, budget ceiling, and dependency. Distinguish reversible experiments from commitments such as tooling, leases, hiring, inventory, public claims, or financing. Schedule decision gates before those commitments. The gate must state who decides and what choices are available: proceed, revise, pause, or stop.
Maintain a risk register that covers market, technical, supply, financial, legal, privacy, security, operational, and team risks relevant to the venture. Score consistently, but do not let a numeric score replace judgment. Record the cause, possible event, consequence, existing control, early warning, owner, and response. Escalate matters that require licensed or regulated expertise. A founder cannot self-approve a legal conclusion, engineering certification, tax treatment, or investment representation through a project checklist. Review the plan at a fixed cadence and update assumptions when evidence changes; preserve prior versions so later decisions can be understood.
Practice
Convert a ninety-day task list into five evidence milestones, two formal decision gates, and a risk register with ten venture-specific entries.
Evidence to keep
Milestone map, gate briefs, risk register, change log, and dated decision record signed or acknowledged by the authorized owner.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 5
Objective: Establish decision rights, recurring reviews, and visible work controls that a small venture can actually maintain.
Open Lesson 5: examples, worksheet & feedback →Young ventures often confuse involvement with accountability. For each recurring process and important decision, name one accountable owner, contributors, required inputs, authority limits, and the escalation path. A responsibility map should clarify who decides pricing exceptions, approves spending, changes product requirements, publishes claims, accepts supplier deviations, and communicates with funders or customers. Avoid assigning a committee as the owner. Separate access to systems and money where practical, and document approval thresholds. Founders remain responsible for decisions even when specialists prepare analysis or coordinate work.
Choose a small operating cadence. A weekly review can cover customer evidence, cash, delivery, pipeline, product or supply issues, risks, and the decisions due next. Use a consistent scorecard with definitions and owners; do not add a metric unless someone will act on a change. Record decisions, assumptions changed, actions, owner, and date. Monthly, compare actual results with the plan and remove routines that create reporting without learning. The objective is faster, more reliable decisions, not more meetings. Confidential, financial, employment, or regulated information should remain in approved systems with access based on role and business need.
Practice
Design and run one simulated weekly operating review using a seven-metric scorecard, decision log, and responsibility map.
Evidence to keep
Meeting agenda, metric dictionary, responsibility map, approval thresholds, decision log, and action register from the simulation.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 6
Objective: Create a concise venture narrative whose claims can be traced to organized, current, permissioned evidence.
Open Lesson 6: examples, worksheet & feedback →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.
Practice
Write a two-page founder operating brief and build a redacted evidence-room index that supports every material claim in the brief.
Evidence to keep
Versioned narrative, claim-to-source matrix, permission log, evidence-room index, access classification, and missing-evidence list.
Ready to move on when
Module provenance
Mapped sections or criteria: Write your business plan · What new business owners need to know about federal taxes
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Free operational lesson
List every belief that must be true for the venture to work. Score each belief by impact and strength of evidence. Test the highest-impact, lowest-evidence assumption before expanding the plan.
Start each work cycle by naming the decision, its owner, deadline, consequences, and minimum evidence needed.
Label observations, sourced facts, estimates, interpretations, and assumptions so confidence is visible rather than implied.
Prioritize assumptions that combine high business impact with weak evidence, then use the smallest ethical test that could change the decision.
Date sources, retain versions, record permissions, and connect each change in direction to the evidence that caused it.
Review evidence before tooling, inventory, hiring, public claims, debt, or equity commitments that are difficult to reverse. Validate the problem without disclosing enabling technical details. Before a public demonstration, publication, offer for sale, crowdfunding campaign, or another disclosure that could affect intellectual-property rights, obtain timely advice from qualified IP counsel. A commercial evidence gate does not determine patent strategy.
Worked example
A founder believes independent repair shops will buy a sensor that predicts equipment failure. Four friends like the concept, but no shop has committed time or money.
Everyone hates downtime, the market is huge, and our revolutionary sensor will save shops thousands. We need funding to finish the product and launch nationally.
We are testing whether multi-bay repair shops with recurring lift downtime will pay for earlier warning. Six of nine interviewed managers described the same failure pattern; two supplied maintenance logs and one agreed to a paid, non-production pilot subject to safety review. Price, sensor accuracy, certification needs, installation cost, and false-alert tolerance remain unproven. The next gate is a controlled feasibility test and buyer review. Before disclosing enabling technical details or making a public offer, the founder will obtain timely advice from qualified IP counsel; this commercial test does not decide patent strategy.
Why it matters: The improved narrative is narrower and less dramatic, but it is more useful because it shows sources, commitments, unresolved risks, and the next responsible decision.
03 Control the work
Common failure modes
Positive comments are weak evidence unless the person fits the segment and makes a meaningful commitment such as time, data, a pilot, or payment.
Industry totals do not establish reachable customers, purchase frequency, conversion, capacity, or the economics of the venture's actual channel.
A detailed spreadsheet can still be speculative. Mark sources, ranges, dates, confidence, and sensitivity instead of presenting one precise case as fact.
Capital without a staged use-of-funds plan can accelerate waste. Tie each amount to evidence, a decision gate, and a value-creating milestone.
Operating measures
Percentage of critical assumptions with current, traceable evidence above the team's stated minimum standard.
Use it to decide: A low rate directs the next work cycle toward validation rather than expansion or irreversible spending.
Low, base, and high estimates of selling price less variable delivery cost, expressed in dollars and percent.
Use it to decide: If the low and base cases cannot support acquisition, overhead, and risk, revise price, scope, cost, or segment.
Share of due milestones that meet their predefined evidence criteria without waivers or retrospective rewriting.
Use it to decide: Repeated misses trigger scope, owner, capacity, or thesis review before the next commitment.
Days that material decisions remain open beyond their agreed decision date.
Use it to decide: Long aging requires escalation, a smaller test, or an explicit pause rather than silent drift.
04 · Applied case lab · 2026.08.31-practice-3
The packet contains contradiction and incomplete evidence on purpose. Each assignment now identifies the exact fictional inputs available to the learner. Complete a bounded starter, mark missing records instead of inventing them, and compare your reasoning with the debrief—not with a pretend single perfect answer.
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.
CB01 · citable versioned case brief
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.
Judgment required: Decide whether evidence supports another narrow test, a different segment, or a pause, and state what observation would change that decision.
Do not assume: Do not interpret interview agreement, a nonbinding letter, or a broad downtime estimate as proven demand.
Judgment required: Separate technical differentiation from ownership and licensing questions, then gate external claims pending qualified review.
Do not assume: Do not represent patent, copyright, trade-secret, or license status without appropriate evidence and counsel.
Bounded case starter
Separate interview observations from founder interpretation and decide which segment merits the next ethical test.
Deliverable: A starter customer-and-problem evidence table at the aggregate level, a missing-interview-record gap log, and a revised problem statement.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F09, 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.
Workbook plan: 3 authored artifacts with 5 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The strongest analysis narrows the segment and preserves negative evidence. It treats log sharing and conditional pilot interest as stronger than compliments, while recognizing that one commitment is not market proof.
Bounded case starter
Map one order from awareness through installation, monitoring, support, renewal, and end-of-service handling.
Deliverable: An order-flow diagram and ranked dependency register with accountable owners.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F04, F05, F07, F08, F09, 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.
Workbook plan: 2 authored artifacts with 4 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The model should reveal installation, monitoring, support, data, and supplier dependencies. A learner may choose different channels, but every choice must expose who performs the work and when cash moves.
Bounded case starter
Test the proposed offer without converting unknown safety or cost assumptions into facts.
Deliverable: Three offer packages and a sourced low-base-high unit-economics worksheet.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F04, F05, F06, F09, 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.
Workbook plan: 2 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: A credible model uses ranges because several costs are missing. The purpose is to identify breakpoints and next quotes, not to manufacture a precise margin from incomplete inputs.
Bounded case starter
Replace the immediate 250-unit order and generic raise with evidence milestones and formal decision gates.
Deliverable: A bounded ninety-day milestone starter, a risk register covering the material risks supported by F06 through F12, and one pre-purchase and one pre-field decision-gate brief.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F06, F07, F08, F09, 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.
Workbook plan: 4 authored artifacts with 10 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: A responsible gate defers inventory and claims until technical feasibility, buyer behavior, and cost evidence improve. Different budget ceilings can be defensible when the evidence threshold is explicit.
Bounded case starter
Clarify who may approve claims, spending, repository use, pilot conditions, and customer communication.
Deliverable: A responsibility map, approval matrix, weekly agenda, and seven-metric scorecard.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F06, 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.
Workbook plan: 4 authored artifacts with 13 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Authority should not follow enthusiasm. The founder remains accountable, while qualified specialists decide matters within their competence and reviewers can block unsupported public claims.
Bounded case starter
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.
Completion boundary: 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.
Workbook plan: 3 authored artifacts with 10 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The best narrative is candid about what is unknown. Traceability and controlled access make the brief useful without exposing sensitive records or implying validation that has not occurred.
Self-review standard
There is no single universal go-or-stop answer. A strong submission shows how evidence quality, reversibility, safety, and cash exposure determine the next bounded decision. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.
Route to: Appropriately qualified engineer, safety reviewer, insurer, and applicable certification or regulatory specialist
Learner boundary: The learner organizes questions and evidence but does not approve technical safety or compliance.
Route to: Qualified IP or business counsel and accounting, tax, or authorized financing professionals as applicable
Learner boundary: Training artifacts are not professional opinions and cannot authorize claims or a capital transaction.
05 Editable working tool
Record one critical belief per row. Use a direct source or observation for current evidence, choose a test that could disconfirm the belief, and assign a real owner and review date. Add as many rows as needed, export a CSV, or print only this tool. Entries are not transmitted. They last only in this tab unless you opt into device-only saving in the learning-work panel. No account or cross-device sync is provided.
| Assumption | Why it matters | Current evidence | Next test | Owner and date |
|---|---|---|---|---|
Completed example
Data boundary: Work only in an approved system. Do not place passwords, payment-card data, government identifiers, health information, export-controlled material, client secrets, or unpublished invention details in this public worksheet.
Each two-question check works independently. Review any answered question immediately; you do not need to finish all twelve. Feedback is formative, not a verified grade or credential.
07 Sources and handoffs
Module provenance distinguishes external authorities, legal-status evidence, and Wealth Synergy internal operating standards. Requirements change; verify current source text and obtain qualified advice when a decision carries legal, financial, technical, employment, safety, or regulatory consequences.
sba-plan-your-business · Official guidance
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
Primary voluntary framework for governing privacy risk in data collection, use, communication, and protection.
Open reviewed external source ↗irs-starting-a-business · Official guidance
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
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 ownerUse the Validate stage when the founder needs a coordinated customer, market, pricing, and preliminary economics evidence plan.
Explore the handoff →Use Funding Navigator only after the capital need, milestone, eligibility facts, repayment capacity, and ownership preferences are explicit.
Explore the handoff →Future facilitated pathway · not open
The public case lab is available now. A future facilitated cohort may add assignments, feedback, and human capstone review only after a named qualified facilitator and reviewer, schedule, rubric, privacy controls, support, price, refund terms, and delivery terms are published in writing. No enrollment or payment is accepted here.
Course material supports professional development. It does not replace legal, tax, accounting, cybersecurity, engineering, regulatory, employment, translation, or other qualified professional advice where that expertise is required.
The public knowledge check and portal review markers are learning aids only. They do not award a credential. Pilot curriculum and credential assessment are in quality review; Foundry Academy is not currently representing these pages as accredited instruction or an automatic path to a certificate.
Participation does not guarantee employment, client work, funding, licensure, certification by a public authority, or any business outcome.
Use the public foundation
All public materials and case files are available without enrollment. A fit conversation is non-binding and does not reserve a place in a future pilot.
Ask about this track