Software that adapts to you — not the other way round
Does this sound familiar?
Your company's most important data lives in three places: a spreadsheet, an inbox, and a colleague's head. Quotes get copied by hand, nobody can find a customer's history in time, and the month-end report is half a day of clicking.
Meanwhile you are paying for a boxed system nobody likes using, because it was not built for your work. The fee goes out every month — and every month you work around it just the same.
This is not your fault. The software is wrong, not your process.
What I build
CRM and customer management. Every customer, every history, every quote in one place. Who called last, what we promised them, when to follow up — by search, not from memory.
Back-office and internal systems. Quote, order, invoice, stock, delivery, job sheet — following the steps of your own process, not the logic of a foreign template.
Applications you can use on a phone. The warehouse worker marks things off from their phone, the technician closes the job sheet on site, the manager sees the numbers on the move. The same system, comfortable everywhere.
A customer portal. Your client logs in and sees their orders, their prices, their documents. Fewer phone calls, fewer emails, more satisfied customers.
Management reporting. One screen with what actually matters: turnover, pending quotes, stalled jobs. Not a monthly spreadsheet hunt.
Integrations. The system talks to the store, the invoicing tool, the warehouse, the courier and the accountant. The data moves on by itself.
Already have a system? You are still in the right place
Most companies stay with bad software because they believe switching means months of chaos. It does not — if someone knows how to do it.
I take it over as it is. Unfamiliar code, missing documentation, a developer who walked away, old technology: with me that is not an excuse, it is part of the job. I look at what is there and tell you what can be saved.
Your data comes across. Customers, history, orders, documents — nothing is lost. That is not an option, it is a baseline requirement.
No downtime. The switch happens in steps: the old system keeps running until the new one is ready. You do not stand still for a single day.
It is renewed inside and out. Not only faster and safer, but finally something your team actually wants to use. The best feedback so far has always been the same: "why didn't we do this sooner?"
Why me?
One person, one point of responsibility. Not an agency chain where one person writes the quote, another does the work, and nobody owns the mistake. The same developer who quoted writes the code — you call me, I pick up.
You see it working every two weeks. Not months of silence followed by a surprise. Every two weeks a version you can open and try: you say during the build if something is off.
A fixed quote, no detours. We settle at the start what is needed — then that is what the contract says, and that is what gets built.
The system is yours. Full source code, every access credential, no licence fee and no mandatory monthly fee. I do not lock you in: any developer can carry it on. You stay because you are satisfied, not because you cannot leave.
You do not have to learn systems. If a change is needed — a new field, a new rule, rewritten text — just tell me and I do it.
How we proceed
- Conversation. You describe how you work today and where it hurts. I ask questions — many of them, because the accuracy of the quote depends on it.
- Quote. In writing, itemized: what gets built, by when, for how much. You also see what is not in it.
- Build. A working version every two weeks that you can try out. The direction can be refined along the way.
- Handover. Training, documentation, full access. I am available afterwards too — I do not disappear with the last invoice.
Frequently asked questions
What does a custom system cost?
As much as the work in it — which is why I do not work from a price list but look at your process and give a fixed price for it. The first conversation is free, and afterwards you will know exactly what to expect. What is certain: no licence fee, no per-user monthly fee, and no surprises after the fact.
Wouldn't it be cheaper to buy an off-the-shelf CRM?
If your process is standard, then absolutely — and I say so before selling you anything. But an off-the-shelf system is a monthly fee, you pay per user, and your work has to be bent to fit it. With custom development you pay once, the system is yours, and your process stays as it is. Where that difference shows up over several years, the custom system is cheaper — and far more usable.
How long until it is usable?
The full system takes weeks, sometimes months — but you do not have to wait until the end to see it. You get a working version every two weeks, and typically you can start using the part that eats the most time halfway through the build.
What if I realise mid-project that I want something different?
That is why I work in two-week cycles. What fits in the agreed scope, we adjust as we go; what goes beyond it gets a clear price before anything is built. No surprise invoices.
Will all our data come over from the old system?
Yes, that is part of the takeover. Customers, history, orders, documents — I move them over and verify that nothing is missing. Your data is not the property of the old software vendor: it is yours.
Who will operate it afterwards?
Whatever we agree. Many leave it with me, because then it is one phone call; others have their own IT people take it on — both work, because the full source code and all access are yours. There is no mandatory package here.
We are a small company. Aren't we too small for this?
Quite the opposite: in a small team it matters most when two hours of someone's day are freed up. It is not a question of size but of whether there is repetitive work you solve with a person today. If there is, there is something to talk about.