You hired six remote SDRs, gave them company email addresses, trained them on your pitch, required CRM updates, and put every rep on the same daily standup. Your payroll vendor calls them “1099 contractors,” so you move on to pipeline.
That label may survive bookkeeping. It may not survive an audit.
Contractor vs employee classification is decided by the working relationship, not by the title in your software or the agreement sitting in your shared drive. The U.S. Department of Labor says employees receive minimum wage and overtime protections under the Fair Labor Standards Act, while independent contractors generally don't because they're considered to be in business for themselves. Its updated rule took effect on March 11, 2024, and returned attention to the economic realities of the relationship. (U.S. Department of Labor guidance)
SDR and BDR teams create a particularly awkward collision. Founders want flexible, cross-border talent. Revenue leaders want consistent hours, scripts, activity targets, call reviews, and clean reporting. Those management habits make sense operationally, but they can also make a “contractor” look exactly like an employee.
| Working pattern | Likely classification concern | Founder takeaway |
|---|---|---|
| Fixed schedule, company CRM, mandatory meetings | High behavioral control | Treat the role as employment unless counsel says otherwise |
| Flexible hours, own tools, project deliverables | Stronger contractor indicators | Document the independence in practice, not just on paper |
| Commission-only work with company scripts and lead lists | Compensation alone doesn't decide status | Control and integration still matter |
| Cross-border rep working through a local entity | Local employment rules may apply | Review the worker's country and state before onboarding |
A founder rushing to build a remote SDR team can make one expensive mistake before the first pipeline review: accept a payroll vendor's “1099” label and assume the classification problem is solved. The label changes nothing if the company still trains, schedules, supervises, measures, and manages the reps like employees.
The contract may say contractor. The accounting system may show contractor payments. An agency, tax authority, or court will examine the relationship in practice. For an SDR team, that means looking at call blocks, required meetings, manager feedback, CRM activity, scripts, and whether the rep is embedded in the company's revenue process.
The historical risk is well established. A Government Accountability Office report cited IRS estimates that, in 1984, about 756,000 of 5.15 million employers, roughly 15%, had misclassified about 3.4 million workers as independent contractors. The GAO connected classification with tax withholding, labor protections, and legal exposure, rather than treating it as a payroll label. (GAO discussion cited by the Department of Labor)
A genuinely independent business usually controls how it delivers a result. Remote SDR and BDR teams often operate under the opposite model. The company sets prospecting hours, assigns lead lists, requires an Outreach or Salesloft sequence, mandates Salesforce updates, runs Zoom standups, reviews recordings, supplies talk tracks, and scores activity against a quota.
That system may be the right way to create predictable pipeline. It also creates a dense record of behavioral control.
The uncomfortable test: If the rep looks, acts, and is managed like staff, the contractor label will not make the relationship independent.
Paperwork loses its force when daily operations contradict it. A contract can promise that the rep chooses the method. The calendar can require attendance. The agreement can offer flexibility while Slack records a manager asking why yesterday's call count was low. Auditors and courts will focus on those operating facts.
The Department of Labor generally distinguishes employees, who receive wage and hour protections, from independent contractors, who are generally treated as operating their own businesses. The IRS examines behavioral control, financial control, and the relationship between the parties. (IRS worker classification framework)
Onboarding therefore requires more than selecting a status in a vendor portal. Review what the rep does, who controls the work, who provides the operating setup, whether the engagement continues indefinitely, and whether the rep performs a central company function.
An SDR selling your product to your ideal customer profile is performing a core revenue function. That fact deserves a serious classification review before the team scales. Clever naming will not persuade an auditor, and it will not change how the team works.
A remote SDR can look like a contractor on paper while operating like an employee every workday. The classification question turns on the operating model, not the label in the agreement. If your manager assigns accounts, sets the cadence, reviews calls, and tracks activity, those facts deserve more attention than the contractor checkbox.
The IRS organizes its review into three buckets:
The IRS explanation of the three control categories describes the same framework. Treat it as an operating review, not a paperwork exercise. A remote SDR using your systems and following your playbook can create control evidence before the first commission is paid.
The Department of Labor's 2024 FLSA rule examines six economic-realities factors:
The analysis weighs the facts together. One favorable contract clause does not erase an indefinite role on the core sales team. The DOL rulemaking materials explain the rule and its factor-based approach.
| Factor | IRS Common-Law Test | DOL Economic Realities Test | SDR Red Flag |
|---|---|---|---|
| Control | Behavioral control over methods and schedule | Nature and degree of control | Fixed hours, scripts, daily activity management |
| Money | Financial control, expenses, tools, payment | Opportunity for profit or loss and investments | Company supplies the operating stack |
| Relationship | Benefits, contracts, ongoing relationship | Permanence and integration | Indefinite role on the core sales team |
| Business role | Type of relationship | Integral work factor | Rep directly generates pipeline for the company |
| Expertise | Usually part of behavioral analysis | Skill and initiative | Training and playbooks supplied by the company |
A sales consultancy with its own clients, systems, pricing, and methods may fit contractor treatment more comfortably. A remote SDR assigned your accounts, trained on your messaging, and measured against your pipeline usually presents problems under both frameworks.
For a practical explanation of the ABC concept, employee classification as easy as ABC offers useful context. It does not replace advice on your facts, but it shows why real-world control can outweigh the label.
My investor-deck test: Describe the rep's day as you would describe it to an investor. If you say, “We train them, assign the accounts, manage their schedule, inspect their activity, and review their calls,” you have already described the relationship an examiner will analyze.
Federal analysis and state analysis can point in different directions. The IRS uses its common-law control framework, while the Department of Labor applies the economic realities approach under the FLSA. States may add tests that are less forgiving, and California's ABC test is the example every distributed sales team should understand.
California presumes the worker is an employee unless the hiring entity proves all three prongs:
Miss one prong and the worker is treated as an employee under that test. California may also apply the Borello framework in situations where the ABC test doesn't govern, so founders shouldn't assume one analysis covers every engagement.
A contractor who builds their own prospect list, chooses their hours, uses their own systems, serves multiple clients, and sells through an independently developed methodology has a stronger argument for independence.
Now change the facts. The rep uses your CRM, follows your sequence, attends daily standups, pitches your ICP, receives your playbook, and is reviewed by a sales manager. Under California's ABC test, the arrangement faces serious trouble. The work is close to your usual course of business, and the company appears to control the manner of performance.
Other states add their own complications. New Jersey uses an ABC-style analysis. Massachusetts has a strict ABC predecessor. Pennsylvania is known for a demanding reading of worker status, and newer state statutes continue to codify enforcement tools and penalties. The exact result depends on the worker's location, the employing entity, the work performed, and the applicable statute.
A distributed team can therefore produce a split result. The same operating model might be treated differently in Texas and California, with the stricter jurisdiction shaping the practical risk. Founders hiring nationally need a state-by-state classification matrix, not one universal contractor policy. For a practical review of legal red flags for founders, use the checklist alongside counsel familiar with the worker's location.
The cleanest way to understand classification is to remove the labels and inspect the day.
Maya is a full-time remote SDR in Texas. She works set hours, uses company tools, receives a base salary plus quota, joins sales meetings, and reports to a manager. The company trains her on messaging, assigns accounts, and expects her to follow the team's operating rhythm.
Maya is a W-2 employee under the IRS control framework and the DOL economic realities analysis. The company controls the work, the relationship is ongoing, the role is central to revenue generation, and Maya has little independent opportunity to create profit or loss through her own business decisions.
Devon is a part-time BDR who works evenings and gets paid only on commission. That sounds contractor-friendly until you inspect the rest of the arrangement. Management supplies the lead lists and scripts, reviews the pipeline, monitors outcomes, and keeps Devon in the sales process over time.
Flexible hours and commission pay don't settle the issue. Devon's investment is limited, the company supplies key inputs, management controls the method, and the work is integrated into the sales function. He likely fails contractor status despite working fewer hours and carrying no base salary.
The danger for founders lies in compensation design. Commission is not a magic classification shield. A worker can be economically dependent on a company even when payment depends on meetings or closed revenue.
Rica is a contractor in the Philippines. She sets her own hours, works from her own laptop, serves multiple clients, and receives payment per qualified meeting. Those facts support independence under many U.S. classification factors.
They don't answer the local-law question. Philippine Department of Labor standards may still treat the relationship as local employment depending on the actual arrangement, economic dependence, control, and statutory requirements. Cross-border hiring creates two analyses, not one. The U.S. company's preferred label can't erase the worker's local protections.
Cross-border rule: Classify the relationship where the work happens, then check the hiring entity, tax, benefits, and termination rules before the first login.
The lesson from Maya, Devon, and Rica is simple. Classification is fact-driven. Hours, tools, supervision, payment, client portfolio, integration, and local law matter more than whether the agreement says “contractor” in bold type.
Misclassification does not arrive as one neat invoice. For a remote SDR or BDR team, exposure can spread across payroll taxes, wage claims, unemployment programs, workers' compensation, benefits, and local employment obligations.
Federal reclassification can trigger minimum-wage and overtime claims under the FLSA, along with tax withholding and employment-tax obligations that never appeared in the contractor ledger. Classification also affects labor protections, tax treatment, and legal risk, as noted earlier.
The IRS-related penalty summary lists potential unintentional penalties including $50 per missing W-2, roughly 1.5% to 3% of wages, 40% of unpaid employee FICA, and 100% of the employer's matching FICA. Willful cases may reach 20% of wages, 100% of FICA on both sides, and criminal penalties of up to $1,000 per worker and one year in jail. (Summary of IRS-related misclassification penalties)
| Layer | What's owed | Typical range |
|---|---|---|
| Federal wage and hour | Unpaid minimum wage or overtime where applicable | Depends on the facts and covered work |
| Federal tax reporting | Missing forms, wage-related penalties, unpaid employee FICA, and employer matching FICA | $50 per missing W-2, roughly 1.5% to 3% of wages, 40% of unpaid employee FICA, and 100% of employer matching FICA for described unintentional penalties |
| Willful federal conduct | Higher wage and FICA penalties, with possible criminal exposure | Up to 20% of wages, 100% of FICA on both sides, and up to $1,000 per worker plus one year in jail |
| State programs | Unemployment insurance, disability obligations, workers' compensation premiums, and related assessments | Varies by state and lookback period |
| International employment | Social contributions, local benefits, severance, tax, and immigration obligations | Varies by country and worker facts |
The practical problem is scope. An inquiry that starts with one SDR can expand to the whole team when every rep shares the same contract, manager, CRM workflow, working hours, and pay design. A remote setup does not make that pattern less visible. It often makes the repeated operating model easier to document.
Do not budget around the cheapest label. Budget around the management system you run. If your “contractors” follow manager-set schedules, use company tools, attend recurring pipeline meetings, and carry ongoing quota coverage, the penalty stack is only one audit away from becoming real. Saving payroll taxes is a poor trade for an arrangement that was employee-shaped from day one.
Contractor status can be legitimate. It just needs to describe a real independent business, not a full-time SDR wearing a contractor costume.
A credible contractor relationship usually has several of these traits:
A fractional outbound consultant building a cold email playbook during a defined pilot can fit this model. So can a closing BDR who handles overflow demos during a product-launch spike, controls their availability, invoices for agreed services, and works with multiple clients.
The familiar trap is a full-time quota-carrying SDR who works your hours, follows your process, uses your systems, and attends your meetings. Calling that person a contractor because the budget looks friendlier isn't strategic. It's deferred payroll, deferred benefits, and deferred legal exposure.
Use contractor status for an independent business, not for an employee you hope won't ask for employee treatment.
Cross-border teams add payment complexity. If you're considering digital-asset compensation or international contractor payments, a crypto payroll guide for web3 firms can help you think through payment mechanics, documentation, and operational risks. It doesn't determine classification, but it can prevent a payment workaround from becoming another compliance headache.
Before choosing the cheaper-looking structure, compare the full employment cost, benefits, taxes, insurance, and administration. hireSDR.com's cost analysis gives founders a practical way to model that decision instead of staring only at the contractor invoice.
Start with the facts, not the preferred outcome. A founder-ready review should move in this order:
A recruiting marketplace can source and screen SDR and BDR candidates, but sourcing alone doesn't solve classification. hireSDR.io offers SDR-trained talent, Contractor of Record and Employer of Record options, built-in payroll and compliance support, and jurisdiction-specific contract templates for cross-border engagements. That setup can absorb much of the withholding, payroll, benefits, and documentation workload, while the founder still owns the final business decision about how the worker will be managed.
The management model must match the chosen structure. No provider can turn a tightly supervised employee into an independent contractor by changing the invoice recipient. You still need to review schedules, scripts, KPIs, manager check-ins, tool ownership, and the role's place in your revenue operation.
For teams managing distributed workers, managing global HR records is part of the operating discipline. Keep contracts, classification analysis, payment records, location details, and material changes in one controlled system. Future-you will appreciate the boring paperwork when present-you gets an audit letter.
hireSDR.com helps founders source SDR and BDR talent across multiple countries and supports EOR and Contractor of Record structures that fit the actual engagement. Visit hireSDR.com to compare compliant hiring options before you put another remote rep into a contractor-shaped role.
Most appointment setting programs convert only 1–2% of outbound touches into booked meetings. If a vendor prices itself around meetings without qualification gates, you're buying...
Your SDR interviews are probably selecting for polish, not production. That is how teams hire reps who sound sharp in a panel, then freeze when...
Most companies treat the new hire onboarding process like a polite welcome ritual. That's the mistake. A remote SDR doesn't become useful because someone walked...
Tell us who you need. We'll have pre-vetted candidates in your inbox within 72 hours. No commitment until you hire.