A contract administrator on every job, 24/7. Rory catches the extras, keeps every job moving, and tells you what needs you first.
Rory catches the extras, keeps every job moving, and tells you what needs you first.
Nobody asked Rory for any of this. Not one of these rows was logged by a person.
Sits on AroFlo or Buildxact, and the inbox you already live in. No migration.
AroFlo
BuildxactMicrosoft 365Google WorkspaceXero Unwritten work never announces itself. It's a sentence four replies into a thread, a drawing with nothing marked, something said in a meeting, a walkthrough nobody followed up. By claim day it's just work you did.
| Job | VO | $ | Sent? |
|---|---|---|---|
| Kennedy St | VO-012 | 3,000 | ?? |
| Henderson | VO-013 | 4,200 | y |
| Office Fit-out | ?? | ?? | |
| Bathroom Reno | VO-009 | 1,850 | n |
RE: RE: FW: Henderson slab quote
Revised drawings, rev C
Quick change to the ensuite...
Payment claim, June
Did the tiler confirm Thursday? Was the benchtop $14k or $12k? Who's chasing the certifier?
Client · mobile
Mate did you get my email about moving the window? Need to know today
BUNNINGS
$842.50
which job??
Never invoiced. Not on time, hours wasted.
It reads everything on the job the way a contract administrator would, and has the next step written before you get to it. The hire a growing builder could never justify.
A client agrees to extra work in an email. Rory logs it against the job, prices it, and puts it on the next invoice.
Variation and delay notices drafted inside the contract's window, so the claim still stands.
The sparky hasn't confirmed, a certificate is outstanding, a client is waiting on a reply. The chase is written before the job stalls.
The same extra, twice. What happens today, and what happens when Rory's watching.
"Mate, while you're in there, can you move the door across a bit and run the power to the other wall?"
One of eighty that dayYou read it between two other things and reply "no worries".
Nobody's careless. It just never became a record while it was fresh.
The contract gave you five days. Nothing told you the clock had started.
"I never approved that." Nothing to point at, so you wear it.
"Mate, while you're in there, can you move the door across a bit and run the power to the other wall?"
One of eighty that dayApproved 7:50am, from the ute. The email, the notice and the photos are on the claim with it.
You run the job. Rory handles the paperwork around it: on site, on the drawings, in the quote you haven't started.
It ranked the inbox overnight. The extras that need you are on one page.
Rory reads it against the job. It's already a priced variation, ready for your yes.
Record it. The transcript goes to everyone. Extra steel is a variation, and the chase to Dave is already written.
Say it on site. The crack at the garage is raised as an extra, and the chase to the sparky is written.
Take photos as you go. The insulation email is ready for the subbie, and the extra is on the claim.
Compared overnight against last night's set: who comes back, and what it costs.
Drafted from what you've charged and the supplier list. Where there's no cost on file, it says so.
It knows who's ringing and which job they're on, answers what's safe, and logs the rest. The rough-in move is already a note on Henley, waiting on you.
No slides and nothing to install. You'll know within a few weeks whether it's worth having.
A chat with Kosta
Founder of Rory. Ask him anything.
Kosta looks at how you run things, the jobs, the inbox and your system, and shows you where Rory would fit.
Beside the system you already use. You see what it catches, and nothing goes out unless you say so.
Keep it if it's earning its place. If it isn't, you stop. That's a useful answer too.
No migration, no sales process, no pressure.
Start here
See the demo
on one of your jobs.
We'll show you where the extras are slipping, and where Rory would catch them.
Early birdCome in early and the rate you start on is the rate you keep. See pricing.
One scenario. Alongside your current system. A few weeks. Nothing sends without you.
Most builders run the whole business out of their head. Rory holds it for you, so the jobs keep moving while you're on the tools.
Profit left on the table · Free, two minutes
Unwritten work walks profit out the door. Put your numbers on it.
Extras agreed in a thread and never invoiced. Hours on paperwork that shouldn't need you. Over a year, that's a number. One caught $5,000 extra covers a year of Rory for one person.
Rory is priced per person, not per business. One each for whoever's wearing the admin, on the inbox they already work out of.
Prices in AUD, per person. Founding rates while Rory's in private beta: the rate you start on is the rate you keep. Nothing is charged today.
One person
$149 /mo $134 /mo billed yearly
Your own Rory, for the builder handling the admin themselves.
Two or more
$119 /person/mo $107 /person/mo billed yearly
For two or more people sharing the jobs and the record.
Custom
Let's talk
For larger offices that want a conversation first.
Rory on Call is an optional add-on, per person, on top of these plans.
AroFlo and Buildxact hold the job: quotes, claims, invoices — once someone remembers to put them in. They don't watch the inbox. They don't notice the extra buried in a thread, or the drawing that moved. That's a contract administrator's job, and most growing builders don't have one on every job. Rory is that person: it reads the email against the job, catches the extra before it slips, drafts the variation and the chase, and files it back into the system you already run. You tap okay.
No. Keep AroFlo or Buildxact, and the inbox you already live in. Rory sits on them. Nothing to migrate, no retraining. It never becomes the system you run the job in.
No. Never. Rory drafts everything and waits. Nothing gets sent, updated, or logged without you tapping okay. If that ever changes, you'll be the one to change it.
Most of them, you do. The ones that slip are the ones nothing told you about: a change agreed four replies in, a drawing revised with nothing marked. Builders who catch all of it have a contract administrator whose whole job is catching it. Rory is those eyes without the hire, and you still approve everything.
No. We'll still miss some, just far fewer. Anyone promising total capture is selling you something. What changes is that a miss becomes the exception you can see, not the default you can't.
No. Days, not months. Connect the inbox and the job system you already run. You'll see drafts the first week.
Rory is built first for the growing builder: roughly five to thirty people, already on AroFlo or Buildxact, with nobody whose whole job is the commercial side of a project. That's usually a project manager wearing the admin. Sometimes it's the builder. If a job doesn't justify another full-time person, you put Rory on it instead. One-off callouts with no extras have nothing here to catch.
Per person, not per business: one Rory for whoever's wearing the admin. There's a plan for one person, a plan for a crew that shares the jobs, and a conversation if you're a larger office. The rates, the currency and what you're actually signing up to are all on pricing, or see demo and we'll walk you through it.
Yes. You approve everything before it goes anywhere, and there's a record of what was agreed and when. Your data stays in your region.
Always. Email Kosta directly at kosta@folkware.com.au. No assistant. You'll hear back from the founder.
Folkware builds software for the trades, from Adelaide. Extras leak before they reach a system. Rory watches the job, and Footing holds it.
Watches the job
A contract administrator, in software. It reads your emails, drawings, site notes and meetings, catches the variations and the RFIs, drafts the notices and the chases, and files them into the system you already run.
Footing Holds the job
The layer under Rory. One system that holds the whole job, built by the same team so Rory runs deepest there. Optional: Rory works just as well on AroFlo or Buildxact.
See FootingEvery builder should get paid for all the work they do. Not most of it. That's the belief Rory is built on.
There are plenty of tools for construction. You've probably got five of them. And the extras still slip, because the change lives in the inbox and nobody's watching it.
Rory isn't another piece of construction software. It's a set of eyes on the job you're too busy to watch, at a fraction of putting a person on it.
Here's what I keep seeing. Builders fix this by hiring. Extras still slip past a contract administrator, every salary thins the margin, and more people means more admin to keep in step. The fix makes the problem bigger. Rory keeps the whole job moving without adding a head.
The point of it: you get paid for everything you do, and you stop bringing admin home at night.
Got a question? Email me directly at kosta@folkware.com.au. No assistant. I read every one and I write back.
Nothing sends without you. Get your number Email Kosta
