Giving you the keys: what owning your AI looks like the week after we leave.

When a team weighs in-house against managed, the quiet worry is always the same. In-house sounds like we train you, wave goodbye, and leave you to figure it out. That is a fair thing to fear. So here is the honest version of what the week after handover looks like, what is actually in your hands, and what your champion does the first time they want a new app with nobody to call.

What is literally handed over

Setup is not a course that ends with a certificate and a wave. By the end of the four weeks, you own a working setup, not a memory of one. Here is what stays with you.

• The toolchain in your names.The chat, the app builder, the automation layer, and the rest are all set up under your team's accounts, on your billing, with a year of subscriptions for both trained seats included. Nothing routes through us. We could disappear and it would all keep working.
• The reference app. We build one real app together, for a real problem in your business. It is live and in use, not a demo. It is also the template your team copies from for everything after.
• The patterns.The way you go from “this task is annoying” to a working app: how to scope it small, where to point each tool, how to test it on a real person. That repeatable method is the actual product.
• The docs. Plain-language notes on how your setup fits together and how to build the next one, written for your people, not for engineers.
• Optional office hours after. If you want a safety net for the first stretch, we stay reachable for questions. Most teams use it less than they expect, which is the point.

The first build with nobody to call

Picture the moment the fear is really about. It is a few weeks after we have gone. Your champion spots a task worth automating, and there is no consultant in the room. Here is what they actually do.

• They open the reference app and look at how it was put together. They are not starting from a blank page. They are copying a shape that already works.
• They scope it small, the way they were trained to. One workflow, one clear input, one clear output. No grand build.
• They use the chat tool to draft the logic, the app builder to make it usable, and the automation layer to connect it to where the work already lives. Same pattern, new problem.
• They put the rough version in front of the person who does the job, watch where it is clunky, and fix it.

It is slower than the reference app the first time, and that is normal. The second one is faster. By the third, the worry about being stuck has quietly gone, because the evidence is sitting on their screen.

Why we try to make ourselves unnecessary

We say plainly that the goal of Setup is to not be needed. That can sound like a slogan, so here is why it is in your interest and not just ours.

If your team can only build with us in the room, you have not bought a capability. You have bought a dependency with a nicer name. Every new app would mean another call, another fee, another wait. That is the exact thing in-house is supposed to remove.

So we train for independence on purpose. We hand over the patterns and the docs instead of keeping the clever bits to ourselves. We build the reference app with your people, not for them, so the knowledge ends up in their hands and not just in our heads. A handover that leaves you able to keep going is the whole job. We own the IP on both paths, but on Setup you also own the ability to use it without us.

The honest risk of owning it

Owning your AI is not free of cost, and pretending otherwise would be dishonest. There are two real risks, and you should hear them before you choose.

The first is decay. A capability you do not use fades. If the trained seats stop building for months, the patterns get rusty and the confidence slips. This is no different from any skill. Use it and it compounds. Leave it and it does not.

The second is that someone has to keep championing it. Owning the keys means someone on your side carries the role: spotting the next problem worth automating and keeping the habit alive. We train two people for exactly this reason, so the capability does not walk out the door if one of them gets busy or moves on. But it still needs a person who cares, and that person has to be yours.

When you would rather we keep the keys

None of this means in-house is the right answer for everyone. Some teams hear all of the above and decide they would simply rather we hold the keys and run it. That is Run, and it is a deliberate, valid choice, not a lesser one.

With Run we build the apps, host them, and keep them working. Your team uses them through a secure link, with no toolchain to own and no champion to keep. It is an A$1,500 discovery (credited to the work) plus A$150 a month of hosting per workflow. If nobody can spare a few hours a week, or you genuinely want the result and never the wheel, that is exactly what Run is for. You still own the IP. We just hold the keys.

The difference between the two is not quality or speed. It is who you want holding the keys the week after we leave. If the answer is your own team, Setup hands them over. If the answer is us, Run is doing its job.