# Map. Build. Run.

Source: https://cruxlabs.com.au/how-we-work

Every engagement follows the same three stages. We map the business in two to three weeks and give you a fixed price, build in short releases you can use, then run it with you or hand it over. Each stage ends with something you keep, even if you stop there. Built in Melbourne, working Australia-wide.

## The three stages

### Map
Map · The Blueprint · 2 to 3 weeks. We map how the work really moves, list the AI worth building with its payback, design the system and give you a fixed quote. You keep: the Blueprint document.

### Build
Build · Weeks, not months. We build in short releases you can use, on your real data, with every change passing the same checks before it ships. You keep: the code, the data, the accounts.

### Run
Run · Ongoing. After launch you choose: we run it for you, you ask and it builds, or we teach your team. You keep: the choice, every month.

## Your IT team keeps the keys.

In-house or outsourced, we work with them, not around them. They keep the tenant, the accounts and the access. We build the agents inside it, document every change, and hand over what we built.

## Fast because we build with AI. Safe because every change is checked.

Not WordPress, not drag-and-drop tools. Real code you own, built to grow with the business.

1. Every change is checked for leaked passwords and keys.
2. New outside software waits seven days before we use it.
3. Nobody sees your data unless they are given access.
4. Money kept to the exact cent, never rounded.
5. A permanent record of who changed what, and when.
6. A written undo plan before every live change.
7. A second reviewer checks every risky change.
8. Hosted in Australia, built to the government's Essential Eight security checklist.

[Security and privacy, in detail](https://cruxlabs.com.au/security)

## After launch, nobody holds the keys but you.

| | We run it for you | You ask, it builds | We teach your team |
|---|---|---|---|
| For | Owners who want results, not another tool to learn | Teams with one or two people who like to tinker | Founders and operations leads who want full control |
| What we set up | The system, hosting, monitoring and monthly improvements | The system plus a workspace where you describe a change in plain words, and it is built, tested and shown to you to approve | The method your team uses to plan, build, test and release changes on your own code, with our checklist |
| How a change ships | We build it, test it and release it, and tell you what changed | You describe it. It is built. The tests check it. You approve the release | Your team builds it, with office hours if they get stuck |
| You own | Everything | Everything, and the power to change it | Everything, and the skill |

## A fixed price before work starts, sized to your business.

Every job gets a fixed price before work starts, sized to your business. Start with one fix, such as quoting, bookings or a website that loses leads, or build the whole system. The Blueprint maps your work in two to three weeks and ends with that fixed quote; its fee comes off the build. After launch, choose how you keep growing: a monthly plan where we run it, a workspace where you ask and it builds, or training so your team builds it.

**Our promise.** Sprint: if no workflow is running by the end of the Sprint's second day, we finish it afterwards at no extra cost. Blueprint: the fee is credited in full to your build.

[See the AI Workflow Sprint](https://cruxlabs.com.au/workshops/ai-workflow-sprint) · [Book a call to start the Blueprint](https://cruxlabs.com.au/contact)

## Questions

**How long does a build take?**
The Blueprint takes two to three weeks. Builds ship in short releases from the first weeks, and the Blueprint sets the date for the whole system.

**What happens if we stop after the Blueprint?**
You keep the Blueprint. It is yours to take to anyone.

**Who hosts it?**
We do, in Australian data centres, in a database you own. The details are on the Security page.

**How many meetings will this take?**
Only the ones that produce a decision: discovery, a weekly look at the working version, and a review at the end. Discovery happens in person when it matters.

## Start with the map. Keep it either way.

[Book a call](https://cruxlabs.com.au/contact) · [See our work](https://cruxlabs.com.au/case-studies)