Published July 21, 2026 · Kiyansh Group
When you bring on contract IT talent, the engagement model decides who carries the taxes, who holds the liability, and who is on the hook if the classification is ever challenged. W-2, corp-to-corp, and 1099 are not interchangeable labels for the same thing. Picking the wrong one is one of the easier ways to turn a routine hire into a tax and legal problem, so it's worth understanding what each actually means.
Talk to us about staffing →On a W-2 contract, the person works for you on a project but is legally employed by the staffing vendor for the duration. The vendor runs payroll, withholds income tax, pays the employer half of FICA, covers unemployment insurance, and carries workers' comp and liability. At year end the contractor gets a W-2 from the vendor, not from you.
This is the cleanest model from a client's risk standpoint. Because the vendor is the legal employer, the classification question is largely settled, and the tax and insurance burden sits with a company that specializes in carrying it. You direct the work; they handle the employment machinery.
The trade-off is cost. The vendor is carrying real employer burden and prices it into the bill rate, so a W-2 rate looks higher than a C2C rate for the same person. What you're buying with that difference is a settled employment relationship and someone else holding the compliance risk.
Corp-to-corp, or C2C, means the contractor operates through their own company, usually an LLC or S-corp, and that company contracts with the vendor or client. There is no employment relationship with the contractor personally. Payment goes business to business, and the contractor's own entity is responsible for its taxes, its insurance, and its benefits.
C2C is common with experienced IT professionals who run themselves as a business, and with H-1B contractors working through their sponsoring employer's company. Because the contractor's entity carries the employer burden, the markup layered on top is thinner, which is why C2C bill rates tend to come in below W-2 rates for equivalent talent.
The catch is that C2C only holds up if the contractor's company is real: properly formed, carrying its own insurance, and genuinely operating as a business. A shell with no coverage and no substance doesn't move the risk off you, it just delays the moment someone asks questions. On any C2C engagement, confirm the entity is legitimate and insured before work starts.
A 1099 engagement is a direct relationship with an individual treated as an independent contractor. No taxes are withheld, no employer FICA is paid on their behalf, and they receive a 1099 form reporting what they were paid. They handle their own taxes and carry their own liability.
The reason 1099 is the trickiest model in IT is that the classification has to match the reality of the work. The IRS and state agencies look at behavioral control, financial control, and the nature of the relationship. If you set the hours, direct the day-to-day, provide the tools, and the person works only for you for months on end, that looks like employment no matter what the paperwork says.
For a contractor genuinely running their own practice, serving multiple clients, and controlling how the work gets done, 1099 can be appropriate. For a full-time embedded developer taking daily direction from your lead, it usually isn't, and treating them as 1099 is where misclassification claims come from.
Misclassification is the headline risk. If a worker is treated as 1099 or thin C2C but functions as an employee, a reclassification brings back employer taxes, unemployment contributions, penalties, and sometimes benefit claims. Agencies weigh the substance of the relationship over the label, so a signed contract calling someone independent does not settle the question on its own.
Co-employment is the quieter one, and it mostly affects W-2 contract arrangements. When a contractor is on the vendor's payroll but takes daily direction from your managers, both companies can be seen as sharing employer responsibilities. It isn't inherently a problem, but it needs to be managed: keep the vendor as the clear employer of record, route HR and pay matters through them, and avoid treating a contractor exactly like a badged employee on things like reviews and internal benefits.
The practical defense is consistency. The engagement model on paper should match how the work actually runs day to day. When those two drift apart is when the exposure builds.
Choose W-2 when you want the simplest risk profile and the contractor doesn't have their own company, or when the engagement is long, embedded, and directed by your team. You pay a bit more in the rate and get a settled employment relationship in return.
Choose C2C when you're working with an established independent professional or an H-1B contractor through a sponsoring employer, and their entity is real and insured. It's efficient and cost-effective for talent that genuinely operates as a business.
Reserve 1099 for true independents who serve multiple clients and control their own work. If any part of that description doesn't fit, treat it as a signal to move to W-2 rather than force the classification. A good staffing partner will steer you toward the model that matches the reality of the role instead of the one that looks cheapest on the invoice.
From a client's risk standpoint, W-2 is usually the cleanest because the vendor is the legal employer and carries the tax and insurance burden. C2C is fine when the contractor's company is real and insured. 1099 is only safe when the work genuinely fits independent-contractor rules.
No. H-1B status requires employment through a sponsoring employer, so those contractors come through C2C via that employer's company, not as 1099 independents. Trying to place an H-1B worker as 1099 is both an immigration and a classification problem.
Agencies look at how much control you have over the work: setting hours, directing daily tasks, providing tools, and an ongoing exclusive relationship all point toward employment. If the day-to-day looks like employment, the label on the contract won't override it.
Not sure whether a role should be W-2, C2C, or 1099? Kiyansh will match the engagement model to how the work actually runs, so the classification holds up later.
Start a conversation →