Google AppSheet for Business

For most business editions, yes. Google's own announcement lists AppSheet Core as included by default for Business Starter, Standard and Plus, Enterprise Starter and Standard, Frontline Starter and Standard, Nonprofits and Education Standard, with Enterprise Plus, Enterprise Essentials Plus and Education Plus already covered. Your domain has to be verified. One thing we will not assume on your behalf: India's newer Base tier postdates that announcement, so if you are on Base we check your own admin console rather than telling you what it ought to be. Checked September 2026.

Spreadsheets and cloud file storage. According to AppSheet's published plan comparison that means Google Sheets, Forms, Drive, Calendar and Docs, and also Microsoft Excel held in Office 365, Dropbox or Box, plus Airtable and Smartsheet. It is worth correcting a claim you will see repeated elsewhere: the included Core tier is not restricted to Google-only sources. The real boundary is different — databases, REST and OpenAPI, and SaaS services such as Salesforce, BigQuery, Apigee and OData sit on the Enterprise Plus tier. So if your data lives in a spreadsheet or a file, you are already covered; if it lives in a SQL database or another product, you are not.

The short rule is that AppSheet is for when a person needs a screen, and Apps Script is for when nobody does. If somebody has to enter, check or approve something — particularly away from a desk — build an app. If the work happens on a schedule, generates a document, or lives inside a spreadsheet as a formula, write a script. Where it genuinely overlaps, the deciding question is usually who will maintain it: AppSheet can be adjusted by a trained non-developer, and a script cannot.

It depends on who is using the app and how. This is exactly the question worth settling before anything is built rather than after, because the answer changes the economics of the whole idea — an app that a dozen office users touch is a different proposition from one used by sixty people in the field. We establish the licensing position for your specific edition and user mix in writing as part of the quote, rather than assuming the included tier covers everybody.

AppSheet supports offline use, which is the usual reason it comes up for work in plantations, on sites and along routes where connectivity is unreliable. It is worth designing for deliberately rather than hoping: decide what has to be available offline, what happens when two people change the same record before either syncs, and how somebody knows their data has actually reached the office. Those are design decisions, not settings, and they are the difference between an app people trust and one they keep a paper copy alongside.

Partly, and that is worth taking seriously rather than brushing aside. If the data behind it is a Sheet, then it is a Sheet — with the same characteristics under load, the same absence of real integrity constraints, and the same behaviour when two people write at once. For a register that a handful of people update, that is entirely fine. For something the business will genuinely depend on in three years, decide deliberately whether a spreadsheet should be the system of record. We have set out that argument in more detail on the Apps Script page and it applies equally here.

The platform is usually already yours, so what you are buying is the design and build, and we quote that against a written specification. The prices quoted above are AppSheet's own published list in US dollars, checked September 2026; what a business in India actually pays depends on the tier and the arrangement, so we confirm the current figure when we quote rather than repeating a headline. If the honest answer is that a Google Form and a Sheet would do the job, we will tell you that instead.