How we work
Four steps, in this order
We take one job at a time and run it the same way each time. You know what you are getting, what it costs and when you will have it before we build anything.
Step 01
Look
We sit with the people who do the work and measure where the time goes. We look at the job as it is done today, not as the manual says it is done.
- You get
- A short list of where time is lost, in order, with what each would take to fix.
- We need from you
- A few hours with the people who do the job, and a look at the systems they use.
Step 02
Plan
We pick one job with you and write down what we will build, what it costs and when you will have it. If AI will not pay for itself on that job, we say so here.
- You get
- A written plan for one job: what is in, what is out, the price and the date.
- We need from you
- A decision from someone who can say yes.
Step 03
Build
We build it in the systems you already run and put a working version in front of your people early. They test it on real work before it replaces anything.
- You get
- Something you can use, early, and a say in how it changes.
- We need from you
- Time from the people who will use it, to try it and tell us what is wrong.
Step 04
Hand over
Your team runs it. We stay close after it goes live, watch it on real work and fix what does not hold up.
- You get
- Written instructions in plain words, and a named person to call.
- We need from you
- One person on your side who looks after it from here.
On every job
Five things that do not change
- 01
One job at a time
We prove one thing saves your people time before we start the next. You can stop after any job and keep what was done.
- 02
A named person on each side
You know who is doing the work, and we know who can make a decision. Nobody is passed between teams.
- 03
You see it working early
You are shown a working version on your own work, not a presentation about one.
- 04
A person answers for it
We use AI to research and to draft. Nothing reaches you until one of us has checked it and is willing to put their name to it.
- 05
We say when the answer is no
Some jobs are better left as they are. We would sooner tell you than build something that does not earn its keep.
Questions we are asked
Before you start
How long does a job take?
It depends on the job, which is why the plan comes before the build. You are given a date in writing before we start, and we tell you early if it is at risk.
What does it cost?
The plan gives a price for one job before anything is built. You agree to that job, not to an open-ended engagement.
Do we have to replace the systems we have?
No. We start from the systems you already run and connect or add to them. We recommend replacing one only when it is the thing holding the work back.
Do we have to use Route Royal, Vellon or Q?
No. We offer them in Australia and use them where they fit. When our advice points to one of them we tell you, and we set out the other choices.
What if it does not work?
That is what the first job is for. It is small enough to judge quickly, and your people test it on real work before it replaces anything. You decide whether to go on.
Who will we be dealing with?
The people doing the work. You are given a named person at the start and they stay with the job.
Next step
Tell us about one process that costs your people time. We’ll tell you whether we can help.
What happens next
- 01
You tell us about one process
A few lines is enough: what the work is, who does it and how often.
- 02
We ask some questions
A short call to understand how it runs today.
- 03
You get a straight answer
Whether we can help, what we would build and what it would cost.
Pyrmont NSW 2009
+61 401 472 649