Integrations
Your workspace, connected to the assistant you already use
Quantifiable runs a Model Context Protocol server. Point a compatible AI assistant at it, authorise it through OAuth, and it can read your projects, estimates, takeoffs and programmes — and, if you let it, draft work for you to approve. It arrives with your permissions, not a shared key.
What it is
The protocol assistants actually speak
Most software answers the integration question with a REST API and a stack of documentation nobody reads. The Model Context Protocol is the emerging standard for connecting AI assistants to real systems, and it is what Quantifiable exposes — not a wrapper over an API, but the integration surface itself.
A single endpoint
One address on your workspace, speaking JSON-RPC over HTTP. Each request carries one message and receives one response, with no long-lived session to manage or reconnect.
Around sixty tools
Reading across projects, estimates and bills, takeoffs and quantities, cost centres, the cost library, schedules of works, tenders, programmes, variations, valuations, invoices, reports, portal shares, CRM and workspace settings.
Described, not documented
The assistant asks the server what it can do and receives the tool list with its schemas. There is nothing to keep in sync, and the list it sees is already filtered to what your permissions allow.
Decimal across the boundary
Money and quantities cross as exact decimal strings rather than numbers, so a value cannot lose precision on the way out to an assistant and back.
Writes
Classified by risk, and gated on a human
Letting an assistant read your data is one decision. Letting it change a priced document is a different one entirely, and the product treats it that way. Write operations are graded, and the graded ones behave differently.
- Applied immediately
- Low-consequence work an assistant can simply do — creating a project, adding a CRM contact, drafting a task. Recorded in the audit log like any other change.
- Queued for approval
- Anything that touches priced or client-facing work waits in an approval queue in the application. You see exactly what is proposed, and it happens only when you approve it.
- Proposal only
- The most consequential operations cannot be performed by an assistant at all. It may put a proposal in front of you; issuing and certifying stay in human hands.
Isolation
The connection cannot reach another firm's data
Tenant isolation is enforced in the database, not by the code that handles the request. Every tool runs inside a transaction scoped to your workspace, and the MCP layer holds no privileged database role — there is no elevated path for it to take, correct request or malformed one. A dedicated test suite runs two workspaces with overlapping identifiers against every tool and asserts that nothing crosses. It runs in continuous integration, so it has to pass before anything ships.
In practice
What firms actually ask it
The value is not automation for its own sake. It is being able to ask a question in plain language against live commercial data, without exporting anything to a spreadsheet first.
Interrogate a portfolio
"Which live projects have variations submitted but not agreed, and what do they total?" — answered from current data rather than last month's export.
Prepare for a meeting
Pull the current position on a job — programme status, valuations certified, variations outstanding — into a briefing without opening six screens.
Draft and hand over
Have an assistant draft bill lines or a schedule from a brief, then review and accept them in the application where the audit trail is.
Work where you already are
Ask from the assistant on your desktop rather than switching context into another system to look one number up.
Setting it up
A few minutes, in your settings
Connection details live in Workspace settings, under Integrations. Copy the server address into your assistant, complete the sign-in, and choose what it may do. Owners and administrators can see every connected assistant, what it is permitted to do and when it was last used, and can revoke any of them on the spot. Every call it makes is rate limited and recorded.
Also connected
The rest of the working day
Beyond the MCP server, Quantifiable connects to the services a practice already runs on.
Google Calendar
Two-way synchronisation of project deadlines and milestones, updating in both directions rather than pushing a read-only copy.
Email from your own domain
Send project correspondence from your firm's verified sending domain, with a per-project tracking address so replies file themselves against the job.
Client payments
Invoice your clients and take card payment through the portal, settled directly to your own account.
Xero
Paid invoices sync through to your accounts, so the commercial record and the financial record agree without re-keying.
SMS notifications
Alert portal users to something needing their attention by text, on explicit opt-in.
Exports you own
Excel, CITE, BCIS, NBS, IFC and MS Project, generated in the background and downloaded when ready. Your data leaves in formats other tools read.
Connect your assistant to real commercial data
Authorise it with your own permissions, keep priced work behind an approval, and keep the audit trail intact.