"I'd like a site where my clients can also book, pay and follow their file." That sentence, said in one breath, actually contains two projects: a website and a piece of software. The first is counted in weeks, the second in months. Knowing which one you're asking for changes everything — the budget, the timeline, and even who you should hire.
The real difference: who works, you or the visitor?
Forget the technology for a moment. A brochure site is a leaflet : it speaks, the visitor reads. A web application is a service desk : the visitor comes in, identifies themselves, fills something in and gets something back. The leaflet informs; the desk processes.
That's where the analogy stops, because the consequence is very concrete. A leaflet has nothing to remember. A service desk has to know who you are, what you're allowed to do, what you did yesterday, and what to answer when two people ask for the same thing at the same time. That memory and those rules, invisible on screen, are most of the work.
- Presents your business, your offers, your references
- Content that rarely changes, updated by you
- Goal: be found and make people want to call
- A contact form, no user accounts
- Measured in weeks
- Accounts, roles and permissions
- Data that lives: created, modified, kept in history
- Goal: replace a manual process
- Business rules, edge cases, scaling
- Measured in months
The three-question test
You don't need technical vocabulary to decide. Three questions are enough, and you already know the answers.
Do your visitors need to log in?
A username and a password, because each person must see information that belongs to them.
Do they create data you have to keep?
An order, a file, a booking, a document — something that still exists tomorrow.
Are you replacing a spreadsheet or a notebook?
If the project makes a shared sheet or a binder disappear, that's a sign that doesn't lie.
A single "yes" : you're talking about an application. Budget and timeline change scale.
When the brochure site is enough — and that's fine
There's a stubborn misconception: that the brochure site is the "budget" option, the step you settle for when funds are short. It's false. For a vast majority of tradespeople, practices, restaurants and shops, the brochure site is exactly the right tool, and an application would be money out the window.
The brochure site is the right choice when what's at stake isbeing found and inspiring trust : appearing in Google when someone searches for your trade in your area, showing your work, reassuring, and prompting a call or a message. A website does that job very well — provided it's fast, readable on a phone and properly ranked.
A good brochure site isn't an "easy" project either: local search visibility, loading speed, clarity of message and quality of the writing make all the difference between a site that brings clients and a brochure nobody sees. That's what we handle in our offers for website creation.
When you really do need an application
Conversely, some needs simply don't fit into a website, whatever you do. If your clients need to follow the progress of their file, if your teams enter information in the field, if you manage stock, schedules or multi-step approvals, then you need software — the fact that it opens in a browser changes nothing.
The most reliable sign is the spreadsheet that has become unmanageable. Almost every business application we build replaces a shared sheet that grew until it became dangerous: nobody knows which version is authoritative any more, two people overwrite each other's work, and one copy-paste mistake costs a day. That's the moment a custom tool becomes worth it — the subject of our article on the time it takes to build an application or an ERP.
The most frequent case: the in-between
In reality, most requests are neither entirely one nor entirely the other. It's a brochure site plus one building block : a presentation site with a booking module, a client area for uploading documents, an online quote, an order tracker.
Good news: that in-between is handled very well, as long as you name it. The method that works is to separate the two layers : a solid brochure site, online quickly, already bringing you clients while the business block is built alongside. You don't block six months of visibility waiting for a big project to finish.
The bad method, the one you see most often, mixes everything into one vague quote. You pay an application price for a website result, or the other way round — and nobody is happy.
Torn between the two? That's exactly what the first conversation is for: laying out your need plainly and telling you honestly which side it falls on. No commitment, and no pushing you towards the more expensive option.
Take stock with us →What it really costs
Let's be direct on one point: nobody can give you a firm price without knowing your scope, and be wary of anyone who does. A price quoted blind is either padded to cover the unknown, or artificially low to win the signature — with the extras arriving afterwards.
What we can be perfectly clear about is what moves the invoice. In our projects, the budget gap between two requests that "look alike" almost always comes from these three factors.
The number of roles
An anonymous visitor costs almost nothing. As soon as there's a client, an employee and an administrator seeing different things, the invisible work multiplies.
Connections to what exists
Payment, invoicing, calendar, accounting software, an ERP already in place. Every system to connect is a small project within the project.
The level of demand
An internal tool for five people doesn't face the same constraints as a service open to thousands of clients, where security and availability become critical.
An honest order of magnitude, without selling you dreams: a professional brochure site is counted in weeks of work, a business application in months. The budget ratio between the two rarely plays out at a factor of two — more like five or ten. That's precisely why the question "site or application?" deserves to be settled before any price discussion, not after.
And while we're on costs: security and nFADP/GDPR compliance aren't an optional line added at the end. As soon as you store client data, they're part of the base — we explain why in our article on cyber risks for SMEs.
The mistake that costs the most
It goes both ways, and we see it about as often on one side as the other.
Choosing the application out of ambition. A project starts with the idea of a full platform, with a client area, dashboards and notifications, while the business hasn't yet confirmed that anyone is buying the service. Six months and a substantial budget later, the tool works — but there's nobody in it. The real need was to be visible and win the first ten clients.
Choosing the site out of thrift. The opposite costs just as much, more quietly. You rig up bookings in a contact form, manage files in a spreadsheet on the side, add an extension here, a module there. After two years the whole thing is held together with tape, nobody dares touch it, and it all has to be redone — having paid twice.
In both cases the cause is the same: the question was never asked frankly at the start.
Our real work: telling you when you don't need an application
At Renova Softwork, the most useful part of our job often comes before the first line of code: the scoping. That's the moment we translate "I'd like a site where clients can also book" into a precise, costable scope, sized above all to your real situation.
We regularly turn down application projects. Not for lack of appetite — it's the part we most enjoy building — but because the need described can be solved with a good brochure site and two off-the-shelf tools, for a tenth of the budget. Selling the rocket to someone who needs a van means winning a project and losing a client.
And when the application is justified, we build it on foundations meant to last: roles thought through from the start, clean data, security and compliance built in as standard. That's the point of our offers for custom software — start useful, and grow when the need really grows.
The same reasoning applies to the building block everyone is asking for right now: we apply it to conversational assistants in our article "AI chatbot for SMEs: useful or gimmick?".
Frequently asked questions
What's the difference between a brochure site and a web application?
A brochure site presents information: the visitor reads, then contacts you. A web application puts the user to work — they log in, enter data, trigger actions, and the tool applies business rules. The difference isn't necessarily visible on screen, but it completely changes the architecture, the timeline and the budget.
How do I know which side my project is on?
Ask yourself three questions: do my visitors need to log in? Do they create data I have to keep? Am I replacing a spreadsheet or a notebook? Three "noes" and a brochure site is enough. A single "yes" and you're talking about an application.
Can we start with a site and add an application later?
Yes, and it's often the best strategy. You put a brochure site online quickly so it starts bringing you clients, then build the business part alongside, on foundations designed to connect to it. You don't block months of visibility waiting for a big project.
Why do quotes vary so much for "the same" project?
Because the scope is almost never the same, even when the description is. Three factors explain most of the gap: the number of user roles, the existing systems to connect (payment, invoicing, calendar), and the level of demand on security and availability. A serious quote spells out those three points.
Is a brochure site still enough today?
For a large share of tradespeople, practices, shops and restaurants: yes, easily. What matters is being found at the right moment and inspiring trust. A fast site, readable on a phone and well ranked locally, does that job better than a complex platform nobody uses.