The short answer: the price follows what the software has to handle. That means the people who use it and the rules it follows. It also means the systems it connects to, and the data it starts with. Two tools that look alike can differ a lot in price. The difference sits behind the screen.

We don’t publish a price list, because a number without a scope says little. This guide explains what moves the price instead. It should help you judge a quote, ours or anyone else’s.

What decides most of the price

Who uses it, and what each person may see

One kind of user is simpler than several. Every role adds screens, and every rule about who may see what adds work and tests. Say each company may see only its own records. Then that rule must hold everywhere, not on one screen. In our own E-Bike Battery Passport, the database itself enforces it.

The rules of your business

Most of the work is not the screens but the rules behind them. What happens when an order is cancelled halfway? Who approves a change, and can it be undone? Each rule is small. Together they are the product. A written list of them is the best way to get a quote you can rely on.

Connections to other systems

Linking to accounting software, a webshop or a CRM often costs more than people expect. The other system decides what is possible, and its quirks become part of your project. A well-documented API is quick to connect. An old system without one can take longer than everything else.

The data you already have

Moving data from spreadsheets or an old system is a piece of work in itself. Data is rarely as clean as it looks. A column means one thing in one year and something else the next, and duplicates hide everywhere. Plan time to clean it, and to check the result with the people who know it.

Where and how it is used

A web app that runs in any browser is the most affordable start. A mobile app adds the app stores, and two platforms to test. Working offline adds more again. Every change made without a connection has to be sent and checked later, without ever being recorded twice.

Sign-in and security

Accounts, password resets and permissions are expected today, and they are real work. So are backups, monitoring and keeping libraries up to date. None of it shows in a demo. Leaving it out is how cheap software becomes expensive.

What you pay after launch

The build is not the whole cost. Software runs on hosting, sends email through a service and depends on libraries that need security updates. Expect running costs for:

  • hosting and the database;
  • services such as email delivery;
  • updates that keep it secure and working with new browsers and phones;
  • small changes, as you learn how people use it.

Ask any builder what these will be, and in whose accounts they run. In our custom software work, hosting, monitoring and backups can be set up in your own accounts.

How to keep the price down

  1. Start with one process. Pick the one that costs the most time today, and solve that first.
  2. Write down what it won’t do. A list of what waits is as useful as a list of features. Our article on why most MVPs contain too much goes deeper.
  3. Use what already works. If a standard tool handles part of the job well, connect to it rather than rebuild it.
  4. Bring real examples. The spreadsheet, the email thread, the paper form. They show the rules faster than any description.

Questions to ask about any quote

Which roles and rules are included? Which connections, and who maintains them? What happens to the data you have now? What runs after launch, and in whose accounts? And what is left out?

When you shouldn’t build

Custom software makes sense when the way you work is part of your strength. It also makes sense when standard tools force your team into costly workarounds. It doesn’t when a standard tool does the job well. Email and most office work are better bought than built. If a spreadsheet works for a few people and rarely goes wrong, keep it.

Sometimes the honest answer is a smaller step. That could be a better spreadsheet, or one link between two tools.

How we work out a price

We start with a conversation about what you need and how the work runs today. From there we propose a first version, with its scope and price. The scope says what is in it, and what is not. Then you know what you are paying for before anything is built.