Custom Business Software
Standard software maps the average. What sets a company apart sits where the standard does not fit — and then lives in side lists, note fields and informal agreements that are written down nowhere. Custom business software turns this around: the process defines the application, not the application the process. What gets built follows your process, not a finished product.
- spreadsheets
- scattered tools
- coordination by email
- paper forms
- conventions without a system
- one central application
- roles and permissions
- approvals with a record
- reporting from live operations
- traceable changes
When standard software does not map an important business process properly, I build the software that does.
How to tell that this is about you.
If more than two of these sentences sound familiar, a conversation is worthwhile.
What a project in this area looks like.
Not a fixed template, but the order in which the decisions are made. Reverse that order and you pay for it later.
- 01
The structure first
Which things occur in your process — customer, order, device, invoice —, how they relate, and who may see what. This decision carries the entire later application. Changing it later means rebuilding large parts of it.
- 02
Not every process needs a system
This is where it is decided which processes get a fixed path at all — not every one needs one. For those that do, who is responsible and what follows from a step is settled before the first screen.
- 03
An interface for daily work
Designed for the person who works with it every day, not for the demo. Few steps for the common case, a clear path for the rare one.
- 04
Connection to existing systems
The ERP stays authoritative for master data, the new application runs the process. Who holds which data is agreed before anything is built.
- 05
Traceability
Who changed what and when, and on whose approval. Without this layer it is hard to evidence in a dispute who decided what, when and on what basis.
The capabilities that come together here.
Which of them are used follows from the process — not the other way round.
What is explicitly not included.
A boundary you only learn about in conversation costs both sides time.
- Not a replacement for an ERP, inventory management or accounting system
- No customising of someone else's off-the-shelf product
- No application without a named subject-matter contact on your side
The questions I will ask.
So you know where it is heading — and whether you already have the answers today.
- Which process costs the most time today without getting any better for it?
- Where does the data live today, and which system is authoritative for it?
- Who decides in this process, and how is that decision visible afterwards?
- What happens today when somebody skips a step?
You cannot buy this ready-made. What gets built follows the way your company works.