One product shipping. One set of engines underneath.
Portfolio and Engagements have separate buyers and can be bought separately. They are not separate systems. A customer record written by one is read by the other one, with no integration in between, because it is the same code and the same record.
Every product reads the same customer.
Before any engine runs, there has to be one account, one set of contacts, one contract and one ARR figure that everything agrees on. That foundation is platform, not product, which is why a health score and a renewal quote never disagree about what the customer is worth.
Every record carries its origin, so you can always tell what came from your CRM and what was created here. Your CRM stays the system of record for the account; the fields it does not hold (health, renewal posture, delivery status) live here and write back only where you enable it.
The assistant built into the platform.
Mira is our AI assistant. She sits inside Portfolio and Engagements rather than beside them, so she can read one customer’s whole history (the calls, the tickets, the survey answers, the renewal) and answer questions about it.
She works the way a good analyst does. Every insight arrives with a confidence figure, the signals behind it, and a sentence on why she raised it. She proposes the work and stops there. Nothing touches a customer record, and nothing reaches a customer, until one of your team approves it.
Ranked by severity with the ARR attached. Each one carries a confidence percentage, the signal it came from, and a sentence on why it surfaced. Approve or dismiss, and both are recorded.
Write her guidance in your own words: how your team prepares an executive review, what a QBR has to cover, and when to apply it. Enable, pause or edit it later. We do not write these for you.
Executive summary, objectives, questions to ask, open risks, outstanding commitments, and a recommended tone. Versioned, so you can see what she knew last quarter.
A follow-up email is written and then sits there. Delivery is a separate step someone triggers. She drafts; a person sends.
Conversations she can hold, and share with a colleague. Transcript search across every recorded meeting, jumping to the timestamp.
She reads through your own role and field permissions. She cannot summarise a record you would be refused if you opened it yourself.
Then it runs on its own.
Most processes fail because someone has to remember them. Everything below is a template your team writes plus a trigger or a clock that fires it, with no scripting and nothing for IT to schedule.
Your administrators build all of it. None of it is a professional-services engagement, and none of it needs a ticket to us.
Your team runs it, without asking us.
Configuration that needs a support ticket is configuration you do not control. Everything below is administered inside your own workspace, and every change is attributed to the person who made it.
Create roles, set capabilities and move people between teams. Module access follows entitlements with real start and end dates.
Health components, weights and thresholds are yours to set, and previous versions are kept so you can see what a score meant last quarter.
Connect and disconnect sources yourself, and see what each one is permitted to read.
Which topics Mira may address, and which classes of action she may take without asking first.
Question types, conditional logic, trigger events and ordered steps, built by the people who run the process.
Approvals, ownership changes and access grants across the workspace, with the enforcement detail on the trust page.
Frankfurt and Tokyo, on the same day you turn it on.
Half your company adopting a platform is the expensive outcome: you pay for all of it either way. Language, vocabulary and branding are settings your administrators control without us.
A language cannot be switched on until its translation coverage is complete. Most platforms ship the gaps and let your team in Osaka find them.
Call them clients instead of accounts and that holds in every language, including on fields you added yourself. Every override is audited.
Direction, date and number formats are set per language, so one workspace serves teams who read in opposite directions.
Accessibility gets the same treatment, and we publish the contrast figures. what we verify, and how.
Branding and administration →Everyone you employ has to be able to use it.
Built to WCAG 2.1 AA, with the contrast figures published rather than asserted. It is decided in the design system, so it holds across every screen instead of the ones someone remembered.
An independent audit and a VPAT are not done yet. Ask and we will tell you where that sits. If you hit a barrier, tell us and you get a fix or a date, in writing.
See it on your own data.
Bring an account you are worried about, a forecast you do not trust, or an onboarding that went badly. Forty-five minutes.