Skip to content
Calango Lab — homeCalango Lab
03 When off-the-shelf won’t do

The software follows your process.

For the process that won’t fit off-the-shelf software. We research it, build it and keep it running — because custom software with nobody looking after the server afterwards is half a job delivered.

When off-the-shelf won’t do

Stock control with rules of your own, work-order management, a customer portal, integration between systems that don’t talk, management reporting, and automating what is done by hand today.

The research starts with the people who run the process every day, not with the org chart. That’s where the rules nobody ever wrote down turn up — the ones that sink projects at the end.

What actually changes
three parallel spreadsheetsone source of truth
export it and retype itautomatic integration
a report assembled by handa dashboard that updates itself
the process bends to the softwarethe software follows the process
01

Research with the people who use the system day to day

02

Development in partial releases, validated at each step

03

Training for the team

04

Technical documentation and a user manual

05

A warranty period for fixes after completion

Questions

What people usually ask

How do I know custom is worth it?

When off-the-shelf software exists and solves the problem, it wins — it’s cheaper and it has been tested by thousands of companies. Custom is worth it when the process is the company’s competitive advantage and bending it to fit a tool would cost more than building the right thing.

Who builds it? Is it one person?

It’s a small team of three: development, DevOps and infrastructure. On larger projects a core of specialist partners joins as the scope demands, but the research, the architecture and the ongoing support stay with the people you already know — building it and running it aren’t sold by different companies.

Does the system lock us in to you?

No. Code, database and technical documentation are handed over, and the user manual with them. The dependency that remains is the one any software has on whoever maintains it — and that one is contractual, not technical.