Case study
Operations software for a multi-division contractor
A home services contractor in Colorado was running 4 divisions across 2 states: gutters, insulation, windows, and drywall. Operations were spread across spreadsheets, whiteboards, and disconnected CRM tools. Over the engagement I built four systems that replaced that patchwork.
01
Field Operations Platform
The problem
Scheduling lived on a whiteboard and in the operations manager's head. Crews found out about job changes by phone, job costs were reconciled after the fact in spreadsheets, and change orders were approved over text with no paper trail.
The approach
A multi-tenant platform so each division has its own space while the owner sees everything. Drag-and-drop scheduling and dispatch, a crew mobile app for clock in/out, checklists and job-site photos, job costing that tracks labor, materials, and subs against the estimate, and change orders that go through a customer approval portal. Built custom rather than forced into an off-the-shelf tool because the divisions run genuinely different workflows.
The outcome
Scheduling, dispatch, field data, and job costing now live in one system instead of a whiteboard plus three spreadsheets. Change orders have an auditable approval trail.
Next.js · FastAPI · Railway · Supabase
See the Field Operations Platform package02
Accounts Receivable Dashboard
The problem
Receivables were tracked across separate spreadsheets, one per division, updated by hand. Nobody had a single number for what was outstanding, and overdue invoices slipped because follow-up depended on someone remembering.
The approach
A real-time AR dashboard that syncs invoices, payments, and credits directly from the CRMs the business already used (Housecall Pro and ServiceMinder). Aging buckets for current, 30, 60, and 90+ days, automated alerts when an invoice goes overdue, a customer payment portal, and a multi-division view so the owner sees one consolidated picture.
The outcome
AR visibility went from a spreadsheet-per-division to one unified dashboard, with overdue follow-up triggered automatically instead of from memory.
Dual CRM sync · Aging buckets · Automated alerts
See the Accounts Receivable Dashboard package03
Permit Monitoring System
The problem
New construction leads were reactive: the team heard about projects late, often after competitors had already reached the builder.
The approach
An automated pipeline that pulls building permits from Denver open data, scores and tags each permit by trade and division, estimates contract value, attaches builder information, and routes it to the right person on the team as new permits are filed.
The outcome
A proactive lead pipeline built on real construction activity. The first time it ran, the owner texted a builder from the list within minutes.
Open-data ingest · Scoring & tagging · Division routing
See the Permit Monitoring System package04
Local SEO (5 sites, 2 states)
The problem
The divisions' websites weren't showing up when homeowners searched locally, and there were no city-level pages to rank for the markets they served.
The approach
Technical SEO fixes, Google Business Profile optimization, and a scalable city + service page template rolled out across five sites in two states, backed by review strategy, citation building, and call tracking so leads are attributable.
The outcome
Multiple city pages ranking on page one across several markets, with call tracking showing which pages generate calls.
City pages · GBP · Technical SEO · Call tracking
See the Local SEO (5 sites, 2 states) package“I'm impressed with Talha Jaleel's grasp of our world. He's a pleasure to work with — made this process easy and respectfully pushes for feedback where he needs it.”
Running on the same patchwork?
If your operation is spread across spreadsheets and tools that don't talk to each other, a scoping call is the fastest way to find out what it would take to replace it.