On this page
Low-code promises software without a programmer, and partly delivers. A form that collects registrations, a small database, an internal app for one team: these take an afternoon to a few weeks in a visual builder. Anyone who used Excel, Access or FileMaker knows the idea; Forrester named the cloud platforms low-code in 2014. Large players include Microsoft Power Apps, OutSystems and Mendix. With no-code tools such as Airtable, Webflow or Zapier, no code is involved at all.
Since 2024 there is a third kind: AI app builders such as Lovable and Bolt. You describe what you want in a sentence and the tool writes the code. You write no code, but code exists, and someone has to understand it when something breaks. How such a tool compares for a company website is in Lovable vs WordPress, and whether it is safe in is Lovable good.
Where you sit on two axes
standardhow specific your way of working isspecific
A decision aid, not a law. Start small where you can, and see after a few months where you get stuck.
Four ways to build an application
| No-code | Low-code | AI app builder | Custom | |
|---|---|---|---|---|
| Who builds | You | Someone technical | You with prompts, a developer when it breaks | A developer or agency |
| Speed | Hours to days | Days to weeks | Hours to days for a prototype | Weeks to months |
| Cost | Subscription per user | Licence per user plus build time | Subscription plus code review | Build up front, then hosting |
| Leaving | Hard | Hard | You have the code, if someone understands it | You own the code |
What a platform costs per user
With a custom application you pay for the build up front, then hosting and maintenance, but no licence per user. Where the break-even lies depends on how many people use it and for how long. What custom work costs is set out in custom software development cost, and the trade-off itself in build vs buy software.
When low-code is enough, and where custom starts
- Choose no-code or low-code ifa handful of people use it and the process is simple, if you want to test an idea before investing, or if you are connecting existing tools; then Zapier, Make or n8n often suffice, see Make, Zapier or n8n.
- Choose custom ifper-user costs climb while the application stays the same, if you have rules no platform knows, if clients must log in themselves, or if your data is sensitive and you want to decide where it lives.
Two examples from our work. For Business Centrum, a payroll bureau, we replaced a spreadsheet with a management platform: a record per employer, tasks, documents, a log and a client portal, with two-factor sign-in and encryption of sensitive codes. For DA Logistics, a haulier, we built a transport platform that tracks fuel under Belgian excise rules to the litre, with a driver app in three languages. Both are the kind of work where low-code platforms hit their limits; moving off spreadsheets is covered in replacing Excel with software.
Keep a list of what the platform cannot do
Every time the tool forces a workaround, write it down. If you outgrow it, that list is your requirements document, and the low-code version is a working example of what you need. Your data can usually be exported; the logic has to be rebuilt.
What owners ask before building it themselves
What is the difference between low-code and no-code?
No-code is built entirely with blocks and settings. Low-code is mostly visual but lets you add code where the platform falls short, so it needs more technical skill and can do more.
Is an AI app builder fit for a business application?
For a prototype, yes. For something your business runs on, with customer data and permissions per user, have the code reviewed by someone who understands it.
Where does our data live on a low-code platform?
On the vendor's infrastructure, in the region its plan allows. Check that it is in the EU if you handle EU personal data, and that you can export all of it.
