What a partner does

Source and manage an expert bench against a written qualification bar, and keep it full for the length of the engagement. Verify each candidate's identity and right to work. Flow the confidentiality obligations down to every named individual. Deliver candidates in rolling tranches rather than one batch at the end, and replace anyone who drops out or is excluded so the bench stays at strength.

That is the whole job. You are not asked to build tooling, author guidelines, design a QA regime, or stand behind a quality statistic — those are ours.

What DeepenSkill handles

The operating layer you would otherwise have to build.

Routing

Demand arrives as a routing invite against a specific mandate, carrying a codename and a redacted scope. You respond; awarded work becomes a project with milestones. Invites can only be issued to partners who have completed onboarding — the state is computed, never hand-ticked.

Vetting gates

Credentials verified, a standardized domain test, then a practical gold agreement exam in the review console. The sequence is enforced in the service layer, so no stage can be skipped, and every advance or failure is written to a vetting record with an outcome and a reason.

Independent validation

A Deepen validation team, separate from the team running production, scores the output against gold reference data and reports the agreement statistics. The platform rejects a validation report authored by the party that delivered the work — including yours, and including ours.

Milestone payables

Payables accrue when the lab accepts a milestone, are approved on the platform, and are recorded there against the engagement. No money moves through the platform and it holds no bank details — remittance is a label, settlement is offline.

Tooling & access

Review console accounts are provisioned per expert after qualification is passed, never before, with roles scoped to the work. The console has its own authentication and tenancy; sessions never cross between systems.

Customer anonymity

The end customer's identity is stripped from every partner-facing field by a redaction function in code, not by policy. You work a codename. A no-direct-approach attestation is the contractual backstop to the technical control.

Two engagement shapes are available: you source and manage the bench, or you additionally run production and carry the tooling cost. What is never delegated is validation — a quality report written by the party that produced the work is rejected by the platform, and that is exactly what makes the claim we make to the lab true.

What we ask of you

Five onboarding items, and two hard gates.

  • An organisation profile with real capability rows

    Legal name, website, country and HQ, the regions and languages you cover, your delivery model, and at least one domain capability row: the domain, bench count, seniority mix and typical ramp time. The capability rows are what the matching picker reads — a partner with none is invisible to it.

  • Six compliance attestations, each signed by a named person

    Confidentiality flow-down to each individual, right to work, data handling, subcontracting disclosure, no direct approach to the end customer, and accurate representation. Any certification you upload must carry an issuer and an unexpired date.

  • A contracting record

    Legal entity, registered address, tax jurisdiction and reference, invoicing contact and a remittance method label. The platform deliberately holds no bank details.

  • Named contacts, one of them confirmed

    A primary operations contact and an escalation contact, each with name, email, phone, timezone and working hours — and the primary's email confirmed by a single-use link. Changing that email clears the confirmation, so plan mailbox changes around a batch, not into one.

  • Acceptance of the partner terms

    Accepted by an organisation admin, capturing the typed name, the document's content hash and a timestamp. This item is never waivable — a signature is a signature.

The two hard gates: commercial terms are agreed before sourcing opens, and onboarding is complete before any routing invite can exist. The second one is enforced by the platform, not by goodwill. Expect an interview as part of approval, and expect a same-business-day response expectation on escalations — immediate for anything touching safety or confidentiality.

What you get back

Demand you would not otherwise reach, without building the tooling, quality regime or lab relationship yourself — and you keep your own clients, contracts and commercial relationships untouched.

You also get honest reporting on your bench: a weekly bench-level summary covering items delivered, on-time percentage, bench-aggregate gold accuracy and agreement, rework count, exclusions by category and the next batch volume, plus a per-batch one-pager. Send-backs come with reason categories so you can act on them. Per-expert scores stay with us, because they are the lab's quality evidence and not a management tool we hand out.

No earnings figures, take rates, partner counts or bench sizes are published here. Commercial terms are walked through on the first call, and they are agreed in writing before any sourcing begins.

FAQ

  • Who is a sourcing partner?

    A specialist recruiting agency, BPO or expert network that can find and manage practising specialists — clinicians, attorneys, PhD scientists, senior engineers, robotics and controls people — and stand behind identity verification, right to work and confidentiality flow-down for each named individual.

  • Do we ever learn who the end customer is?

    No. Opportunities are presented under a codename with a redacted scope, and the customer's identity is stripped from every partner-facing field by a redaction function in code. A no-direct-approach attestation is the contractual backstop to that technical control.

  • Who validates the work our experts produce?

    Deepen does, through a validation team separate from the team running production. The platform rejects a validation report authored by the party that delivered the work, so validation is never delegated to the partner who supplied the bench. It is what makes the independence claim we make to the lab true.

  • How and when are partners paid?

    Payables accrue when the lab accepts a milestone, are approved on the platform and recorded there. No money moves through the platform and no bank details are held in it — remittance is a text label and settlement happens offline against terms agreed before sourcing opens.

  • What performance information do we receive?

    Bench-level reporting on a weekly cadence — items delivered, on-time percentage, bench-aggregate gold accuracy and agreement, rework count, exclusions by category and the next batch volume — plus reason categories for any send-back. Per-expert scores are not shared.

  • Do we keep our own client relationships?

    Yes. A DeepenSkill engagement is additional demand routed to your bench. Your existing clients, contracts and commercial relationships are yours and are not touched by working with us.

How to apply

Email skill@deepen.ai with your legal entity name and website, the domains and regions you cover, the seniority mix and rough size of the bench you could stand up, your typical ramp time, and any certifications you hold with their issuer and expiry. If it is a fit we will come back with an interview slot; approval requires that interview, and onboarding follows it.