Custom software: how it works.
When a bought tool will not fit, what a first version should look like, and how an engagement runs from the workaround you live with to software that is yours.
Last updated
When custom is the right call.
Custom software is worth it when the workaround your team lives with is costing more than a system built around the real work. Spreadsheets between tools, copy-paste into a CRM, a process no product quite fits. The gain is software they actually use, handed over as yours.
It is one of four capabilities, alongside cloud, data and AI. AI is added where it earns its keep — we will not put a model on a job a simpler system should do.
The product still needs a home that stays up — that is cloud infrastructure. How the engagement runs across all four capabilities is in tech consulting.
How an engagement runs.
Same shape as the rest of the work: start where the time goes, ship something real, then keep it running.
The job, not the stack
We pin down the workaround and what “working” means — before anyone picks a framework. You leave the first call knowing whether custom is the right call, and what it would take.
A first version they can try
Built around real examples from your work. Your team tries it, breaks it, and tells us what is missing. That is the design process.
Hardened and handed over
In your environment — your cloud or a private appliance — with documentation and training. You own it.
Kept running
Patched, monitored, improved as the business grows. We stay involved because you want us to.
What to ask any software partner.
Whoever you talk to — us included — these questions separate a partner from a pitch.
Will we own it?
Accounts, source, documentation. If the answer is a licence you can never leave, keep walking.
Do they ship a first version you can use?
A working slice in weeks beats a six-month specification. You should see the real work, on your data, before the rest is committed.
Where does it run?
Your cloud account or an appliance on your premises — not a shared box you cannot see into.
What happens after go-live?
Handover, training, and a clear offer to keep it running. You should not need to book a call to change a label.
Frequently asked questions
When is custom software worth it versus buying a tool?
When the workaround is taking over the week — five tools, a spreadsheet in the middle, and a process no off-the-shelf product quite fits. If a good SaaS tool already does the job, buy it. Custom is for the work that is yours.
How long does a first version take?
Weeks, not a year. A first version your team can try, break and improve — then we harden what they actually use. You should see something real before you commit to the whole picture.
Who owns the software when you are done?
You do. Accounts, documentation, the running product. We stay because you want us to, not because the system is locked to us.
Do we need a developer on staff afterwards?
No. Handover and training are part of the work. We can keep running it, or your team can — you should not be stuck either way.
What does custom software cost?
It is quoted per project after a short call, because the job is yours. Most clients start with one painful workflow, not a rebuild of the company.
Tell us the workaround your team lives with.
Send a few details and we will set up a short call. No obligation, no hard sell.