Shared payer-payee graphs for contractors
Anthony Mironov, CEO of Wingspan, on why 1099s are eating payroll
This reveals that contractor software wins by becoming the system of record for relationships, not just for payments. A single contractor may bill several clients, carry one reusable profile, and need insurance, tax forms, onboarding, and support to move with them. That breaks the core assumption inside classic payroll systems, where one company owns one worker record, and is why Wingspan is built around a shared payer payee graph instead of a single employer database.
-
The fragmentation is operational, not just market structure. Contractors often stitch together five to seven tools for banking, invoicing, taxes, and insurance, while companies fall back to banks, Bill Pay, or QuickBooks until contractor count reaches roughly 50 to 100 and reconciliation, compliance, and classification work start to fail.
-
The best comparison is not employee payroll, but a commerce network. Wingspan describes the product as needing to look more like Shopify, because the hard part is managing many recurring buyer seller relationships with reusable identity and compliance data, not running one employer centered HR stack.
-
This is why incumbent HCM and payroll vendors either bolt on contractor tools or partner. Gusto is still centered on SMB employer payroll, while Rippling bundles contractor payroll inside a broader workforce suite. Wingspan instead targets high contractor density accounts and embeds into platforms like Insperity that need native 1099 coverage without rebuilding their architecture.
The market is heading toward platforms that can carry a contractor’s identity, payment rails, and financial products across every client relationship. As more work shifts to blended W-2 and 1099 teams, the winners will be the systems that make contractor onboarding feel instant, keep money moving inside the network, and turn fragmented contractor admin into one portable profile.