Turn Google Sheets into a web app

How a Google Sheet becomes the system

It usually starts with a Google Form. Requests, orders or job sign-offs come in through the form and land as rows in a sheet. Someone adds a status column, then a tab for each team, then a few lookup formulas. A colleague writes some Apps Script to send an email when a row changes. A year later the business runs on it.

That setup is free, quick and genuinely useful. It starts to strain in ways that are specific to shared Google sheets:

• Sharing is all or nothing at the file level. Anyone who can edit can see every row, sort the whole tab, or delete a column by accident.
• Protected ranges help, but they are easy to forget and hard to manage once many people and tabs are involved.
• The Apps Script was written by one person, runs under their account, and stops working when they leave or their account is suspended.
• Scripts hit Google’s quotas, such as the limit on how long one run can take and how many emails can be sent per day.
• Large sheets slow down long before reaching Google’s cell limit, especially with IMPORTRANGE, QUERY and heavy formulas.
• Customers, contractors or field staff need to see their own records only, and a shared sheet cannot do that safely.

Your options: AppSheet, Glide or a custom app

Google Workspace teams have a few ways to put an app on top of their data. Each one is a fair choice in the right situation:

• AppSheet: Google’s own no-code app builder. It reads directly from your sheets and is included with some Workspace plans. Good for internal forms and simple workflows, but complex logic gets awkward, and the data still lives in the sheet with its limits.
• Glide: builds polished mobile-friendly apps from a sheet very quickly. Well suited to directories, simple portals and field checklists. Pricing and limits are tied to users and rows, and deeper business rules are harder to express.
• More Apps Script: you can build quite a lot with Apps Script and HTML Service. It stays tied to the sheet and to whoever maintains the code, so it tends to make the original problem bigger.
• A custom web app: the data moves into a proper database, the forms and scripts become tested features, and each person gets the exact access they need. More upfront work, with no row, user or logic limits.

What a spreadsheet to database app changes

When a spreadsheet becomes a database app, the rows stop being a grid that anyone can edit and become records with rules around them. In practice that means:

• Your team still signs in with their Google accounts, but each person sees only the records and actions their role allows.
• Forms check entries before they are saved, so no more typos in a status column breaking a formula.
• Every change is logged with who made it and when, rather than digging through version history.
• Automations run on the server, not under one person’s Google account.
• The app still connects to Gmail, Google Calendar and Drive, and can export to Sheets for anyone who likes a spreadsheet view.
• Customer or partner portals become possible, showing each outside user only their own data.

Google Sheets to web app, step by step

1. Map the sheets, forms and scriptsWe list every tab, formula, Google Form and Apps Script trigger, and note who touches each one.
2. Find the real processWe talk to the people who use the sheet to learn the steps and rules that live in people’s heads, not in cells.
3. Design the screensYou click through designs of the app before code is written and tell us what to change.
4. Build in roundsWe build the most used parts first and your team reviews each round, alongside the sheet they already use.
5. Import and check the dataWe clean up the rows, import them, and compare counts and totals with the sheet with you.
6. Switch and keep a copyThe team moves to the app, the Google Forms are pointed at it or retired, and the sheet stays as a read-only archive.

What it costs

Custom projects at Zoti start at $499/month, on a monthly plan covering design, development, hosting and ongoing changes. The price depends on how many sheets, forms, scripts and user roles are involved and what the app needs to connect to. You get a written quote before work begins.