Tooling Shaped to How You Govern
The EO Platform is built on Unix philosophy and everything as code: each tool does one thing well, and the ownership assignments, decision rights, and governance records it operates on are plain text you own. That is what makes it adaptable rather than something you conform to.
Custom development is the hands-on work of shaping it to a specific organization — building the tools, integrations, and orchestration that make the model enforceable given the governance structures you already have. It is for organizations that do not want to, or cannot, build that adaptation themselves.
What the Work Covers
New tools composed into the pipeline — where a governance activity in your context has no tool yet, building one that takes clean input, produces clean output, and composes with what is already there.
Integration with the systems you already run — identity providers, HR systems, board or committee tooling, ticketing. The platform routes and records; it does not ask you to replace what works.
Orchestration for your structure — routing decisions and escalations to the people who actually hold the authority in your organization, and flagging drift against your specific ownership map rather than a generic one.
Migration into everything-as-code — moving existing org charts, RACI matrices, and decision logs out of slides and spreadsheets into plain-text, version-controlled form, so the history survives the tooling.
No Lock-In by Construction
Because every record is plain text and human-readable without the tooling, what gets built stays yours. If you stop working with me, the data is still legible and the tools still run. That is a property of the platform’s design, not a promise layered on top.
Ownership and the License
The platform’s source is licensed under the AGPL, which means changes to it are expected to be published — upstreamed into the platform itself if they are generically useful, or released under the same license if they are not. That is the default, not a courtesy. If you need to keep specific custom work proprietary — an integration or orchestration piece that reveals more about your governance structure than you want public — that is available as a separate commercial license exempting that work from the AGPL’s publication requirement, priced accordingly. The exemption license is available on its own, too — if your own team builds the change, you do not need to engage me for the development to get it.
A Good Fit If
The model fits your organization but the standard tooling does not quite reach your governance structure. Or you want the platform running against real decisions rather than evaluated in the abstract.
If what you actually need is the organization’s own capability built up, that is EO Team Enablement. If you need the seat held and the structural decisions made, that is Enterprise Architect (Interim). If the model itself, not the tooling, is what does not fit, that is EO Model Custom Adaptation.
If you want the platform running against your own governance structure, get in touch — early engagements also shape where the platform goes next.