Staff tool on a no-code builder

About $0/month for 10 staff in tool bills: $0 for AppSheet. Usage profile: 1,000 monthly active users with light use: about 100,000 requests, 3,000 emails, 200,000 analytics events and 5 GB of stored files a month, and a database under 1 GB. AI apps add 50 questions per user a month at about 4,000 input and 500 output tokens each (200M input and 25M output tokens). Internal tools are priced for 10 staff instead.

• AppSheet Core is included in most paid Google Workspace plans; Google's admin help lists the editions, including Business Starter, Standard and Plus. Otherwise Starter is $5 and Core $10 per user a month, and you can prototype free with up to 10 test users. Source
• AppSheet's paid plans list 'Run apps offline with background sync', which matters for back rooms and fridges with no signal. Source
• Retool is free up to 5 users; Team is $10 per builder and $5 per staff user a month, billed annually. Source

1. Decide builder or custom code

   For a small staff tool, a builder usually wins: there's nothing to host, patch or debug at 6 a.m. before opening.

   • Write down the three to five jobs the tool must do (for example: log today's counts, see low stock, enter a wholesale order, mark it delivered).
   • For each job, note who does it, on what device, and whether there's Wi-Fi where they do it.
   • Pick a builder if every job is a form, a list, a filter or a simple calculation. Build custom only if a job needs logic or integrations the builder can't do.
   • Pick AppSheet if the business already uses paid Google Workspace; pick Retool if the data is already in a database or the tool must call your other systems' APIs.

   Done when: You have a one-page list of jobs, users and devices, and a written reason for the builder you chose.

2. Check your Workspace plan and turn on AppSheet

   AppSheet Core is included in most paid Google Workspace editions, so check before paying for anything.

   • In the Google Admin console, check your edition under Billing. Google's admin help lists the editions that include AppSheet Core, including Business Starter, Business Standard and Business Plus.
   • Turn AppSheet on for your organization (or for the staff group only) in the Admin console's additional Google services.
   • If your edition doesn't include Core, prototype for free (up to 10 test users) and buy Starter ($5) or Core ($10) per user a month only when you go live.
   • Make the app's owner a shared business account, not one person's account, so the app survives someone leaving.

   Done when: A staff account can open appsheet.com and create an app without a payment prompt.

   Docs: about.appsheet.com, support.google.com

3. Lay out the data in Google Sheets

   Each sheet is a table, each row is a record, and each record has a unique id. Getting this right matters more than any screen.

   • Create one spreadsheet with a tab per table: Items, Counts, Customers, Orders, Order Lines and Staff.
   • Give every tab an ID column; let AppSheet generate ids with UNIQUEID().
   • Link tables by id columns (an Order Line has an Order ID and an Item ID), never by names that can change.
   • Put one header row at the top of each tab and no merged cells, totals or notes in the data area.
   • Add a Staff tab with each person's Workspace email and role (staff or manager).
   sheets/layout.csv

   tab,columns
   Items,ID | Name | Unit | Par level | Active
   Counts,ID | Item ID | Date | Quantity | Counted by
   Customers,ID | Name | Contact email | Delivery notes
   Orders,ID | Customer ID | Delivery date | Status | Created by
   Order Lines,ID | Order ID | Item ID | Quantity
   Staff,Email | Name | Role
   

   Done when: Every tab has a header row, an ID column, and links to other tabs by id.

4. Generate the app and set column types

   AppSheet builds a first version from the sheet; you then fix the types so forms and links work.

   • Create the app from the spreadsheet in AppSheet and add every tab as a table.
   • Set types: Ref for id links (Item ID refers to Items), Date, Number, Enum for Status, Email for emails.
   • Mark the ID column as the key and the Name column as the label in each table.
   • Build the views staff need: a form for today's count, a list of low-stock items (count below par), and an order form with order lines inline.
   • Remove the views staff don't need; fewer buttons means fewer mistakes.

   Done when: A staff member can enter today's count for every item and an order with three lines, without help.

   Docs: support.google.com

5. Control who sees and changes what

   Staff should edit today's work; managers change items, prices and customers.

   • Require sign-in and limit the app to your Workspace domain.
   • Look up the signed-in user's role from the Staff tab, and use it to hide manager-only views and actions.
   • Use security filters so staff see only what they need, for example orders for this week.
   • Make edits to Items and Customers manager-only.

   Done when: A staff account can't edit item par levels or see the manager views; a manager account can.

   Docs: support.google.com

6. Make it work on the floor, offline

   Back rooms and walk-in fridges often have no signal. Paid AppSheet plans run apps offline and sync in the background.

   • Install the AppSheet app on the shop's phones or tablets and sign in with Workspace accounts.
   • Check the app's sync settings (Delayed Sync and Sync on Start) so work entered offline is kept and sent on reconnect, and test with the device in airplane mode.
   • Test what happens when two people edit the same order offline, and decide who wins (usually: one person owns each order).
   • Keep images small and the data tabs trimmed so the first sync on a new device is quick.

   Done when: A count entered in airplane mode appears in the sheet within a minute of reconnecting.

   Docs: support.google.com, about.appsheet.com

7. Automate the reminders

   The tool earns its keep when it tells people things: low stock, tomorrow's deliveries, a missed count.

   • Add an automation that emails or notifies the manager when an item's latest count is below its par level.
   • Add a daily summary of tomorrow's wholesale orders for whoever bakes or packs them.
   • Send to a shared address or group, so the alert doesn't depend on one person.

   Done when: Setting a test item's count below par sends one alert to the right people.

   Docs: support.google.com

8. Roll out and keep it healthy

   Train in ten minutes, watch the first week, and plan for the day it outgrows a spreadsheet.

   • Show each person the two or three screens they use, on their own device.
   • Check the sheet daily in the first week for blanks, duplicates and wrong items, and fix the form that let them in.
   • Use the spreadsheet's version history as your backup, and export a copy monthly.
   • If the sheet gets slow or you need stricter permissions, move the data to a database, and check which database connectors your builder's plan includes.

   Done when: After a week, every count and order is in the app, and nobody keeps a paper backup.

• For 10 staff: $0 if your Workspace edition includes AppSheet Core; otherwise AppSheet Starter at $5 × 10 = $50 a month, or Core at $10 × 10 = $100.
• Retool instead: 1 builder at $10 + 9 staff at $5 = $55 a month, billed annually.
• A custom app instead: hosting and database can be free at this size, but most of the cost is the hours spent building and maintaining it.
• If the tool stores staff personal data (phone numbers, hours, pay), keep it to what the job needs and restrict it to managers.
• Food businesses may have record-keeping rules (temperatures, allergens, lot tracking) where you operate; check what must be kept and for how long before relying on the app as the record.
• Data in Google Workspace is covered by your Workspace terms and admin settings; check them if customers or regulators ask where records are kept.

These point to obligations to check; they aren't legal or tax advice.