AI-assisted development, run by your own team
AI-assisted development in four to six weeks, run by your own team and your own product owner: a way of working, the line in your repositories, one real feature shipped.
What it is
- 14 900 €, four to six weeks
- 24 900 €, eight to twelve weeks
- Fixed, agreed up front
- Fix it
The gap is rarely the tools. Most teams already have AI assistants, and the pace of delivery has not moved with them. Writing code got cheap; review, testing and release still move at the old pace. What moves delivery is the line: how a team plans, specs, builds and releases, with people at both ends and agents carrying the work in between.
People move from writing code to planning the work and overseeing the line. Your product owner plans in the backlog, specs are written from the queue, and agents build and simplify in loops until the outcome is met. A person approves the merge and decides what reaches production: the one who wrote a change never approves it.
This is not a platform we install and licence back to you. We build our own product, Brain, this way, so the bar is enterprise: every change starts from a written spec and passes the same checks before it merges. We bring that practice to your team, with the tools you choose, and the proof is one real feature shipped on your own code before we leave.
The shift
Where AI already is, before anyone decided it should be.
An assistant in every editor
Coding assistants ship inside the tools your developers already use.
Writing got cheap, shipping did not
More code arrives. Review, testing and release still move at the old pace.
Who wrote this change?
In regulated work, customers and auditors ask. Few teams can answer for AI-written code. The question is whether your delivery changed, not whether developers use AI.
Faster means a new line, not more licences
- A developer picks a task
- Types faster with AI
- A bigger pile to review, same release pace
- Stories in the backlog
- Agents write the spec, build and loop until the outcome is met
- People oversee and release
People move from writing code to planning the work and overseeing the line. Agents carry the work in between, even when nobody is watching.
Three things you can point at
In control is not a document. It is three things a leadership team can hold.
The way of working
Plan, spec, build, verify, release, with people at both ends. Your product owner plans the work; a person approves the merge and decides what goes live.
The line
Stages, loops, gates and guardrails in your repositories, tuned to protect quality without boxing the agents in. Agents build and simplify in loops until the outcome is met.
One real feature, shipped
Planned by your team, carried by agents, released by people. Built the new way on your own code before we hand over.
Four to six weeks, one feature shipped
We start from a practice we run on our own product and customer projects, never from zero. The weeks follow your calendar, not our effort.
-
Readiness check
Delivery baseline measured, one real outcome chosen from the backlog, with the CTO and tech lead.
-
The line set up
Backlog, specs, loops and gates in your repositories, with your tools, with the tech lead and a developer or two.
-
Run the line
Agents carry work from the queue, your team plans and oversees, we coach alongside.
-
Ship and hand over
The feature is shipped, and the before and after is reviewed with the CTO.
Who does what on the line
People at both ends, agents in between. Approve and release are two decisions on purpose: the one who wrote a change never approves it.
Roadmap, stories and priorities live in the backlog. People: the product owner.
Written by agents from the queue, checked against the story. Agents, the tech lead approves.
Agents build, verify and simplify in loops until the outcome is met.
Forward: built what the spec says. Backward: met what the story needed. Agents and gates.
A person approves the merge and decides what goes live. People: your team.
All of it stays in your environment, in your own repositories and pipeline, yours to develop further.
Two sizes
Base is one team and one repository. Extended is the same work where several teams, vendors or regulators are involved, and it includes Base.
You want proof on one team
14 900 €
What it covers
- The readiness check, the way of working, and the line set up in your repositories.
- One team and one repository, a standalone setup with our default gates.
- One real feature shipped the new way, a basic traceability log, and a review with your CTO.
You want it to become how you build
24 900 €
What it covers
- Everything in Base, across several teams or repositories, integrated with your pipeline and ticketing.
- One real feature per team, a full audit trail for regulated work, and gates tuned with your security team.
- Your own owner trained and handed over, closing with a review and a 90-day follow-up.
Fixed price, agreed before the work starts. Started with Base and want the rest? What you paid for Base is credited in full.
Which one fits
Not sure? We will recommend one, and say so when Base is enough.
Base
- Four or more developers, your own or hired
- Your own product owner runs the roadmap
- Light regulation, or none
- You want to see it work before you scale it
Extended
- Several teams or repositories
- Regulated work that needs a full audit trail
- An existing pipeline the tooling must fit into
- Your own people should own and develop it
What stays yours
Whatever you decide next, these leave with you.
The backlog and the product knowledge, written so every agent reads them.
The spec and build loops, the guardrails and the hand-off rules.
The quality gates and the pipeline that run on every change.
The traceability log: which story, which spec, which checks, who approved.
The same ladder we used in cloud
For the CTO who grew up with a cloud adoption framework. Same structure, one level each: why, path, control, check. This module sits on the path.
Recon: where your business is with AI.
AI Software Accelerator: a module on the path, bought on its own.
In control of AI: the model, blueprint and register.
A review of every AI use, repeated.
Where this sits
A ready-made module on the Map it, Fix it, Run it path, in Fix it. You can buy it on its own.
Set your team up to build this way in your own environment, and hand it over.
See how the path worksOne path, and it compounds
It starts with one problem worth solving. Bring us yours and we will name the price and the date before you commit to anything.