Ask questions across the whole portfolio, raise the work, receipt what's been paid and draft the letters — from a normal conversation with Claude, Microsoft Copilot or the Word & Excel add-ins, connected to the Urbanise Strata platform your portfolio already runs on.
Built for the platform built for scale. Urbanise Strata brings accounting, communication, building and community management into a single cloud platform — with automation across levies, arrears and admin. Urbanstep.ai connects your AI tools to all of it, through Urbanise's supported APIs.
Plans, lots and owners, levies and arrears, budgets, suppliers, insurance, tasks and payment runs — all of it becomes something your team can simply ask for. Every action either only looks something up, changes one record, or is guarded because it can't be undone.
Plans, lots, owners and committees. Arrears by lot, the full levy ledger, and what's owing as at a date for a settlement enquiry. Budget versus actual, term deposits, insurance renewals, and whether a trade is still covered. Answers land in Excel as a table, or in Word as a letter, when that's what you need.
Raise a maintenance or by-law task with the photo attached. Receipt a levy payment, raise a special levy or a recovery charge, enter a supplier invoice with the scan attached, record a new owner after settlement. Every change is confirmed with you before it goes through, and read back afterwards so you can see how it landed.
Delete an accrual, an owner's associated contact or an Urbanise login when it shouldn't be there, and drive a payment run through its states. Eight actions are flagged as irreversible, so each one is read back and named before anything happens — and where correcting the record would do the job instead, your assistant says so.
A secure, dedicated server per organisation, built on Urbanise's supported APIs. Access runs on your existing Urbanise credentials and permissions — nothing happens your own account couldn't do.
Every one of the 91 actions is listed in the User Guide, in plain language, with an example you can try.
Raise the task, receipt the payment, charge the recovery costs, check what's waiting to go out. Each one a sentence.
The hesitation with AI in a strata business isn't capability — it's control. Roughly half of what's here changes something in Urbanise, and some of it moves money, so every one of those actions sits behind a gate you set.
A connection holds either read access or read-and-write access. Separately, a whole deployment can be switched to read-only without touching a single credential. Either gate alone stops every change; both have to be open before anything is written.
They're filtered out of the list your assistant reads, so it never offers something it isn't permitted to do — and never has to be trusted not to try.
Deleting an accrual, removing an owner's associated contact, deleting a user, and the five payment-run state changes are annotated so your assistant asks for explicit confirmation before any of them. Money movements — receipting levies and invoices, dispatching a batch — can't be reversed through the assistant either, and say so up front.
An update reads the whole record first, any group of actions can be switched off, and the server can only ever reach your own portfolio. The User Guide sets out how a change is made safely.
Every action in plain language, and what's shipped so far.
The Strata MCP Server is live for Urbanise Strata managers. Tell us where to reach you and we'll set up your organisation's dedicated server — it ships read-only until you open the write gates.
Also for law firms: LegalStep.ai, the Actionstep version.