Ask questions across the whole portfolio, raise the work, receipt what's been paid and draft the letters — all from a natural conversation with Claude, Microsoft Copilot, or the Word & Excel add-ins, connected directly to the Urbanise Strata platform your portfolio runs on. Plans and lots to levies, arrears and payment runs.
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.
Everything Urbanise holds — plans, lots and owners, levies and arrears, budgets, suppliers, insurance, tasks and payment runs — becomes something your team can simply ask for. Each action is named, and each one is allowed to do exactly one kind of thing.
Query any plan, lot or owner across your whole portfolio — contact details, entitlements, committee roles, who settled when — without clicking through building by building.
Urbanise automates levy notices and debt recovery — the server lets you interrogate all of it: arrears by lot, the full levy ledger, what's owing as at a date for a settlement enquiry, and admin and capital works fund balances.
Who you can send to a building and whether they're covered: trades with current public liability and licences, a plan's preferred and blacklisted lists, policy renewals and sums insured, and the standing instructions the committee wants on every work order.
Budget versus actual by fund, uninvoiced disbursements, term deposits and their maturity dates — landed in Excel as a ready-to-work table. Arrears letters and owner notices drafted in Word with live portfolio data. Dashboards are great; a sentence is faster.
Raise a maintenance request, a by-law follow-up or a compliance item with a priority, a due date and someone assigned to it — then attach the photograph, the quote or the report. It lands in a real person's queue, so it's confirmed with you first and written so they can act on it cold.
Raise a special levy or a debt-recovery charge, receipt a levy payment against a lot, enter a supplier invoice with its scan attached, and receipt payments against the invoices the owners corporation has issued. Money movements can't be reversed through the assistant, so the amount, date and lot are confirmed before anything goes through — and the ledger is read back to show you how it landed.
Record a new owner after settlement and the disposal date on the outgoing one, correct a postal address, add a supplier or renew its certificate, record a tenant when a lease starts, or let a car space out of the common property. Every update reads the whole record first, so nothing already on file is quietly dropped.
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.
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. 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.
Updating a lot, a plan, an owner or a supplier reads the whole record first and sends it back complete, so fields you didn't mention aren't quietly blanked. Deletions are read back and described before anything is destroyed.
The server is organised into 16 groups, and any group can be switched off for a deployment. A manager with no need for payment-batch handling or user administration has those removed entirely, rather than relying on nobody calling them.
The strata client the server acts on comes from its configuration and is never something a request can supply. A test enforces that no action exposes it — so there's no path, accidental or otherwise, to another management company's data.
Waitlist members get their dedicated servers provisioned first when we open early access.
Early feedback directly shapes which strata workflows we prioritise — so you can grow the portfolio without growing the admin. Tell us what eats your week.
The Actionstep MCP Server is already in firms' hands — this is the same engine, tuned for strata.
The server is built and documented. See exactly what it can do across your portfolio, and what's shipped so far.
We're opening early access to Urbanise Strata managers soon. Join the waitlist and we'll be in touch with your organisation's dedicated server details.
Curious how it works today? The Actionstep version is in early access right now.