I build software for a living, and I still tell business owners to try no-code tools for business apps before they ever call someone like me. That surprises people. It should not.
Here is the honest version: most internal apps that Indonesian SMEs need, a stock checker, a delivery log, a simple approval form, do not need custom code. They need to exist by next week, work on a phone, and cost less than one month of a junior developer's salary. No-code tools for business fit that brief almost perfectly.
But there is a second half to this story that the no-code vendors will not tell you, and it is where I have watched companies get quietly trapped. So let me give you both halves.
What no-code actually means in 2022
No-code platforms let you assemble working software from visual building blocks instead of writing code. The ecosystem has matured a lot in the past two years. The tools I see working in practice right now:
- Airtable for the data layer. Think of it as a spreadsheet that behaves like a database, with views, forms, and permissions.
- Glide to turn that data into a clean mobile app your field staff can use, no app store approval needed.
- Softr to build customer-facing portals and simple member sites on top of Airtable.
- Zapier to connect these to email, Google Sheets, or your accounting tool when something changes.
A realistic build: a distributor with 12 sales reps puts their product catalog and daily visit log into Airtable, wraps it in Glide, and every rep has an app on their phone within a week. Total cost, roughly Rp 1.5 to 3 million per month across subscriptions. A custom version of the same thing would run Rp 80 to 150 million and take three months.
Where no-code genuinely wins
I recommend no-code without hesitation in three situations.
Internal tools. Attendance logs, asset registers, purchase request approvals, maintenance checklists. These apps have a known set of users (your staff), forgiving performance requirements, and workflows you can change weekly. This is the sweet spot. If you are also thinking about tracking customer conversations, the same logic applies, and I wrote about the minimum version of that in CRM Basics: Stop Losing Customers in Your Chat History.
Prototypes and validation. If you have a business idea that needs an app, build the ugly no-code version first. One founder I advised spent two weekends on a Glide app to test whether warung owners would actually pre-order stock through their phones. They would not. That answer cost him Rp 500 thousand instead of Rp 200 million.
Bridging the gap while you grow. No-code buys you time. You get the operational benefit now, learn what your real requirements are, and only commission custom software once the process is proven.
Where it will quietly trap you
Now the uncomfortable part. Every no-code platform has ceilings, and you usually hit them after you depend on the tool, not before.
Scale limits. Airtable caps records per base (50,000 on the Pro plan as of early 2022). That sounds like a lot until your transaction log grows by 500 rows a day. At that pace you have less than a year before you are archiving data just to keep working.
Ownership and export. Your data is exportable, usually as CSV. Your logic is not. The automations, the views, the app structure, all of that lives inside the vendor's platform and cannot be moved. If the vendor raises prices, changes plans, or shuts down a feature you rely on, your only options are pay up or rebuild.
Performance and complexity ceilings. No-code apps get slow and fragile as logic accumulates. When you have 40 Zapier automations feeding three Airtable bases and nobody remembers why zap number 23 exists, you have recreated technical debt without writing a line of code. I explain that dynamic in Technical Debt Explained: Why Your App Gets Slower to Fix, and yes, it applies here too.
The single-builder problem. Often one enthusiastic staff member builds the whole thing. When they resign, you own a system nobody understands. Document as you build, even if it is just a Google Doc listing every automation and why it exists.
A simple decision test
Before building anything in no-code, answer four questions:
- How many records will this hold in two years? Under 30,000, go ahead. Over 100,000, plan for custom software from day one.
- Is this customer-facing and revenue-critical? If your customers pay you through this app, the reliability bar is higher than most no-code stacks can guarantee.
- Could a departing employee take the knowledge with them? If yes, require documentation before launch, not after.
- What is your exit plan? Know how you would export the data and what a rebuild would cost. Write it down while you are calm, not during a crisis.
If the answers are comfortable, build it this week. Genuinely. Speed is the whole point.
When to graduate to custom software
There is a clear signal: when you find yourself fighting the tool instead of using it. Workarounds stacked on workarounds, staff maintaining a shadow spreadsheet because the app cannot do something, monthly subscription costs creeping past Rp 10 million. At that point the no-code tool has done its job. It proved the process works and taught you your real requirements, which makes the custom build cheaper and better scoped than it ever could have been at the start.
Deciding who should do that custom build is its own question, and the wrong answer is expensive. I compare the options honestly in Agency vs Freelancer vs In-House: Who Builds Your Software?.
The practical takeaway
No-code tools for business are the fastest, cheapest way to get working internal apps and to test ideas before committing real money. Use them aggressively for internal tools and prototypes. Respect their ceilings on scale, ownership, and complexity. Document what you build, know your record counts, and keep an exit plan in a drawer.
The trap is not using no-code. The trap is forgetting that you are renting, not owning, and being surprised when the landlord changes the terms. Rent smart, and no-code is one of the best deals available to a small business in 2022.