How we build: plan, build, launch, train
Four steps, in the same order every time. You see working software early, your team is involved throughout, and you own what we build.
Plan: what should we build first?
We start with the people who do the work, not just the org chart. We map the workflow, the data and the tools, and agree on one clear thing to build first. If you've done a Build Plan, this part is already done.
Usually inside a Build Plan, 1–2 weeks
- Working sessions with you and your team
- Workflow, data and tools mapped
- One tool, one scope, agreed in writing
- Fixed fee before anything is built
Build: how do we make it?
We build in short rounds and show you working software early. Your team tries it on real work and tells us what's wrong. We change it. No disappearing for three months and coming back with a surprise.
First Build: 2–4 weeks
- Short build rounds with regular check-ins
- Real work used for testing from the start
- Changes made while they're still cheap
- Plain-English updates, no jargon
Launch: how does it go live?
We set the tool up inside the software you already use and connect it to your systems. We test it on live work alongside the old way, then switch over once your team trusts it.
Part of every build
- Set up in your existing tools
- Connected to your CRM, accounting or email where needed
- Run side by side before switching over
- Access and data use documented
Train: how does your team take it over?
We train the people who use the tool, and the person who'll own it day to day. You get short guides and a clear map of how it all fits together, so it keeps running after we step back.
Built in, not bolted on
- Hands-on training on real tasks
- Short how-to guides and handover docs
- AI use policy if you don't have one
- Ongoing help through Build Partner, if you want it
How do you handle our data?
Plain answers. Before any build starts, you get a short written summary of what data the tool touches and where it goes.
Do you work inside our existing tools?
Yes, wherever possible. Your data stays in the systems where it lives today. We add AI to those systems rather than copying everything somewhere new.
Who owns what you build?
You do. The code, setup, prompts and documentation belong to your business. You can keep running it with or without us.
Will our data be used to train public AI models?
No. We don't train public models on your data, and we use business-grade AI services and settings that don't use your data for training.
How will we know what happens to our data?
We explain it in plain English: what the tool reads, what it writes, which services it uses and who can see what. No legal fog.
Who has access while you're building?
Only the people who need it, for as long as they need it. We use access you can see and remove, and we hand everything back at the end.
Start your build
Book a short call. We'll talk through what you want to build or fix, and tell you plainly whether we can help.