How it works

From discovery to first standup in a few short weeks.

Every engagement runs the same playbook. No bespoke pitches, no last-minute “we found someone better.” The process below is the system — written down, instrumented, audited.

1

Tell us the role

A succinct scoping call. Skills, timezone, team fit, must-haves.

Day 1
2

We source & vet

Technical screens, language assessment, references. Only finalists reach you.

Day 2–10
3

You interview

Your normal interview process. You pick the developer who fits.

Day 11–18
4

Sign one contract

Pay-as-you-go MSA, SOW per developer. No setup, no annual commit.

Day 19
5

They start working

Integrated into your team. One US invoice each month. We handle the rest.

Day 21
02 · vetting in depth

Four gates, two human reviewers, one decision per applicant.

G1

Communication assessment

30-minute language + collab review

Spoken English fluency, written async clarity, conflict-handling responses. Every developer placed has been signed off by a US-based reviewer.

G2

Technical screen

60-minute structured assessment

Stack-specific exercises scored against a public rubric. Two reviewers, blind to candidate identity, must agree to pass.

G3

Systems interview

90-minute architecture walk-through

Designed by a Staff+ engineer in the candidate's stack. Same questions, same rubric, every time. Calibrated against engineers already placed.

G4

Live pairing

2-hour real-codebase session

Candidate ships a small change against a benchmark repo while we watch the process — testing, instincts, debugging, comms under load.

We track quarterly funnel numbers (acceptance rate, time-per-gate, rejection reasons). The trailing average funnel on the home page is sourced directly from this same dataset.

03 · money flow

Developers will get paid after your invoice settles.

The “funding gate” is a system invariant. It’s not a policy or a promise — it’s enforced in the platform itself, the same state transition shown below.

  • INVOICEIssued on the 15th for the following month's services.
  • SETTLEMENTFunds land in sourceBOLD's account via ACH.
  • GATE RELEASESLinked developer payout queue unlocks automatically.
  • PAYOUTSExecute on the 20th and the 5th — Wise or ACH to dev banks.

Disputes pause the funding gate. No developer payout fires on a disputed invoice — money is held by sourceBOLD until the dispute resolves.

// Every contractor / recruiter / reimbursement payout // links to a specific client invoice. The transition FUNDING_PENDING → PAYMENT_READY // requires that linked invoice to be PAID // (one-off path) or its payment row to be SETTLED. // Override authority: // Payments Manager — NONE // Executive Admin — only with captured // reason, audit-logged, // hash-chained.
04 · money math

What every dollar pays for, per developer.

Per active developer · monthly
Client pays sourceBOLD+$$$$
Developer receives$$$
Recruiter installment (months 1–3 only)$
sourceBOLD margin (from month 4)$

sourceBOLD margin is zero in months 1–3 — the recruiter installment fully consumes the spread. We make money when retention works, which is why we vet for it.

05 · who handles what

What sourceBOLD runs — and what we don’t touch.

sourceBOLD

Operations, money, compliance

  • Sourcing & vetting funnel
  • Contracts, IP transfer, NDA
  • Monthly invoicing & ACH collection
  • Multi-currency developer payouts
  • Reimbursement workflow & audit
  • GDPR-aligned handling, encryption, hash-chained audit trail
  • Compliance purge + retention policy
Your team

Engineering and decision-making

  • Final dev selection (always yours)
  • Day-to-day technical direction
  • Code review and architecture calls
  • Performance feedback to sourceBOLD
  • Approving reimbursements
  • Reviewing & paying monthly invoices
Ready when you are

Scale your team.
Surge ahead.

A succinct scoping call. Pre-vetted candidates. First standup in a few short weeks.

See how it worksNo card. Same-day response.