The Enterprise Freelance Playbook
Everything you need to know about enterprise freelancing, whether you're a company trying to build a freelance program that actually works, or a freelancer building toward bigger clients.
Where does your freelance program actually stand?
Most enterprise teams manage freelancers the way they manage everything else, by solving problems as they come up. That works until it doesn't. Each section below starts with a question. Find the description that sounds most like your situation. The guidance that follows is specific to where you are, not where we think you should be.
You have a fast track, either a pre‑approved vendor relationship, a very streamlined internal process, or a small enough roster that procurement knows the drill. This is genuinely uncommon at enterprise scale.
Manageable, but you're probably absorbing delays into project timelines without naming it. The friction exists, it's just become normal.
The most common situation for enterprise creative and marketing teams. Each freelancer is a new vendor record, a new W-9, a new contract, a new approval chain. The system wasn't built for this use case.
Usually means onboarding speed depends on who's available in procurement that week, whether the freelancer has worked with you before, or which team is making the request. Inconsistency is its own kind of friction.
The root cause of slow onboarding is almost always the same: your procurement system requires a new approved vendor record for each freelancer, and that process takes time regardless of how urgent the project is. The fix is either streamlining that internal process, which requires procurement buy in and ongoing maintenance, or eliminating the per freelancer setup entirely by routing all freelance work through a single pre‑approved vendor. Neither option is instant. But if two week onboarding is a pattern rather than an exception, the cost is real: in delayed projects, in defaulting to whoever is already set up rather than whoever is best, and in the signal it sends to freelancers about what it's like to work with you.
Basil becomes a single pre‑approved vendor in your procurement system. Every freelancer after that onboards through Basil, same day, without a new vendor record. Worth evaluating if onboarding delay is a recurring problem. Not necessary if your current process is working.
Why the per freelancer vendor onboarding process is the root cause of slow project starts, and what the structural alternatives look like.
Read the article →
Your bench is built. The challenge isn't finding talent, it's the infrastructure that makes working with your existing people fast, compliant, and easy to manage. A talent marketplace won't help you. Operations infrastructure will.
The most common situation. Your existing relationships carry most of the weight, but you occasionally need to find someone new. The infrastructure question matters more than the sourcing question for teams in this position.
The agency is solving a real procurement problem, they're an approved vendor, payments flow cleanly. The question worth asking annually: how much of the markup is for talent they actually found versus talent you brought to them? Those are different value propositions at very different price points.
Makes sense for one off projects or specialized skills you rarely need. The compliance gap worth knowing: platforms cover payment compliance for talent sourced through them. Your existing freelancers, the ones you've built relationships with outside the platform, aren't covered.
Most enterprise in house creative and marketing teams overestimate their sourcing problem and underestimate their operations problem. Before evaluating any platform or service, the more useful question is: of the freelancers we hired in the last twelve months, what percentage were people we already knew? For most teams, the answer is 70 to 80 percent or higher. That means the primary value driver isn't who finds the talent, it's who handles the infrastructure around talent you've already found.
Most Basil clients bring their own freelancers. Sourcing is available through our referral network if you need it, but it's not the core value for most teams. If you're primarily working with people you already know, the operations layer is what matters.
The thing to periodically verify: that your current process covers state level 1099 obligations, not just federal filing. About 30 states have separate requirements, and most teams assume federal filing covers them. It often doesn't.
The scramble usually means records aren't being maintained throughout the year, someone is reconstructing payment history in December instead of tracking it as it happens. Fixable with the right system but requires changing a habit, not just trying harder at year end.
This is more common than anyone admits. Freelancer compliance tends to fall between teams, not quite HR, not quite finance, not quite legal. If nobody owns it clearly, it's probably not being handled completely.
Correct for payments that flow through the agency. Worth confirming: freelancers you pay directly, even occasionally, even small amounts, are still your compliance responsibility. The agency coverage ends at the edge of what they actually process.
The compliance issue with the most legal exposure isn't 1099 filing, it's worker classification. Between 10 and 30 percent of US employers are currently misclassifying workers, often without knowing it. The IRS test looks at behavioral control (are you directing how the work gets done or just what gets delivered?) and financial control (does the freelancer work for multiple clients?). A well written scope of work focused on deliverables rather than hours and process is one of your clearest signals of a legitimate contractor relationship, and one of the most common gaps in how enterprise teams document freelance engagements. The administrative compliance layer, W-9s, 1099s, state filings, is the visible part. Classification is the part that creates real exposure.
Basil handles domestic 1099 compliance as the payor of record, W-9 collection, TIN verification, SOW generation, and 1099-NEC issuance at year end. Basil also manages international compliance for select countries. For expansive international compliance, global EOR platforms might be the better fit. If compliance ownership is unclear on your team, having a payor of record removes the ambiguity entirely.
A detailed breakdown of US freelancer compliance, from worker classification tests by state to 1099 filing obligations and Freelance Worker Protection Acts.
Read the compliance guide →
You're ahead of most teams. Worth reviewing: whether your SOWs are focused on deliverables (what gets produced) rather than process (how and when the freelancer works). The distinction matters for worker classification.
Small projects are exactly where disputes happen, because the stakes feel low enough to skip the paperwork but high enough to create frustration when expectations diverge. Inconsistent coverage is almost as risky as no coverage.
A SOW that doesn't define revision rounds, definition of complete, and what's out of scope protects nobody. It establishes that an agreement existed without specifying what was actually agreed to.
Common and usually fine until it isn't. The problem surfaces when scope changes, when a freelancer invoices for work you didn't expect, or when an audit asks for documentation of contractor relationships.
The element most teams omit entirely is the definition of complete, and that's the one that causes the most friction mid project. Without it, "done" means something different to the client and the freelancer, and the conversation about whether revisions are in scope happens at the worst possible time. The other thing SOW templates do that most teams don't think about: a deliverable focused scope, one that specifies what gets produced, not how and when the freelancer works, is one of your clearest documentation signals of a legitimate independent contractor relationship. Your SOW is simultaneously your project protection and your classification protection. A weak one leaves both exposed.
Basil generates a digital SOW for every project automatically. Both parties sign digitally. A PDF is archived. A PO opens in your procurement system. If inconsistent SOW coverage is a pattern on your team, a platform that generates them automatically removes the decision of whether to do it.
What to look for in a vendor of record platform, and what features actually change how your team operates versus which ones just add complexity.
VOR features guide →
This is a real competitive advantage, even if it doesn't feel like one from the inside. Freelancers who get paid predictably prioritize the clients who pay predictably. You're probably getting better availability and faster responses to urgent requests than you realize.
"Occasionally late" looks different from your side than from the freelancer's. Independent workers don't have the same financial buffer that full time employees have. An invoice that's two weeks late isn't an inconvenience for them, it's a cash flow problem.
If freelancers are bringing this up to you, it's already affecting the relationship. The ones who don't bring it up have quietly moved you down their priority list. According to the Freelancers Union, 71% of independent professionals experience late payments, and the average freelancer is carrying $6,000 in unpaid invoices at any given time.
Worth finding out. The gap between how your AP team thinks payments are going and how your freelancers experience them is often significant, and it's affecting your relationships with people your team depends on.
Payment reliability is a talent strategy, not just a finance function. The freelancers who are most in demand have options. They're making decisions about which clients to prioritize based on the full picture of what it's like to work with you, and payment experience is one of the clearest signals in that picture. The root cause of late payments at enterprise companies is almost never bad intention. It's structural: your AP system processes freelancers the same way it processes any other vendor, subject to the same cycles and delays. Consolidating freelance payments under a single vendor relationship means your AP cycle processes one invoice, from the VOR, on its normal schedule, and the VOR handles disbursement to the individual freelancer on a separate, faster timeline.
Basil is the payor of record. Freelancers invoice Basil. Basil invoices you. Freelancers get paid on NET 15 to 30 terms, within 3 to 5 business days of processing, independent of where your AP cycle is that week. If payment reliability is a known issue, this is the structural fix rather than a process improvement on top of a broken process.
What freelancers actually prioritize when choosing which clients to work with, and why payment reliability is almost always the answer.
Read the article →Some of it might not apply at all.
