Custom software: if you have a different problem, we build the solution

What we typically build

Customer records and job tracking

Customers, jobs, photos and notes in one place instead of on a phone and in a folder. The usual starting point is a tradesperson or a service business where everything about the same customer is spread across texts, email and memory. A proper record pulls it together, so whoever drives out to the job can see what happened last time.

Internal tools

Replace the spreadsheet everyone is afraid to touch with a real system. Almost every business has a spreadsheet that has outgrown what a spreadsheet can carry: too many tabs, too many formulas and one person who understands it. An internal tool does the same things, but with rules instead of discipline.

Booking and appointments

Customers book themselves, so you stop coordinating over Messenger. We do not have a booking system in production at a customer yet, and we would rather say so than pretend otherwise. The mechanism is the same one as in the shift plan: open slots, someone claiming one, and rules for what is allowed when.

Recording and documentation

Fill it in on a phone, get a PDF out the other end. Inspections, checks, snag lists and timesheets are still often written on paper and typed up again afterwards. That is exactly the double work that disappears when the recording happens where the work happens.

What we do not build

There are jobs we say no to. Not because they are impossible, but because they demand something a one-person company should not promise:

• Payroll calculation and payments. The rules change, and mistakes hit people's personal finances. We are happy to build the thing that feeds the numbers into your payroll system, but not the payroll system itself.
• Payment handling. We do not build card and payment handling ourselves. If money has to be taken, it goes through an established provider.
• Health and patient data. Sensitive personal data brings documentation and operational requirements beyond what we take on.
• Systems that need round the clock monitoring. If somebody has to react at three in the morning when something stalls, we are the wrong supplier.

The list is shorter than the list of things we happily build, but it is more useful. It tells you in a minute whether to keep reading.

How we work out whether it makes sense

It starts with a half hour conversation. It is free, and there is no quote waiting at the end of it. We talk about how the job is done today, who spends time on it, and what goes wrong when it goes wrong.

Afterwards we say one of three things. Either there is a system here, and we describe it and put a fixed price on it. Or there is a system here, but it is smaller than you expected, and then we build the smaller one. Or you should not spend money on software for this, and here is what to do instead. That third answer is not rare.

If we say yes, the job is written down before anything is built: what the system has to do, who uses it, and which rules it has to enforce. That document is what the price hangs on, and it is also what keeps either of us from being surprised along the way. Development typically takes 4 to 6 weeks, and you see the system while it is being built rather than only at the end.

Finally the system is set up on your own accounts, you are handed the code and the credentials, and we show you how to use it. From there it is yours. If you want something changed later it is ordered as a job, and you are not obliged to order it from us.

What does it cost?

Smaller tools start at 12,000 DKK. Larger systems typically land between 25,000 and 60,000 DKK. The price is agreed and fixed before work begins, and all figures exclude VAT.

Under normal use there are no ongoing costs, because the system runs on your own accounts. Changes after handover cost 850 DKK per hour. See all prices, or look at the shift planning system if you want to see what the model looks like on a finished product.

Frequently asked questions