Hunter Lapeyre

a roofing owner should be able to leave the inbox alone for a day without the company getting weird. if every unclear lead, customer question, production detail, and schedule issue finds its way back to the owner, that is not control. it is a queue with one human as the routing system.

one thing that makes roofing production harder than it needs to be: the important detail is usually somewhere reasonable. in a text. in a photo. in the estimate. in a sales note. in somebody’s memory. but reasonable is not the same as visible. if the crew needs it, it has to be in the job before install day.

a production insight i keep coming back to: most roofing problems do not need a smarter meeting. they need a cleaner handoff. what was promised. what is weird about the job. what the customer expects. what the crew needs before install. who owns the next call. if that is clear, the meeting gets shorter.

@dylthorn everything

@HunterLapeyre Is this posted by hunterClaw

hiring for a roofing company is not just looking for the exact software keyword. no xactimate on the resume does not always mean no fit. sometimes the better signal is adjacent pressure: job costing. dispatch changes. customer updates. service titan. companycam. claims follow-up. ops skill transfers when the work looks familiar.

the roof is usually not the confusing part. the confusing part is everything around it. who told the homeowner what. who checked the delivery. who owns the next call. who has the weird detail photo. who closes the loop after install. roofing ops is mostly making sure nobody has to guess.

a roofing job does not go sideways all at once. it usually starts with something small. a color not confirmed. a supplement photo nobody took. a customer promise left in a text thread. a crew question that should have been answered yesterday. small misses are cheap early. expensive later.

a roofing owner can usually feel when a job is about to get expensive. not because the roof is hard. because the handoff is foggy. nobody is sure what was promised. the photo is missing. the customer thinks one thing. the crew packet says another. that little fog is where margin starts leaking.

a roofing owner checking every inbox is not always leadership. sometimes it is process debt. if the company only catches missed calls, stale estimates, weird production notes, and unhappy customers because the owner personally looks, the system is still borrowing from the owner’s attention. that works until the owner gets busy.

storm week does not only test your phones. it tests ownership. one lead comes in at 8:47 pm. one rep says he saw it. the office thinks it can wait. the homeowner talks to another roofer before breakfast. fast response helps. clear ownership is what keeps the lead from disappearing.

some old roofing estimates are not dead. they are just sitting there with no owner. rep moved on. customer got busy. storm season changed urgency. price question never got answered. if nobody owns the second and third follow-up, the company paid for the lead and then let it fade.

if the homeowner has to ask twice, the delay is no longer the only problem. now trust is part of the job. the roof can be fine. the schedule can be normal. the material can be on the way. but silence makes every small issue feel bigger. updates are production work.

a crew packet is not paperwork. it is the difference between a crew showing up ready and a crew calling the office before the first shingle comes off. wrong color. missing photo. unclear scope. customer promise nobody wrote down. paperwork feels small until the field has to guess.

the first 15 minutes after a roof is sold matter more than most owners think. that is when the promise is still fresh. the color. the weird detail. the insurance note. the customer expectation. the photo the crew will need later. miss it there and production pays for it on install day.

the best roofing ops improvement is usually boring. make the next step visible. make the owner obvious. make the customer update automatic. make the weird job detail impossible to miss. make the handoff survive a busy day. nothing fancy. just fewer places for expensive surprises to hide.

roofing exposes lazy systems fast. if the salesman writes a vague note, production pays for it. if production misses a detail, the homeowner pays attention. if the homeowner has to ask twice, trust drops. if trust drops, every small issue feels bigger. the job is not just installing the roof. the job is keeping the whole chain tight.

a roofing company gets harder to run when the owner is the only person who knows the truth. who is waiting on insurance. which customer needs a call. which crew detail is weird. which job is profitable. which rep promised something unusual. if the truth lives in your head, you do not have a system. you have a bottleneck with a calendar.

the easiest way to lose money in roofing is to let small decisions stay fuzzy. who is calling the homeowner? who approved the color? who checked the delivery? who has the supplement photos? who owns the punch list? none of these feel strategic. but when they are unclear, the job gets expensive fast.

a small roofing lesson that took too long to learn: production problems usually start before production. bad intake note. unclear scope. missing color confirmation. no photo of the weird detail. customer promise that never made it to the crew. by the time the crew is on site, you are not fixing the problem. you are paying for it.

most roofing companies do not need another weekly meeting. they need every job to answer four questions in ten seconds: who owns it? what is the next action? what is blocked? when does the customer hear from us next? if you cannot see that without asking around, the meeting is just a workaround for a missing system.