Insights

Custom development: when the standard is not enough

Standard software covers ninety percent. For the remaining ten percent we develop – and we also say when it is not worth it.

Roland Kainbacher – Porträt Roland Kainbacher 5 min
Illustration: Praktische Funktionen im Überblick

Standard software covers ninety percent. The remaining ten percent are often exactly what sets a project apart – billing according to municipal rules, a connection to an existing booking system, a process that does not exist anywhere else yet. For those ten percent we develop.

Why we do this

Zemtu grew out of running our own carsharing service. We know the situation where something is missing and there is no setting for it. That is why custom development is not an exception here but part of the cooperation.

This sets us apart from platforms that have to work the same way for everyone. With us the question is not "is that possible?" but "is it worth it for your project?".

What usually gets adapted

  • Appearance. Logo, colours and wording are standard. Beyond that, flows in the app can be changed or features hidden that would only confuse your audience.
  • Billing. Municipal rate models, social rates, membership fees, cost centre logic in corporate fleets – rarely is anything off the shelf a fit here.
  • Interfaces. Connections to accounting, ERP, mobility networks or the customer account on your existing website.
  • Access technology. If you use hardware we have not integrated yet, we review the interface and connect it.
  • Reports. Analyses in the format your supervisory board, funding body or accounting actually needs.

How an adaptation runs

It starts with a description of the problem, not of the solution. Often it turns out during the conversation that part of it can be solved with existing means – then you save the development.

For the rest we estimate effort and cost and define exactly what will be built. You receive the implementation for testing before it goes live. Larger projects are split into stages so you see early where things are heading.

What becomes part of the standard

Some adaptations only make sense for one project. Others turn out to be something several operators need. In that case we take it into the software – and maintain it further without you carrying the cost alone.

That has a pleasant side effect: your adaptation survives updates instead of creating effort with every new version. We are open about what falls into which category.

When we advise against it

Not every idea should be built. If an adaptation only covers a special case that occurs twice a year, a manual step is often cheaper than development plus ongoing maintenance. We will say so.