Skip to content
Private beta · Accepting a small number of design partners

Contractor accounts payable for agencies

Pay global contractors.

Without losing the work, approval, or margin behind the payment.

One controlled pay cycle from request to reconciliation. Your agency keeps custody of its funds and authorizes every payment.

See a sample pay cycle →

30 minutes · Founder-led · No commitment

Pay run · July 15Illustrative preview
Maria López · milestone 2 of 38,000
Jonas Petrov · sound design1,950
Ritika Shah · brand systems4,800
Signatures 2 of 3 · your Safeevery check green
Approved → signed → reconciled✓ Record complete
Agency-controlled walletMulti-approver signingDestination-change holdsComplete payment records

Private beta currently uses USDC on Base. Local-bank and USD payouts are planned, not live.

01 · Product proof

See one contractor payment stay connected from completed work to closed books.

Northwind Summer Rebrand
Client revenue
$24,000
Contractor milestone
$8,000
Contractor
Maria López · Creative Director
Rail
USDC on Base
Company wallet
Northwind Agency Safe
FRAME 01

The contractor requests against the correct milestone.

Maria submits the $8,000 request with the invoice, deliverable link, approved payout destination, and milestone record already attached.

Submitted for project approval
FRAME 02

The project lead approves the work in context.

The reviewer sees the client, project, budget, milestone, deliverable, requested amount, and prior changes before approving.

Work approved
FRAME 03

Finance sees every condition before the pay run is prepared.

The destination is verified. The 24-hour change hold is clear. The request is within policy. The agency wallet has enough USDC. Fees and signer requirements are visible.

Ready for pay run
FRAME 04

The agency signs from its own company wallet.

Lootrunners prepares the Safe transaction. Northwind's authorized signers review the payment and provide the required signatures. Lootrunners never holds the funds or private keys.

Awaiting 2 of 3 signatures
FRAME 05

The payment closes with the accounting and project record attached.

The completed record includes the transaction reference, approval history, receipt, fees, client, project, milestone, accounting mapping, and remaining project margin.

Paid and reconciled
Open the full sample pay cycleIllustrative product preview · Sample data · Not a live customer account

02 · The operating gap

The transfer can be complete while the pay cycle is still open.

A contractor can receive the money while operations and finance are still trying to answer:

What work did this cover?
Which client funded it?
Who approved the milestone?
Did the payout destination change?
Which people signed?
What fees applied?
Which account and project should receive the cost?
What margin remains?

The money moved. The operating record did not.

Email invoicesSlack approvalsProject toolsWallet spreadsheetsSafe transactionsAccounting cleanupOne controlled pay cycle

03 · How it works

Go from complete request to reconciled project cost in four controlled steps.

01

Collect a payment-ready request.

The contractor submits against the correct engagement and milestone with the invoice, amount, evidence, and approved payout destination attached.

02

Approve the work with the project context visible.

Project and finance reviewers see the client, project, budget, milestone, documents, destination state, and approval history in one record.

03

Put a verified transaction in front of the right signers.

Lootrunners checks the destination, holds, approval policy, duplicate status, balance, fee, and signing threshold before preparing the Safe transaction.

04

Close the payment with proof already attached.

The completed payment carries its transaction reference, receipt, approval evidence, fees, project attribution, accounting mapping, and reconciliation status.

See how USDC pay runs work →

04 · Why Lootrunners

Built around the agency pay cycle—not generic payroll or general accounts payable.

Worker platforms manage the worker relationship.

Contracts, onboarding, compliance, payroll, and local payout delivery are their core job.

Wallets and payment providers move money.

They execute or transmit the transaction.

Accounting systems record the books.

They hold the financial record after the transaction is understood and categorized.

Lootrunners controls the agency-specific handoffs between them.

Connect the client-funded work, milestone, approver, contractor destination, company-wallet signature, fees, receipt, and project cost.

Lootrunners can sit beside your existing contractor, project, wallet, and accounting systems. It does not need to replace every tool your agency already uses.

05 · Agency visibility

Know what is ready to pay, what is blocked, and what the project will keep.

See payment readiness before pay-run day.

Approved requests, missing evidence, destination holds, policy exceptions, balance issues, and pending signers are visible in one place.

Keep contractor cost attached to client work.

Every payment remains connected to the client, project, engagement, and milestone behind it.

See project cost and margin before month-end.

Combine client revenue, contractor payments, and payment fees to understand the economics of the project.

Give accounting a structured record.

Receipts, approvals, transaction references, fees, and account mappings arrive as part of the workflow instead of a reconstruction exercise.

06 · Controls before movement

Your agency authorizes the money. Lootrunners controls the process around that decision.

Lootrunners prepares a complete, policy-checked decision for the authorized people in your organization.

New destinations require verification.
Changed destinations trigger a 24-hour hold.
Finance reviews destination changes.
Higher-value payments can require additional approval.
Safe signing thresholds remain under agency control.
Balances and fees are visible before signature.
Duplicate-payment and network checks run before preparation.
Sensitive actions remain on the payment record.

No pooled customer funds. No shared private keys. No automatic release without the agency’s required authorization.

Read the security model →

07 · Outcomes by role

One pay cycle. A clearer answer for everyone responsible for it.

Founder or owner

Know whether the project made money.

See the revenue, contractor cost, payment fees, and remaining project margin in the same operating record.

Operations lead

Know exactly what is waiting and on whom.

See incomplete requests, missing evidence, pending approvals, wallet holds, signer state, and reconciliation exceptions.

Finance lead

Review one controlled pay run instead of many disconnected transfers.

See the full context before signing and receive the structured record after settlement.

Project lead

Approve completed work without becoming the payment help desk.

Review the milestone and evidence, then let the contractor follow the remaining status in the portal.

Contractor

Request payment once and see what happens next.

Submit against the correct milestone, maintain an approved destination, and download the final receipt.

08 · Your existing stack

Keep the systems that own the work, wallet, and books.

Lootrunners is designed to control the handoffs around the payment—not force an immediate replacement of every agency system.

Accounting

QuickBooksGuided in beta
XeroGuided in beta
Structured CSVImport/export

Wallet & settlement

SafeGuided in beta
USDCAvailable in beta
BaseAvailable in beta

Project & client data

Client importGuided in beta
Project importGuided in beta
Milestone recordsGuided in beta
Project toolsPlanned
See integrations and readiness →

09 · Implementation

Map the current pay cycle. Prove the controls. Run the first close together.

Phase 01

Map

Document how requests, approvals, destinations, signing, payment, and reconciliation work today.

Phase 02

Configure

Import the core records and set the roles, approval policies, destination controls, project structure, wallet process, and accounting mappings.

Phase 03

Prove

Run a destination check, test payment, approval scenario, Safe-signing review, and reconciliation rehearsal using agreed data.

Phase 04

Operate

Run the first live pay cycle and first close with founder-led support, then move into the agreed monthly operating rhythm.

The plan and target date are agreed after the pay-cycle review. Timing depends on wallet readiness, data quality, verification requirements, and workflow complexity.

See the implementation process →

10 · Pricing

Implementation first. Controlled operations after.

The setup fee builds the agency-specific operating system around the pay cycle. The monthly fee supports the configured workflows, pay-run preparation, records, reconciliation, and operating review included in the selected plan.

Launch

From $3,500 setup · $750/mo

For agencies with up to 15 active contractors and one core pay-cycle workflow.

See Launch pricing →

Operations

From $6,000 setup · $1,500/mo

For agencies with up to 50 active contractors, multiple approval policies, accounting integration, and recurring project-level reporting.

See Operations pricing →

Custom

From $10,000 setup · $2,500/mo

For multiple entities, advanced controls, custom systems, or vendor-review requirements.

Contact sales →

Network, provider, and Lootrunners fees are disclosed before a live pay run is signed. The agency controls and funds its own company wallet.

See full pricing and deliverables →

11 · Founder

Built with the discipline used for systems that cannot be casual.

Daniel Oh, founder

Daniel Oh Founder

Daniel is a senior platform and security engineer who has designed infrastructure, compliance controls, and internal systems for large engineering organizations. Lootrunners applies that operating discipline to agency contractor payments: visible ownership, least privilege, controlled changes, complete records, and a workflow people can actually operate.

Senior Platform & Security Engineer · Enterprise cloud security and compliance · University of Michigan · Computer Engineering

12 · Private beta

Shape a controlled contractor pay cycle around real agency work.

Lootrunners is accepting a small number of design partners that pay 10–100 contractors across multiple countries. We will map the current process, configure the workflow, and supervise the first test payment, pay run, and reconciliation.

5–50 employees10–100 active contractorsThree or more countriesQuickBooks, Xero, or structured CSVRecurring monthly contractor paymentsOpen to an agency-controlled USDC wallet during beta
Apply as a design partner

Applying does not create a purchase commitment. Go-live depends on product readiness, company-wallet setup, verification requirements, and workflow complexity.

13 · FAQ

Questions finance and operations should ask before a payment system touches the workflow.

Does Lootrunners hold our funds or private keys?

No. Your agency controls and funds its own company wallet. Lootrunners prepares the workflow, checks, transaction data, records, and reconciliation around the payment. Your authorized signers make the final decision.

Why use USDC?

The private beta uses USDC on Base as the settlement rail because it supports direct wallet-to-wallet payments with visible transaction proof and generally low network costs. The rail does not replace approvals, destination controls, records, or reconciliation.

Do we need an existing Safe?

Not necessarily. The supported company-wallet process can be guided during implementation. Your organization remains responsible for wallet ownership, signer selection, recovery procedures, and key management.

Does Lootrunners replace our contractor-management platform?

Not necessarily. Contractor, payroll, EOR, and HR platforms can continue to manage worker relationships and compliance. Lootrunners is focused on the agency pay cycle and project context around the payment.

Does Lootrunners replace QuickBooks or Xero?

No. Lootrunners prepares and connects the payment record so the accounting system receives clearer, structured information.

Which contractor payout methods are live?

The private beta supports USDC on Base to an approved contractor wallet. Local-bank and USD payout methods are planned and must not be described as live.

What does implementation require from us?

A named owner, access to the current workflow and sample records, accounting mappings, company-wallet participation, approval-policy decisions, and participation in the first supervised test and live pay run.

How long does implementation take?

The target date is agreed after the pay-cycle review. Timing depends on wallet readiness, data quality, verification requirements, integrations, and workflow complexity.

Is Lootrunners payroll, escrow, or tax software?

No. Lootrunners provides workflow, controls, records, and reconciliation around agency-controlled contractor payments. It does not determine worker classification, hold funds in escrow, or provide legal or tax advice.

Pay the contractor. Keep the operating record. Close the project cost.

Bring the current workflow to a 30-minute review. We will show you where Lootrunners fits, what would need to change, and what implementation would require.

Founder-led · No commitment · Private beta