The product problem
Service operations rarely fit clean SaaS templates. Real businesses have accounts, sites, assets, agreements, inventories, technicians, exceptions, and legacy data that must become understandable software.
What GCG delivered
Ongoing development of the platform, including:
- AI-drafted technician work instructions, grounded only in the ticket, asset history, and documents supplied, run on AWS Bedrock and metered against the tenant's AI budget
How the platform is organized
The platform is multi-tenant and permissioned. Its feature areas include tickets and SLA tracking, sites and assets, parts and branch inventory, technician trips and reports, service agreements with service pricing, company users and seats, AI budget and usage, and billing.
The browser client and the API are separate repositories. The API holds the database migrations, backend tests, Docker runtime, and AWS infrastructure definitions.
How it is tested and released
The browser client has a Playwright end-to-end suite. Development and production run as separate application stacks.