Choosing a model
A roofing virtual assistant, or a back office
These are not two prices for the same thing. They are different arrangements with different failure modes, and one of them is genuinely the better answer for a lot of roofing companies. This page includes which.
An owner looking for help with the paperwork side of a roofing company will find two categories of answer. One offers an individual, engaged directly, working to your instructions. The other offers a managed set of functions with defined coverage and a written scope of work. The marketing for both tends to describe the same benefits, which is why the choice is usually made on price and then regretted for structural reasons.
The difference is not seniority, capability, or location. It is what you are buying: a person whose time you direct, or an outcome somebody else is accountable for producing. Everything else follows from that, and both arrangements are legitimate.
The actual distinction
Engage a virtual assistant — the arrangement most of this market sells — and you have acquired capacity that somebody has to manage. There is an individual who can do work you specify, and the owner remains responsible for specifying it, training them into your context, checking the output, covering the gap when they are away, and finding a replacement when they leave. That last item is the one owners consistently underprice, because it is invisible right up until it happens.
Engage a back office and you have acquired a function that somebody else runs. The scope of work says which functions, what happens inside each, and what the reporting looks like. Continuity, coverage during absence, documentation and the training of whoever performs it sit on the other side of the line. You manage an outcome rather than a person, and if the outcome is not being produced that is a conversation about the scope rather than about an individual.
Which means the real question is not who is cheaper. It is whether the work you need covered can safely depend on one individual being available, and whether you want to be the one holding it together when they are not.
What a label settles, which is nothing
The vocabulary in this market is unhelpful, because the same words cover very different arrangements. Two providers using identical language can deliver an individual working to your direction and a documented function with cover behind it, and the words will not tell you which you are getting.
Federal wage law makes the same point about employment status in a way worth borrowing. Under 29 CFR 541.2, “A job title alone is insufficient to establish the exempt status of an employee,” and status “must be determined on the basis of whether the employee’s salary and duties meet the requirements of the regulations in this part.” The rule exists because titles are cheap and duties are not — the label is not evidence of the thing.
Apply the same test when you are choosing. Do not ask what an arrangement is called; ask what is covered, who covers it when the usual person cannot, whether the procedure is written down, and who holds it if the arrangement ends. The answers separate the two models far more reliably than the vocabulary does.
What changes if you employ somebody directly
Some owners resolve this by hiring, which is a legitimate third answer and sometimes the best one. It is worth being clear about what it moves onto your side of the line, because the comparison is often made against a version of employment that leaves the obligations out.
Engaging somebody as an employee attaches employer obligations from the first payroll — including obtaining Form W-4, Employee’s Withholding Certificate, and the payroll, recordkeeping and eligibility-verification duties that travel with it. None of that is difficult, and plenty of roofing companies handle it without thinking about it. But it is real work that belongs in the comparison, and it lands on whoever is already doing the administration — frequently the same owner the arrangement was meant to relieve.
This describes obligations in general terms to make a comparison legible. It is not legal, tax or employment advice, it makes no determination about your company or any particular engagement, and the rules that apply depend on circumstances. Your own counsel or accountant is the right place for those questions.
When the other option is the right one
There are roofing companies for which a virtual assistant is genuinely the better arrangement. Saying so here is cheaper for everybody than discovering it three months into an engagement that was never a fit.
A virtual assistant fits one well-defined recurring task
If what you need is a specific repeating job — the same entry, the same chase, the same weekly report — then a documented department around it is structure you are paying for and not using. One capable individual doing one clear thing is efficient, and adding scope around it makes it worse rather than better.
The operation is genuinely small
Below a certain size the coordination a department provides costs more than the coordination problem it solves. A company where the owner already sees every job, every invoice and every call does not have a continuity problem to fix — it has a capacity problem, and capacity is what an individual supplies.
You want direct day-to-day control
Some owners want to direct the work, change priorities hour by hour, and be the one who decides sequence. That preference is legitimate and it is a poor match for a scope-and-cadence arrangement, which deliberately puts a document between you and the daily decisions. If reading that sentence produced resistance, believe the resistance.
You already have a good internal person
The right move there is usually to take repeatable work off them so their judgement goes where it is worth most — not to replace them. An enquiry that would end with a capable internal person being displaced is one we will push back on, because it is normally a worse company afterwards.
When a department is the right one
The case for the other shape is narrower than the marketing suggests, and it comes down to three conditions rather than a general claim of superiority.
Span is one. When the work crosses functions — the call that becomes a booking that becomes a job record that becomes an invoice — the handoffs between them are where things get lost, and a single individual holding all of it is holding those handoffs in their head. Continuity is another: work that cannot pause needs somebody behind whoever is doing it, and that redundancy is either designed in or discovered missing. Transferability is the last. Where the process is written down it survives turnover on either side, and the company ends up owning something it did not own before.
Where those conditions hold, the department pages set out what each function actually covers and where its boundary sits — including the things each one declines to do.
Questions owners ask when choosing
Is one model simply better than the other?
No, and a page that concluded otherwise would not be worth reading. They solve different problems. A virtual assistant is the right answer when the work is a defined, repeating set of tasks that one competent individual can hold, and when the owner wants direct day-to-day control over how it is done. A back office department is the right answer when the work spans functions, has to continue through absence, and needs to be handed to somebody other than the owner.
What actually breaks first with a single point of contact?
Continuity, almost always before capacity. The arrangement works well until the day it needs to work without that individual — illness, holiday, a second job, or leaving. At that point the company discovers how much of the process existed only in one head, and the cost of that discovery lands in the week you can least afford it. Capacity limits are visible and plannable; continuity gaps are neither.
We had a bad experience with this before. Why would this differ?
It might not, and the honest test is structural rather than a promise. Ask what happens when the individual doing your work is unavailable, ask who else has done it, and ask to see the written procedure for it. If the answers are vague, the arrangement is a person rather than a function regardless of what it is called — and that is true of us as much as of anyone else you ask.
Does a department mean we lose control of how things are done?
You trade day-to-day direction for a written scope and a reporting cadence, which is a real trade rather than a free upgrade. Some owners strongly prefer the direct version, and for them the trade is a loss. What you get back is that the process is documented, so it can be inspected, corrected and continued — and if the arrangement ends, the procedure is yours.
Can we start with one function and see?
That is the usual and the recommended path. A single function run properly is a fair test of whether the arrangement suits you, and it is a far better test than a broad scope neither side has thought through. If it works you extend; if it does not you have lost one function rather than your whole back office.
What if we already have someone in-house doing this?
The question becomes what that person should stop doing rather than whether to replace them. In most companies the useful move is to take the repeating, documentable work off an experienced individual so their time goes to the parts that genuinely need judgement and context. Replacing a good internal person with an external arrangement is rarely the right recommendation, and we will say so.
How do we decide without getting this wrong twice?
Write down the functions you actually need covered, then ask of each whether it can survive the person doing it being away for two weeks. The functions that cannot are the ones that need a department behind them. The ones that can are genuinely fine held by an individual, and paying department prices for them is waste.
Where to go next
- How working with us works The three steps in, and how a handover is reversed if the fit turns out to be wrong.
- What shapes a scope of work The five dimensions an engagement is priced against, and why no figure is published.
- All nine departments The full function list, each with the failure it prevents and the limit it works inside.
Rules referenced above
Both were fetched and read while this page was written, and the clauses in quotation marks were copied out of the documents they are attributed to rather than recalled.
- 29 CFR 541.2 — Job titles insufficient — U.S. Office of the Federal Register (eCFR)
- About Form W-4, Employee Withholding Certificate — U.S. Internal Revenue Service
Not sure which one you need?
Describe what is actually piling up. If the answer is the other model we will tell you, and you will have lost a phone call rather than a quarter.