No-Code vs Low-Code: How to Build Custom Business Apps That Actually Scale

Most teams start a custom business app project by asking the wrong question: “Should we use AppSheet or Apps Script?” I’ve watched dozens of teams waste weeks arguing that choice — only to discover they were comparing tools that are built for different layers of the same stack. AppSheet is not a competitor to Apps Script. AppSheet delivers the user interface; Apps Script runs the logic. The best production systems I’ve built use both, together, with a single Google Sheet underneath. Here’s how to decide which tool owns which layer, what it really costs per user, and the hybrid pattern you’ll likely end up with.

The One-Line Test: Interface vs Logic

Before you write a single expression, run a quick mental test. If your problem is about forms, buttons, mobile views, GPS capture, or role-based access for people, you need a no-code app builder like AppSheet. If your problem is about data processing, API calls, webhooks, or automating Google Workspace apps, you need a low-code scripting runtime like Apps Script.

Here’s the blunt version: AppSheet is the front-end. Apps Script is the back-end. In the no-code and low-code world, they are not rivals — they are complements. But most people pick one and try to force the other’s job into it, which is where I see projects stall for weeks.

AppSheet: The No-Code UI Layer

AppSheet is a no-code platform that sits directly on top of Google Sheets. Point it at a spreadsheet and it generates a mobile and web app — complete with forms, lists, offline sync, camera access, GPS capture, and per-role permissions. A warehouse supervisor can get an iPhone app that scans barcodes and logs inventory without a single line of code. That’s the promise of no-code business-apps, and AppSheet delivers it well for small and mid-sized teams.

What AppSheet struggles with: complex expressions, heavy data processing, or anything that needs to call an external API with custom headers and authentication. Its expression language is powerful but not Turing-complete. If you need to calculate a business-hours SLA due date or reconcile thousands of rows, AppSheet will make you miserable.

Apps Script: The Low-Code Logic Layer

Apps Script is a JavaScript runtime embedded in Google Workspace. It’s not a UI builder. It’s an automation engine that can manipulate Sheets, Gmail, Calendar, Docs, and Drive. It can also call any REST API, receive webhooks from Stripe or Twilio, and integrate with AI services like OpenAI, Anthropic, or Gemini. That makes it the perfect low-code tool for the logic layer of a business app.

Apps Script is also “low-code” in the sense that you write a small amount of JavaScript, but you don’t manage servers, deploy pipelines, or worry about infrastructure. It runs on Google’s servers, has built-in quotas, and integrates natively with Google Workspace. If you already live inside the Google ecosystem, it’s the cheapest and most controllable way to build custom logic for your business-apps.

Choosing the Right Tool for Each Job

Here is a practical decision matrix I give to clients. Use it as a checklist when you’re scoping a build:

• Field staff with phones (offline, GPS, camera): Use AppSheet. The mobile UI, sync, and capture features are exactly what this needs.
• Internal CRUD tool for under ~10 users: Use AppSheet. The UI quality is worth the setup time.
• Form with dependent dropdowns and per-role permissions: Use AppSheet. This is its bread and butter.
• Quick prototype to validate an internal idea: Use AppSheet. You can go from spreadsheet to demo in an afternoon.
• Custom logic or heavy data processing (>1,000 rows): Use Apps Script. Loops, arrays, and math are far cleaner in JavaScript.
• AI integration (OpenAI / Anthropic / Gemini): Use Apps Script. It can call external APIs with fetch, no special connectors needed.
• Webhook receiver (Stripe, Twilio, Magento): Use Apps Script. Deploy it as a web app and receive POST requests directly.
• Customer-facing portal with custom branding: Use Apps Script. You can serve HTML and CSS from the script, giving you full control.
• A tool 50+ employees use daily: Use Apps Script. Cost and control become the dominant factors at scale.
• A production system meant to last 5+ years: Use Apps Script. Code is easier to maintain, version, and audit than a no-code configuration.

Notice that both tools keep your data in the same place — a Google Sheet you own. This is the critical architectural insight. Because the data layer is shared, choosing one tool now doesn’t lock you out of the other later. You can start with AppSheet for a quick UI, then add Apps Script behind it as your logic grows.

The Real Cost: Per-User Fees vs a $0 Scripting Layer

AppSheet is priced per user. As of recent pricing, you’re looking at roughly $5 per user per month for Starter, $10 per user for Core, and $20 per user for Enterprise Plus. That adds up fast. A 30-person warehouse team on AppSheet Core is $3,600 per year, every year, forever. At 100 users, it jumps to $12,000 per year.

Apps Script, on the other hand, costs $0 per user under standard Google Workspace quotas. There is no per-user fee at any headcount. You pay only for Google Workspace itself, which you probably already have. If your app is mostly logic — moving data, calling APIs, sending emails — Apps Script can run that for free, inside your existing Google Workspace subscription.

Does that mean AppSheet is a rip-off? No. It’s a good tool for the right problem. The rough break-even is around 10 to 15 users. Below that, the UI quality AppSheet provides is worth the fee. Past 20 users, the math shifts hard toward Apps Script — especially if you’re looking at a multi-year horizon. The more users you have, the more you should question whether you really need a per-user license for what is essentially a set of forms and dashboards.

The Hybrid Pattern That Wins

Here is the architecture I ship most often: AppSheet for the UI, Apps Script for the logic, and one Google Sheet underneath. Field staff use an AppSheet app to enter data, view records, and capture photos. When the app needs something the no-code expression language can’t express cleanly, an AppSheet Automation action calls an Apps Script “Call a script” bot. The script does the heavy lifting, writes the result back to the same Sheet, and the AppSheet UI picks it up automatically.

This pattern gives you the best of both worlds. Your non-technical team gets a polished mobile app. Your technical lead gets the flexibility of JavaScript. And because the data lives in Google Sheets, everyone can audit what’s happening at any time. You also avoid the trap of vendor lock-in: if AppSheet ever gets too expensive, you can rebuild the UI as a simple Apps Script web app without touching your data or your logic.

A Concrete Example: SLA Due Dates

Suppose you’re building a support ticket tracker. AppSheet captures the ticket beautifully — customer name, issue type, priority, and a timestamp. But then you need to compute an SLA due date: eight working hours from the ticket’s creation time, skipping nights and weekends. AppSheet’s expression language can’t do that cleanly. So you create an AppSheet Automation that calls an Apps Script function, passing the created-at timestamp. The script calculates the due date and stores it back in the Sheet. AppSheet displays it in the ticket view.

How to Deploy This Without a Developer

If you’re not a developer, you might be worried that “low-code” still sounds like code. That’s fair, but you have options. Apps Script functions like the one above are often copy-paste-ready from forums or community templates. You can also use an AI chatbot to generate the script for you — describe what you need in plain English, get a JavaScript function, and paste it into the Apps Script editor. No-code and low-code tools are designed to reduce the barrier to entry, not eliminate it entirely.

For more complex builds, you can also hire help. Platforms like Fiverr and Upwork have specialists who can wire up AppSheet and Apps Script projects for a few hundred dollars. I’ve seen five-figure projects saved by a $300 integration script that automated a manual Excel process. The key is to know what you’re buying: a UI layer from AppSheet, a logic layer from Apps Script, and a clear data contract in Google Sheets.

A Decision Framework for Your Next Business App

When you’re scoping a new internal tool, use this simple sequence:

1. List your user cases and compute volumes. How many users, how many rows, how much processing?
2. Separate the interface from the logic. Underline the forms and dashboards in one column, the calculations and integrations in another.
3. Estimate the total cost of ownership. Multiply AppSheet’s per-user price by your headcount and by 5 years. Then compare that to the cost of a one-time Apps Script build.
4. Start with the cheapest Often that’s an Apps Script web app with a Google Sheet backend. If you later need a more polished mobile experience, add AppSheet on top — your data is already there.
5. Prototype quickly. Don’t build for months. Get a working version in a week, test it with real users, and then iterate.

The biggest mistake I see is treating no-code and low-code tools as rivals. They are not. AppSheet is a beautiful interface generator. Apps Script is a powerful automation engine. When you combine them — one Google Sheet underneath, AppSheet in front, Apps Script behind — you get a custom business app that is fast to build, cheap to maintain, and easy to scale. Most teams only need that, and they need it now, not after three more meetings.