CapitalOS is structured as a separate company from OSG
Corrected the site's description of the OSG/CapitalOS relationship everywhere it appeared, and established the conditional related-party disclosure language now standard on every page describing the relationship.
What changed
CapitalOS originated as a methodology OSG developed to solve its own institutional readiness and fundraising challenges, with OSG as the first implementation environment. As the methodology proved itself, it became clear it had commercial value independent of OSG.
Alternatives considered
- Keep CapitalOS as an internal capability of OSG, available only to OSG.
- Spin CapitalOS out as a fully independent company with no formal relationship to OSG beyond its origin.
- Structure CapitalOS as a separate company while OSG continues as its Customer Zero client under a documented commercial engagement.
What was decided
Adopt the third option. OSG and CapitalOS are separate legal and commercial entities. Neither owns the other. OSG remains Customer Zero under a documented commercial agreement with defined scope, milestones, governance provisions, and commercial terms. Beneficial ownership and governance structure between the two companies have not yet been formalized.
Why
Keeping CapitalOS internal forfeits commercial value once the methodology generalizes beyond OSG's specific needs. A fully independent spinout with no formal relationship forfeits the Customer Zero evidence that makes the methodology credible. A separate company under a documented engagement preserves both.
What evidence informed it
A direct strategic clarification, made explicitly because earlier site content described CapitalOS as though it were OSG's own internally-built product — an inaccuracy identified and corrected once the actual corporate structure was stated plainly.
What happens next
Reviewed once beneficial ownership and governance structure are formally finalized. If the parties are determined to be related parties under applicable standards, this record and the site's disclosure language will be revisited.
Impact
Corrected the site's description of the OSG/CapitalOS relationship everywhere it appeared, and established the conditional related-party disclosure language now standard on every page describing the relationship.
Institutional Learning
What every entry is ultimately for — not just recording that something happened, but what changed because it did.
Site content was found to describe a corporate relationship that no longer matched the actual structure.
CapitalOS's status changed from an implied internal capability of OSG to an explicitly separate, commercially engaged company.
OSG's public materials now require a standing disclosure discipline for a relationship that isn't yet fully resolved — related-party status pending formal determination.