One process, built properly, for one price.
For the work you would rather never think about again. Fixed scope, one price agreed before anything starts, built inside your own accounts on the tools you already pay for.
What actually gets built
Something that takes information in one shape and puts it out in another, the same way every time, without a person doing it by hand.
The most common ones are post-meeting workflows, where a finished call becomes a filed summary, updated contact records, assigned tasks and a drafted follow-up email. Then document pipelines, which turn raw files into a consistent, client-ready format. Then reporting, where the same numbers get pulled and laid out on a schedule instead of on a Friday afternoon.
A person always approves anything that leaves your business. Automations draft, people send. Internal filing and record updates run unattended once you have watched them work for a while.
Builds live in your own accounts and your team runs them day to day. After the first 30 days of support, most clients keep us on monthly so that someone is watching when a tool changes underneath a process that was working fine.
Builds are sized by shape, not by hours
Every one includes a scoping call, testing on your real data, one revision round, and a handoff document with a screen recording.
Small
One input, one output, an existing template, no live data. A report format, a standardised email, a cleanup routine.
Medium
Multi-step, two or more sources, real judgment in the middle. A tuned comparison model, a document builder.
Large
Live connections, scheduled, multi-stage and client-facing. A full brand pack, a pipeline automation.
Teams that have been through the five weeks get a standing discount on every build after that, for as long as they keep working with us.
See the trainingFive steps, no surprises in the middle
The same sequence every time, whether the engagement ends up being a build, the training, or neither.
-
The discovery call 30 minutes, free
We map one process end to end. Who touches it, how often, which tools it passes through, and where it usually goes wrong. Expect specific questions rather than a pitch. You will do most of the talking.
-
The written map Within two days
A document with what we found and an honest read on whether it is worth automating. If the answer is that you should delete the process rather than automate it, that is what it says. Yours to keep either way, with no obligation.
-
A fixed scope and price Before any work starts
If it is worth building, you get a written scope with one price. Not an hourly estimate that drifts. You approve it before anything begins, and the number does not move unless you change what you asked for.
-
Build and test on real cases Two to four weeks, typically
We build it against your actual files and run it on real past examples so you can see it working before it touches anything live. You see it early and often, not at the end.
-
Handoff and training Included
We show your team how it works, hand over plain-language documentation, and stay available for 30 days. Everything runs inside your own accounts. After that first month most clients move onto ongoing support, because tools change and a process that ran cleanly in month one often needs a look by month six.
There is no price list, and that is on purpose.
A two-step workflow and a twelve-step workflow are not the same job. Printing one number would mean quoting you something that is wrong in one direction or the other.
What you get instead is the shape of it: one fixed price, in writing, after the discovery call and before any work begins. No hourly billing, no scope-creep invoices, no retainer you have to remember to cancel. If the project grows because you want something added, we quote that separately and you decide.
What moves the number
- How many steps the process has
- How many tools it has to connect to
- Whether those tools have clean integrations or awkward ones
- How many people need training on it
- Whether it runs on a schedule or on demand
What we will not do
The four we turn down
Saying this out loud is cheaper for both of us than finding out three weeks in.
Automate a process that should be deleted
Some work only exists because it always has. Automating it makes it permanent. We will say so.
Build something that emails your clients unsupervised
Automations draft. People send. This is not negotiable and it is the rule that makes teams willing to adopt anything.
Take on a process that is genuinely judgment
If the answer changes every time based on things nobody can write down, a person should keep doing it.
Quote before we understand the work
A price given before scoping is a guess you end up paying for. That is what the call and the map are for.
Questions
What people ask before the first call
What actually happens on a discovery call?
You describe one process the way you would explain it to a new hire, and we ask a lot of specific questions about who does what and when. There is no slide deck and nothing to prepare. Thirty minutes on video, and the more specific you are about the process, the more useful it is.
Is the call really free, and is there a catch?
It is free and the written map that follows is yours to keep whether or not you hire us. The reason it works as a business is simple: mapping a process is the only reliable way to know whether it is worth automating, so we would have to do it before quoting anyway.
Do I need to know what I want built?
No. Most people arrive knowing something takes too long without knowing which part. Working that out is the point of the call, and the honest answer is sometimes that nothing is worth building yet.
How long until something is actually running?
For a single process, typically two to four weeks from approved scope to handoff. The variable is almost never the AI, it is how many systems the automation has to reach and how cooperative those systems are.
Do you only build for real estate?
No. The training is built for real estate teams, but builds get scoped per project and the industry does not much matter. If the work is repetitive and the files look roughly the same each time, the shape is the same whatever business you are in.
What if we would rather learn to do this ourselves?
Then start with the training instead of a build. That is the more common path now, and teams that go through the training get a standing discount on any builds they commission afterwards.
Bring one process, not a shopping list.
Thirty minutes, free, no pitch. You leave with a written map of how the work actually flows and an honest read on whether automating it is worth your money.