Case study: a startup with a remote team in 5 countries pays all payroll in USDC
Five countries, one payment cycle: the hard part was not the rail, it was the classification.
A startup with people in five countries treats pay day like a race. Someone exports the spreadsheet, someone else checks the destination details, individual transfers go out, some arrive the same day and some the following Thursday, and someone in Buenos Aires messages asking why less arrived than agreed. Every month, the same.
At Soulbit Academy we present this as a synthetic and realistic example, not a real client. The names do not exist and the figures are illustrative, though consistent with typical costs and timelines. A nearby case, on the agency side paying freelancers, is in an agency pays its freelancers in USDC. This one is different: here the whole payroll moves, employees included, and the hard work happens before touching any platform.
The company profile (illustrative case)
Call the company "Ribera", a 19-person software startup legally based in Colombia. Its product sells by subscription to regional clients and annual revenue is around 1.4 million dollars.
The team is spread across five countries: six people in Colombia, five in Argentina, three in Mexico, three in Spain and two in Brazil. Total monthly payroll runs about 78,000 dollars. The legal composition is mixed: Colombia has employment contracts; elsewhere the company engages people under services agreements, with contracts and invoices.
Finance is run by a head of finance supported by the operations lead. The goal they set was not "use crypto". It was shortening the payment cycle and no longer receiving messages about amounts that do not add up.
The problem: five countries, five calendars
Cost was not what hurt most, though it was there. What hurt was the spread of timings and the lack of predictability.
Every corridor behaved differently. Some payments landed in a day, others in four. Some arrived complete, others with deductions that appeared along the way. As a public reference, the World Bank's Remittance Prices Worldwide series puts the average cost of sending money across borders at 6.36% of the amount and close to 15% through a bank channel. Those are remittance figures rather than payroll, but they describe the same plumbing, and the BIS cross-border payments programme exists for precisely that reason.
Why does unpredictability weigh more than cost?
Because a person organises their month around the date they get paid. A three-day delay is not a financial problem for the company, but it is for someone with a direct debit due. When that delay repeats and differs by country, it stops being an administrative matter and becomes a trust matter.
What was not a payments problem: classification
The project started where nobody expected: in a legal review, country by country, of how each person was engaged.
The reason is simple. Employees and contractors are paid differently, with different documents and different obligations, and that classification follows the facts rather than the name on the contract. The full analysis is in contractor vs employee in LATAM. Switching the payment rail without settling that would have been repainting the front of a structural problem.
The review, run with local counsel in each country, took around six weeks and produced two contract adjustments and one reclassification. Only after closing it did the company touch the operational side. The head of finance summed it up like this: the platform solved 20% of the project, and that 20% came last.
How the monthly cycle ended up
With classification settled and the verification file approved, the cycle became a one-morning routine.
| Dimension (illustrative case) | Before | After |
|---|---|---|
| Transfers launched per cycle | 19 individual transfers | One recurring cycle with 19 lines |
| Time until everyone is paid | 1 to 4 business days by country | Minutes from execution |
| Team hours per cycle | Around 9 | Around 2 |
| Queries from the team about amounts | 4 to 6 every month | Fewer than 1 |
| Traceability per person | Assorted bank receipts | On-chain identifier per line |
| Payment in local currency | Depending on each country's bank | Only Colombia via local rail; elsewhere each person handles it |
The procedure they adopted is the standard one: calculate in their own system, build the batch, validate destinations against the verified record, fund the balance including fees, approve under dual control and execute. The full operational detail is in how to schedule recurring payroll in stablecoin. In Colombia the final leg reaches local currency, as explained in paying payroll with stablecoins in COP.
One habit turned out to matter more than expected: the pay date became untouchable. The team had previously absorbed small shifts of a day or two when someone was travelling or a bank window closed. Once the cycle no longer depended on banking hours, the company committed to a fixed date and kept it, including when it fell on a weekend. That commitment, more than the settlement speed itself, is what the team noticed first.
Reconciliation moved to the same day, line by line, with identifier, gross amount and fee recorded separately. The accounting procedure is in how to reconcile stablecoin payments in accounting.
The conversation with the team
This part appears in no technical guide and it shaped the outcome more than anything else.
The company did three things before the first cycle. It explained what USDC is, a digital dollar issued by Circle backed by cash reserves and US Treasury bills, promising nothing beyond that. It decided and wrote down who absorbs the network fee, which in their case is the company, so the amount received matches the amount agreed. And it made clear that nobody was obliged: anyone preferring to keep getting paid by transfer could.
Of 19 people, 15 accepted the change in the first quarter, 3 joined later and 1 never migrated. That last case was not pushed.
What did the team ask most often?
Three things, in this order. Whether the value could move, which the company answered by explaining the asset's backing without promising absolute stability. How to get into local currency, which they handled by sharing general information and leaving the decision to each person. And what happens if they gave the wrong destination details, which is why the company required a test transfer before adding anyone to the cycle.
What did not work
| Initial expectation | Actual outcome | How the company handled it |
|---|---|---|
| Migrate 100% of the team | 18 of 19 people | Kept traditional payment for whoever declined |
| Remove the legal side of the problem | Classification stayed the company's own work | Annual review with local counsel in each country |
| Pay local currency in every country | Only Colombia has a local rail in V1 | Each person handles their conversion; communicated up front |
| One team member in a specific country | Conversion to local currency proved costly and awkward | Returned to the previous scheme with no penalty |
| Stop calculating and reporting payroll | The rail neither calculates nor reports anything | Continues with its payroll system and accountant |
| Earn yield on the dollar balance | Not available in V1 | The balance is used as operating treasury |
The country where it did not work deserves a mention, because it is the most instructive part. The person received USDC without trouble, but converting into their local currency cost time and fees, and the net amount they ended up with was worse than before. The company did not insist. A payment rail that improves the average but worsens one specific case is not imposed: the exception is accepted.
What another company can take from this
Three conclusions travel well.
First: the order matters more than the tool. Classifying each person properly, country by country, is the real work, and doing it after changing the rail means redoing everything.
Second: adoption is earned with information and without obligation. Explaining the asset without overselling it, writing down who absorbs fees and allowing someone to opt out produced more adoption than any internal announcement would have.
Third: measure what actually hurt. The company did not measure fees saved, it measured cycle hours and team queries. Those two numbers fell, which is why the project counted as a success, even with one person outside it and one country where conversion is still awkward.
Frequently asked questions
Is this case based on a real Soulbit client?
No. It is an illustrative, synthetic case. The company does not exist and the figures are invented, though consistent with typical costs and timelines in cross-border payments. It shows the order of magnitude of the problem and what changes, not a promise of results.
Can formal employees be paid in stablecoin?
It depends on the labour law of each country, and that question comes before the payment rail. The case resolves the formal side under the applicable law in each jurisdiction and uses the rail only to execute the payment. No platform substitutes for that analysis, which belongs with local labour counsel.
What about people who need local currency?
Outside Colombia, each person handles the conversion themselves, because V1 has a local banking rail only in that country. In the case it worked well in three countries and badly in one, and the company treated that as a limit of the project rather than forcing it.
Who absorbs the network fee on a payroll payment?
An internal policy decision worth taking before the first cycle and writing down. In the case the company absorbs it, so the amount received matches the amount agreed. Leaving it undecided produces small, repeated complaints that erode trust.
How long did implementation take?
In the case, around three months, and most of it was not technical work. It was reviewing each person's classification with local counsel, preparing the company verification file and agreeing the terms of the change with every member of the team.
Want your company to add stablecoins to its operations?
Join the Soulbit waitlist and start paying payroll, collecting and managing treasury without SWIFT.
Join the waitlist