We say the awkward parts early, because they explain the competitive picture rather than apologizing for it.
A measure is defined once, stored in the product, and used by every view that quotes it. Two people building the same report get the same number.
Where a figure isn't computed, we say so instead of filling the gap with a zero. A page that hides a gap teaches you to distrust every number on it.
This version manages work with a start, a finish, a budget and a plan. Operations management is the next version — and we say that in the first conversation.
| Area | Status | Detail |
|---|---|---|
| Analytics, Budget, Vitals, Finance, Change | Shipped | Deployed and demonstrable across many buyer profiles from one codebase. |
| Commercial availability | Pilot | Built and deployable; not yet taking payment. Closing that gap is the top of the plan. |
| Single sign-on | Roadmap | Not built. On the plan. |
| Public API | Roadmap | Designed, not built. |
| SOC 2 | Roadmap | Checklist maintained against the actual system; certification not yet pursued. |
| Operations & org-wide procurement | Roadmap | The next version. The codebase is shaped for the extension. |
We'll run these cuts against a slice of your own completed projects — not our demo data. If the answers are dull, that's worth knowing early, and we'll say so.
Book a demo