The Build, Buy, or Partner Framework for Embedded Payroll
Payroll shows up on your roadmap before you are ready for it. A restaurant operator asks why they export hours from your product and retype them somewhere else. A clinic administrator asks whether you can just handle the paychecks.
We already ran the ARPU, lifetime value, and payback math in an earlier piece. The numbers work. This is the harder question: how you actually launch.
Start with the part most roadmaps get backwards. No customer ever renewed because a Form 941 got filed correctly. They renew because scheduling, hours, and pay live in one place and nobody retypes anything. Simply put, payroll compliance is table stakes nobody will ever compliment you on. The workflow around it is where you win.
That does not pick your path. It tells you what you are solving for: handling the compliance layer at the lowest cost in engineering attention. There are three ways.
Build
Building means owning the engine end to end: calculation, withholding, filing, remittance, funding, and the compliance operation that keeps it current.
The calculation is the easy part. A competent team ships a working gross-to-net calculator in a quarter.
Everything downstream is the problem. Every state runs its own withholding and unemployment insurance regime, each with separate registration, deposit schedules, and forms. Below that sit local taxes: city, county, school district. Pennsylvania alone has thousands of jurisdictions levying earned income taxes under Act 32, where the rate depends on both work and home location, resolved by geographic boundary rather than mailing address.
None of this is exotic. Payroll companies handle it every day and handle it well. But they handle it with dedicated compliance staff, a filing calendar, standing agency relationships, and someone whose job is to notice when a jurisdiction changes a rule. That is an organization, not a feature.
Square is the reference case. Square Payroll launched June 2015, in California only. It reached all 50 states and DC in October 2018. Three and a half years, at a company with a large engineering organization and the balance sheet to fund it. In 2015 there was no API like Rollfi to call, which is no longer true.
Build when the table stakes are the product. That is true for fewer platforms than believe it.
Buy
Two versions, and they are not close.
Reselling. You route customers to an existing provider. Fastest path to yes, almost no engineering. But referral fees are a fraction of what the provider earns, and you have handed off a relationship that touches your customer's business every two weeks. Your product becomes where they schedule shifts. The provider becomes where they run their business. Reasonable holding pattern, poor destination.
Acquiring. Toast is the reference case. Toast launched Payroll & Team Management in May 2019, then acquired StratEx that July, its first acquisition, price undisclosed. It had raised $250 million at a $2.7 billion valuation three months earlier.
The detail worth sitting with: StratEx sold HR software and consulting services. Toast did not buy a codebase. It bought an operating business, including the people delivering labor law compliance support to restaurant operators. An acquisition hands you a services organization, a support queue, a filing calendar, and state registrations someone maintains forever.
You do not buy your way out of the table stakes. You hire them.
Partner
Rent the table stakes, keep the workflow.
Your provider handles calculation, filing, remittance, and compliance maintenance through an API. You keep the interface, the customer relationship, the pricing, the workflow, and the accuracy of what goes in. You hand off multi-jurisdiction tax calculation, filing and remittance, agency correspondence, money movement and its licensing, and regulatory monitoring.
That middle one is easy to skim past and it is the one you will feel. Notices arrive. An agency questions a registration or misapplies a deposit. Someone has to work it to resolution, on the phone with a state revenue department instead of shipping product. We do that, directly with the IRS and the relevant state authorities.
What we will not tell you is that it all disappears. If a worker is classified wrong or a work address is stale, the filing built on that data is wrong too. We can amend returns, correct filings, and argue a case where there is one. We cannot turn bad data into good data. A provider owns the machinery. You and your customer own the inputs. Anyone claiming the whole category of risk goes away is selling you something.
The dependency is real, so diligence matters. Ask how a provider's financials are verifiable: we are a division of Priority Technology Holdings (Nasdaq: PRTH), so ours are in public filings. Ask about scope, because payroll rarely stays payroll. We cover payroll and benefits, and Priority's infrastructure extends to banking, payments, and wallets.
Shopify is the reference case, though not in payroll. Shopify Payments is powered by Stripe. Merchants set it up in the Shopify admin, see Shopify branding, get Shopify support, and pay Shopify. No badge at checkout, no second login. Shopify built the best merchant experience on someone else's rails and kept the customer, the interface, and the economics.
The four questions that decide it
Is payroll your product or your feature?
If a customer would buy payroll from you without buying anything else, build or acquire. Otherwise partner. Most platforms are in the second category and describe themselves as the first.How much compliance operation do you want to run?
Ask who inside your company owns the fix when a filing error hits two thousand customers in one quarter. If nobody comes to mind, that is your answer.What margin do you need, and over what horizon?
Referral pays this quarter and caps forever. Building pays best long-run and costs years first. Partnering sits between the two. The math is here.Where does your engineering leverage go furthest?
Every engineer working on state unemployment insurance registration is not working on what your customers chose you for. Compliance maintenance has no finish line.
Payroll is one of the few features where customers forgive a mediocre interface and never forgive a wrong number. That is why the table stakes deserve to be taken seriously, and why they are the wrong place to spend your best people. Decide who carries them, then go win on the part that shows.
Considering the partner path?
RollFi provides embedded and white-label payroll and benefits infrastructure. You own the experience, the customer, and the margin. We handle calculation, filing, remittance, and compliance. As a division of Priority Technology Holdings (Nasdaq: PRTH), we can extend into embedded banking, payments, and wallets when your customers start asking for those too.
Bring the hard questions. The ones above are the right ones.
About Rollfi
Rollfi empowers banks, vertical SaaS platforms, accounting firms, and fintechs to add payroll and benefits to their offerings through white-label solutions and robust APIs. With Rollfi's infrastructure, platforms can unlock new revenue, boost customer retention, and gain valuable payroll data insights. Fast deployment and full regulatory coverage make Rollfi the easiest way to turn your platform into a one-stop shop for essential business services.
Payroll shows up on your roadmap before you are ready for it. A restaurant operator asks why they export hours from your product and retype them somewhere else. A clinic administrator asks whether you can just handle the paychecks.
We already ran the ARPU, lifetime value, and payback math in an earlier piece. The numbers work. This is the harder question: how you actually launch.
Start with the part most roadmaps get backwards. No customer ever renewed because a Form 941 got filed correctly. They renew because scheduling, hours, and pay live in one place and nobody retypes anything. Simply put, payroll compliance is table stakes nobody will ever compliment you on. The workflow around it is where you win.
That does not pick your path. It tells you what you are solving for: handling the compliance layer at the lowest cost in engineering attention. There are three ways.
Build
Building means owning the engine end to end: calculation, withholding, filing, remittance, funding, and the compliance operation that keeps it current.
The calculation is the easy part. A competent team ships a working gross-to-net calculator in a quarter.
Everything downstream is the problem. Every state runs its own withholding and unemployment insurance regime, each with separate registration, deposit schedules, and forms. Below that sit local taxes: city, county, school district. Pennsylvania alone has thousands of jurisdictions levying earned income taxes under Act 32, where the rate depends on both work and home location, resolved by geographic boundary rather than mailing address.
None of this is exotic. Payroll companies handle it every day and handle it well. But they handle it with dedicated compliance staff, a filing calendar, standing agency relationships, and someone whose job is to notice when a jurisdiction changes a rule. That is an organization, not a feature.
Square is the reference case. Square Payroll launched June 2015, in California only. It reached all 50 states and DC in October 2018. Three and a half years, at a company with a large engineering organization and the balance sheet to fund it. In 2015 there was no API like Rollfi to call, which is no longer true.
Build when the table stakes are the product. That is true for fewer platforms than believe it.
Buy
Two versions, and they are not close.
Reselling. You route customers to an existing provider. Fastest path to yes, almost no engineering. But referral fees are a fraction of what the provider earns, and you have handed off a relationship that touches your customer's business every two weeks. Your product becomes where they schedule shifts. The provider becomes where they run their business. Reasonable holding pattern, poor destination.
Acquiring. Toast is the reference case. Toast launched Payroll & Team Management in May 2019, then acquired StratEx that July, its first acquisition, price undisclosed. It had raised $250 million at a $2.7 billion valuation three months earlier.
The detail worth sitting with: StratEx sold HR software and consulting services. Toast did not buy a codebase. It bought an operating business, including the people delivering labor law compliance support to restaurant operators. An acquisition hands you a services organization, a support queue, a filing calendar, and state registrations someone maintains forever.
You do not buy your way out of the table stakes. You hire them.
Partner
Rent the table stakes, keep the workflow.
Your provider handles calculation, filing, remittance, and compliance maintenance through an API. You keep the interface, the customer relationship, the pricing, the workflow, and the accuracy of what goes in. You hand off multi-jurisdiction tax calculation, filing and remittance, agency correspondence, money movement and its licensing, and regulatory monitoring.
That middle one is easy to skim past and it is the one you will feel. Notices arrive. An agency questions a registration or misapplies a deposit. Someone has to work it to resolution, on the phone with a state revenue department instead of shipping product. We do that, directly with the IRS and the relevant state authorities.
What we will not tell you is that it all disappears. If a worker is classified wrong or a work address is stale, the filing built on that data is wrong too. We can amend returns, correct filings, and argue a case where there is one. We cannot turn bad data into good data. A provider owns the machinery. You and your customer own the inputs. Anyone claiming the whole category of risk goes away is selling you something.
The dependency is real, so diligence matters. Ask how a provider's financials are verifiable: we are a division of Priority Technology Holdings (Nasdaq: PRTH), so ours are in public filings. Ask about scope, because payroll rarely stays payroll. We cover payroll and benefits, and Priority's infrastructure extends to banking, payments, and wallets.
Shopify is the reference case, though not in payroll. Shopify Payments is powered by Stripe. Merchants set it up in the Shopify admin, see Shopify branding, get Shopify support, and pay Shopify. No badge at checkout, no second login. Shopify built the best merchant experience on someone else's rails and kept the customer, the interface, and the economics.
The four questions that decide it
Is payroll your product or your feature?
If a customer would buy payroll from you without buying anything else, build or acquire. Otherwise partner. Most platforms are in the second category and describe themselves as the first.How much compliance operation do you want to run?
Ask who inside your company owns the fix when a filing error hits two thousand customers in one quarter. If nobody comes to mind, that is your answer.What margin do you need, and over what horizon?
Referral pays this quarter and caps forever. Building pays best long-run and costs years first. Partnering sits between the two. The math is here.Where does your engineering leverage go furthest?
Every engineer working on state unemployment insurance registration is not working on what your customers chose you for. Compliance maintenance has no finish line.
Payroll is one of the few features where customers forgive a mediocre interface and never forgive a wrong number. That is why the table stakes deserve to be taken seriously, and why they are the wrong place to spend your best people. Decide who carries them, then go win on the part that shows.
Considering the partner path?
RollFi provides embedded and white-label payroll and benefits infrastructure. You own the experience, the customer, and the margin. We handle calculation, filing, remittance, and compliance. As a division of Priority Technology Holdings (Nasdaq: PRTH), we can extend into embedded banking, payments, and wallets when your customers start asking for those too.
Bring the hard questions. The ones above are the right ones.
About Rollfi
Rollfi empowers banks, vertical SaaS platforms, accounting firms, and fintechs to add payroll and benefits to their offerings through white-label solutions and robust APIs. With Rollfi's infrastructure, platforms can unlock new revenue, boost customer retention, and gain valuable payroll data insights. Fast deployment and full regulatory coverage make Rollfi the easiest way to turn your platform into a one-stop shop for essential business services.
Payroll shows up on your roadmap before you are ready for it. A restaurant operator asks why they export hours from your product and retype them somewhere else. A clinic administrator asks whether you can just handle the paychecks.
We already ran the ARPU, lifetime value, and payback math in an earlier piece. The numbers work. This is the harder question: how you actually launch.
Start with the part most roadmaps get backwards. No customer ever renewed because a Form 941 got filed correctly. They renew because scheduling, hours, and pay live in one place and nobody retypes anything. Simply put, payroll compliance is table stakes nobody will ever compliment you on. The workflow around it is where you win.
That does not pick your path. It tells you what you are solving for: handling the compliance layer at the lowest cost in engineering attention. There are three ways.
Build
Building means owning the engine end to end: calculation, withholding, filing, remittance, funding, and the compliance operation that keeps it current.
The calculation is the easy part. A competent team ships a working gross-to-net calculator in a quarter.
Everything downstream is the problem. Every state runs its own withholding and unemployment insurance regime, each with separate registration, deposit schedules, and forms. Below that sit local taxes: city, county, school district. Pennsylvania alone has thousands of jurisdictions levying earned income taxes under Act 32, where the rate depends on both work and home location, resolved by geographic boundary rather than mailing address.
None of this is exotic. Payroll companies handle it every day and handle it well. But they handle it with dedicated compliance staff, a filing calendar, standing agency relationships, and someone whose job is to notice when a jurisdiction changes a rule. That is an organization, not a feature.
Square is the reference case. Square Payroll launched June 2015, in California only. It reached all 50 states and DC in October 2018. Three and a half years, at a company with a large engineering organization and the balance sheet to fund it. In 2015 there was no API like Rollfi to call, which is no longer true.
Build when the table stakes are the product. That is true for fewer platforms than believe it.
Buy
Two versions, and they are not close.
Reselling. You route customers to an existing provider. Fastest path to yes, almost no engineering. But referral fees are a fraction of what the provider earns, and you have handed off a relationship that touches your customer's business every two weeks. Your product becomes where they schedule shifts. The provider becomes where they run their business. Reasonable holding pattern, poor destination.
Acquiring. Toast is the reference case. Toast launched Payroll & Team Management in May 2019, then acquired StratEx that July, its first acquisition, price undisclosed. It had raised $250 million at a $2.7 billion valuation three months earlier.
The detail worth sitting with: StratEx sold HR software and consulting services. Toast did not buy a codebase. It bought an operating business, including the people delivering labor law compliance support to restaurant operators. An acquisition hands you a services organization, a support queue, a filing calendar, and state registrations someone maintains forever.
You do not buy your way out of the table stakes. You hire them.
Partner
Rent the table stakes, keep the workflow.
Your provider handles calculation, filing, remittance, and compliance maintenance through an API. You keep the interface, the customer relationship, the pricing, the workflow, and the accuracy of what goes in. You hand off multi-jurisdiction tax calculation, filing and remittance, agency correspondence, money movement and its licensing, and regulatory monitoring.
That middle one is easy to skim past and it is the one you will feel. Notices arrive. An agency questions a registration or misapplies a deposit. Someone has to work it to resolution, on the phone with a state revenue department instead of shipping product. We do that, directly with the IRS and the relevant state authorities.
What we will not tell you is that it all disappears. If a worker is classified wrong or a work address is stale, the filing built on that data is wrong too. We can amend returns, correct filings, and argue a case where there is one. We cannot turn bad data into good data. A provider owns the machinery. You and your customer own the inputs. Anyone claiming the whole category of risk goes away is selling you something.
The dependency is real, so diligence matters. Ask how a provider's financials are verifiable: we are a division of Priority Technology Holdings (Nasdaq: PRTH), so ours are in public filings. Ask about scope, because payroll rarely stays payroll. We cover payroll and benefits, and Priority's infrastructure extends to banking, payments, and wallets.
Shopify is the reference case, though not in payroll. Shopify Payments is powered by Stripe. Merchants set it up in the Shopify admin, see Shopify branding, get Shopify support, and pay Shopify. No badge at checkout, no second login. Shopify built the best merchant experience on someone else's rails and kept the customer, the interface, and the economics.
The four questions that decide it
Is payroll your product or your feature?
If a customer would buy payroll from you without buying anything else, build or acquire. Otherwise partner. Most platforms are in the second category and describe themselves as the first.How much compliance operation do you want to run?
Ask who inside your company owns the fix when a filing error hits two thousand customers in one quarter. If nobody comes to mind, that is your answer.What margin do you need, and over what horizon?
Referral pays this quarter and caps forever. Building pays best long-run and costs years first. Partnering sits between the two. The math is here.Where does your engineering leverage go furthest?
Every engineer working on state unemployment insurance registration is not working on what your customers chose you for. Compliance maintenance has no finish line.
Payroll is one of the few features where customers forgive a mediocre interface and never forgive a wrong number. That is why the table stakes deserve to be taken seriously, and why they are the wrong place to spend your best people. Decide who carries them, then go win on the part that shows.
Considering the partner path?
RollFi provides embedded and white-label payroll and benefits infrastructure. You own the experience, the customer, and the margin. We handle calculation, filing, remittance, and compliance. As a division of Priority Technology Holdings (Nasdaq: PRTH), we can extend into embedded banking, payments, and wallets when your customers start asking for those too.
Bring the hard questions. The ones above are the right ones.
About Rollfi
Rollfi empowers banks, vertical SaaS platforms, accounting firms, and fintechs to add payroll and benefits to their offerings through white-label solutions and robust APIs. With Rollfi's infrastructure, platforms can unlock new revenue, boost customer retention, and gain valuable payroll data insights. Fast deployment and full regulatory coverage make Rollfi the easiest way to turn your platform into a one-stop shop for essential business services.