From Scheduling Chaos To Operational Visibility
Triangle Contractors had real demand, active crews, property teams making requests, and work moving through the business. The issue was not effort. It was that scheduling, request intake, crew coordination, quality-control visibility, and invoice preparation were being held together by informal systems.
This was a flexible, hands-on engagement where Arcwise moved from operational diagnosis into practical workflow stabilization. That is different from the default diagnostic scope: the diagnostic finds the friction and defines the path; implementation is scoped separately when the business needs help turning the finding into a working operating layer.
Situation
A busy contractor with an informal operating layer.
Triangle Contractors of NC serves multifamily and field-service work where timing, property access, crew coordination, job details, quality control, and billing handoff all matter. Like many owner-led businesses, the company had grown around a process that worked because the owner could personally keep the moving parts in view.
That kind of system can look fine from the outside. Work gets done. Property teams get answered. Crews stay busy. But underneath, the owner becomes the router, scheduler, memory bank, crew dispatcher, and back-office translator.
Problem
The business had workflow demand, but not enough workflow visibility.
Work requests arrived through calls, texts, voicemails, and informal messages.
The owner had to interpret each request before it could become schedulable work.
Scheduling depended on a notebook, crew availability checks, and manual follow-up.
The same information later had to be reconstructed into spreadsheets and invoice prep.
Pricing, quality-control scheduling, and back-office handoff depended too heavily on owner memory.
Arcwise Approach
Start with operational reconnaissance, then stabilize the bottleneck.
The useful first move was not to buy a large contractor-management platform. It was to inspect how work actually moved, identify the repeated handoffs, and structure the data before automation or heavier software decisions entered the picture.
Diagnose the flow
Map how requests entered the business, what had to be clarified, and where work stalled before scheduling or billing.
Stabilize the intake
Create a structured request path so the same core details were captured consistently instead of reconstructed later.
Build lightweight visibility
Use tools already available to the business to create a practical operating layer for scheduling, pricing review, quality control, and invoice preparation.
Solution Built
A custom four-platform automation system — built with AI, designed from scratch.
Rather than stitching together off-the-shelf connectors or buying a contractor management platform, Arcwise designed and built a custom automation system from the ground up — four integrated platforms, connected by roughly 3,000 lines of AI-generated Google Apps Script code, and assembled using AI build tooling including MCP servers and AI-assisted browser automation.
The result is a system that behaves like purpose-built software — because it is. Built specifically for how this business operates, not adapted from something built for the median user.
Platform Integration Map
Google Form
Google Sheets
Google Calendar
QuickBooks Online
Stage 1 — Structured Intake (Google Form)
A custom intake form captures all required job details at the point of request — property, unit, work type, access notes, timing, and contact information. No more requests arriving through texts, voicemails, and informal calls.
Stage 2 — Scheduling & Workflow Hub (Google Sheets)
Form submissions feed directly into a Google Sheets-based operations layer. Custom Google Apps Script code routes, organizes, and flags work requests automatically — triggering downstream actions without manual data entry or re-keying.
Stage 3 — Crew Calendar Automation (Google Calendar)
Approved work orders automatically generate calendar entries with full job context — property, unit, timing, work scope, and access details. Crews check the calendar. The owner stops writing Sunday-night text summaries.
Stage 4 — Invoice Automation (QuickBooks Online)
Completed work triggers automated QuickBooks Online workflows for invoice preparation — pulling structured job data directly from the Sheets layer into the billing pipeline. Accounting handoff no longer depends on owner memory or spreadsheet cleanup.
Build Infrastructure
The integration layer is custom Google Apps Script — JavaScript-based, running server-side inside Google Workspace. Dozens of individual scripts, roughly 3,000 lines of code in summation, built and iterated using AI code generation (Claude, ChatGPT Codex) and wired together using MCP servers and AI-assisted tooling. No third-party connector platforms. No monthly SaaS integration fees. Fully owned, fully auditable, built to the exact requirements of this business.
Reported Result
12-15
hours per week saved
Result
Less reconstruction. Faster requests. Clearer crew visibility.
The owner/operator reports saving roughly 12-15 hours per week in administrative scheduling and invoice-prep work.
Most of that time came out of the repetitive, low-value admin work the owner least wanted to keep doing.
Property managers and maintenance contacts gained a faster, more flexible way to submit job requests through a structured form.
Scheduling visibility made it easier to reply quickly when a request could or could not fit the calendar.
Crews no longer had to wait for a manually written Sunday-night text with the property, unit, timing, and work details.
Calendar updates now give workers a clearer place to check the where, what, and when before the week starts.
The integration layer — Forms, Sheets, Calendar, and QuickBooks Online — runs on custom Google Apps Script code built entirely with AI tooling. Zero manual data re-entry between platforms.
The system was designed, built, and deployed without purchasing a single contractor management platform or third-party integration service.
Build infrastructure: Claude, ChatGPT Codex, MCP servers, AI-assisted browser automation — assembled into a working production system.
Owner / Operator
Less time spent reconstructing requests, writing crew updates, cleaning spreadsheets, and preparing work for invoicing.
Property Teams
A clearer request path with faster feedback on whether work could fit the schedule.
Field Crews
Calendar-based visibility into where to go, what unit to work on, and when the job was scheduled.
Why It Matters
The lesson is not more software first. It is understanding what you actually need — and then building it precisely.
Most small businesses are told their only options are: buy a big platform, hire a developer, or stay manual. This build proves a third path.
Starting from operational reconnaissance — mapping how work actually moved through the business — we identified exactly what needed to be connected and exactly how. From that design, a custom four-platform automation system was built using AI as the engineering layer: AI-generated code, AI-wired integrations, AI-assisted iteration.
The result is software that behaves like it was built for this business — because it was. Owned outright. No ongoing SaaS fees for the integration layer. No vendor dependency. No features you don't use charging you monthly for the privilege.
That's the Arcwise approach: diagnose the real workflow, design the right architecture, and build something that fits — using AI as the build engine.
Share this case study
https://arcwise.io/case-studies/triangle-contractors-operational-visibilityInspect the workflow before buying another tool
If your business depends on informal scheduling, owner memory, spreadsheet cleanup, or manual invoice preparation, Arcwise can help inspect the workflow before you spend money on another tool.