Skip to content

Custom software and web

Your processes are the reason your business works. We build the software around them — not the other way round.

What you get out of it

The spreadsheet has become an application

A process runs through a file three people open at once, and nobody knows which version counts. That is not a tooling problem but a grown process with no system behind it.

Two systems that know nothing of each other

Inventory here, accounting there, and a person in between retyping numbers. An interface costs once; the retyping costs every month.

The software exists, just not for this case

The market covers ninety per cent, and the missing ten are the business. The question is then not buy or build, but what to buy and what to build.

How it works

  1. Look at the process

    Before technology is discussed, the process is written down as it runs today — detours included. The detours are the actual brief.

  2. Build the smallest useful slice

    Not the whole system, but the part that changes something first. It goes live before the second part begins — otherwise you are building on assumptions.

  3. Hand over, do not tie down

    Source code, build instructions and credentials are yours. If you want to take over operations or switch, that is a move, not a negotiation.

What you receive

  • Source code in your repository, not ours
  • Build instructions that run through on an empty machine
  • Migrations committed to the repository — no state living only in a database
  • Documentation of the decisions, not just the buttons