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

Founder-led implementation

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

Lootrunners is implemented around the way your agency approves work, controls its company wallet, and closes contractor costs today. The setup is done with you—not handed over as an empty account.

See pricing →

What implementation accomplishes

By the first completed cycle, your agency should have:

A documented request-to-reconciliation workflow
Named owners for every decision
Configured project and finance approvals
A defined company-wallet signing process
Verified contractor payout destinations
Client and project attribution
Accounting mappings
A completed test-payment procedure
A completed live pay run
A reviewed reconciliation package
Operating documentation for the next cycle

The four phases

Implementation runs in four bounded phases, each with a named deliverable.

Phase 01

Map the current pay cycle.

Who submits requestsWhat makes a request completeWho approves the workWho approves the paymentHow destinations are collectedHow the company wallet is controlledWho signsHow payments are categorizedHow reconciliation happensWhere exceptions occur

Deliverable — Current-state pay-cycle map

Phase 02

Configure the operating model.

Organization and rolesContractors and engagementsClients, projects, milestonesApproval policiesHigher-value thresholdsDestination verification & holdsCompany-wallet workflowAccounting accounts & classesNotification ownershipException handling

Deliverable — Configured beta workspace and operating policy

Phase 03

Prove the route before the full payment.

Contractor requestEvidence completenessApproval routingDestination verificationDestination-change holdTest paymentSafe transaction preparationSigner reviewReceipt generationReconciliation output

Deliverable — Test-payment and readiness review

Phase 04

Run the first live pay cycle and close.

Final request reviewPreflight checksPay-run preparationAgency signingSettlement statusContractor communicationReceipt reviewAccounting exportReconciliationPost-cycle retrospective

Deliverable — First controlled pay run and reconciliation package

Who should participate

Five roles. One person can hold several in a smaller agency.

Agency owner

Sponsors the workflow and resolves policy decisions.

Operations lead

Owns the recurring pay-cycle process.

Finance lead or bookkeeper

Defines review, account mappings, close requirements, and exceptions.

Wallet owner or signers

Confirm the company-wallet policy, signer threshold, and authorization process.

Project representative

Defines what constitutes completed and approved work.

Before we can move

What we need from you — and what we will never ask for.

A named internal owner
A sample contractor list
A sample client/project structure
A sample payment request or invoice
Current approval rules
Accounting chart and classes where relevant
Company-wallet ownership decision
Named signers
USDC on Base readiness
Agreement on the first test and live cycle

Do not submit private keys, seed phrases, or wallet-recovery material — we will never ask for them.

Timing

Timing is agreed after the workflow is understood.

The implementation plan and target date are agreed after the pay-cycle review. Timing depends on company-wallet readiness, data quality, contractor verification, approval complexity, accounting structure, integration requirements, number of entities, and availability of the agency participants.

Wallet readinessData qualityVerificationApproval complexityAccounting structureIntegrationsEntitiesParticipant availability

After the first close

The monthly operating rhythm.

Pay-run preparation

Readiness and exception review before every cycle.

Contractor onboarding

New people, destinations, and verification handled in-flow.

Project-cost review

Cost, fees, and margin visible per project each month.

Accounting export + reconciliation review

The books receive a structured record, reviewed together.

Monthly operations report

What ran, what blocked, what changed.

Workflow changes

Policies evolve with the agency, not against it.

Start with the process you have now.

Bring one real pay cycle to the review. We will identify the implementation path and the conditions required to go live.

Founder-led · No commitment · Private beta