Who we are

Built for engineering teams that want their hours back.

Place the top 3% of developers across the Americas into US engineering teams — without the agency markup, the marketplace whiplash, or the payment-risk theatre.

02 · the team

Operators who ran projects before they ran sourcing.

Founded by engineering leaders who spent a combined two decades inside US-based product teams, engaging contractors the hard way. sourceBOLD was built because every existing option broke in a different place. Headquartered in Saratoga Springs, Utah.

IW
Ian Wilson
PRESIDENT
Two decades of operating experience inside US software companies. Leads the client side and the standards we set together.
RC
Rebecca Christine
SECRETARY
Background in corporate operations and compliance at US growth-stage companies. Stewards governance, contracts, and entity filings.
ZF
Zia Fyle
TREASURER
Background in treasury and payment operations at US fintech and platform companies. Manages cash flow and banking relationships.
MBR
María Belén Ravaza
RECRUITER
Background in technical recruiting across Latin American engineering markets. Runs the vetting funnel and the developer experience end-to-end.
03 · what we believe

Three commitments we wrote down so we couldn’t quietly back out.

01

Vetting that’s measured, not just a claim

Acceptance rate, time-to-placement, and retention are tracked internally and calibrated against placement outcomes. If a metric slips, we ask hard questions rather than ship a placement we can’t justify.

02

Money flow as a feature, not a footnote

No floating payments while your invoice clears. Period. The platform enforces this in code — same payout schedule every cycle, reconcilable against your bank statements.

03

No employees on either side

sourceBOLD does not employ developers, and our clients do not employ developers through us. Engagement is contractor-to-contractor, with sourceBOLD as the platform and counterparty.

04 · trust & security

Security isn’t a sticker. It’s the architecture.

The portal is built on a zero-trust default-deny architecture: every server boundary checks role and identity before responding. Sensitive fields — bank details, government IDs — are encrypted at the field level. Every state change writes a row to a tamper-evident audit chain.

We maintain a subprocessor list, retention policy, and compliance purge workflow as internal operating practices. The platform enforces the rest in code — zero-trust default-deny, field-level encryption, hash-chained audit.

Zero-trust default-deny
Every server boundary checks role + identity
State privacy laws
Compliance purge workflow
AES-256 at rest
Field-level encryption for PII / banking
Cryptographic audit log
Tamper-evident hash chain
05 · how we handle your money

We do not float, lend, or co-mingle.

Client funds settle into our operating account, are matched 1:1 against linked developer payouts, and are dispatched on a published schedule. Disputes pause the gate. Override authority is restricted to Executive Administrators and every override writes a captured-reason audit row.

The state transition shown is the actual invariant — not a diagram of one. Your CFO can hold us to it by reconciling our payout schedule against your invoice settlement dates.

// Excerpt from internal architectural rules. // Available to clients on request. // Every payout (contractor, recruiter, // reimbursement) links to a specific // client invoice. State transition: FUNDING_PENDING → PAYMENT_READY // requires linked invoice = PAID, // or its payment row = SETTLED. // Override authority: // Payments Manager — NONE // Executive Admin — captured reason, // audit-logged, // hash-chained.
06 · get in touch

Got a question? Send a message.

Tell us what you’re scoping. We reply within one business day, from a real engineer — not a sequencer.

We reply within one business day.

By submitting, you agree to our Terms and acknowledge our Privacy Policy. We don’t share your message with anyone outside sourceBOLD.