Eleven modules. One record. One trail.
Most organisations run sales, dealing, wealth and service on four systems that were never introduced to each other. AcuityQ™ runs them on one — which is why a case raised on Monday and a quote issued on Thursday are visibly the same customer, without an integration, a nightly sync, or a spreadsheet in between.
Front office
The desks that talk to customers and bring revenue in.
Sales desk
A day’s agenda, smart-view buckets by where the lead actually stopped, an in-product dialler, and meetings that are logged where they happened.
5 screens
Read the detailDealing desk
Live portfolio fetched at open and never cached, product comparison that re-ranks per client, calculators, and post-trade checking of every instruction.
6 screens
Read the detailWealth & field desk
A named book, portfolio reviews on a cadence per segment, geo-verified meetings, and a mobile workspace that keeps working with no network.
5 screens
Read the detailQuoteDesk
Quotes built from a bill of materials per vendor, discounted inside a policy that names the approver, issued as one versioned customer document.
4 screens
Read the detailPartner desk
A workspace for franchise partners and other non-employees: masked contacts, dialling through the platform, scope that stops hard at their own code.
6 screens
Read the detailService
Everything that happens after a customer has a problem.
Demand
Where leads come from, who owns them, and what happens when nobody acts.
Oversight
One number, drilled from the enterprise to one person, without changing screen.
Command centre
Enterprise to line of business to zone to region to branch to person — one drill, six levels, every chart and table obeying the same scope.
5 screens
Read the detailReporting & analytics
Dashboards per desk and role, scheduled reports to named recipients, exports that carry the filters that produced them, and a Power BI route for the rest.
3 screens
Read the detailFoundation
The customer record, the permission model and the trail, shared by everything above.
Customer 360 & portal
One customer record every desk reads, holdings fetched live and never persisted, and a self-service portal writing to the same case the agent is working.
6 screens
Read the detailGovernance & administration
Capabilities rather than tiers, an entitlement matrix you can read, a four-layer taxonomy, integration hub, DPDP controls and an audit trail with no off switch.
7 screens
Read the detailWhy one record matters
The same customer, in every direction
An operations head takes a call about a settlement file that did not arrive. The case is raised. Three weeks later a relationship manager quotes the same firm for an additional terminal licence, and a wealth RM has a portfolio review due on the principal.
In four systems those are four customers with similar names, and nobody selling knows the account has an open case. In AcuityQ they are one organisation record: the open case, the opportunity and the review cadence are on the same screen, and the person approving a discount can see all three before signing it.
This is not an integration. There is no sync window, no mapping table and no nightly job that can fail quietly. It is one database, one permission model, one trail.
Schematic — one organisation record
The approver sees the open case before deciding on the discount. Whether that changes the decision is your policy; the software's job is that nobody can say they did not know.
Honest limits
What the platform is not
Four boundaries that hold across every module, so nobody spends a procurement cycle discovering them. If one of these is a requirement, AcuityQ is the wrong product and we would rather say so now.
Not a telephony platform
Calls are dialled through your switch, logged and linked. AcuityQ does not run the switch, the IVR or the recording.
Not a core or back-office system
Holdings, ledgers, order execution and account opening live in the systems that own them. AcuityQ reads them live and never claims to own them.
Not a BI platform
Reporting answers questions about leads, cases, quotes, people and margins. There is no modelling layer and no end-user SQL.
Not an identity provider
AcuityQ authenticates its own users and can sit behind SSO where you have it deployed. It is not your directory.
Walk the platform with someone who built it
Thirty minutes, scoped to your sector and your desks. Simcomm replies within one working day.
Or open the demonstration — every screen above, ungated, seeded with invented data.