# Software that keeps performing

> Software maintenance and further development without a queue. We put the Code Agent on the repository you already have. You ask for every change in the chat, see it in a preview, and an architect reviews it before it goes live.

URL: https://spartner.software/software-that-keeps-performing

---

For software already running at another agency

Existing software?
**Put an agent on it**

Your application runs, but a one-hour change means two weeks of waiting at your current agency. We put the Code Agent on the repository you already have. After that you ask for every change in the chat, you see it in a preview, and an architect reviews it before it goes live. The same checks and the same three gates as in our factory, on your code.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

Software maintenance and further development without a queue

## What you ask for in the chat

Maintenance and further development are both just tasks in the same list

### Update

Outdated packages, a new version of your framework, missing tests. You ask for it, the agent builds it and the tests run with every pull request.

### Integrate

A link to your accounting system, your CRM or a supplier. Every integration is a task with acceptance criteria, so data flows and nobody does the same work twice.

### Speed up

Slow screens, heavy queries, high hosting costs. You name the screen, the agent measures and improves, and you click through the preview to see whether it is noticeably faster.

### Secure

Security patches and dependency updates pass the same checks as any other task. An architect looks at them before they are merged.

## Cars get an MOT, software really should too

Just like an engine that regularly needs oil, your platform needs updates, tidied-up code and new features to keep running smoothly. At an agency that work sits in a queue. In the factory it is a task that starts the moment you ask for it.

### What that gives you

- A change starts the moment you ask for it, not at the next planning round
- Every change runs through tests, code style and static analysis
- An architect reviews every implementation in the preview before it goes live
- The code stays in your own repository and you keep the intellectual property

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

## From a queue at your agency
to asking in the chat yourself

The same six stations as in our factory, but on the code you already have. If you want to see the factory itself, read [how the factory works](https://spartner.software/how-we-work).

1. ### Your request

It starts in the chat, on your existing project. First we connect your repository and look at what is there: which code, which pipeline, which backlog. Then you describe what you want to change and how you will measure it. That can be a new screen, but also a bug or a package that has not been updated in two years.
2. ### The build plan

For existing software the build plan is short, often a single task with acceptance criteria. A larger change becomes several, each task in its fixed place. You see the size before anything starts and you give your approval. That is the first gate.
3. ### Agents build

A planner writes the task instruction, a builder implements it in your codebase, 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 and every task is exactly one pull request. On your project screen you see what the agent is doing now.
4. ### Architect reviews

Every implementation is reviewed in the preview before it is submitted. One of our architects looks at architecture, security and whether it feels right to use, and in existing code pays extra attention to what changes unintentionally. You click through the same preview. That is the second gate.
5. ### Merge and deploy

Nothing is merged without approval. That is the third gate. Merging and deploying is always done by a person, and that person can be you, because the code sits in the repository you already had. Almost no hand work touches the code itself; the decision is another matter.
6. ### Go-live

Your change is live in your own environment. You ask for the next one in the chat and it passes through exactly the same six stations. Overdue work simply goes into the same list as tasks. You are not waiting for a planning round at an agency, because a task starts the moment you ask for it.

[A multi-website CMS we have been maintaining for years](https://spartner.software/our-work/multi-website-cms-with-statamic-3)

What does software maintenance and further development cost?

No quote and no estimate up front. For every change you see the size of the build plan before you give your approval. You pay for building from your AI balance, and you follow your consumption and your remaining balance continuously. The review by our architects sits on the three gates.

[See the pricing](https://spartner.software/pricing) [Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

## A critical look at legacy

## Why "throw it away and start over" is rarely smart

You will recognise it: the person who built it is gone, documentation is sparse and the code feels like spaghetti. That does not automatically mean starting over.

### Damaged yet valuable foundations

Legacy code often contains unique process logic and links to internal systems. Rewriting those one-to-one costs time and money, and only pays off at the very end.

### Risks of a big-bang rebuild

1. Long periods in which nothing is allowed to change
2. Loss of domain knowledge
3. Unforeseen regressions that surface late

Modernising step by step (think strangler pattern and feature toggles) gives calm and continuity. In the factory every one of those steps is simply a task in the build plan, with a pull request you review in the preview.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

## Practical tips you can apply tomorrow

## Start small, big impact

1. Update your dependencies weekly, not yearly. Small updates are small tasks.
2. Place a top-level README with set-up instructions in five steps.
3. Add health endpoints for monitoring: /status returns 200 OK.
4. Automate database migrations with version control.
5. Put overdue work in the same list as tasks, so it stops being pushed back.

### Bonus: test coverage

In practice you will often find that 60% coverage is enough for confidence. 100% sounds great, but slows you down. Missing tests for a critical part are something you ask for as a task; the agents write them and they run with every following pull request.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

## Looking ahead to the future

## From reactive to predictive maintenance

Machine learning may sound like a buzzword, but predictive monitoring sees performance degradation coming based on anomalies in your logs. You might call it magic, until you see the data.

### Concrete scenarios

- Detect memory leaks before the application falls over
- User-flow analysis to decide which feature you ask for first
- Security scans that follow CVE feeds and put the patch in your list as a task

Such tooling is often open source and costs mainly configuration time, not hefty licence fees. And configuration is exactly the kind of task you ask for in the chat.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

### "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.

### "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](https://spartner.software/our-work/custom-build-search-engine-for-rental-properties)

**Norbert Wegter** Owner of 123wonen and Expat Homes Holland

### "Doijer & Kalff"

After transferring our D&K portal to Spartner, we have elevated the further development and continuity to a higher level. Although the D&K platform was originally developed internally, our technical expert can now focus on other innovations within Doijer & Kalff. Spartner provides the quality we need without excessive costs. They have seamlessly taken over the care of our portal, allowing us to benefit from a flexible capacity that perfectly aligns with our future plans and innovation goals.

**Reinier van Bergen** Managing Director at Doijer & Kalff

### "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

### "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](https://spartner.software/our-work/lynn-the-smart-ai-legal-robot)

**Marco Caspers** Software Development Manager at Lynn Legal

### "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](https://spartner.software/our-work/powerful-3d-construction-drawing-software)

**Bjorn Gubbels** Owner of Masterbloc

### "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](https://spartner.software/our-work/multi-website-cms-with-statamic-3)

**Marco Leenders** Head of Automation

### "Flexible collaboration with yearly updates"

The projectteam of the city of Groningen is very enthusiastic about the "Roomfinder" platform.

[Real estate management software for student rooms](https://spartner.software/our-work/real-estate-management-software-for-student-rooms)

**Gemeente Groningen** Projectteam

### "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](https://spartner.software/our-work/open-source-package-for-laravel)

**Josh Mountain** Co-Founder at [IncentivePilot.com](https://incentivepilot.com)

### "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](https://spartner.software/our-work/custom-build-erp-for-all-student-residences)

**Maurice Evers** Head of Student Housing Department

### "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](https://spartner.software/our-work/development-of-eherkenning-connections-and-services)

**Maarten Bremer** CTO / Founder Ensured

### "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](https://spartner.software/our-work/legal-automation-platform)

**Niels Winters** Managing Director JuriBlox

## Frequently asked questions

Practical answers to the questions we hear most often about software maintenance and further development.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

### Why should I trust Spartner with code you did not write?

Since 2004 we have built and maintained software for startups and SMEs, and we have been taking on existing projects for years. First we connect your repository and look at what is there. What we find, we put on the table openly, and the agent only starts work once you agree.

### How quickly can you start?

As soon as your repository is connected, you ask for your first change in the chat. A task starts the moment you ask for it, not at the next planning round. With a large monolith we first take a longer look at what is there before the agent picks up the first task.

### Will maintenance not cost more than a rebuild?

Not necessarily. By working task by task you spread your consumption and avoid a long period in which nothing is allowed to change. For every change you see the size of the build plan before you give your approval, and you follow the use of your AI balance continuously. A rebuild swallows budget and attention in one go.

### How do you safeguard security?

Security patches and dependency updates are tasks like any other: tests, code style and static analysis run on them, and an architect reviews every implementation before it is merged. A critical vulnerability you report in the chat and pick up as the very next task.

### Can I keep launching new features in the meantime?

Yes. Overdue maintenance and new features sit as tasks in the same list. One task is built at a time, so you decide the order: that one screen first and the package updates after, or the other way round.

### What if my old freelancer suddenly returns?

No problem. The code sits in your own GitHub or Bitbucket the whole time, every change is in there with a readable description and you keep the intellectual property. Whoever carries on with it, everything is in one place.

### Do you work in fixed planning rounds?

No. There is no planning round your change has to wait for. You ask for it in the chat and the task starts at that moment. You set the pace: one task a month or ten a week.

### What do we agree on quality?

Every task has acceptance criteria that we set down together in the chat, and the agents check them themselves. On top of that, tests, code style and static analysis run with every pull request, and an architect reviews every implementation in the preview. If you want a measurable target, such as a load time for a screen, you put it in the acceptance criteria.

### Do I have to migrate to your platform?

No. The Code Agent works in the repository and the pipeline you already have. You do not have to move anything, and you can stop at any moment, because the code is and stays yours.

[Bring us your project](https://spartner.software/contact?start=eigen_applicatie)

[LinkedIn](https://www.linkedin.com/company/spartner-software/) [Medium](https://medium.com/spartner) [Twitter](https://twitter.com/spartnerNL) [Facebook](https://www.facebook.com/SpartnerNL/)

## 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.

[Show me this on my own site](https://mind.spartner.nl/onboarding/chat/code/) [Tell us about your project](https://spartner.software/contact)

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

Arne Schoenmakers

CEO

[Office +31 43 851 69 58](tel:+31438516958) [Arne direct +31 6 81295375](tel:+31681295375) [Arne@spartner.nl](mailto:Arne@spartner.nl)
