Solutions
Custom software at an agreed price
An internal tool, a customer portal or an MVP. We agree the scope first, and after that it is a fixed price and a fixed delivery date.
≈ DKK 24,000–96,000
When this makes sense
- A spreadsheet has quietly become business-critical
- Off-the-shelf software almost fits, and the gap is costing you
- You need something real in front of users to know whether the idea holds
How it works
- 01
Scope
We write down what is in and what is out. That is what makes the price an agreement you can hold me to.
- 02
Build
You see demos along the way, so you can change direction early, while it costs hours instead of weeks.
- 03
Ship
Deployed, documented and handed over. The code and the infrastructure are yours, and you are not tied to me.
What you get
- Scope agreed in writing before anything is built
- Agreed price and a fixed delivery date
- Demos along the way instead of one big reveal
- You own the code and the infrastructure
Off-the-shelf system or custom software
If an off-the-shelf system can do what you need, it is almost always the cheaper choice, and I will tell you when that is the case. A booking system, CRM or accounting package that a thousand other businesses already pay for is maintained by somebody else, and you share that bill with every other customer. Custom software makes sense when the way you work is what sets you apart, and the standard system forces you to work like everybody else.
The usual sign is a spreadsheet that has grown into the tool the company actually runs on, or three systems that each do part of the job while somebody moves data between them by hand. In that situation a small system built for the task is often cheaper over three years than the licences and the hours spent making the standard tools fit together.
What typically gets built
Customer portals where your customers can see orders, documents or status themselves instead of calling to ask. Internal tools for quotes, planning or quality control that replace a spreadsheet with too many tabs. Booking flows with rules a standard system cannot express. And smaller SaaS products or MVPs, where an idea needs to reach real users before more money goes into it.
Nearly all of those systems need to talk to something you already have. That can be e-conomic or Billy for invoicing, Shopify or WooCommerce for orders, HubSpot or Pipedrive for customers, or a supplier's API. The integrations are built with a queue, retries and an alert that reaches a person, because that is where systems usually break quietly.
What the price depends on
A defined build typically costs DKK 24,000–96,000 ex. VAT. Where it lands in that range depends mostly on four things: how many different kinds of user the system has to handle, how many other systems it connects to, whether data has to move over from an old system, and how many special business rules have to go into the code.
The price is agreed in writing once the scope is described, and after that it is fixed. If the job is too big to describe properly up front, we split it, so the first part becomes a usable system and the rest is priced once you have tried it. That gives a better product than a large specification nobody could test against reality.
Ownership, documentation and handover
The code lives in your own repository, the hosting and the domain are in your name, and the documentation comes with the first delivery. The system is built in ordinary, widely used technologies such as TypeScript, React, PHP, Laravel and Postgres, so the next developer can read it without first learning a home-made framework. If you later want an in-house team or another supplier to take over, that is planned from the start rather than negotiated afterwards.
Common questions
- What does custom software cost in Denmark?
- Danish agencies typically quote from around DKK 150,000 for an MVP, and DKK 250,000 to 600,000 for a mid-sized web application. My builds typically cost DKK 24,000–96,000 because there is one person here and no agency to pay for. In return I take on fewer projects at a time.
- Who owns the code?
- You do. Both the code and the infrastructure setup. You can take it to another developer whenever you like.
- What if the scope changes along the way?
- We price the change in writing before I build it. Nothing surprising turns up on the final invoice.
- How long does it take to get a system built?
- A defined build is typically delivered from 3 weeks, and the first usable version usually arrives within a few weeks. Larger systems are split into deliveries, so you can start using parts of them while the rest is built. The delivery date is agreed together with the price.
- Can the system connect to e-conomic, Billy or our CRM?
- Yes, and that is part of most jobs. e-conomic, Billy, Shopify, WooCommerce, HubSpot and Pipedrive all have usable APIs, and most suppliers with an API can be connected. The integration is built so a failure is noticed and reported, rather than data quietly ceasing to sync.
- Can we or another developer keep working on it afterwards?
- Yes. The code lives in your own repository and is written in widely used technologies with documentation, so an in-house developer or another supplier can take over. If you want me to handle ongoing development that is possible too, but it is not a condition.
Other things I do
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.