App builders
AppSheet consultant: Google Workspace apps and automation.
Most paid Google Workspace plans include AppSheet Core, and Business and Enterprise plans include Workspace Studio. SBD works out what you can do with what you already pay for, builds the apps and flows in your own Workspace, and tells you when the work has outgrown them, for teams of 5 to 1,000 people.
- Tool
- appsheet.com
- Usually paired with
- Google Sheets, Gmail, Google Drive, Make
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on AppSheet
- Work out what your Workspace edition already includes
- Build data-capture and approval apps on Sheets
- Set up Workspace Studio flows across Gmail, Chat and Drive
- Move the data to a proper database when a sheet struggles
What we sync
Workflows we are asked for
- AppSheet inspection app to Google Sheets
- AppSheet stock request with an approval step
- Workspace Studio Gmail summary to a Chat space
- AppSheet form to a Make or n8n workflow
Often paired with
Tools AppSheet usually needs to talk to.
-
AppSheet and Google Sheets
The spreadsheet most operations start in, and the one most integrations have to respect.
-
AppSheet and Gmail
Google Workspace email, which is where most small-company processes still begin.
-
AppSheet and Google Drive
Google Workspace file storage, Docs and Slides.
-
AppSheet and Make
Visual automation with scenarios, routers and good error handling, formerly Integromat.
What we do
What SBD would build on Google Workspace
AppSheet makes data-capture and approval apps from sheets and other data sources. Workspace Studio builds AI-assisted flows across Gmail, Chat and Drive. Google says Studio grew out of what it released in alpha as Google Workspace Flows, so older guides under that name may describe a different product. Between them they cover a field inspection app feeding Google Sheets, a stock request with an approval, or a Gmail summary posted to a Chat space.
SBD has no published case study on AppSheet or Workspace Studio. The comparable published work is a project management system on Google Sheets, Apps Script and Make for a five-person photo studio, and a cashback system with Make and Google Sheets in the stack. Both solved Workspace problems with other tools, and we will show you where AppSheet would have changed them.
AppSheet plans
What your Workspace plan includes in AppSheet
AppSheet's help pages, read in November 2026, list Core licences for each domain-verified user on Business Starter, Standard and Plus, Enterprise Starter, Standard and Plus, Enterprise Essentials Plus, Education Standard and Plus, Frontline Starter and Standard, and Workspace for Nonprofits. The list changes, so we check your edition in the admin console.
Core connects to standard sources such as Google Sheets, Excel, Airtable and Smartsheet. BigQuery, PostgreSQL, MySQL, SQL Server, Oracle, Salesforce and on-premises databases need Enterprise Plus, as do team-level governance policies. AppSheet's pricing page, also read in November 2026, lists Starter at $5, Core at $10 and Enterprise Plus at $20 per user per month, with Publisher Pro at $50 per app per month for public apps. Publisher Pro has no user sign-in or security filters, so it does not suit anything private.
The licence an app needs depends on its creator's licence, and users of a Core creator's app need Core or a User Pass. Check this before rolling an app out to contractors outside your domain.
Workspace Studio
Workspace Studio and its limits
Google's Studio page, read in November 2026, says it is generally available on all Business and Enterprise plans, and it lists connectors to tools including Asana, Jira, Mailchimp and Salesforce. A flow can only reach data the person who started it may access. Google also says Studio does not override Workspace DLP controls for services like Drive, and that wider coverage for third-party services is not yet planned, so an admin should decide which outside services may connect.
Google's limits page, read on the same date, allows 25 flows per person, counted whether on or off, 100 steps per flow, and 25 active flows started by Gmail events. There is also a daily cap on runs across all of a person's flows, and Google does not publish the number. Flows belong to people, which suits personal and team routines. For a process the company depends on, we would use something with shared ownership and error handling.
Choosing a platform
When AppSheet and Studio are the right choice, and when they are not
Choose them when your staff already sign in with Google, the data is in Sheets or a similar source, and you would prefer not to buy another subscription. A working AppSheet app on a plan you already pay for is often the right first step.
We would suggest something else in these cases:
- Customers or partners need to sign in and see their own records. A portal on Softr or a custom build fits better.
- A sheet is struggling as the database, with many editors and growing rows. Move the data to Supabase or Airtable first.
- A workflow crosses several systems outside Google and has to alert someone when it fails. Make or n8n gives you run history and retries.
- Your company runs on Microsoft. Look at Power Automate instead.
Engagement and cost
How a Google Workspace engagement with SBD works
Every engagement starts with an Automation Audit at $500, credited in full to your build. We check what your edition includes, map the work and tell you which parts need no new software. Workflows start at $1,500, internal tools at $3,000 and multi-module systems at $5,000, as a fixed price set after the audit, built in your own Workspace.
Read next
Sources
- AppSheet, Pricing (Starter, Core, Enterprise Plus, Publisher Pro), checked 2 November 2026
- AppSheet Help, How to choose a subscription (editions, data sources, licence rules), checked 2 November 2026
- Google Workspace, Workspace Studio (availability, connectors, Flows lineage, data controls), checked 2 November 2026
- Workspace Studio Help, Learn about Google Workspace Studio limits, checked 2 November 2026
In every build
Standards we apply to every build.
Under the hood
- Upserts keyed on the record
Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.
For the team
- Slack or email notifications
Alerts go to a named person on your team, by Slack, email or WhatsApp.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
Keys and data
- Keys are kept in a vault
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts for connections
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
The offer
Connect AppSheet to the rest of your stack.
We agree a fixed scope in a discovery call, and most builds go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.
- ScopeOne call to agree the workflows, the fields and the owner, written up the same day.
- BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
- Go-liveWe test in a sandbox first, then switch over. It takes longer only where a vendor has to approve something.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about AppSheet.
Is AppSheet included in Google Workspace?
AppSheet's help pages, read in November 2026, list Core licences for users on most Business, Enterprise, Frontline, Education and Nonprofit editions. We check your edition in the admin console before planning anything.
What happened to Google Workspace Flows?
Google says Workspace Studio is an evolution of what it released in alpha as Google Workspace Flows. Older guides using the Flows name may describe a different product.
AppSheet
Start with the one AppSheet workflow your team still runs by hand.
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call