An agency that wins more work than its team can build has four ways to cover the gap: a freelancer, staff augmentation, outsourcing the project, or a white-label partner working inside its own process. The four differ less on hourly cost than on what a client never sees on the invoice, which is who manages the work, who carries the delivery risk and who owns the code at the end. Pick on those, and the price question mostly answers itself.
Picture a 14-person agency in October. A retainer client wants a second product live before January, the senior developer who knows their stack has just given notice, and the job ad for a replacement has produced two applicants worth a call. Each option below is read against that week.
What each option means, side by side
A freelancer is an individual you contract directly, usually by the hour, who works on your tasks under your direction. Staff augmentation is a contract in which a firm supplies developers who work under your direction, while the firm stays their employer. Outsourcing means you hand a defined project to a vendor that builds it with its own team and its own process, usually against a fixed scope. White-label subcontracting means a partner's engineers build work that you deliver to your client under your own brand, normally inside your repositories and your standups.
The labels blur in sales decks, and the same arrangement gets sold under two of these names. So ask any provider two questions: who directs the daily work, and whose name does the client see? The answers tell you which of the four you're actually buying.
| Freelancer | Staff augmentation | Outsourcing | White-label partner | |
|---|---|---|---|---|
| Who directs the daily work | You | You | The vendor | Your process, their tech lead |
| Who carries delivery risk | You | Mostly you | The vendor, within the agreed scope | Shared, as the contract sets it |
| Where the code lives | Your repos | Your repos | The vendor's, handed over at the end | Your repos |
| What the client sees | Your brand | Your brand | Often the vendor, unless the contract says otherwise | Your brand, or a disclosed partner if you choose |
| California classification risk | Highest | Low, the firm is the employer | Low | Low, if the partner is a real business |
| What usually breaks first | Availability | Your tech lead's calendar | Change requests | Fit, if you skip a pilot |
Notice that price isn't a row. A cheap option that lands its risk on your tech lead isn't cheap for a 14-person shop, because that lead is also the person selling the next project.
Freelancers are the fastest to start and the hardest to defend in California
The pool is real. The US Bureau of Labor Statistics counted 11.9 million independent contractors on their main job in July 2023, 7.4 percent of total employment, in a survey it released on 8 November 2024. And 80.3 percent of them said they preferred the arrangement to a traditional job, so plenty of good developers want exactly this.
The trouble is the law, not the people. California's ABC test treats a worker as an employee unless the hiring business shows three things: the person is free from its control, the work is outside the usual course of its business, and the person runs an independent business of the same kind. A development agency's freelancer writing code for its clients usually fails the middle test, because writing code for clients is the agency's usual course of business. The business-to-business exemption can apply instead, but only when all 12 of its criteria hold, and we walk through them as an intake checklist.
Settle two more things before the first commit. Code a contractor writes isn't work made for hire by default, so you need a signed assignment, which the code ownership post covers. And if the freelancer is offshore, the tax paperwork changes, which is its own short read.
Our opinion: for a California agency, a solo freelancer on client code is the option most likely to look fine for a year and then fall over the day someone asks the classification question. A known freelancer for a two-week bump is still a sensible call. A freelancer who has quietly become a permanent member of the team is a hire you haven't admitted to.
Staff augmentation gives you hands, and you keep the management
The closest BLS category, workers provided by contract firms, was 862,000 people in July 2023, 0.5 percent of total employment.
In the October example, what it costs the agency is the tech lead's calendar. An augmented developer needs tickets written, code reviewed and questions answered in your time zone, and the delivery risk stays with you, because you direct the work. That's a fair trade when the engagement is long and the lead has room. It's a bad one when the lead is the bottleneck you were trying to relieve, which is the usual reason an agency starts looking in the first place. If you'd rather not manage the developers yourself, a dedicated team moves more of that load to the provider.
Outsourcing hands over the project, and the client gets a second voice
Outsourcing suits a build that can stand alone: an internal tool, a separate mobile app, a migration with a frozen spec. The vendor runs its own process and carries the delivery risk inside the scope you agreed.
Agency work rarely holds still that long. When your client changes their mind every week, each change becomes a change request between you and the vendor, and you end up as the translator in the middle, carrying the relationship risk without the control. The contract model decides who pays for those changes, which is what fixed price vs time and materials is really about. And if the vendor touches a California client's customer data, the CCPA contract terms have to reach them too, as section 7051(b) spells out.
A white-label partner: their engineers, your process, your brand
A white-label partner looks like staff augmentation from the inside and like your own team from the outside. Their engineers work in your repos, join your standups and ship under your name, and you mark up their cost to your client. How that markup works, and where it goes wrong, is in our piece on white-label economics. On California classification, a subcontractor firm that sends its own staff fits the business-to-business exemption better than an individual does.
The risk is fit. You only find out whether a partner's engineers write code you'd sign off on after they've written some, so start with a paid pilot task you can judge on its own before you commit a client's deadline to them.
It's the wrong answer more often than partners admit. Skip it when the client contract forbids subcontracting or names the people who must do the work. Skip it when the job needs someone on site every day. Skip it for a spike that lasts two weeks, because onboarding will eat most of it. And if the work sits on a federal small business set-aside, check the SBA 50% rule before you subcontract any of it.
Which one to pick, by the shape of the spike
- A short bump on a stack your team knows, with someone you've used before: a freelancer, set up as a real business if you're in California.
- A long engagement where your tech lead has spare hours to manage: staff augmentation.
- A self-contained build with a stable spec that doesn't need your brand on it: outsourcing.
- Client work under your name, longer than a month, when your leads are already full: a white-label partner, starting with a pilot task.
We sell the fourth option, so weigh this accordingly. In the October example, it's the only one that adds capacity without adding management load to the person who's already stretched. If that matches your week, see how our agency partner arrangement works or tell us the scope. If your spike looks like one of the first three, the posts linked above will get you further than a sales call would.
Sources
- U.S. Bureau of Labor Statistics: Contingent and Alternative Employment Arrangements, July 2023 (released 8 November 2024)
