Software built around the work no off-the-shelf package fits

They have one thing in common: small, clear tools a team uses every day, designed in the language of the people doing the work.

If a reasonably priced product already does what you need, we will tell you to buy it. Custom software makes sense when the rules are specific to your company, when packaged products do not talk to SAP, your ERP or your existing tools, or when data must not leave the company.

The real cost of custom software is not the first version but the years of maintenance after it. So we start small: one version that solves one job and actually gets used, then growth driven by that use.

A shared spreadsheet works up to a point. Then there are several copies, nobody knows who changed what, a formula breaks and no one notices. We turn it into an application that keeps the same fields and habits, so everyone sees the same data and every change is recorded with who made it. People can still export to Excel; the difference is that the correct data lives in one place.

We design with the person who does the work and put a first version in front of them as early as possible. A working version instead of a long specification: the user tries it, says what is missing, and the next version follows from that. For small tools that loop is measured in days, for larger applications in weeks.

Critical rules are protected by automated tests. Installer, user documentation and training are part of every delivery, and maintenance continues after go-live.

For one team we built a tool that sends the planned work to the team every morning and evening through Teams and e-mail; the plan is entered once and the tool handles distribution. For a manufacturer we built a modular platform that carries the repetitive SAP work of several teams; each new process is a new module.