Where this is going, without the dates we cannot hold
Roadmaps with quarters on them are usually fiction by the second quarter. This one publishes order and status instead: what is running, what is being written, and what is designed and waiting. When something moves, this page moves with it.
Live
LiveRunning in production and available to use. If it is here, you can point it at something today.
1 of 12
Web Compliance Agent
Scans a website for accessibility, SEO and security-header problems and returns a prioritised fix list.
In build
In buildCode is being written now. These are the next things to cross into live, in roughly the order listed.
4 of 12
Messaging Agent
Turns the traffic across your messaging channels into tasks, deadlines and answers, with reply drafts you approve.
Unified Dashboard
Every module in one workspace, with a single view of what needs you now.
Calendar & Reminders
One calendar of record. Deadlines land automatically and chase themselves.
CRM
Contacts, deals and follow-ups that keep themselves current so nothing slips.
Planned
PlannedDesigned, scoped, and not started. Listed because you deserve to know where the platform is going before you commit to it — and labelled, because you should not have to discover the difference after signing.
7 of 12
Cybersecurity Posture
Continuous posture scoring mapped to the frameworks your buyers actually ask about.
Regulatory Compliance
Jurisdiction-aware obligations, consent records and breach workflows in one place.
Research Agent
Multi-source research returned with its citations, including market and trade-show intelligence.
ERP · MRP
Inventory, demand and resource planning that anticipates instead of reacting.
Email Agent
Triages the inbox, surfaces what needs you, and drafts the rest for a one-tap approval.
Business-Case Agent
Models, projections and board-ready narratives built from your own operating data.
Knowledge Management
The answer your team needs, with the document it came from attached.
How something moves from planned to live
A module becomes in build when it has a schema, a permission model and a first working path — not when it has a design document. It becomes live when it is running in production against real data, with the audit trail and the approval gate wired in. Nothing skips the gate to hit a date, because the date is not published in the first place.
If a module you need is on the planned list, that is worth a conversation. Order is not fixed, and a customer who needs something is the best reason we have to build it next.
Need one of the planned ones sooner?
Tell us which, and what it has to do on day one. Sequencing follows real demand more than it follows our preferences.