


Contents (20 sections)
- Off-the-shelf, configurable or custom: what are we talking about?
- When custom software is worth it, and when it is not
- What drives the price of custom software
- Scope: screens, business rules and users
- Integrations with your other tools
- Permissions, roles and audit trail
- Migrating existing data
- Hosting, security and maintenance
- How long does it take to build custom software?
- The stages of a project, from first conversation to go-live
- Who owns the code of custom software?
- Questions to ask a developer before signing
- Examples from our own projects
- Frequently asked questions
- What does custom software cost?
- Is custom software more expensive than an off-the-shelf product?
- Can we start small and add to it later?
- What happens if our needs change during the project?
- Should we budget for maintenance?
- A price you build, not one you guess
Custom software has no list price. Yet its price is no mystery: it is built from a handful of factors that can be named, and acted upon. This guide starts with what custom software is and when it is not worth it, then covers what drives its price, how long it takes, the stages of a project, who owns the code and the questions to ask a developer. It closes with examples from our own projects and a few questions and answers.
We do custom software development in Strasbourg for small and mid-sized companies, non-profits and local authorities, and what follows is what we say in a first conversation. You will not find a price grid here: our price ranges are on the pricing page. This guide explains what will put your project at the bottom or the top of the range.
Off-the-shelf, configurable or custom: what are we talking about? #
Off-the-shelf software is sold identically to thousands of companies: accounting, email, appointment booking. You use it as it is, you usually pay a subscription per user and per month, and its vendor decides what it becomes. It is almost always the cheapest choice at the start, and often the right one.
Configurable software starts from a common base that gets adapted: extra fields, approval workflows, modules switched on. Many ERP and CRM products work this way. Configuration has a cost, sometimes a high one, and it stops where the vendor decided it would.
Custom software is written for a single organisation, from the way it actually works. It does only what you need, it follows your rules instead of imposing its own, and you own its code. In return, everything it does has to be designed, written, tested and then maintained: that work is what you pay for. Most of the time it takes the form of a web application that opens in a browser, with nothing to install on anyone's computer.
When custom software is worth it, and when it is not #
The first question is not price, it is usefulness. When a product on the market covers most of your needs, take it. Rebuilding accounting, payroll or a shared calendar makes no sense: proven products exist, and your way of working would gain nothing. We say so in the first conversation, even when it costs us a project.
Custom software becomes worthwhile in three situations. The product on the market does not fit your business, and you spend your time working around it with exports, re-keying or a spreadsheet kept on the side. Licences cost more than the tool brings in: a subscription is paid every year, forever, while a development pays for itself over time. Or an internal tool is reaching the end of its life, an Access database or an Excel workbook that has become critical, and that will stop working on the day the person who understood it leaves.
There is also a middle path: keep the product on the market for what it does well, and write a smaller tool alongside it to fill the gap. It is often the cheapest project of all.
What drives the price of custom software #
The price of custom software is mostly working time. Five factors determine that time, and they are the ones we look at in a first conversation.
As a guide, here are our price ranges, excluding VAT. They are starting points, not list prices: every project gets a written quote. The details are on the pricing page.
| Service | Price range |
|---|---|
| Custom business application | from €15,000 excl. VAT |
| Brochure website | from €1,900 excl. VAT |
| Managed services and maintenance | from €250 excl. VAT a month |
| Time and materials, per day | €450 to €550 excl. VAT per day, depending on the profile |
Scope: screens, business rules and users #
This is the heaviest factor. It is measured in screens, business rules and types of users. A business application used by one team in-house does not take the same work as a platform open to your customers, with sign-up, a personal account area and card payments, even on an identical subject. A pricing calculation with discounts, or an approval workflow with several levels, often takes longer than the screen that displays it. Scope is also where you have the most room to manoeuvre: a tighter scope costs less and is delivered sooner.
Integrations with your other tools #
Every system the software has to talk to adds an interface to write, test and then monitor: accounting, a payment provider, email, a company directory, text messages, a machine on the shop floor. The cost depends on the other side. A service with a documented API connects without any particular difficulty; an old program that can only produce one file a night takes more work and more care.
Permissions, roles and audit trail #
Who sees what, who can change what, and who did what. A tool where everyone has the same rights stays simple. As soon as management, staff, partners and customers each have a different scope, you need roles, permissions per area and a change log that cannot be rewritten, some of which the GDPR requires. Every screen and every action has to respect these rules, and every rule has to be tested.
Migrating existing data #
Migrating clean data is quick. Migrating files built up over ten years is much less so: duplicates, columns used for something other than their heading, dates in three formats, totals that do not add up. The data has to be cleaned, the totals checked with you, and sometimes the old and new tools have to run side by side for a while. This item is often underestimated, because it does not show on the mock-ups.
Hosting, security and maintenance #
Software has to run somewhere, be backed up, patched and monitored. An internal tool used during office hours does not call for the same monitoring as a platform that takes orders at night. This running cost is priced separately from the project, every month, and it belongs in the calculation from day one.
Then there is the way the work is priced, which mostly changes who carries the risk. At a fixed price, the price and the schedule are firm, and the developer absorbs any estimation gap; this requires a scope that can be described in advance. On a time and materials basis, you pay for the time spent, which suits a need that becomes clearer as you go. Price ranges per type of project are on our pricing page.
How long does it take to build custom software? #
We give everyone the same answer: a showcase website takes weeks, a business application takes months. Timelines depend on the same factors as price, with one nuance: adding developers does not shorten a project in the same proportion, because decisions and approvals have their own pace.
Three things most often stretch a schedule, and none of them is technical. The availability of the people who decide: a business question left unanswered for two weeks blocks the screen that depends on it. Third parties: getting access to a supplier's API sometimes takes longer than connecting to it. And data, when cleaning it reveals cases nobody had described.
What shortens the perceived timeline is delivering in stages: the first features are in testing on your side well before the end of the project. If a deadline is fixed, a trade fair or a regulatory obligation, whatever must be ready on that day comes first, and we say clearly what will wait.
The stages of a project, from first conversation to go-live #
It all starts with a first conversation, free with us, in which you describe your need and the tools you use today. Then comes scoping: we document your process as it really is, exceptions included, because exceptions are where generic software fails. Scoping leads to a written quote, with a detailed scope, a price and a schedule, before the first line of code. We cover the steps to build custom software in a separate guide.
Screens are designed before they are built, so that your users can correct course early: a change costs little on a mock-up and much more on a screen already wired to the database. Development then moves forward in small steps, with a demonstration each time, on a staging environment kept separate from production. Automated tests check the code, then come the data migration and acceptance testing, in which your teams check that everything works as planned.
After go-live, every fixed-price delivery is covered by a three-month warranty with us. Then the software's life begins: fixes, small changes, security updates. Maintenance of custom software is not compulsory, but software nobody looks after ages quickly, and you notice at the worst moment.
Who owns the code of custom software? #
The answer should be: you do. It is not automatic, and it is the clause of the contract to read most carefully. Under French law, software written by an outside contractor belongs to its author until the rights have been assigned in writing. A contract that says nothing on the subject leaves you the right to use the software, not necessarily the right to have someone else develop it further.
Check three things. That the contract provides for the assignment of rights and says when it takes effect: with us, it is complete upon full payment for the work. That you actually receive the source code and its documentation, not just access to the software. And that the essential accounts, domain name, hosting, email sending, are in your name or will be handed over. If you ever change provider, you should leave with all of that, plus an export of your data in open formats.
Questions to ask a developer before signing #
Two quotes are hard to compare if you do not know what they contain. Ask first what is included and what is not: scoping, testing, go-live, documentation, data migration, warranty. Then ask how a change along the way is handled. At a fixed price, it should go through a priced amendment that you accept or decline, never through a line that appears on the invoice.
Ask who writes the code and who will maintain it: a team that designs, builds and then maintains does not rediscover the software at every intervention. Ask where it will be hosted, who has access, and whether backups are actually restored from time to time. Ask which technologies will be used: widespread technologies will let you find someone else in five years, an exotic stack will not.
Finally, ask to see an application the developer has written and that is running today, and what the next stage will cost once the warranty ends. A developer without a clear answer before signing will rarely have one afterwards.
Examples from our own projects #
Price differences are easier to explain with real cases. Here are four pieces of software we have written, from the smallest to the broadest.
At one end, our availability detection robot. The need fitted in one sentence: be told as soon as a slot opens up on a booking website. The program reads the site like a visitor and sends an email and a text message as soon as a slot appears. One user, no roles, no data to migrate: the cost stays modest, because the scope does.
In the middle, the membership management platform written for a dance association that we do not name: members, enrolments, fees, schedule and workshops. Roles and rules did most of the work. The treasurer, the secretary, teachers and members do not see the same things; each class has a capacity and a waiting list per dance role; payments go through card via HelloAsso or are entered by hand.
Broader still, BuyStep, a professional marketplace for energy equipment, named with the client's consent: six languages including Arabic, a supplier audit from which the platform derives a score, subscriptions collected through Stripe and a full administration area. BuyStep also shows that well-built software can evolve without a rewrite: its database, framework and interface were replaced one by one, without touching the business core.
Finally, Madaris is not a client commission: it is a product we publish, school management software for private schools in Morocco, in three languages, with one instance per school. It is a publisher's work, carried on over time to serve many schools. By contrast, it is a reminder that a tool written for a single organisation can stay much simpler.
Frequently asked questions #
What does custom software cost? #
There is no single price, because no two pieces of software are identical. A simple internal tool costs far less than a platform open to your customers, with card payments and a personal account area. As a guide, with us, a business application starts at €15,000 excl. VAT. Our price ranges are published on the pricing page, and the written quote follows a free first conversation.
Is custom software more expensive than an off-the-shelf product? #
At the start, almost always. Over several years, not necessarily: a per-user subscription is paid indefinitely, and the time lost working around a poorly suited tool has a cost too.
Can we start small and add to it later? #
Yes, and it is often the best way to go. A first phase focused on the core of the need is delivered sooner, is tested in real conditions and lets you decide what comes next based on facts.
What happens if our needs change during the project? #
That is normal. At a fixed price, a change of scope is covered by a priced amendment that you accept or decline before it is carried out. On a time and materials basis, the need adjusts continuously, since you pay for the time spent.
Should we budget for maintenance? #
Yes. Software needs security fixes, backups and monitoring. With us, every fixed-price delivery has a three-month warranty; beyond that, maintenance is covered by a contract priced according to how critical the application is, which you are free to take out.
A price you build, not one you guess #
The price of custom software is a sum of choices. Scope, integrations, permissions, data and operations are decided, and each can be reduced, moved to a second phase or accepted knowingly. What costs a lot is mostly surprises: a data migration discovered too late, a change that was never priced, maintenance that was forgotten.
Our custom software development follows this logic: a free first conversation, a written quote that details the scope, code that is yours upon payment, hosted on our servers in France and then looked after, if you wish, by the team that wrote it.
Do you have a project, a tool reaching the end of its life, or a quote you would like to understand? We can review it with you: what genuinely calls for custom work, what a product on the market would do just as well, and what the rest would cost.






