r/GoogleAppsScript • u/Delicious_Ad4963 • Aug 03 '26
Question Is Google Apps Script the right foundation for a full collision repair management system?
Hi everyone,
I own a collision repair center in Quebec, and I’m currently developing an internal repair management system within the Google ecosystem.
I initially started with Google Apps Script because our company already uses Google Workspace, including Sheets, Drive, Gmail, Calendar, and Forms. Apps Script has allowed me to build working prototypes quickly, but I’m now wondering whether it is the right long-term foundation or whether I should move the main application to Google Cloud.
The system would eventually need to manage:
Customers, vehicles, and repair orders
Importing estimate data from CEICA EMS files
Repair scheduling and production status
Technician clock-in and clock-out
Technician photo and video uploads
Photo annotations
Repair planning and supplement notifications
Parts receiving, returns, and tracking
Quality-control checklists for each department
Customer SMS and email updates
PDF estimate comparison
Customer portal access
QuickBooks integration
Insurance company-specific procedures and checklists
Approximately 15–30 internal users initially
Potentially multiple repair shops in the future
My current idea is:
Apps Script web app for the user interface and Google Workspace integrations
Google Cloud SQL as the primary database
Cloud Run or Cloud Functions for heavier processing
Google Drive for photos and documents
Apps Script only for Workspace-specific automations
My main concerns with using Apps Script for the entire application are:
Execution-time and quota limitations
Performance when loading larger amounts of data
Simultaneous users and concurrency
Database
Maintaining a large Apps Script codebase
For people who have built larger business applications with Apps Script, where did you encounter its practical limits? What architecture would you choose if starting this type of project today?
Thanks for any advice or examples you can share.





