Why don't you name a price straight away?

Because a fixed price per phase without research is a guess. You pay for that guess later as extra work. The lower limit is the starting price at the top of this page, excluding VAT. What your software costs is only in the report from the discovery.

What do I get for the discovery?

A report setting out what the software does and doesn't do, which integrations are possible and where the risks are. And a fixed price per phase. The discovery is yours, even if you don't carry on with us afterwards.

Can you connect to the system we use now?

We work that out in the discovery. If the system offers an integration, we use it; if not, we look at exports or a layer in between. If it can't be done, that's in the report before you have anything built.

What if we want to switch to another developer later?

You can. Code and accounts are in your name from day one, and the documentation comes with them. Another developer can pick up where we left off.

Custom software: know first, then build

Software of your own is a large outlay. That's why every project starts with a paid discovery. It sets out what the software does and doesn't do, where the risks are and what each phase costs, fixed. Then you decide whether we build. If you go ahead with us within three months, we credit the discovery against the first phase. The discovery is yours, even if you don't carry on with us afterwards.

from €9,500All prices are starting prices, excluding VAT.

after a paid discovery of €1,500, credited against phase 1 if you proceed within 3 months

Paid discovery: scope, risks, a fixed price per phase · API integrations · cloud account in your name

Plan your project

What you get

The discoveryWe map who will use the software, what the steps are today and which systems need connecting. You receive a report with scope, risks and a fixed price per phase. The price of the discovery sits next to the starting price at the top of this page.
DashboardsOne view of figures that are now scattered across systems and spreadsheets. You set who sees what, role by role.
Client portalsA secure area where your customers log in to check orders, documents, invoices or the status of a request.
IntegrationsWe connect your software to what you already use, such as your accounting package, customer records or scheduling. Documented, so another developer can take it further too.
Hosting in your nameHosting, database, backups and separate environments for testing and for real work, set up in an account in your name. Code and accounts are in your name from day one.
Measured on every updateOn every update we measure how quickly the key screens load. The agreed load time is in your contract.

How it runs

First conversationYou tell us which work gets stuck and which systems you use today. You get a reply within one working day. If an off-the-shelf package is the better choice, we say so at this point.
DiscoveryWe talk to the people who will use the software and look at your systems and data. We test whether the integrations are possible. The report contains scope, risks and a fixed price per phase.
Your decisionYou decide whether we build, and in which phases. If you go ahead with us within three months, we credit the discovery against the first phase. If you don't go ahead, you keep the report.
Building in stagesEach phase has a fixed price. Along the way we show working versions on a test version and your team tries them out. If the first design isn't right for you, you can stop with no further costs.
Launch and handoverThe software goes live in your own account and you get the documentation. The code was in your name all along.
Maintenance, if you want itAfter that we can update the software, keep an eye on it and keep developing it. When we can be reached and how quickly we respond are agreed per contract.

When you don't need us

For accounting, customer management, scheduling or a standard online shop, good packages already exist. Building your own means paying for something you could simply buy. If you only need two packages to exchange data, a link tool is often enough – look at automation first. If your way of working isn't clear yet, try it in a spreadsheet first. You'll have a better idea of what you want built.

Tools

TypeScript · Next.js · React · Docker · AWS · Google Cloud

Under the hood

TypeScript, Next.js and React, with APIs to your accounting package, CRM or online shop. Hosting, database, backups and separate test and production environments in a cloud account in your name, for example with AWS or Google Cloud, with documentation. The discovery delivers a data model, a list of integrations with their limits (API, export or a layer in between) and a phasing with a fixed price per phase.

Questions we often get

Why don't you name a price straight away?: Because a fixed price per phase without research is a guess. You pay for that guess later as extra work. The lower limit is the starting price at the top of this page, excluding VAT. What your software costs is only in the report from the discovery.
What do I get for the discovery?: A report setting out what the software does and doesn't do, which integrations are possible and where the risks are. And a fixed price per phase. The discovery is yours, even if you don't carry on with us afterwards.
Can you connect to the system we use now?: We work that out in the discovery. If the system offers an integration, we use it; if not, we look at exports or a layer in between. If it can't be done, that's in the report before you have anything built.
What if we want to switch to another developer later?: You can. Code and accounts are in your name from day one, and the documentation comes with them. Another developer can pick up where we left off.