Hypothetical case study
Founder-Led Secondary: A Hypothetical Case Study
A constructed case showing objective definition, stakeholder alignment, valuation, information control and closing gates.
Constructed scenario · not a customer result
Key takeaways
- — Liquidity, cap-table and governance objectives should be stated separately.
- — Transfer rights, information access and approvals shape the feasible process.
- — A hypothetical case illustrates a sequence; it does not claim a customer outcome.
Operating brief
Know when to use it, what it needs and what it must produce
When to use
- Use this resource when a team wants to examine decision sequencing, trade-offs and controls through a bounded teaching scenario.
- Use it at the planning or review stage for private-company liquidity, before an output is circulated or relied upon by Founders, Private-company boards, Investors.
- Reopen it after a material fact, document, assumption, market condition or rule changes in the applicable jurisdiction.
Required inputs
- A written objective defining the decision, intended user, transaction stage and permitted use for Founder-Led Secondary: A Hypothetical Case Study.
- A controlled source pack covering the case classification, starting facts, assumptions, alternatives, decisions and evidence status, with an owner, date and version for each item.
- A scope statement identifying included entities, periods, jurisdictions, materiality thresholds and explicit exclusions.
- A responsibility map naming the preparer, case-method editor, decision owner and any specialist reviewer.
- An open-items register that preserves missing information, conflicting evidence, estimates and unresolved dependencies.
Required outputs
- a decision map that separates facts from assumptions and identifies transferable and non-transferable lessons.
- A dated decision and exception log connecting every material issue to an action, approval, protection or accepted risk.
- A release record showing the approved version, reviewer, reliance boundary, next review date and superseded version.
Evidence standard
Build from attributable, current and reconcilable sources
- 01Use primary, regulator, exchange, issuer, contractual or directly attributable sources first; label secondary commentary as interpretation.
- 02Record a stable source identifier, publication or effective date, retrieval date, owner and permitted-use restriction.
- 03Reconcile repeated facts across financial, legal, commercial and operational records instead of selecting the most convenient value.
- 04Keep verified facts, management representations, estimates, assumptions and analyst judgments in separate fields.
- 05For the applicable jurisdiction, confirm current requirements and transition provisions with authoritative sources and qualified professionals.
Operating workflow
Seven controlled stages from question to maintained release
- 01
Frame the decision
State the private-company liquidity decision, intended user, required output, time horizon and reliance boundary. Convert broad interest into a question that can be answered and reviewed.
Gate: The sponsor approves the objective, scope, audience and exclusions.
- 02
Establish the evidence perimeter
Create the source register, request missing evidence and classify access restrictions. Record dates, versions and owners before analysis begins.
Gate: Critical sources are present or the decision owner accepts a documented evidence gap.
- 03
Normalize facts and assumptions
Reconcile definitions, periods, units, currencies, entity boundaries and transaction terms. Keep source facts separate from estimates and judgments.
Gate: Material conflicts are resolved, escalated or visibly carried as exceptions.
- 04
Build the working output
Apply this hypothetical case study to the approved inputs. Preserve source-to-output traceability, formula transparency and one accountable owner per work item.
Gate: The preparer completes every required field and records all deviations.
- 05
Challenge and test
Test completeness, internal consistency, reasonableness, downside conditions and compliance with the stated method. Ask what evidence would change the conclusion.
Gate: The case-method editor confirms that the scenario classification is explicit and no illustrative result is presented as a customer outcome.
- 06
Decide and release
Resolve or accept exceptions, obtain required specialist input and record decision authority. Lock the approved version before authorized circulation.
Gate: All critical exceptions have an owner and disposition, and release authority is evidenced.
- 07
Monitor and refresh
Track triggering events and complete the annual review. Version corrections and preserve the prior release so downstream users can identify what changed.
Gate: The next review date and event-driven triggers are assigned to an accountable owner.
Governance
Roles, responsibilities and release evidence
| Role | Responsibility | Required evidence |
|---|---|---|
| Decision sponsor | Owns the purpose, scope, materiality standard and final use of the private-company liquidity output. | Approved scope, decision record and accepted exceptions. |
| Preparer | Builds the source register, performs the work, records assumptions and maintains version control. | Completed working file, source links and preparer sign-off. |
| Case-method editor | Challenges the method, evidence, calculations, completeness and consistency independently of preparation. | Review notes, resolved comments and reviewer approval. |
| Specialist adviser | Confirms matter-specific legal, tax, regulatory, accounting or technical treatment in the applicable jurisdiction where required. | Dated advice, source citation or documented professional confirmation. |
| Release owner | Controls circulation, access, retention, correction notices and the next scheduled or event-driven review. | Release register, authorized recipient list and review date. |
Release controls
Quality checks required before reliance
- Completeness: every required field or work item is complete, marked inapplicable or carried as an explicit exception.
- Traceability: every material fact, formula and conclusion links to a dated source or documented assumption.
- Consistency: names, dates, units, currencies, definitions and transaction terms agree across the working pack.
- Challenge: a reviewer independent of preparation tests reasonableness, downside conditions and contrary evidence.
- Authority: required decision makers and qualified specialists approve matters within their responsibility.
- Release: the approved version, reliance boundary, recipients and superseded versions are recorded.
- Maintenance: the annual review and event-driven triggers have named owners.
Limitations and professional-review boundary
- — This resource is an educational and operational framework; it does not establish the facts or professional conclusions for a specific private-company liquidity matter.
- — Rules, filing practices, market conventions and professional responsibilities in the applicable jurisdiction may change after the stated update date.
- — Illustrative sequences, thresholds and outputs must be adapted to the governing documents, transaction structure, materiality and risk appetite.
- — No output should be treated as legal, tax, regulatory, accounting or investment advice without appropriate qualified review.
Starting condition and decision frame
In this constructed scenario, a founder seeks partial liquidity while the company wants a long-term investor and an orderly ownership register.
- — Define acceptable size and buyer profile
- — Review transfer and consent rights
- — Set confidential information boundaries
Illustrative execution sequence
The board aligns objectives, advisers verify constraints, a limited buyer set receives controlled information, bids are compared and approvals are tracked to closing.
- — Record conflicts and recusals
- — Reconcile valuation and tax inputs
- — Update registers after completion
Companion asset
Secondary decision map (PDF)
A structured working pack with the case workflow, evidence standards, roles and release controls.