The 6-Hour Tax: What Consultants Pay Every Week in Assembly Work
A consultant I know was spending six hours every week just assembling client artifacts.
Not on strategy. Not on client calls. Not on the thinking that actually drives results. Assembling.
Pulling data from three sources. Reformatting reports into the client’s preferred layout. Copying status updates into slide decks. Making sure everything looked cohesive when it came from a shop of one.
Six hours. Every single week. Just to make it look like the work happened.
Three hundred hours a year. Twelve full work weeks. Not on bad work — on work that shouldn’t require her at all.
Why Assembly Work Is Invisible
Here’s the insidious thing about assembly work: it doesn’t feel like a problem while you’re in it.
It feels like “doing client work.” You’re pulling data, creating deliverables, maintaining professional standards. It’s client-adjacent. It’s billable-adjacent. It has the texture of productivity.
But it’s not strategy. It’s not the analysis that takes real expertise. It’s not the conversation that builds the relationship. It’s the formatting, the packaging, the logistics of making your actual work presentable.
“It’s assembly. And it’s a tax on every hour you actually bill.”
The problem compounds as you grow. More clients means more assembly. You can’t easily offload it to a VA because they don’t know your work well enough to do it without your review. You can’t hire a junior person because you’d spend as long explaining it as doing it yourself. So it stays on your plate, week after week, quietly consuming time you could spend growing the practice.
The Five Forms of Consultant Assembly Tax
You have the analysis. The insight is done. Now 90 minutes of putting it into a slide deck that doesn’t misrepresent the nuance. The thinking was 30 minutes. The packaging is three times that.
Pulling progress from your project tool, translating it into language your client understands, making it look like a coherent narrative instead of task statuses. Every week. For every client.
Client A uses a different CRM than Client B. Client C sends you data in a spreadsheet that doesn’t match your template. Forty-five minutes reconciling before you can do anything useful.
The scope is clear in your head. Writing it into a professional document that matches previous proposals, uses consistent language, and looks like it came from the same firm — that’s the slow part. Not the thinking. The production.
Condensing three weeks of work into an update that reads clearly, leads with what they care about, and doesn’t require a 45-minute call to explain. Drafting, rereading, tightening. The meeting prep that shouldn’t require two hours of prep.
What Happens When You Get That Time Back
The consultant I mentioned started using Sandbox to handle the assembly layer — the artifact generation, the status packaging, the report formatting. It runs in the background. She reviews and sends.
She got those six hours back in week one.
Here’s the part that mattered: those six hours didn’t disappear back into different admin work. They went somewhere specific — a new client engagement she’d been too stretched to take on.
That’s the asymmetry. Assembly consumes six hours. A new client engagement generates five to ten times that in revenue. When you reclaim the time, the business grows. Not incrementally. Structurally.
Before (Assembly in Her Hours)
- 6 hrs/week on packaging and formatting
- 4 clients max before bandwidth hit
- New client proposals delayed by capacity
- Strategic thinking happens in leftover time
- Growth capped by her own weekly hours
After (Assembly in the Background)
- 6 hrs/week reclaimed for billable or growth work
- 6 clients without proportional overhead increase
- New client onboarding takes days not weeks
- Strategic thinking in prime hours, not evenings
- Growth capped by client fit, not her time
The Question Worth Asking
Most consultants accept assembly as the cost of running a lean practice. It feels like overhead that’s just part of the job — unavoidable, background noise.
It isn’t. It’s a structural problem with a structural solution.
When you describe what you need in plain language — “draft the weekly status update for Client A, using the project tracker and last week’s update as sources” — and an execution layer produces it for your review, the six hours become twenty minutes. The work still happens. You just stop being the one assembling it.
The question isn’t whether you’re good enough at assembly to keep doing it. You clearly are. The question is whether those six hours are the highest-value use of your time — and if not, what becomes possible when you get them back.
For her, it was a new client. For most consultants I talk to, it’s some version of the same thing: the thing they’ve been putting off because there just wasn’t room.
Running a consultancy and spending hours every week on assembly that shouldn’t require you?
Book 20 minutes. I’ll show you what the assembly layer looks like when it runs in the background — artifact generation, status packaging, report formatting, outreach sequencing. Using your actual clients as the example, not a demo account.
→ Book at cal.com/edgarinvillamar/15min
Or reach out directly: rob@sandboxgtm.com