Insights · Software development

Custom or standard systems: when does building pay off?

When a custom-built system beats standard software, what AI has done to the math, and how to find the answer for your own business without risking a cent.

Eddie Blomkvist 8 min read

The question almost always comes up in the same situation. The company has grown, the spreadsheets have multiplied and someone has just received a quote for an industry system that does eighty percent of what you need. The last twenty percent, the part that describes how you specifically work, you will have to handle with manual steps and good intentions.

At that point we usually get asked whether it would be better to build a custom system. A few years ago the answer was mostly no. Custom development was expensive, slow and associated with projects that overran both time and budget. Today the answer is yes much more often, because the conditions have changed fundamentally.

What a standard system is good at

A standard system is built for many. That is its strength and its weakness at the same time. The strength is that it is in place right away, that someone else maintains it, and that processes that are the same for every company, such as accounting, payroll and VAT, are handled correctly without you having to think about it.

We recommend standard systems without hesitation for exactly those processes. Nobody should build their own accounting. Visma Net and monday.com are the core of most of what we do, and they get better every year.

The problem arises when the standard system has to cover what sets you apart from your competitors. There, the system is built for an average business, and you are not the average. Then the customization starts: consulting hours to bend the system, add-ons that cost per user, and ways of working that change to fit the tool instead of the other way around.

The signals that you have outgrown standard

There are a few patterns we recognize after many mapping sessions. If three or more of them fit you, it is worth running the numbers on a custom system.

  • The spreadsheets are your real system. The standard system exists, but the real work is planned, tracked and reported in Excel or Google Sheets, often in files only one or two people understand.
  • You pay for customizations of something you do not own. Every change requires the vendor's consultants, and what you pay for still belongs to the vendor.
  • The process is your competitive advantage. You win business on how you deliver, plan or handle customers. A system that forces that into a generic template removes exactly what makes you better.
  • License costs grow with every hire. When you hire ten people, the system gets ten licenses more expensive, without doing anything more for you.
  • None of the standard solutions covers the flow from start to finish. You have three systems and one person copying between them.

If you only recognize yourselves in one or two points, it is usually better to restructure what you have. We cover that reasoning in the article on whether to rebuild or start over in monday.com, and the same logic applies to most systems.

How AI has changed the math

What made custom development expensive was never the idea. It was the hours. Writing, testing and documenting code by hand took months, and every month cost money.

With AI as a parallel engine in development, that math has changed. The developer describes, reviews and decides, while AI writes large parts of the code, suggests tests and produces documentation. What used to take a week often takes a day. We go through how it works in practice, and what it does not change, in the article on AI-accelerated software development.

The consequence is that a custom-built system is no longer automatically the expensive option. Lay out the comparison over three years and the picture is often different from what many expect.

Standard system with customizationsCustom system built with AI
Time to first versionWeeks, but the customizations take monthsFour to six weeks to production
Cost over timeLicense per user, every year, plus consulting hours for changesFixed price for the build, then ongoing management as needed
Fit with your processesEighty percent, the rest is handled manuallyBuilt around how you actually work
OwnershipThe vendor owns the system, you rent itYou own the code, data and system
ChangesWait for the vendor's release planMade in short iterations as the business changes
RiskLow at the start, grows with every customizationPrototype and fixed price before the build, so the risk is taken early and in a controlled way

The table is simplified, and there are businesses where the standard system wins on every row. The point is that you can no longer assume the answer. It has to be worked out.

When you should still choose standard

We build custom systems, but we advise against it in several situations. Be honest with yourselves on these points.

  • The process is not your competitive advantage. If what you need is an ordinary CRM or an ordinary project tool, there are excellent standard systems, and we are happy to set them up.
  • You have nobody who can own the system. A custom system needs a person in the business who understands it and can prioritize changes. Without one, ongoing management becomes an external cost with no direction.
  • The need is temporary. A system for a campaign or a single project rarely justifies custom development.
  • The regulations are heavy. Accounting, payroll and other things governed by law should live in systems where someone else is responsible for following the rules.

In practice, most end up with a combination. Standard systems for what is the same for everyone, a custom system for what is unique to you, and an integration that lets them talk to each other. We describe that architecture in the article on how monday.com and Visma Net fit together.

How to find the answer without risking anything

The best thing about today's pace of development is that you do not have to decide based on a PowerPoint. You can see the system before you decide.

Our approach is built around that. Day one is a free discovery call where we go through the business, the processes and the biggest bottlenecks. On days two to five we build a clickable prototype of the most important flow, using your real terms and examples. You test it with the team, and only then do we set the scope and a fixed price. If you do not want to go ahead, it costs nothing, and you still have a clearer picture of what you need. The whole week is described day by day in Prototype in five days: how it works.

That is how we think the decision between custom and standard should be made. Not based on what was true five years ago, but based on what you see on the screen after five days.

Frequently asked questions

What does a custom system cost compared with a standard system?

It depends on the scope, but the comparison should be made over several years. The standard system costs a license per user every year plus consulting hours for customizations. The custom system costs a fixed price for the build and then ongoing management as needed, with no license per user. For companies with many users or large customization needs, the custom system often becomes cheaper within two years.

How long does it take to build a custom system today?

With AI as a parallel engine in development, we have a clickable prototype ready in five days and the first version in production in four to six weeks. Comparable projects used to take six to twelve months.

Do we have to replace our existing systems?

No. Most of the custom systems we build complement Visma Net, monday.com or other systems already in place, and are integrated with them. The custom system handles what is unique, the standard systems handle what is generic.

Who owns the code if we build a custom system with Straviont?

You do. The code, the data and the system are yours, with no license cost per user and no lock-in. If you want to manage it with someone else in the future, you can.

Isn't it risky to build your own?

The risk lies in building something that does not get used. That is why we start with a free prototype that you test with the team before any budget decision, and set a fixed price before the build starts. You see a working system early instead of a report after six months.

Next steps

Read more about how we work with custom systems, or book a discovery call and we will look together at whether your business has outgrown standard.

Ready to challenge
the way you work today?

Tell us briefly about your situation and a senior advisor will get back to you with a time to talk. Free of charge, no commitment.

We reply within one business day. Your details are only used for this. Prefer email? contact@straviont.com