One process that runs itself, right up to your approval.
You already know which recurring job takes the most time. We map it, build around it, test it against your real history, train your team and check the result after thirty days.
This is for you if you can already name the process
You know which job it is, who does it, and roughly what it costs you every month.
- Answering one customer question means opening three systems and asking two people.
- Quotes and proposals get assembled by hand from things that already exist somewhere.
- Someone spends a chunk of every week chasing information that should have arrived with the request.
- The same report gets rebuilt every month from the same four sources.
Your systems stay exactly where they are
We do not replace anything or start a migration. We remove the assembling, retyping and chasing that happens around your systems, and we leave the checking and the sending with your team on purpose.
How a workflow actually runs
Six stages. The first four prepare, and only the last one changes anything — after someone you name has approved it.
- 1 · WatchSomething happens
A job is completed, an email arrives, a date comes into range. Nobody has to remember to check.
- 2 · RetrieveIt gathers what it needs
From the sources you approved, and only those. Read-only unless you decide otherwise.
- 3 · CheckIt applies your rules
The rules you wrote, in your words. This is where your business logic lives.
- 4 · DraftIt prepares the work
Assembled and ready, with the sources attached. Nothing has happened yet.
- 5 · Approval
Someone you name approves
One person, chosen by you. Everything above was preparation.
It waits here - 6 · Act
Then it acts
The agreed action, with tested approval controls and a scoped recovery plan.
The step that does it
Illustrative of the shape every build takes. Your rules and your approver.
What you get, and how it runs
One working process, plus everything your team needs to run it without us.
- A map of how it works today — exceptions included, which is where the detail lives
- The built workflow — tested against real historical cases from your business
- Written rules and approval points — inside the process, not bolted on
- Training for the people who run it — the ones doing it daily
- An agreed success measure — set before we build, using your numbers
- A 30-day result review — we come back and check it against that measure
- Handover documentation — written for your team, not for a developer
We sit with the people who run it and map what actually happens.
Against real examples, so the exceptions surface early.
Historical cases, written rules, approval points confirmed.
Trained, live, and checked again after 30 days.
The build
Scope is confirmed in writing before we build anything, so the number is agreed before work starts.
$4,800 + GST, from
Final price depends on the systems involved and how many exceptions the process has. Both are settled during discovery.
The initial fit conversation is free. Any paid discovery and its fee are agreed separately before work starts; you approve the build quote afterwards.
- 1You describe the process
What it is, who runs it, how often.
- 2We tell you if it is a good fit
Honestly, including when it is not.
- 3Discovery and scope
Written down and priced before anything is built.
- 4Build, train, review
Live with your team, then checked after 30 days.
Questions people ask
Will this change the systems we already pay for?
No. Your systems stay exactly where they are. This removes the manual work happening around them, which is usually where the time actually goes.
Why from $4,800 rather than a fixed price?
Because the exceptions decide the effort, and they are rarely visible in the first conversation. We confirm scope in writing before building, so the number is agreed before work starts.
How long does it take?
Typically three to six weeks from scope confirmation, depending on how many systems are involved and how quickly we can see real examples.
What happens if it gets something wrong?
Your team reviews important outputs. We scope logging, stop controls and recovery for the systems involved. AI can be wrong and some external actions cannot be reversed, which is why approval and exception handling matter.
What if discovery shows it is not worth doing?
We tell you, and you have not spent the build budget. You keep the map.
Do we need the Opportunity Session first?
Not if you can already name the process, who runs it and what it costs. If you cannot, the session will save you money.
Tell us about the process
Describe the job, who runs it and roughly how often. We will tell you whether it is a good candidate and what we would need to confirm before quoting it.
Or call 0494 609 651, or email hello@masterkeyit.com.au.
We read and answer every enquiry ourselves. If we are not the right fit for what you need, we will tell you, and point you at what is.