No-Code
No-code can accelerate your project, but technical choices remain. Compare workflows, dependencies, and costs before committing to a solution.

Sur cette page4 sections
You have an idea for a service, you open a tool, you move a few blocks around, and a first page starts to take shape. Honestly, I understand the appeal. You finally move from "we should do this" to something you can show and try out.
No-code allows you to build websites and applications with visual tools, without writing every line of code yourself. I develop with code, but I don't see why one should look down on a tool that allows someone to test their idea. What interests me happens after the first page: how will the project work in real life?
Then two people request the same time. Does the first booking block the slot? Does someone need to accept the request? And if the client cancels, who is notified and at what point does the slot become available again?
These are the questions that define the service. Drag-and-drop can help us create screens and certain rules; it cannot decide for us how our business should operate. It's the same when writing everything by hand: flawless code doesn't fix a misunderstood booking rule.
At this stage, insisting on a fully custom application can complicate the start without adding much. The project primarily needs to meet its users, not give us an opportunity to build an impressive infrastructure.
The choice becomes more interesting as the business evolves. A specific rule, a link with software already in use, or multiple access levels might be simple in one platform and complicated in another. I prefer to look at these cases early on, while we can still choose calmly.
With Bubble, for example, retrieving your data and exporting an application ready to run elsewhere are two different things. Applications remain tied to the platform; rebuilding their functionality elsewhere requires work. Not all no-code tools have the same rules, so this example doesn't apply to the whole category.
That doesn't make it a bad choice. It simply changes the conversation if your goal is to keep the option to leave, or if the service is to become the heart of your business. We then look at exports, subscriptions, and integrations with as much attention as the page editor.
If an existing tool meets your needs well, I'd rather we use it than have you fund its reproduction. If adaptations start to look like a series of workarounds, however, we can discuss another foundation before accumulating technical debt.
The right starting point for us to work together is your actual user journey. Show me what the person needs to be able to do, and what is blocking you today. We can then choose how to achieve it without turning "with or without code" into a religious debate.
No-code allows you to build websites and applications with visual tools, without writing every line of code yourself. I develop with code, but I don't see why one should look down on a tool that allows someone to test their idea. What interests me happens after the first page: how will the project work in real life?
The form looks great, but two people want the same slot
Imagine a small business offering appointments. You add a calendar, a name field, and a booking button. Visually, the work seems almost finished.Then two people request the same time. Does the first booking block the slot? Does someone need to accept the request? And if the client cancels, who is notified and at what point does the slot become available again?
These are the questions that define the service. Drag-and-drop can help us create screens and certain rules; it cannot decide for us how our business should operate. It's the same when writing everything by hand: flawless code doesn't fix a misunderstood booking rule.
A first version can already provide a real service
To gather requests, test an offer, or replace a spreadsheet sent by email, a visual tool can be very suitable. You can have a few people try out the user journey, see where they hesitate, and fix it before going further.At this stage, insisting on a fully custom application can complicate the start without adding much. The project primarily needs to meet its users, not give us an opportunity to build an impressive infrastructure.
The choice becomes more interesting as the business evolves. A specific rule, a link with software already in use, or multiple access levels might be simple in one platform and complicated in another. I prefer to look at these cases early on, while we can still choose calmly.
Renting a space doesn't mean you own the walls
A hosted platform may let you modify many things without necessarily allowing you to take the entire application to another host. It's a bit like a commercial space you fit out for your business: you can own what you put inside without owning the building.With Bubble, for example, retrieving your data and exporting an application ready to run elsewhere are two different things. Applications remain tied to the platform; rebuilding their functionality elsewhere requires work. Not all no-code tools have the same rules, so this example doesn't apply to the whole category.
That doesn't make it a bad choice. It simply changes the conversation if your goal is to keep the option to leave, or if the service is to become the heart of your business. We then look at exports, subscriptions, and integrations with as much attention as the page editor.
My job isn't to sell you as much code as possible
Custom-built allows for finer tuning of certain rules and more choice of components. It also requires developing, testing, and maintaining what has been built. You remain dependent on software, services, and people; you shift part of the responsibility to the project.If an existing tool meets your needs well, I'd rather we use it than have you fund its reproduction. If adaptations start to look like a series of workarounds, however, we can discuss another foundation before accumulating technical debt.
The right starting point for us to work together is your actual user journey. Show me what the person needs to be able to do, and what is blocking you today. We can then choose how to achieve it without turning "with or without code" into a religious debate.




