Your request goes in.Working software comes out.

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.

Our software factory




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.

  1. Your request

    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.

  2. The build plan

    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.

  3. Agents build

    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.

  4. Architect reviews

    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.

  5. Merge and deploy

    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.

  6. Go-live

    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.

How the factory works

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.

What partners say
Jurjen Terpstra

"Pragmatic and flexible collaboration"

Spartner has created a customized portal for us for the accountability of large-scale collaborative projects. This enables us and our partners to execute and account for their plans in a shared environment that is secure, transparent, and manageable. The pragmatic and flexible collaboration with Spartner has ensured that we have quickly achieved a functional and user-friendly environment.

Jurjen Terpstra Managing Partner at Wecreate Consulting

Bjorn Gubbels

"As a business you must dare to move forward"

Innovation and change are not always welcomed with equal enthusiasm by our employees, man is a creature of habit but as a company you have to dare to move forward and the need for a contemporary drawing program for the realization of various constructions with our Masterbloc bricks was high. For us but also for Spartner, this challenge was a bit of pioneering and together we had to overcome some hurdles to arrive at a beautiful and efficient business tool. A development and learning process for both parties, in which the feedback of questions and desired adjustments by our employees to Spartner was always in good consultation and we could count on quick feedback and targeted solutions. We continue to exchange experiences with Spartner and look back and forward to a successful collaboration.

Powerful 3D construction drawing software

Bjorn Gubbels Owner of Masterbloc

Hans Lugtenberg

"A deal is a deal"

Yield.inc is a new asset manager in the Netherlands that focuses on excellent customer experience, sustainability and technology. When faced with the question of whether to develop our platform in-house or with a partner, we got in touch with Spartner. We are still 100% behind the choice for Spartner because we own the source code and with Spartner, a deal really is a deal, whether it concerns the delivery date or the agreed budget!

Hans Lugtenberg Partner at Yield Inc.

Niels Winters

"Innovation in legal technology"

As jurists with knowledge of IT, we highly value quality; within code, but also in process. The high work-level and trustworthiness of Spartner gives us the capacity to continuously create innovative features.

Legal tech platform

Niels Winters Managing Director JuriBlox

Josh Mountain

"Have been using Laravel Excel for years"

We requested custom help to a performance challenge we had in our implementation of Laravel Excel. I was amazed how quickly these Laravel artisans achieved significant performance gains, which saved us a lot of development time.

Open source package for Laravel

Josh Mountain Co-Founder at IncentivePilot.com

Norbert Wegter

"A professional software partner since 2010"

Spartner is involved and contributes in our search for innovations and always delivers top-notch work. After the first Huurda.nl version got out-dated, we collaboratively launched a completely new version in 2020.

Custom-built search engine for rental properties

Norbert Wegter Owner of 123wonen and Expat Homes Holland

Maurice Evers

"Higher occupancy rate thanks to our user-friendly platform"

Throughout the great years that we cooperate with Spartner (previously Maatwebsite, Ed.), our software has been developed continuously. Students and landlords actively work with features like allocation, payments, chat, contract generation and more.

Custom built ERP for all student residences

Maurice Evers Head of Student Housing Department

Maarten Bremer

"Innovating in the digital identification network of The Netherlands and Europe"

The pro-active approach of Spartner was crucial in understanding the complexity of the eHerkenning network.

Development of eHerkenning connection and services

Maarten Bremer CTO / Founder Ensured

Marco Caspers

"AI and machine learning as legal tools"

In 2020, we transferred the development of Lynn to Spartner. As a result of their fast development process, the Lynn platform achieves an increasingly central role in the legal world.

Lynn, the smart AI legal robot

Marco Caspers Software Development Manager at Lynn Legal

Dr. Freek Daams

"International collaboration in randomized trial"

Our national workgroup of surgeons actively collaborates with international workgroups thanks to the innovative online research platform.

Anonymous patient records for medical research

Dr. Freek Daams Upper GI en HPB Surgery, VUmc

Marco Leenders

"Spartner extends our capabilities and development capacity"

With weekly calls, using our Azure DevOps sprint system, Spartner actively works together with our innovation, communication and software development departments.

Multi-website CMS with Statamic 3

Marco Leenders Head of Automation

How the factory works

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.


What would you change first?

Enter your web address and say what needs to change. You see it on your own site before you decide anything.

No account needed. You see a first result within a minute.

We have received your message. We will contact you shortly. Something went wrong sending your message. Please check all the fields.