Contractor settlement without a second finance team.
A field-services company needed to pay contractors in stablecoin on jobs that close in hours — and keep an audit trail the existing ERP could accept.
Helios runs crews across three states.
Helios runs crews across three states. Jobs close in the field. Contractors wanted faster settlement than a two-week ACH cycle. Finance wanted a record that looked like the ERP, not a wallet screenshot. A hosted crypto payout vendor created a second set of books and a compliance conversation nobody on the operating team could finish.
Problem, approach, and what shipped.
A case study is a named week with a handover — not a mood board. The record below is what the operator still runs.
- 01
The problem
Helios runs crews across three states. Jobs close in the field. Contractors wanted faster settlement than a two-week ACH cycle. Finance wanted a record that looked like the ERP, not a wallet screenshot. A hosted crypto payout vendor created a second set of books and a compliance conversation nobody on the operating team could finish.
- 02
The approach
We kept Helios as the operator. StablePay would be software they run, talking to the ERP they already trust. The product question was narrow: when is a job payable, who signs that it is payable, and how does that become a payment intent without inventing a new bank. Legal and tax stayed with Helios. We designed the workflow and the records.
- 03
The build
A field-close event in their existing ops tool became the trigger. A supervisor approval created a payable. StablePay issued the payment intent and recorded confirmation. A nightly job wrote a settlement file the ERP already knew how to ingest. The contractor-facing surface was a status page, not a new banking app. Documentation covered the signing boundary: Helios holds keys; we do not.
Outcomes the team can still point at.
- 01
Payable jobs could settle the same day they closed.
- 02
ERP remained the book of record; the gateway remained the payment record.
- 03
The hosted payout vendor was retired after one quarter.
Numbers from the operating week.
- Median contractor settlement
- 14 days → 11 hours
- ERP exceptions after ingest
- < 0.4%
- Second set of books
- Removed
Stack
The product this engagement shaped.
Other operator records.
Have a similar operating problem?
Tell us what the team still runs at 2am. We will say whether it is a product, a build, or a no.