State of build
Which parts of this are real today, and which parts are you being asked to believe in?
What is built, and what is not
Publishing this is a commercial risk. Not publishing it is a bigger one.
Runcible Oversing runs today as a substantial multi-user institutional application in one production environment, with Runcible AI integrated in the same deployment. That is a real thing, and it is also not the same thing as a finished enterprise product. This page draws the line component by component.
If you are evaluating seriously, read this page before the others. It will tell you faster than anything else here whether the timing is right for you.
What runs today
Completeness is measured against what a production enterprise deployment would require, not against our own roadmap.
That distinction matters. A component can be finished by our standards and still incomplete by the standards of a regulated enterprise with an established security review, and it is the second measure that is useful to you.
Built and running (75% and above) Partial (45–74%) Early (20–44%) Outstanding (below 20%)
| Component | State | Completeness |
|---|---|---|
| Institutional object model | Built and running | 85% |
| Work, tasks, and operating state | Built and running | 85% |
| Roles, people, and responsibility | Built and running | 80% |
| Configurable workflow | Built and running | 80% |
| Permissions by state and role | Built and running | 78% |
| Approval and validation cycles | Built and running | 75% |
| Composable workspace and views | Built and running | 78% |
| Resourcing, scheduling, and forecast | Partial | 65% |
| Time, cost, and expenditure | Partial | 60% |
| Contracts, budgets, and invoicing | Partial | 50% |
| Runcible AI integration in the deployment | Partial | 55% |
| Delegated-authority configuration | Partial | 45% |
What is not established
Six areas, named the same way to investors and to you.
These are quoted from Runcible’s own governing statement of proof. They are not a softened customer-facing version of it.
| Area | State | Completeness |
|---|---|---|
| Modernisation of the application | Early | 30% |
| Security and enterprise hardening | Early | 25% |
| Generalised integration with other systems | Early | 20% |
| Repeatable implementation method | Early | 20% |
| Support capacity | Outstanding | 10% |
| Measured customer outcomes | Outstanding | 0% |
The last row is the one to sit with. Runcible has no measured customer outcomes, because Runcible has not yet run an implementation that would produce them. Everything this site describes is an enabled capacity. Where you see a capability described here, read it as the platform makes this possible, never as organisations using it achieved this.
What that means for an implementation
Concretely, what an early customer absorbs.
- Integration is bespoke.What can connect to your existing systems is determined per deployment. Do not assume a connector exists.
- Security review will find gaps.Enterprise hardening is genuinely early. If your procurement requires a completed enterprise security posture up front, the timing is wrong and we would rather establish that in the first conversation.
- Implementation is not yet repeatable.You get direct access to the people who built the system, which is better than a method in most respects and worse in one: it does not scale, so we can only do this with a few organisations at once.
- Support is not a desk.There is no tiered support organisation behind this today.
- You would be the evidence.An early implementation is how measured outcomes come to exist. That is the trade being offered, and it should be priced into your decision.
How this page is maintained
A maturity page that goes stale is worse than none at all.
This page is reviewed whenever a component’s state changes materially, and on a fixed quarterly cadence regardless. The date of the last review is stated below. If that date is more than one quarter old, treat the numbers as unverified and ask us directly.
Last reviewed: pending first publication.
Percentages are judgements, not measurements. They are our own assessment against enterprise-readiness, and reasonable people would place several of them a band higher or lower. They are published because a rough honest scale is more useful to you than a confident vague one.