Contents
Custom software costs $6,800 to $22,400 (€6,000–€20,000)excl. VAT for a focused business app (1 to 3 months), $16,800 to $56,000 (€15,000–€50,000)excl. VAT for a custom ERP (3 to 6 months), and a SaaS platform is quoted case by case. Add hosting, third-party services and maintenance every year.
“How much will it cost?” is the first question in any project, and the most legitimate one. Custom software has no catalog price, but it does have reliable ranges, which depend on the type of tool and the features you need. Here is my public price list, what moves the price, and the costs to plan around development.
Ranges by type of project
These amounts exclude VAT and cover a first version running in production. The quote becomes fixed after scoping.
| Type of project | Indicative budget | Timeline |
|---|---|---|
| PWA built from an existing website | from $4,000 (€3,500)excl. VAT | 2 to 4 weeks |
| AI integration (first use case) | from $2,300 (€2,000)excl. VAT, plus API usage | 2 to 8 weeks |
| Focused business app | $6,800 to $22,400 (€6,000–€20,000)excl. VAT | 1 to 3 months |
| Custom ERP | $16,800 to $56,000 (€15,000–€50,000)excl. VAT | 3 to 6 months |
| SaaS or multi-portal platform | quoted case by case | 3 to 6 months or more |
| Takeover of a project built with AI or no-code | quoted after an audit | depends on the project’s state |
The $6,800 (€6,000)excl. VAT floor for a business app is not arbitrary: it is the minimum for a reliable tool, with user accounts, access rights, a clean database and screens designed for your teams. The full service description is on the business apps page.
The features that push the price up
On top of the core, each feature adds a fairly predictable amount. These are the building blocks used in my estimator, excluding VAT.
| Building block | Indicative amount |
|---|---|
| User accounts and roles | €1,500 |
| Admin back office | €2,000 |
| Customer or partner portal | €2,500 |
| Quotes, invoices and PDFs | €1,500 |
| Online payment | €1,500 |
| Dashboard | €1,500 |
| Connection to other tools | €2,000 |
| Built-in AI | €2,500 |
| Data migration | €800 |
Some factors multiply the total: 10 to 50 users, ×1.1; over 50, ×1.2; premium design ×1.15; an urgent deadline ×1.2. An existing prototype that has already validated the need lowers the total (×0.85).
An illustrative example: a portal where your customers check their orders, with accounts and roles, a back office, a customer portal, payment and a connection to your ERP, adds up to $10,700 (€9,500)excl. VAT in building blocks before multipliers. For 30 users, ×1.1 applies, bringing the building blocks to $11,700 (€10,450)excl. VAT, on top of the project’s base price. The estimator runs this calculation for you in one minute.
The costs around development
A complete budget does not stop at the provider’s quote. Also plan for:
- hosting, in your name: from a few tens to a few hundred euros a year;
- third-party services billed by usage: email sending, text messages, e-signature, AI API calls;
- maintenance and new features after the three months of included support, covered in the cost of app maintenance;
- your team’s time: scoping workshops, mockup reviews, testing each batch;
- training if several teams or sites need it (from $1,700 (€1,500)excl. VAT).
How to set your budget
I recommend working through it in this order:
- Start from the expected gain. What the tool saves or earns each year sets a reasonable budget. The method is in calculating the ROI of a business tool.
- Define a first version. The features you need on day one, not the full wish list.
- Keep a 10 to 15% margin for adjustments discovered during testing.
- Compare over 3 years with the subscriptions the tool replaces.
Sharing a budget range with a provider from the first conversation is not a weakness: it lets them propose the most useful scope for that amount, instead of a quote that misses the mark.
When custom software is not the right investment
I prefer to be clear: custom software is not always the right spend.
- If an off-the-shelf product covers your needs well for a reasonable subscription, keep it.
- If your budget is below $6,800 (€6,000)excl. VAT and the need is real, it is better to configure an existing tool or start with an audit ($660 (€589)excl. VAT for an express audit) that will tell you where to begin.
- If the process is not yet stable, wait: you can only build well what you can describe.
How a project works
- A free 30-minute discovery call to understand your needs and give you a first order of magnitude.
- Scoping (1 to 2 weeks): requirements document, fixed quote, schedule.
- Clickable mockups (1 to 3 weeks), approved before development starts.
- Development in batches, each tested by your team.
- Go-live, data migration, onboarding, then three months of included support.
Prices are fixed, with a 50% deposit at the start. The source code and rights are transferred to you once the project is paid in full. Everything is detailed on the pricing page.
Frequently asked questions
Can we get custom software for less than $6,800 (€6,000)excl. VAT?
Not a business app that can run in production. Below that threshold, you get a prototype at best. Some targeted services do cost less, though: a PWA built from an existing website starts at $4,000 (€3,500)excl. VAT, and a first AI use case at $2,300 (€2,000)excl. VAT.
How is the budget paid?
A 50% deposit is paid at the start, then the balance according to the schedule set out in the quote, usually as batches are delivered. The price is fixed: it does not change as long as the scope approved during scoping stays the same.
Can the quote end up above the estimate?
The estimate gives a range. The fixed quote is drawn up after scoping, once the exact scope is known. After that, only new requests added along the way lead to an additional quote, which you approve beforehand.
Should we budget for team training?
Onboarding is included at go-live. For more in-depth training, for example several teams or sites, dedicated training starts at $1,700 (€1,500)excl. VAT.
How can we reduce the budget without losing what matters?
By reducing the scope of the first version, not the quality. Deliver first what saves the most time, then add the rest in batches. An existing prototype, for example built with a no-code tool, can also lower the cost if it has properly validated the need.