Cost Allocation for Freelancers: The Deep Dive on Shared Expense Math

The concept of cost allocation is simple: when an expense serves more than one income stream, split it proportionally. The execution — especially at the small scale a freelancer operates at — is where the hidden decisions live. This post goes deep on the allocation methods, the edge cases, and the IRS's expectations for freelancers who run multiple streams under a single Schedule C.

Why allocation exists as a concept

Your office pays rent. Your office hosts three side projects. All three projects consume the office, but only one will eventually pay for it if you lump the rent into the biggest stream by default. The bigger stream then looks less profitable than it is; the smaller streams look more profitable than they are. Both distortions lead to bad business decisions.

Cost allocation's only job is to prevent one income stream from silently subsidizing another. Get it wrong and you'll make rate, pricing, or kill decisions based on fiction.

The three defensible methods for freelancers

Larger businesses have dozens of allocation frameworks (activity-based costing, departmental burden rates, standard costing). For freelancers, three methods cover 95% of real cases:

Method 1: Time-weighted (hours)

Split the cost in proportion to hours worked on each project. Most useful for overhead that scales with attention: office space, home utilities, productivity software, your phone bill.

Pros: matches how "workspace-like" overhead is actually consumed. Cons: hours shift, so the allocation shifts monthly — requires recalculation.

Method 2: Revenue-weighted

Split by percentage of total revenue. Most useful for overhead that scales with money moving through the business: merchant accounts, payment processor monthly fees, general liability insurance, accountant retainer.

Pros: aligns with the economic reality that bigger streams generate bigger "money-flow" costs. Cons: over-charges the biggest stream when that's not the actual cost driver (e.g., office rent doesn't scale with revenue).

Method 3: Equal-share

Split the cost equally across active projects regardless of hours or revenue. Useful for genuinely uniform-use shared resources: a domain registrar hosting three vanity domains, a password manager with equal footprint, a business bank account covering all streams.

Not appropriate for any resource where consumption is wildly uneven. Don't allocate a 90%-consulting-used resource equally just because "equal" feels fair.

Mixed-method allocation (the real-world answer)

The right answer is rarely one method for all shared costs. A reasonable freelancer allocation policy looks like:

The edge cases that actually come up

Edge case 1: A project with no revenue yet

You launched a newsletter 3 months ago. No subscriptions yet. Revenue-weighted allocation gives it $0 of shared costs; hours-weighted gives it its actual hour share. The right answer is usually hours-weighted for any pre-revenue project — the work is real even if the money isn't.

Don't give a zero-revenue project zero shared costs just because it's convenient. That's the allocation equivalent of hiding a loss.

Edge case 2: A project you're winding down

You've decided to kill the Etsy shop. It still has inventory selling through, but you're spending zero hours on it. For the wind-down period, revenue-weighted allocation is usually right — hours-weighted would give it nothing while it's still generating revenue.

Edge case 3: A large one-off expense

You bought a $2,000 camera. It'll be used for the YouTube channel (primary) and occasionally for client work (secondary). Don't try to allocate the cost of the camera monthly. Either:

• Immediately expense under Section 179 and allocate the deduction based on the intended use split at purchase
• Depreciate over 5 years (standard for camera equipment) and allocate each year's depreciation based on that year's actual use

For a primarily-one-project asset, most freelancers assign 100% to the primary project and treat the secondary use as incidental. Keep a note explaining the reasoning.

Edge case 4: Inconsistent allocation year over year

What if your allocation shifts because your business shifts? You went from 70% consulting / 30% Etsy in 2024 to 50/50 in 2025. That's not an allocation change — that's a business change. Your method stays the same (e.g., time-weighted), the percentages just update naturally.

The red flag is changing the method itself — switching from time-weighted to revenue-weighted — especially when the change happens to reduce taxable income.

What this looks like at scale (worked example)

Priya runs three streams. Monthly numbers:

Shared costs for the month:

• Home office (simplified method): $125
• Internet + phone: $95
• Figma + Notion + password manager: $48
• Accountant retainer (monthly portion): $200
• Merchant account monthly fee: $15
• General liability insurance: $95

Applying the mixed method:

Observations the single-column approach couldn't have surfaced:

• Consulting and Etsy both look strong on margin, but consulting earns 8× more per hour.
• The newsletter has a respectable 65% margin but at $9.81/hr is barely above minimum wage. The question isn't profitability — it's opportunity cost.
• The accountant retainer ($240 of it) is being carried by consulting because the allocation is revenue-weighted. Priya shouldn't re-allocate to "fix" this — consulting is where the tax complexity lives anyway.

The takeaway

Cost allocation done right isn't perfect; it's consistent and defensible. Pick methods that match how each cost is actually consumed, document the choices, apply them monthly, and let the numbers reveal the business you're actually running.

Related: the profit-per-project pillar guide for the allocation context, shared business expenses for the simpler intro.

Related reads