Custom Web Applications

When a company outgrows spreadsheets

The sign is always the same: an Excel sheet that started as a helper tool has become the company's central system. It has fifteen tabs, three people open it at once, nobody knows which version is correct, and whoever built it hasn't dared take a vacation in six months.

Second sign: an off-the-shelf program you bought handles 60% of what you need, and you handle the remaining 40% manually alongside it. You're paying for a license to software you're adapting your business to, instead of the other way around.

What I build most often

• Work order tracking — an order gets opened, assigned to a contractor, tracked through status, closed with materials and hours used. Field staff see it on their phone.
• Warehouse & inventory — stock in, stock out, current levels, minimum quantities and alerts when something's running low.
• Mini-CRM — clients, contacts, communication history, quotes and job status, with no monthly per-user subscription.
• Scheduling & appointments — who's doing what and when, viewable by day, week and contractor.
• Client portal — the client logs in and sees the status of their job, documents and invoices, instead of calling to ask.
• Internal dashboard — the numbers you check every Monday, on one screen, with up-to-date data.

How it's done

1. Process mapping. I watch how the work happens today, with all the exceptions and "we do it differently when it's urgent". Exceptions are usually what off-the-shelf programs can't handle.
2. First usable version. Not the whole system — just the part that hurts most, finished enough to use in real work. Usually a few weeks.
3. Real-world use & refinement. The first weeks of actual use reveal more than a month of meetings. That's where it gets fine-tuned.
4. Phased expansion. Each next phase is quoted and built only once the previous one is genuinely in use.

This order isn't arbitrary. The most common way a project fails is by spending a year building "everything at once", only to find the business has changed shape in the meantime.

The technical side, briefly

Applications run in the browser, on a computer and on a phone, with no installation. Data lives in a real database with backups, users have separate accounts and access rights. Hosting can be on a server in the EU or on your own server on-site, if your industry requires it.

The code is yours. No lock-in to a single vendor — if you ever want someone else to take it over, they get everything they need.

What this costs

It depends entirely on scope, so the price is set after process mapping. The analysis is free. Smaller systems start at 1,500 KM; larger ones are built in phases with a fixed price per phase, so at every point you know exactly what you've spent and what you got for it. Rough ranges are on the pricing page.