Skip to content
webappsdev

Your spreadsheet has outgrown itself: when to build a web app on Google Workspace

3 min read

Almost every small business runs at least one important process on a spreadsheet. Orders, bookings, job tracking, inventory, leads: a Google Sheet is free, everyone knows how to use it, and it is up and running in minutes.

That is a good place to start. But many spreadsheets quietly take on more than they were designed for, and the cost shows up as lost time, mistakes and missed opportunities.

Signs a spreadsheet has outgrown itself#

  • People are afraid to touch it. One wrong sort or deleted formula and the whole thing breaks.
  • The same data is typed twice, once into the sheet and once into an email, an invoice or a calendar.
  • Customers cannot see their own information, so they email to ask, and somebody looks it up.
  • Everyone can see everything, including the columns they shouldn’t.
  • Nobody knows who changed what, or why the numbers do not match last week’s.
  • It has become slow, with thousands of rows and dozens of tabs.

If three or more of these sound familiar, the process deserves a proper tool.

The good news: you do not have to leave Google Workspace#

Moving off a spreadsheet does not mean throwing away the tools your team likes. A small web application can sit alongside Google Workspace and make it work harder:

  • Staff sign in with their Google accounts. No new passwords, and access ends automatically when someone’s account is suspended.
  • The sheet can stay, as a view. The application keeps the real records in a proper database, and a Google Sheet can still receive a copy for the people who like to filter and pivot.
  • Calendars update themselves. A confirmed booking appears on the right Google Calendar without anyone copying it across.
  • Documents file themselves. Quotes and invoices are generated and saved to the right Drive folder with the right sharing settings.
  • The team hears about it straight away. New orders or problems post to a Google Chat space or arrive by email.

Your customers get a clean, mobile-friendly page to place an order or check a booking. Your team gets fewer copy-and-paste jobs and a record of who did what.

What it costs to run#

The usual worry about custom software is that it adds yet another monthly bill. Hosting on Google App Engine or Cloud Run keeps that small:

  • There are no servers to rent or maintain. Google handles the operating system, security patches and HTTPS certificates.
  • Apps can scale down when nobody is using them. A tool used by a handful of staff during business hours costs very little to run.
  • Budget alerts warn you long before costs become a surprise.

Built with a lean backend such as Go, a typical small-business application runs comfortably on the smallest hosting tier.

How to start small#

You do not need to rebuild everything at once. A good first project is usually one painful process:

  1. Pick the spreadsheet that causes the most trouble.
  2. Write down who uses it, what they enter, and what happens next.
  3. Build a simple application for just that process, with the Workspace connections that remove the most copying.
  4. Keep the old sheet in read-only mode for a few weeks as a safety net.

Once that process runs smoothly, the next one is easier, because the foundations, such as sign-in, hosting and the database, are already in place.

Have a spreadsheet that has outgrown itself? Tell me about it. The first conversation is about your business, not about technology.

Keep reading

  • 3 min read

    PostgreSQL or MongoDB? A practical guide for small businesses

    How to choose between PostgreSQL and MongoDB for a business application, without the hype: what each is good at, what it costs, and the questions that decide it.

  • 3 min read

    Why I build small-business backends in Go

    Go is known as the language of cloud infrastructure, but its biggest benefits go to small businesses: low hosting bills, fewer security updates, and code that stays readable for years.

Got a spreadsheet that has outgrown itself?

Or an idea for a customer portal, or an old app that needs rescuing? Tell me about it. The first conversation is about your business, not about technology.