How the factory works, in six stations
Your request goes in.
Working software comes out.
In the chat you describe what the software has to do. That becomes a build plan of tasks with acceptance criteria, our Code Agents build them one by one and every task becomes a pull request. A person decides at three gates: the build plan, the review and the merge. You follow it live in your own project screen.
From request
to working software
You are not buying hours. You switch on a factory that runs your build plan, with our architects on three gates. Six stations, and the belt above shows them in the same order.
-
Your request
It starts in the chat: what the software has to do and how you will measure it. Not an eighty-page functional design, but a conversation. What we set down there is exactly the set of acceptance criteria the agents check themselves later on.
-
The build plan
Your request becomes an ordered list of tasks with acceptance criteria, from foundation to features, each task in its fixed place. You see the size before anything starts. This is the first gate: nothing happens without your approval of the build plan. After that the factory sets your project up itself, with a repository, quality checks and a preview environment.
-
Agents build
A planner writes the task instruction, a builder implements, a reviewer comments and a fixer works through those comments until tests, code style and static analysis are green. One task is built at a time: task two starts only after the pull request for task one has been merged. Every task is exactly one pull request, and on your project screen you see per task what the agent is doing now.
-
Architect reviews
Every implementation is judged in the preview before it is submitted. That is the second gate. One of our architects looks at architecture, security and whether it feels right to use, because those are questions a person answers better. You click through the same preview.
-
Merge and deploy
Nothing is merged without approval. That is the third gate, and merging and deploying is always done by a person. That person can be you, because the code sits in your own repository from the first task. Almost no hand work touches the code itself; the decision is another matter.
-
Go-live
Your project keeps running in the same environment. You ask for the next feature in the chat and it passes through exactly the same six stations. If you want to know where the whole thing stands, you ask in the chat. You are not waiting for a sprint planning, because a task starts the moment you ask for it.
Where the limits sit
Every limit below is a choice. They are there because the result is better for them.
-
One task is built at a time
The next one starts only after the previous merge. Slower on paper, safer in practice.
-
You see the status, not the code
The project screen shows where every task stands and what is changing. The pull requests themselves stay with us.
-
It does not work out what you need
We make the build plan together. A vague brief produces vague software here too.
-
A person merges and deploys
Always, and that person can be you. Your project sits in your own repository, so you can roll it out yourself.
-
It does not replace user research
Whether something feels right is decided by a person looking at it.
-
It does not stop, we do
The agent keeps running and can be checked at the weekend too, so you can carry on in your own time. Anything that needs a person on our side waits until the next working day.
-
We do not predict what it will use
What building costs depends on what you build. An estimate up front would be a number we could not stand behind. What you do get is your consumption and remaining balance, live.
A new project?
Then it starts in the chat. Your request becomes a build plan, the factory builds the tasks one by one and you watch along.
Existing software that needs to move faster?
Then we put the Code Agent on your existing project. After that you ask for your next feature yourself, in the chat.
We are Spartner.
-
Since 2004 we have built software for startups and SMEs. These days we largely have it built by our own factory.
-
You keep the intellectual property and you keep building in the same environment after delivery.
-
Our architects stand on three gates: the build plan, the review and the merge. Nothing passes them without a person.