Gustav There is a category of business problem that gets misdiagnosed as a tool problem. The CRM is not working. The project management software is a mess. The reporting dashboard takes four manual exports to produce. So the business shops for a better tool, spends two months migrating, and ends up with a slightly different version of the same problem.
The real diagnosis is usually a fit problem. The tool was not built for this business. It was built for the median business in a given category, which means it fits no specific business particularly well.
What the subscription model actually costs you
SaaS pricing is designed to look small. Twenty euros per user per month sounds reasonable. But multiply that by your team size, add the integrations you need, upgrade to the tier that has the features you actually use, and the number compounds quickly.
A ten-person team on a mid-tier CRM platform like Salesforce or HubSpot is often paying 15,000 to 25,000 DKK per year. A project management tool, a reporting tool, an email automation platform - stack three or four of those together and you are looking at 60,000 to 100,000 DKK in annual software spend for a business that is not particularly large.
That money is gone every year. You own nothing at the end of it. And the vendor controls the pricing, the feature roadmap, and the decision about which tier your most-used features live in next year.
The right question is not "what does this cost per month?" but "what will this have cost us in five years, and what do we actually own at the end of it?"
The fit problem nobody talks about
Every SaaS product is a set of decisions made by someone who does not know your business. They decided what a pipeline stage should be called. They decided what fields a customer record needs. They decided how reporting should work and what a dashboard should show.
Those decisions are reasonable for the average business. Your business is not the average business. You have specific pipeline stages that do not map to their defaults. You track customer data that their fields do not accommodate. Your reporting needs do not match their prebuilt views.
So you adapt. You use the closest field. You build a workaround. You keep a spreadsheet alongside the system because the system cannot quite do what you need. After a year of this, the tool is technically in use and practically a burden - and the team has learned to route around it rather than rely on it.
What "custom internal tool" actually means
When I say custom internal tool, I do not mean something exotic or expensive to maintain. I mean a web application built to do the specific things your business needs, with the fields, views, and workflows that match your actual process - and nothing else.
A custom CRM does not have thirty features you will never use. It has the pipeline stages you defined, the customer fields your team actually cares about, and the reporting your managers ask for every week. It looks exactly like your business because it was built from your business.
A custom dashboard does not require four manual exports. It pulls from your actual data sources, calculates the numbers you care about, and shows them in the format your team reads. It updates when the data updates.
A custom proposal tool does not paste your text into a generic document. It knows your pricing, your service definitions, your standard terms, and your brand - and it drafts proposals in your voice from an incoming enquiry.
The honest cost comparison
A custom CRM built to cover the core use cases for a small to mid-sized sales team typically runs in the 25,000 to 60,000 DKK range. That is a real upfront cost. But it is a one-time cost you own outright - no ongoing license fees, no per-user pricing, no vendor deciding next year that a feature you depend on is now in the enterprise tier.
For a team paying 20,000 DKK per year on a SaaS CRM, the payback period on a custom system is two to three years. After that, the custom system is pure saving. And unlike the SaaS platform, it can be changed to match how the business evolves - without asking a vendor for a new feature and waiting twelve months.
Three signals that tell you it is time to build
Not every business should build. Here are the three signals that tell me a business is ready for a custom tool rather than another off-the-shelf product:
Your team has built workarounds around the system. When the spreadsheet lives next to the CRM, when there is a Slack channel that duplicates what the tool should track, when people have stopped logging things because logging them is slower than the alternative - the tool has failed the team.
You have clear, stable processes. Building a custom tool locks in your current workflow. If your process is still being figured out, build in something flexible first. When the process is clear and repeating, that is when custom makes sense.
Your annual SaaS spend on a category exceeds 15,000 DKK. Below that number, the economics of building rarely make sense. Above it, the conversation is worth having seriously.
When off-the-shelf is still the right answer
Off-the-shelf tools are not bad. For a solo operator or a very small team with straightforward needs, a free or low-cost SaaS product is the sensible choice. Setup is fast, cost is low, and the tool gets the job done.
For early-stage businesses still figuring out their process, building too early locks in the wrong thing. Use something off-the-shelf to learn what you actually need, then build when the requirements are clear.
And some categories - accounting, payroll, enterprise data warehousing - are genuinely better handled by specialist vendors. The case for custom is strongest for the internal tools that sit at the centre of your specific workflow: CRM, pipeline tracking, dashboards, proposal generation, workflow automation.
The question is not "build or buy." It is "which option gets us closer to what we actually need, at a cost that makes sense over the next five years?" That question deserves a real answer - not a default.