How we work
From discovery to running it with you
For owners who need something built and do not want to manage a string of vendors. You deal with one team across six stages, and you see working software early instead of waiting for a big reveal.
- 01
Discovery
We learn how the business runs and where it breaks.
- 02
Design
We agree how it will work first: what it stores, who can do what, and what happens when something fails.
- 03
Build
We build it piece by piece, on previews you can open and use.
- 04
Secure
We check who can get in, where keys are kept and the database rules, all before launch.
- 05
Launch
Scripted tests, a rollout plan and a way back if something goes wrong.
- 06
Operate
Once it is live, we watch it, tune it and support it.
The six stages in full
What happens at each stage, and who does it
Each stage has a job. Skipping one does not save time. It moves the problem to later, when it costs more.
-
Discovery
We go through how work moves through your business today: how a customer reaches you, which tools you use, and where things get stuck or dropped.
- Who does it
- You and your team explain the day-to-day. We ask the questions and write it down.
- What you get
- A clear view of what to build, fix, secure or leave alone, and a timeline before you commit to a build.
- Without it
- Software gets built around a guess, and you pay to change it later.
-
Design
We map the information the system will hold, the role each person has, and how it should behave when something fails, such as a payment that does not go through.
- Who does it
- We draft it. You review it and agree it before building starts.
- What you get
- You know what you are getting before the work begins.
- Without it
- Disagreements surface late, when they cost the most to fix.
-
Build
We build one working slice at a time and put each on a preview, a test copy kept apart from your customers, so you can click through it.
- Who does it
- We build. You try each slice and tell us what is wrong.
- What you get
- You see real software early and can change direction while it is still easy.
- Without it
- You wait until the end to find out whether it is right.
-
Secure
We review who can reach what, where passwords and keys are stored, and the rules in the database that decide who can see which records.
- Who does it
- We run the review. You confirm who on your team should have access.
- What you get
- Problems get found before real customer data is in the system.
- Without it
- One leaked key or over-open account can expose your customers’ data.
-
Launch
We run scripted tests, a written list of checks a computer repeats the same way each time. We follow a rollout plan and keep a rollback path, which is a way back to the last working version.
- Who does it
- We run the launch and tell you what is changing and when.
- What you get
- You go live with the checks done and a way back ready.
- Without it
- A bad release leaves staff and customers stuck, with no quick way out.
-
Operate
Monitoring watches the system so problems get noticed. Tuning adjusts agents and workflows as your business changes. Support means you have someone to go to.
- Who does it
- We do, on a Managed AI OS and IT retainer. Or your team does, using the documentation we hand over.
- What you get
- The system keeps working after launch day.
- Without it
- Connections break quietly, and nobody notices until a customer does.
What the Build stage looks like
Watch a sample build move across the board
We break a build into small pieces of work and move each one across a board, so you can always see what is done and what is next. This one is made up. Press Run sprint to watch it, or tap a card to move it yourself.
Sample sprintIllustration only. Drag a card, tap to advance, or run it.
Backlog
Building
Review
Shipped
How to read the board
- BacklogAgreed work that has not started. We choose the order with you.
- BuildingWe are working on it now. Only two cards fit here at once, so work gets finished instead of just started.
- ReviewIt works on the preview. You and we check it before it counts as done.
- ShippedDone and part of the system. You can open it and use it.
What the cards are
- Sign-in and rolesWho can log in, and what each person can see and do.
- Data modelHow your information is organised, such as customers, orders and jobs.
- Admin consoleThe screen your staff run the business from.
- PaymentsTaking money from customers through a payment provider.
- NotificationsAutomatic messages when something needs attention.
- Audit logA record of who did what, and when.
The small picture labelled “preview” fills in as each card ships. The line under it shows the work left going down.
Engagement models
Three ways to work with us
Pick by what you know today. Not sure what you need? Start with A. Know exactly what you want built? Start with B. Already have a system running your business? C keeps it running. The strip shows which of the six stages each one covers.
A focused review of how your business runs today. You get a clear picture of what to build, fix, secure or leave alone.
- Workflow and tool review
- Security and access review
- Prioritized roadmap
- Cost and scope estimates
Best when you know something is wrong, but not what to build.
Covers: Discovery
A scoped build with a defined outcome. We design, build, secure and launch one system or one major piece of it.
- Agreed scope and deliverables
- Working previews throughout
- Testing before launch
- Handover and documentation
Best when you know what you need.
Covers: Design, Build, Secure, Launch
We run it with you. Ongoing operation of your AI operating system, infrastructure and automations.
- Monitoring and maintenance
- Agent and workflow tuning
- Security upkeep
- Priority support
Best once a system is running your business.
Covers: Operate
Words on this page, in plain English
- Scope
- The agreed list of what will be built and what will not.
- Sprint
- A focused block of work with one agreed outcome.
- Roadmap
- An ordered list of what to do first, next and later.
- Retainer
- An ongoing arrangement where we keep looking after your system.
- Handover
- Giving you what you need to run the system yourself, including documentation.
FAQ
Common questions
Where should we start?
If you are unsure what to build, start with a Systems Assessment. If the scope is clear, go straight to a Build Sprint.
How long does a project take?
It depends on scope. We give you a timeline after discovery, before you commit to a build.
What do you need from us?
Time from whoever knows the day-to-day work, honest answers about what breaks, and someone who can try each preview and say what is wrong.
Do you stay after launch?
If you want us to. The Managed AI OS and IT retainer covers ongoing operation, or we hand over with documentation.
Tell us what your business needs to run on.
Answer a few questions and send them to us. We will tell you what we would build, and what you do not need.