Solo HVAC contractor · Wellington, FL · 8 years in business · planning his first hire next year
Before SproutDock — and what changes after.
Walk through how Diego's whole workflow runs through SproutDock. Each stage shows whether the feature is live today, coming soon, or on the roadmap.
Maria Hernandez calls Diego at 9:15 AM. Her AC is blowing warm air. Diego searches her name — she's an existing customer from last summer's capacitor replacement. He opens a new Job for her, sets the priority, and schedules it on the calendar.
The calendar shows the 10-day weather forecast with risk scoring for outdoor work. Diego sees a heat wave starting Thursday. Maria was a Friday slot, but he moves her to Wednesday afternoon instead. She's not going to be without AC during a 95-degree weekend.
Wednesday at 1:30 PM, Diego loads his truck. He pulls up Maria's customer record on his laptop before pulling out of his driveway. Her unit is a Carrier 24ACC636A003, installed 2019. Last service: June of last year, capacitor replacement.
Her customer notes read: “Side gate, code 4829. Dog in yard — friendly but tie up before going to the back unit.” He sees her past Job history right on the page. Diego loads parts in his truck based on what he already knows about the unit.
Diego opens the Job and works through his diagnostic checklist as Tasks: check capacitor, check refrigerant pressure, check contactor, check coil temps. The contactor's burned — not the capacitor this time. He photographs the burned contact points and the meter reading. Files upload straight to the Job.
He marks the diagnostic tasks complete and pulls “Contactor 40A 2-pole” from his Products catalog. The part is now logged against the Job, ready to flow into the invoice.
While Diego is finishing up, Maria's husband emails from his office: “Do we need a new system?” He's been googling “AC compressor replacement cost” for the last twenty minutes.
Diego answers from inside the Job. The email goes from his business domain, threaded under Maria's Job, with the photo of the burned contactor attached. His reply: “It's just the contactor — $40 part. System's fine, you've got another 5-7 years out of it. Photos attached.” The reply takes ninety seconds.
Diego picks the “AC Service Call” invoice template. Line items pre-populate from what he logged on the Job: diagnostic fee, contactor part, labor. He adds a 90-day warranty note and sends it.
Maria receives the invoice by email with a payment link. She pays from her phone using her card. Stripe webhook auto-marks the invoice paid the moment the payment clears. Diego sees the green check appear on his dashboard while he's still loading his ladder back onto the truck.
As Diego is packing up, Maria mentions the annual maintenance plan he told her about last summer. She's ready now. Diego pulls up his pre-built maintenance contract template, fills in her details (auto-populated from her customer record), and sends it.
Maria reads the agreement on her phone right there in the kitchen, draws her signature with her fingertip, taps Send. The signed PDF locks in her file with a timestamp and IP address audit trail. Maria is now Diego's 31st maintenance customer.
Diego sets up his common Job workflows once: “Emergency Service Call,” “Annual Maintenance,” “New System Install.” Each workflow defines the steps that always happen — contract, deposit, scheduled visit, diagnostic tasks, photo review, final invoice.
When Diego creates a new Job and picks the workflow, the steps generate automatically. As each one completes (contract signed, deposit paid, all tasks done), the next one activates. SproutDock comes seeded with HVAC workflow templates Diego can clone and customize.
Today, Diego is solo. The platform handles his single-truck reality. But the same setup carries through when he scales.
When he hires his first tech: same Jobs, multiple staff assigned, communications stay tied to each Job regardless of who responded. When his maintenance book reaches fifty customers: recurring billing automation rolls out, auto-generating tune-up invoices on schedule. When his truck count grows beyond two: dispatch view, client portal where customers see their unit history and schedule their own visits, field upload links so techs can drop photos via QR code without logging in — all on the roadmap.
Same day. Same caseload. Different reality.
Diego spends less time on admin because the system handles the structure. His customers come back because their service history follows them — they don't have to re-explain their AC every time. His maintenance book grows because the closing moment doesn't get lost to paperwork. Every month, the gap between “running a business” and “fixing AC units” gets smaller.