No-Code Tools: Threat or Opportunity for ERP

Every investor and product manager I know is asking the same question in August 2020: why would anyone need custom ERP when Airtable and Notion exist?

Airtable has become the default way companies manage operations. Notion has convinced the entire internet that it can be your database, document store, and wiki simultaneously. Bubble and Webflow are enabling designers to build applications without touching code.

The no-code narrative is compelling: if a non-technical person can build an operational system in an afternoon, why would anyone pay hundreds of thousands for custom software?

I think this question reveals a fundamental misunderstanding of what no-code tools actually do and where ERP begins.

What No-Code Actually Solves

No-code tools are extraordinary at certain specific problems. Let me be clear about this because I think most of the criticism is unfair.

Early-stage operations: A company with three people who need to share a customer list and track projects. Notion or Airtable. It's genuinely better than email and spreadsheets.

Internal tools: Your accounting team needs a tracking system for expense reports. An intake form for marketing requests. No-code is faster than custom development and probably better designed than something a developer would build quickly.

One-off workflows: That specific business process that happens quarterly and requires data from three systems and outputs to five others. No-code can orchestrate that without being a full ERP.

Departments creating their own tools: Finance wants to track monthly budgets differently than the main system. They can build something themselves instead of filing a ticket with engineering.

These are genuinely valuable and no-code tools are genuinely better at them than custom development.

Where No-Code Hits a Wall

The problem emerges when you try to scale a no-code solution into something it wasn't designed to be.

Concurrency: Airtable handles multiple users editing simultaneously. But not really at scale. Put a hundred people editing the same Airtable base and you hit performance issues. Real transaction integrity with concurrent access is hard and Airtable simplifies it, which works until it doesn't.

Data consistency: An Airtable base is flat-ish. You can have lookups and rollups, but complex multi-table transactions where multiple things need to happen atomically don't work the way they do in a real database.

I watched a company use Airtable as their "ERP" and they had this recurring problem: a customer would pay an invoice, the payment would record, but the inventory wouldn't update, so they'd ship out of stock items. The relationships between tables weren't tight enough to enforce consistency.

Scalability at volume: If your business involves processing thousands of transactions per day, Airtable's API hits rate limits. If you're storing years of historical data, the performance degrades. If you need custom calculations on that data, you're importing it into Python or SQL anyway.

Compliance and audit trails: Many industries require detailed audit trails of who changed what and when. Airtable doesn't really support this cleanly. Real ERP systems have mature audit logging. Notion has basically nothing.

Integration complexity: Connecting no-code tools to your actual business systems is tedious. Zapier is great for simple workflows. But orchestrating a complex 15-step process that involves multiple systems, conditional logic, and error handling? You end up writing almost as much code as a real system.

The Efficiency Trap

Here's the sneaky part: no-code tools can make your life much easier initially. You get something working in days. The team loves it. Everyone's productive.

Then six months later, you've built all this business logic in Airtable that only one person understands. You need to add a new workflow. You realize the whole structure needs to be different to support it. You're now committed to an architecture that made sense for the first problem and makes everything else harder.

Real ERP systems have this problem too, but at least you have the architectural flexibility to rethink it. An Airtable base that's central to your business has become a liability, not an asset.

The Integration Question

Here's what surprised me: no-code tools are actually worse at integrating with each other than custom software.

If I build a custom system that talks to your accounting software and your CRM and your inventory system, I can make tight integrations. I can ensure data consistency across all three. I can handle edge cases.

If you use Airtable for operations, Notion for docs, Shopify for sales, and QuickBooks for finance, you're managing five different tools with limited integration. Zapier can move data between them but loose coupling means inconsistencies.

But a custom ERP can integrate everything coherently if someone actually builds it that way.

Where I Think This Goes

The realistic outcome isn't that no-code replaces ERP. It's that no-code handles the 80% of business operations that are straightforward, and custom development handles the 20% that are genuinely complex.

A company with 20 employees runs on Notion and Airtable and Shopify and does fine. The tool costs are low, the learning curve is small, and they can iterate quickly.

A company with 200 employees scaling rapidly needs better-integrated systems. If they try to scale Airtable to handle that, they'll burn time and money eventually. They're better off with a custom ERP or a best-of-breed cloud system that integrates tightly.

The companies I'd warn away from betting entirely on no-code:

High-volume transaction processing: If you're processing thousands of transactions daily, you need database-level reliability.

Compliance-heavy industries: Finance, healthcare, manufacturing. The audit trail and integrity requirements are beyond what no-code provides.

Rapid scaling: If you expect to 10x your business in the next year, building on a no-code foundation you'll outgrow is expensive.

Complex integrations: If your competitive advantage depends on seamlessly connecting multiple systems, no-code tooling becomes a bottleneck.

The Honest Take

I think no-code tools are some of the most important innovation in software in years. They're democratizing technical capabilities. They're enabling non-technical people to solve problems without waiting for engineers.

But they're solving a different problem than ERP. They're saying "here's a tool where you can define data and workflows without code." ERP is saying "here's a system that manages your entire business operation with reliability, scalability, and integration you can count on."

Both are valuable. They're solving different problems for different scales of business.

The real question isn't whether no-code replaces ERP. It's whether no-code tools make custom ERP development less common. The answer is probably yes—the bar for custom development just went up. You need to solve something genuinely complex enough that no-code is clearly inadequate.

That's actually healthy. It means custom ERP development becomes more focused on the things that really matter instead of being the default solution for every operational problem.

By the end of 2020, I think we'll see a clear bifurcation: no-code tools for businesses at certain scales, custom solutions for businesses with genuinely complex needs. The in-between will disappear, which is probably for the best.