Web app development
Website development and custom business software.
Public sites, web applications, and the internal software a company runs on. Built around how your business works, not around a template.
Web development, and where it stops being a website
A lot of projects start out as a website and turn out to be an application. The line is usually accounts: the moment someone has to log in and the page has to know who they are, you are building software, and it needs to be planned like software.
We build both, and we would rather tell you which one you are asking for before there is a budget attached to the wrong answer.
Custom business software
The other common shape is a company that has outgrown its spreadsheets. Quotes, jobs, stock, scheduling, whatever the business actually runs on, spread across files nobody dares change. Replacing that with custom business software is a category of its own.
It is not the same as buying a product. Off-the-shelf tools cost less and you should take one where one fits. Custom earns its price when the process itself is what makes your margin and no product matches it.
What keeps it running afterwards
A web product is not finished when it is deployed. Someone has to be able to change a piece of content, add a user, look at what broke last night. We build the admin side and the monitoring alongside the product, because adding them afterwards costs more.
Hosting, deployment and the database are part of the work, set up and documented rather than discovered on the day of launch.
In this order
What happens, and where the cost sits.
The same three phases whatever we are building. What a first version costs is on the how we work page rather than here.
- 01
Two or three sessions, free
We sit down with you and structure the idea before anyone writes code. Who it is for, what the first version has to do, what it leaves out on purpose. Two or three sessions, and there is no invoice for them. You leave with the idea written down, whether or not we build it.
- 02
A first version
Then we build it. Not a clickable prototype: the design, the mobile or web app, and the backend it runs on, in a state real people can use.
- 03
Then reaching a market
Building the product is the part everyone talks about. Getting it in front of people who pay is the part that decides whether it lives. We have done that inside our own companies, and we are extending it to the products we build for founders. It is new for us, and we would rather say so than sell it as a finished service.
What's included
What you get, whatever the scope.
01
The front end
React in the browser, written so a developer who is not us can pick it up.
02
The application behind the pages
Accounts, permissions, and the workflow the business actually runs on.
03
The admin side and the monitoring
Changing a piece of content, adding a user, seeing what broke last night.
04
Hosting, deployment and the database
Set up and documented before launch rather than discovered on the day.
Proof
What these products did after launch.
Products we designed and built. Most have no write-up on this site, so these are figures rather than links.
Blue Charter : 5M€ funding
iFREQ : 1m€ ARR
Team
Meet the people you'll work with
No account managers in between. The people who design and build it are the people you talk to.
Oscar Fally
Founder · Product & development
Antoine Visart
Design
Elliot Verstraelen
Development
What people ask before a web project.
Is this a website or a web application?
If visitors read it, it is a site. If users log in and it holds their data, it is an application. Plenty of projects are both, and the second half is where the budget goes.
Can you replace our spreadsheets?
Often, yes, and that is usually the clearest version of this work. The first sessions map what the spreadsheets actually do, which is almost never what people describe from memory.
What technology do you use?
React on the front end, and a backend picked to fit the project. We are not attached to any of it. What matters is that a developer who is not us can pick the code up.
What happens after launch?
Someone has to keep it running, and that is worth deciding before launch rather than after. Some teams take it in-house, some keep us on it. Either way it is built to be handed over.
Enough about us, what about you?
Looking for a partner to build your product? Or sitting on a market you know well and cannot build for? Either way, tell us what you are working on.
Let’s talk