AI drafts. People decide. Every release has a way back.
AI makes building faster; it does not make it automatically right. So we work in short loops where machine output is tested, read and approved before it reaches you.
The delivery loop
The outer loop runs once per release. The inner loop between build and review runs many times a day.
Swipe sideways to see the whole diagram.
Six stages, concretely
What happens, what you give, and what you get back at each stage.
Intake
A short call or an email. We find out what should change, for whom, and with which data.
- You give
- The problem in your words, examples
- You get
- Questions back, and an honest first view
Scope
We write down what the first release does and does not do, the price basis and who owns the result.
- You give
- Decisions on priorities
- You get
- A written proposal and agreement
Build with AI loops
AI drafts code, tests and documentation. Every draft runs against automated tests before anyone reads it.
- You give
- Feedback on the mock-up or release
- You get
- Working software early, not slides
Review
Our intention: a person reads every change and an independent review checks it again before release. Security is part of the review.
- You give
- Acceptance on what matters to you
- You get
- Changes you can trust and trace
Ship
Releases go out from a pinned version, with a smoke test after deployment and a tested way back. For native apps, store builds, listings and submission are part of Ship.
- You give
- A go for releases that affect users
- You get
- Release notes in plain language
Operate
We host, monitor and maintain it, or hand it over to your team with documentation and access.
- You give
- Signals from real use
- You get
- A system that keeps working, and the next loop
What AI does, and what people do
No hype: this is the actual split of the work.
| Activity | AI | People |
|---|---|---|
| Understanding the problem | Summarises material you share | Ask the questions, weigh the answers |
| Design and scope | Proposes options and mock-ups | Choose, and agree the scope with you |
| Writing code and tests | Drafts most of it | Set the structure, read every change |
| Quality and security | Runs checks, flags suspicious patterns | Review independently, decide what ships |
| Operations | Reads logs, prepares updates | Approve changes, handle incidents |
Your rights, your data
Every assignment has a written agreement that settles ownership of the result and confidentiality before work starts.
- Rights by agreementRights to the result are agreed per assignment; typically they sit with you.
- Data used only for your assignmentNot for other clients, not for training shared models.
- Security by designEncryption where data originates, backups outside production, incident runbooks and a published contact for vulnerability reports.