CapitalOS — Customer Zero begins
OSG became CapitalOS's Customer Zero from this point forward. Every governance, documentation, and process decision on CapitalOS since has been tested against this real engagement rather than an inferred external market.
This entry uses OSG's earlier framing of CapitalOS as fundraising infrastructure — accurate when it was recorded. See Entry 05 for how that framing changed. Preserved as written, per the Decision Framework — we don't edit a record to sound like we knew the answer from the start.
This entry predates the clarification that OSG and CapitalOS are separate companies under a commercial engagement — see Entry 06. Where this entry describes CapitalOS in terms that could read as an internal OSG product, treat Entry 06 as the current, governing description of the relationship.
What changed
CapitalOS was scoped as fundraising software for founders — templates and tooling built for a customer we had not yet spoken to.
Alternatives considered
- Keep the founder-facing positioning and validate it through founder interviews before building.
- Build the founder-facing product and adjust based on early user feedback after launch.
- Abandon the fundraising-infrastructure idea and pursue a different initiative.
What was decided
Reposition CapitalOS: build it first as infrastructure for OSG's own institutional raise. Founder-facing availability contingent on that raise succeeding.
Why
Designing for an inferred customer produces assumptions dressed up as requirements. OSG had a real, unavoidable need and no trusted tool to meet it. Building for that need directly removes the inference problem, at the cost of a smaller initial audience of one.
What evidence informed it
The absence of trusted institutional-grade fundraising infrastructure was a first-hand, direct constraint on OSG, not a market signal inferred from outside research.
What happens next
Revisited in full once 'a completed raise' turned out to be the wrong graduation test — see the CapitalOS thesis pivot.
Impact
OSG became CapitalOS's Customer Zero from this point forward. Every governance, documentation, and process decision on CapitalOS since has been tested against this real engagement rather than an inferred external market.
Institutional Learning
What every entry is ultimately for — not just recording that something happened, but what changed because it did.
Sustained, adversarial scrutiny of the founder-facing thesis, applied before any product code was written.
CapitalOS's intended first customer changed from an inferred external founder to OSG itself.
OSG became Customer Zero. Every subsequent CapitalOS decision has been tested against a real, internal need rather than an assumed external one.