The No-Code Boom: Who's Actually Using Airtable and Bubble
A look at why no-code tools spread through pandemic-strained teams in 2020-2021, and where they genuinely replace custom software versus where they hit limits.
A year into remote work, a pattern has become impossible to ignore: teams that never would have touched a database schema are now building internal tools on Airtable, spinning up customer-facing apps on Bubble, launching marketing sites on Webflow, and stitching it all together with Zapier. None of these tools are new. What’s new is how fast they’ve spread since last spring.
The obvious explanation is the pandemic itself. When operations teams got cut off from the engineers who used to build them a quick internal dashboard or an ad hoc approval workflow, they didn’t have the luxury of filing a ticket and waiting a sprint. They needed something working by Friday. No-code platforms filled that gap because they let a non-engineer go from idea to working software in an afternoon, without touching a line of code or waiting on a backlog.
Money has followed the usage. Venture funding into no-code and low-code startups has climbed sharply over the past year, and it’s not hard to see why investors are paying attention: these tools shrink the population of people who can build software from “engineers” to “anyone with a spreadsheet-level mental model,” and that’s a much bigger addressable market.
Where it actually works
The clearest wins are internal tools — the unglamorous stuff that never gets prioritized on an engineering roadmap. Inventory trackers, applicant pipelines, event RSVP systems, simple CRMs for a five-person sales team. These are exactly the kind of projects where the cost of custom development was always disproportionate to the value delivered, and no-code closes that gap. Airtable in particular has become a kind of universal glue for small teams who outgrew spreadsheets but don’t need (or can’t justify) a real backend.
Bubble and similar app builders are doing something more ambitious: letting non-technical founders launch actual customer-facing products — marketplaces, booking apps, membership sites — without hiring a developer first. For an early-stage idea that needs validation before it needs to scale, that’s a legitimate and increasingly common path.
Where it hits a wall
The limits show up predictably once usage grows. Performance becomes a real issue as record counts and user counts climb — these platforms weren’t built for scale, and it shows. Customization ceilings are real too: the moment your workflow needs logic the builder didn’t anticipate, you’re either hacking around it or migrating off. And vendor lock-in is a genuine risk — moving years of accumulated logic and data out of a proprietary platform is not a weekend project.
My read is that no-code isn’t replacing custom software so much as absorbing the layer of software that never should have required a full engineering team in the first place. That’s still a big layer, and it’s why funding keeps flowing in, but it’s worth watching whether these tools mature enough to handle real scale, or whether “no-code today, rewrite in Rails tomorrow” just becomes the accepted lifecycle for a growing product.