Price How much will a marketplace cost in Belgium in 2026?
SB
Sebastien Balieu
Dec 11, 2025
A tool that follows your processes , not the other way round.
- Freelance developer in Brussels
- Reply within 24 h
- You talk to the person who writes the code
What you gain by leaving spreadsheets behind
01 
You get back a single source of truth.
The data living in six spreadsheets and three inboxes moves into one tool. Everybody looks at the same number at the same moment, including in meetings.
02 
The tool speaks your team's vocabulary.
An off-the-shelf tool imposes its own logic and vocabulary. Yours follows your steps, your words and your own rules, including the ones that only exist inside your company.
03 
You pay once, not per user.
Per-seat subscriptions get heavy as the team grows: every new arrival adds a line to the monthly bill. A tool you own costs the same for five users as for fifty.
What my clients say
Numinam's contribution to the development of our App has been significant in its success with our B2C and B2B customers.
Stephane Draux
Founder • Spengo
At Nallian we build solutions that are trusted by the world's leading airports, ground handlers and logistics companies. But our website no longer reflected that level of excellence. This redesign ensures our first impression matches the quality of…
Jean Verheyen
CEO • Nallian
Numinam has completely modernized our website. The design is clearer, more credible, and our visitors understand what we do. A real leap in quality. Also worth noting is the excellent collaboration between Numinam and our development agency. Thank…
Olivier Lafosse
Founder & CEO • Heat Me
What you get
Process mapping
Your real steps, your business rules, and what happens today outside the software. Sticky notes, emails and phone calls are often as much a part of the process as the CRM.
Business application
Built in Laravel, hosted wherever you want, reachable from a browser. No installation on workstations, no stray version sitting on somebody's machine.
Access management
Roles and permissions per team, an action log. You know who changed what, and when, without having to ask.
Dashboards
The numbers that matter to you, up to date, with no manual export. An indicator that requires a weekly manipulation ends up unread.
Connections to your tools
Accounting, email, calendar, whatever you already use. The tasks left between two systems are handled with automation workflows.
Migration of your data
Import of your current spreadsheets, with no retyping. That is the condition for the team to actually switch rather than keep their file running in parallel.
Code and documentation
You are the owner, another developer can pick it up. Mainstream technologies, no in-house framework only I would understand.
Tools running in production
Every project arrives with its business rules and its exceptions. My job as a developer: make them fit into a tool the team opens every day.
Nallian
Air cargo software solution
A B2B SaaS website redesign that loads in under a second
Stamp
Gamified city exploration
Turning every building you walk past into a card worth collecting
Harmonia
Family habit-tracking app
Helping families build positive habits at home
Coddy
Escape-game e-commerce platform
Urban escape games
What if the next project here was yours?
Ultra-fast sites and apps, built to measure.
Request a quoteHow the tool gets built
Five steps. The first usable version arrives fast, because a tool is judged in use.
100%
- 8%
01 Immersion
A day with your teams to see how you actually work, not how the process is supposed to run. - 12%
02 Specification
Screens, business rules, priorities. You approve the scope and the budget before development. - 35%
03 First usable version
The core of the tool, put into the hands of a few users. That is where the real business rules show up. - 30%
04 Iterations
We adjust with feedback from the floor and add the secondary modules, in the order they are useful. - 15%
05 Switch-over and follow-up
Data migration, training, fixing edge cases. Then three months of support included.
Prices are published, so you know what to expect before you call.
I charge €595 per working day. The price depends on the number of screens, the complexity of the business rules and the number of systems to connect.
Targeted tool
from €7,140
from 12 days · usable in 6 to 8 weeks
One precise need, a few screens, one team.
Mapping of your real processes
One main module, a few screens
Roles and action log
Migration of your current spreadsheets
Code and documentation are yours
Business application
from €16,660
from 28 days · usable in 10 to 14 weeks
Several modules, multiple roles, dashboards, external connections.
Everything the targeted tool includes
Several interconnected modules
Dashboards per role
Connections to your accounting and your tools
Training and support through the switch-over
Most popular
Complete platform
On quote
Client or partner portal, invoicing, production, several teams.
Everything the business application includes
External portal for your clients or partners
Invoicing and production tracking
Several teams, several entities
Open API for your future integrations
Your questions about internal tools
How much does a custom internal tool cost at Numinam?
I charge €595 per working day. The number of days depends on the number of screens and on how complex your business rules are, far more than on the number of users.
| Type of tool | Budget | What it includes |
|---|---|---|
| Targeted tool | from €7,140 (12 days) | One module, a few screens, one team |
| Business application | from €16,660 (28 days) | Several modules, roles, dashboards, integrations |
| Complete platform | On quote | External portal, invoicing, production, multi-entity |
Compare that amount with what you already pay: ten licences at €60 per month come to €21,600 over three years, without the tool fitting your trade any better.
Why not simply take an off-the-shelf CRM?
Because the right answer depends on how far you sit from the standard. If your process looks like everybody else's, an off-the-shelf CRM costs less and I will tell you so. If your trade has its own rules, the off-the-shelf tool gets paid for in workarounds.
| Custom | Off-the-shelf SaaS | Spreadsheets | |
|---|---|---|---|
| Fit to your processes | Total, by construction | Partial, you adapt | Total but fragile |
| Three-year cost | A fixed investment | A subscription growing per seat | Free in appearance, expensive in hours |
| Room to evolve | You decide what comes next | Depends on the vendor's roadmap | Degrades as volume grows |
| Data reliability | Rules enforced on entry | Good | Silent errors are frequent |
| Ability to leave | The code is yours | Limited export | Immediate |
The most reliable signal: if your team has created a spreadsheet running alongside the official software, the software is not doing the job.
How long before my team can use the tool?
Six to eight weeks for a targeted tool, ten to fourteen for a business application. But the first usable version arrives before that: it is deliberate.
I put the core of the tool into the hands of a few users while the rest is being built. The business rules you discover at that moment are the ones nobody would have thought to mention in a scoping meeting.
What happens if Numinam is no longer available?
That is the right question to ask a freelance about a critical tool, and it deserves a precise answer rather than a reassuring formula.
Concretely: the code lives in your repository from day one, it uses very widespread technologies (Laravel, PostgreSQL) that one developer in two knows, and the technical documentation ships with it. The hosting is in your name. I also work with developers I trust who know my projects and can step in. What I cannot promise is being available forever; what I can guarantee is that my leaving does not block you.
Is it risky to depend on a freelance developer for a critical tool?
There is a risk, and it shrinks through concrete measures rather than promises. Here is how it compares with the alternatives.
| Risk | Freelance | SaaS vendor | Agency |
|---|---|---|---|
| Unavailability | Real, mitigated by documented code | Low | Low |
| Product shutdown | None, the code is yours | Real, the vendor decides | None |
| Price increases imposed on you | None | Real, per seat | Depends on the contract |
| Data loss | None, hosting in your name | Export often limited | None |
| Feature refused | A budget question | A roadmap question | A budget question |
The freelance risk is real on availability and nil on ownership. With a vendor, it is exactly the other way round.
Is my data hosted in Belgium or in Europe?
Wherever you want, you choose. By default I host in Europe, generally in Germany or France, on infrastructure in your name.
If you have a Belgian localisation requirement, for a public tender or an internal policy, that is feasible with local hosts. And if your IT is in-house, the application installs on your own servers.
How much time does my team have to spend during the project?
Count one immersion day at the start, then around two hours a week: a feedback session on what has been built, and answers to the business-rule questions that appear along the way.
It is a real commitment, and it is where the project's success is decided. Tools that end up unused are almost always the ones built without the people who were going to use them.
Can the tool evolve after delivery?
Yes, and it is planned into the architecture. Adding a module, a role or an integration is costed in days, at the same rate, with no rebuild.
Three months of support are included after the switch-over. After that, two options: one-off interventions billed by time spent, or a volume of days reserved every month if you expect regular changes.
The logical next step
Going further
What I learned on the subject, written down in black and white.
Price 
Show me your spreadsheets.
Twenty-five minutes to understand how you work and estimate what a tool built for you would cost.
I also tell you when an off-the-shelf product would do. It is free, no strings attached, and it is me on the phone.