Brightline Home Services · Process auditOperations

Operations Audit

Thirty-one recurring processes mapped from two weeks of calendars, inboxes and the dispatch board. 212 hours a week. Nine ready to automate, seven to delegate, fifteen stay.
Processes mapped
31
two weeks observed
Hours a week
212
across 9 people
Ready to automate
9
64 h a week
Hours returned
68
by month four

The audit followed nine people for two working weeks: calendars, inboxes, the dispatch board and the phone log. Every recurring piece of work that showed up more than twice became a process with an owner, a cadence and an hours count.

01Where the week goes

Admin is the biggest block and the least visible one, because it is spread across everyone in ten-minute pieces. Dispatch and sales are concentrated in two people, which is why both of them say they have no time.

212HOURS / WEEK
Admin64 h
Dispatch48 h
Sales41 h
Finance32 h
Marketing27 h
Admin is 30% of the week and almost none of it needs a person.

02The inventory

Fourteen of the thirty-one processes are shown here, sorted by verdict. Automate means an agent does the work and a person checks it; delegate means someone other than the current owner does it; keep means the owner should keep doing it.

ProcessOwnerHrs / wkCadenceVerdict
Answer inbound calls and DMsFront desk22dailyautomate
Build the next-day dispatch boardOps Lead9dailyautomate
Write and send quotesTechs14dailyautomate
Chase unpaid invoicesFinance8weeklyautomate
Post on Instagram and FacebookOwner6weeklyautomate
Reply to Google reviewsOwner3weeklyautomate
Monday numbers reportFinance4weeklyautomate
Confirm tomorrow's appointmentsFront desk7dailyautomate
Order parts and track ETAsOps Lead11dailyautomate
Onboard a new techOps Lead6monthlydelegate
Reconcile the bankOwner5weeklydelegate
Renew maintenance plansFront desk5weeklydelegate
Vendor negotiationsOwner4monthlykeep
Hiring interviewsOwner6monthlykeep
14 of 31 shown. The remaining 17 (keep, 61 hours) are in the appendix.

03Effort versus impact

Each dot is a process from the inventory, placed by how hard it is to automate and how many hours it returns. The quick-wins quadrant is the plan; the big bets wait until the quick wins have paid for them.

QUICK WINSBIG BETSLATERAVOID1234567891011121314Effort to automate →Hours returned →
AutomateDelegateKeep

04Hours returned, month by month

The projection assumes one process goes live each week from November and returns its full hours a month after launch. It is conservative on purpose: the first month usually returns less, the fourth month more.

18 hNov34 hDec52 hJan61 hFeb68 hMar
One process a week from November. Month four returns 68 hours a week, the equivalent of 1.7 full-time people, without a hire.

05The first five

The first five are chosen for hours returned and for how little they depend on each other. Each one has a tool, an owner who checks the output, and a date.

ProcessHowReturnsLive
Inbound calls and DMsIntake Agent on the phone line and the IG inbox; books straight into the calendar22 hNov 3
QuotesTech dictates on site, the agent writes the quote and sends it within 2 hours14 hNov 10
Parts and ETAsAgent reads supplier emails, updates the job, texts the customer the new date11 hNov 17
Dispatch boardBuilt at 18:00 from the booked jobs, zones and tech skills; Ops Lead edits, never builds9 hNov 24
Invoice chasingThree-step sequence, payment plan offer on step three, human at disputes8 hDec 1

0630 · 60 · 90

The ninety days are sequenced so the front desk feels the change first, the Ops Lead second, and the owner last.

Days 1–30

Intake and quotes live. Front desk stops answering the phone first; the agent does, the human takes the handoffs.

Days 31–60

Parts, dispatch, invoice chasing. Ops Lead moves from building the board to approving it.

Days 61–90

Social posts, reviews, the Monday report. The owner's week drops from 58 hours to 44.