Roof Rejuvenation Business Plan

The purpose of the plan is to force the owner to answer, on paper, the questions the operation will surface anyway. Who is the customer, what are we selling them, how do we produce it, how much does it cost to produce, how many can we produce in a week, who does the work, what does the money look like across the first eighteen months, and what breaks the plan if it goes wrong. Answering those questions in advance turns a launch into a management project rather than a series of surprises.

A useful plan is short enough to read on a Saturday afternoon and specific enough to argue with. Fifty pages of boilerplate does neither. Twelve pages of decisions and numbers does both.

• Who is the customer? Age of home, roof composition, homeowner demographic, decision-maker profile, and the objection pattern the sales team should expect.
• Where are they? Service area boundaries, priority ZIP codes, driving radius, and the number of qualifying households inside that radius.
• Who else is selling to them? Local replacement contractors, other rejuvenation operators if any, and the substitutes the homeowner will consider (do nothing, patch and wait, replace).

Three pages, not thirty. The market section exists to constrain the rest of the plan, not to justify it.

The service definition is what the operation actually sells. It names the chemistry family in use, the application method, the inclusions in a standard job, the standard warranty language the customer receives, and the categorical exclusions. It also names what the operation does not sell, because a clear no protects capacity as much as a clear yes.

Write the service definition tight enough that the sales team, the crew, and the office all describe the offering the same way. Ambiguity in the definition shows up later as callbacks, warranty disputes, and inconsistent pricing.

The operating model is how the work gets produced. It covers the job cycle from booked inspection through invoice, the roles involved at each step, the handoffs between roles, the tools used, and the standard the operation holds itself to. A one-page workflow diagram plus a one-page role list is often enough at the plan stage; more detail belongs in the operating manual.

• Lead intake to booked inspection: response time standard, qualification criteria, and calendar rules.
• Inspection to proposal: what the estimator captures, how the proposal is generated, and how it is presented.
• Proposal to signed contract: expected close window, discounting rules, and financing referral (if any).
• Signed contract to scheduled job: lead time from signature to first available date and how weather cancellations reschedule.
• Scheduled job to completed job: crew composition, cycle time, safety checkpoints, and documentation package.
• Completed job to invoice: warranty registration, homeowner handoff, and payment collection.

• Target average ticket, and the range around it.
• Direct cost per job: labor, chemistry, disposables, and vehicle allocation.
• Gross margin per job at the target ticket, and at the low end of the ticket range.
• Contribution to overhead per job.
• Customer acquisition cost, expressed as marketing plus sales cost per closed job.

The plan states the number, states the source, and states the confidence level. A number without a source is a guess; a number with a source and a confidence level is a decision that can be revisited when reality diverges.

Capacity is the ceiling on revenue in any given week, and it is what most first-year plans get wrong. The relevant question is not how many jobs the crew can do on an ideal day. It is how many jobs the crew can do across a normal week, accounting for weather, drive time, rework, sick days, and the ramp curve of a new hire.

State weekly capacity at three points: minimum defensible, realistic average, and stretch. Marketing spend and sales activity should be dialed against the realistic average, not the stretch. Chasing stretch capacity every week is how quality drifts.

The org chart at plan time is small. Owner, salesperson (often the owner in year one), lead technician, application technician, and part-time office support is a common starting shape. The value of writing it down is that it forces the owner to name who does each recurring task, which surfaces the tasks nobody will own by default.

Name the role, name the person filling it (even if the answer is the owner), and name the succession plan for each role. If the answer is the owner for four of the five roles, the plan needs a hiring milestone before the operation can grow past the owner's personal capacity.

• Weekly cash flow for the first twenty-six weeks. Weekly, not monthly, because the ramp happens week to week.
• Monthly summary for months seven through eighteen.
• Base, conservative, and optimistic scenarios, each with a named assumption set.
• Initial capital outlay broken out by category (equipment, vehicle, training, marketing, working capital).
• Cumulative cash flow line so the payback point is visible on the page.

Do not import someone else's dollar figures. Build the projection against local labor rates, local chemistry cost, the operator's realistic ticket, and the operator's realistic weekly volume. Everything else is fiction.

A risk register is a table of what can break the plan, how likely each risk is, how much damage it does if it fires, and what the operator will do about it. The exercise is short and cheap and it changes behavior; naming the risk in advance makes the response faster when the risk shows up.

• Weather delays exceeding four weeks in a season.
• Loss of a lead technician in the first year.
• A regulatory change to chemistry approvals in the operator's state.
• A warranty claim pattern that indicates an application issue.
• A marketing channel that stops producing at the expected cost.
• A cash flow gap between signed contracts and collected payments.

Note the mitigation, not just the risk. A register of risks with no mitigation column is a worry list.

The plan is not finished when it is written. Set explicit review points: end of month three, end of month six, end of month twelve, end of month eighteen. At each checkpoint replace assumptions with actuals and note what has changed. That practice is what turns the plan from a document into a management tool.

Name the specific milestones the plan is being measured against. First revenue week. First profitable week. First hired crew member. First month at steady-state volume. First month meeting the projected gross margin. Missing a milestone is information; hiding a missed milestone from the plan is not.

• Writing the plan for an audience rather than for the operator.
• Importing sample dollar figures from a template and never replacing them.
• Presenting a single-number financial forecast instead of three scenarios.
• Under-sizing initial working capital and running the operation cash-tight in month three.
• Naming stretch capacity as the planning number.
• Never revisiting the plan after launch.