No new software
OPEXAi is a standard MCP connector, so it works inside Claude, ChatGPT and Microsoft 365 Copilot. Nothing to install, no new logins and no new window to switch to.
OPEXAi
OPEXAi connects Claude, ChatGPT and Microsoft 365 Copilot to your firm’s OPEX projects, lots, contracts, deposits and settlements. Ask in plain English and get answers, documents and updates from live OPEX data, with every action logged.
Why it’s different
Not another system to log into. The same firm account and the same records, with every lookup and change logged.
OPEXAi is a standard MCP connector, so it works inside Claude, ChatGPT and Microsoft 365 Copilot. Nothing to install, no new logins and no new window to switch to.
Generic AI tools can’t see which lots have exchanged or what deposit is held in trust. OPEXAi gives your assistant that view, of your firm’s OPEX data and nothing else.
OPEX issues your firm a connector. Each person adds it to their assistant and signs in with their OPEX login. Lookups work from the first question.
See it in action
Six everyday jobs for a conveyancer acting for a developer, from sales advice to sold out.
A sales advice lands. OPEXAi reads the lot, purchasers, price and deposit, creates the draft contract from the project’s own template and lets the conveyancer know it’s ready. Nothing goes out for signing until they’ve checked it.
Each trust receipt is matched to its contract and recorded with the receipt attached. A deposit that doesn’t add up, like an overpayment, is flagged for a person to check, not forced through.
Ask for a sales report with charts and a spreadsheet of every contract. OPEXAi pulls the live figures from OPEX, and the assistant turns them into a report for you to check and send.
Hand over the developer’s own spreadsheet. OPEXAi compares every lot, shows exactly what will change, holds back anything that needs a closer look, and updates the rest on your yes.
Forward the developer’s email. OPEXAi reads the attachments, sets out the project, vendor, lots and deposit account it will create, and builds them in OPEX once you’ve approved the plan.
Project sold out? OPEXAi finds every exchanged contract and a download link for each, so the assistant can name them by lot, zip them and file them for the client.
Names and figures in the videos are fictional. Email, file and SharePoint steps use your assistant’s own connectors alongside OPEXAi. Claude, ChatGPT and Microsoft 365 Copilot are trademarks of their owners; OPEX is not affiliated with or endorsed by Anthropic, OpenAI or Microsoft.
Security and control
OPEXAi works on your firm’s OPEX records, under your firm’s account, one step at a time. Nothing happens without a signed-in user behind it.
Explore OPEX securityGetting started
Nothing to install. We set your firm up; your team signs in.
OPEX sets your firm up and issues a connector ID and secret.
Each person adds OPEXAi as a connector in Claude or ChatGPT. For Microsoft 365 Copilot, your IT admin publishes an OPEXAi agent once for the firm.
They sign in with their OPEX login to connect, and reconnect every 30 days.
Lookups work from the first question. Changes are switched on when your firm asks for them.
FAQs
Claude, ChatGPT and Microsoft 365 Copilot. Your team keeps the assistant they already use, and OPEXAi connects it to OPEX. For Microsoft 365 Copilot, your IT admin publishes an OPEXAi agent to your organisation once, then each person signs in.
Yes. OPEXAi is a remote MCP server hosted by OPEX. MCP, the Model Context Protocol, is the open standard AI assistants use to connect to business systems. Your assistant adds OPEXAi as a custom connector over HTTPS, and each person authorises it by signing in to OPEX (OAuth), then reconnects every 30 days. If your firm uses an assistant not listed here that supports remote MCP connectors, ask us.
Yes, whatever the assistant looks up. When it looks something up in OPEX, the result goes to your AI provider so it can answer, and that can include purchasers’ personal information. How the provider handles it is governed by your firm’s agreement with that provider, so check its data settings and terms before you connect.
Only if your firm asks us to switch them on. Changes are off by default, so a new firm can look things up but not change anything. Once switched on, the assistant is designed to set out what will change before it does, and every change is logged against the signed-in user.
OPEXAi only ever reaches your own firm’s OPEX data. Each person signs in to OPEX as themselves, and every lookup and every change the assistant makes is recorded in your firm’s audit log against their OPEX account, kept for 24 months. OPEXAi records what the assistant does in OPEX, not your conversation with the assistant.
No. It’s OPEX, reached from inside your AI assistant. Your team can keep working in OPEX as they do today, and use OPEXAi for the lookups, reports and repetitive updates.
OPEXAi connects your assistant to OPEX. Steps like reading an email, saving files to SharePoint or sending a report use your assistant’s own connectors, working alongside OPEXAi.
Get started
Book a walkthrough with our Australian team. We’ll show OPEXAi working in the assistant you already use, on your own OPEX data if you’re a customer or on a sample project if you’re not.