Dev & Engineering · Engineering, IT & AI
Should you build or buy Low-Code / No-Code?
Low-code and no-code platforms let business analysts, operations staff, and developers build internal applications, automate workflows, and create data-driven tools through visual interfaces and pre-built components rather than writing code from scratch.
You can build the apps you need — the honest question is whether you're overpaying for a platform whose governance layer you barely touch. A handful of simple internal apps on an enterprise low-code license is largely shelfware; OSS plus AI coding agents cover the core for a fraction of the cost. Keep buying only where org-wide governance, compliance evidence, and citizen-developer scale genuinely dominate your three-year TCO.
Build it, buy it, or bridge?
When building makes sense
Building internal applications rather than buying a low-code platform makes compelling sense when the people doing the building are developers, when the app will be used by hundreds or thousands of users, and when the workflow is stable enough that a one-time build cost amortizes well. AI coding assistants have changed the math here substantially — build costs that once required weeks of developer time now compress to days, while per-seat licensing on platforms like Power Apps or OutSystems can run $20 per user per month at scale. For a 1,000-user internal app, that's $240K per year versus a one-time custom build that might cost $30–60K with AI-assisted development. The lock-in cost is the other side of this equation: apps built on low-code runtimes are hostage to vendor pricing changes, platform constraints, and roadmap decisions in ways that custom code isn't. Open-source alternatives like Budibase, ToolJet, and NocoBase have demonstrated that building a low-code builder for your own needs is achievable, though reaching general-purpose feature parity with Retool takes years of dedicated investment. The build case sharpens when the workflow is complex enough that platform constraints create constant friction.
When buying makes sense
Low-code platforms still solve a genuine problem: getting non-technical teams to build and maintain internal tools without a developer backlog. Mendix, Retool, and Microsoft Power Apps genuinely empower business analysts and operations staff who can't write code, and the collaboration guardrails — version history, approval flows, access control — matter in enterprise contexts. The deployment model also compresses time to value: a non-engineer can ship a working CRUD application on the same day without any infrastructure setup. The buy case is strongest when the builders aren't developers, when the apps are simple (forms, workflows, dashboards over existing data), and when the iteration pace matters more than long-term cost. Where it gets harder to justify is when your team does have development capacity, when the per-seat math scales into five or six figures annually, and when you find yourself engineering around platform constraints rather than solving the business problem. OSS self-hosted alternatives like Appsmith and ToolJet serve as useful reference points for what a lower-cost path looks like.
The desk read
The premise of low-code platforms is getting squeezed from below. AI coding assistants now generate functional internal apps, CRUD dashboards, and workflow automations from natural language in the time it used to take to configure a Retool canvas. For a stable internal app with 1,000+ users, the per-seat math on Power Apps or OutSystems often loses to a custom-built app over a two to three year horizon, especially when AI dramatically reduces the initial build cost.
Buying still makes sense when the users doing the building aren't engineers. Low-code platforms like Mendix and Retool genuinely empower business analysts and operations staff who can't write code, and the collaboration and deployment guardrails they provide matter in enterprise environments. The build case gets compelling when the people building the app are developers, when the workflow is complex enough that platform constraints create real friction, and when the org is large enough that per-seat licensing is a line item worth scrutinizing.
Vendors in Low-Code / No-Code
Each file covers what the product is, its funding history, and when the index last verified it alive.
Frequently asked
What is low-code / no-code software?
Low-code and no-code platforms let business analysts, operations staff, and developers build internal applications, automate workflows, and create data-driven tools through visual interfaces and pre-built components rather than writing code from scratch.
When does building instead of using a low-code platform make sense?
Building makes sense when the builders are developers, when the app will serve hundreds or thousands of users, and when per-seat licensing costs exceed what AI-assisted custom development would cost over a two to three year horizon.
When does buying a low-code platform make sense?
Buying makes sense when the people building apps aren't engineers, when you need non-technical teams to ship and iterate independently, and when the apps are simple enough that platform constraints don't create friction.
What are the main low-code / no-code vendors?
Representative vendors include Mendix (Siemens), OutSystems, Microsoft Power Apps, Retool. B4 Pro scores the full set.
How has AI changed the low-code vs. custom code comparison?
AI coding assistants have compressed custom build costs by 30–60%, which has meaningfully narrowed the time-to-value gap that used to favor low-code platforms. For teams with any development capacity, the per-seat licensing math on LCNC platforms now deserves closer scrutiny.