How we partner
We are the engineering team behind your AI line. You own the client, the contract and the price. We build, run and report behind you, and everything transfers to you.
- We never contact the BPO's client.
- The BPO sets the price.
- Everything we build transfers to the BPO.
Section 1 — how we partner
We do not contact your clients. Ever.
The three numbered lines are our commitments. They are in the pilot agreement, the MSA and every SOW.
The engagement cycle
| Step | Step | What happens | Paper |
|---|---|---|---|
| 1 | Discovery call | You name one process, its monthly volume, its owner, where its data sits and who signs an NDA. We say whether we can pilot it. | None |
| 2 | Mutual NDA | Ours or yours. Sample documents move only after it is signed. | Mutual NDA |
| 3 | Paid pilot | One process, two weeks, fixed fee. Acceptance criteria agreed before day one. | Pilot agreement |
| 4 | Vendor empanelment | Registration, tax, insurance and security evidence for your procurement file, with the honest status of each item. | Vendor onboarding pack |
| 5 | MSA, signed once | Commercial terms, liability, governing law and the data processing addendum. | MSA and DPA |
| 6 | SOW per project | Scope, fixed fee, acceptance criteria, ownership of outputs, the accuracy floor and the exception ceiling. | SOW template |
| 7 | Build, UAT, acceptance | Weekly demos, your QA on your sample, then sign-off against the criteria in the SOW. | SOW acceptance criteria |
| 8 | Monthly operations retainer | Monitoring, drift detection, exception handling, the monthly SLA report by the fifth business day. | Ops retainer schedule |
| 9 | Next SOW | The next process, scoped from what the first one taught us. | SOW template |
Section 2 — the cycle
Discovery, NDA, paid two-week pilot, vendor empanelment, MSA once, SOW per project, build and acceptance, monthly retainer, next SOW.
Every document in the Paper column exists as a draft. Each one is under lawyer review before first use.
The pilot
One process. Two weeks. A fixed fee, quoted in the scope. Acceptance criteria agreed before day one, measured on your own sample. A human review queue worked by your reviewers. At the end, a written report, the running system and the code, all transferred to you.
A pilot is ready to start when, in one call, you can name the process, its monthly volume, its owner, where its data sits and who signs the NDA.
Section 3 — the pilot
The pilot fee is fixed. placeholder — replace with the pricing model once it is set.
Accuracy targets are agreed per process from your sample, never quoted in advance.
Who we work with
BPO and outsourcing companies of 50 to 2,000 seats, headquartered in or delivering from India, the Philippines or Eastern Europe, with at least one document-heavy or back-office line: finance and accounting, insurance claims, KYC and onboarding, mortgage processing, healthcare revenue cycle, logistics documentation, or customer support with ticket triage.
We work with your COO or your head of transformation on the scope, with your procurement on empanelment, and with your process owner every day of the pilot. Your clients’ security reviewers read our evidence. They never hear from us.
What we decline
| Case | Why |
|---|---|
| Under 50 seats | Too little volume on any one process to measure, and the pilot fee is a large share of your spend. We are set up for partners from 50 seats. |
| Voice-only work with no document or back-office process | Our pilot starts with a document or back-office process. A voice-only pilot has nothing to transfer. |
| No named owner on your side | A pilot without an owner stalls at hand-over. We need one person accountable for two weeks. |
| A request that we contact your client | We never contact the BPO's client. That is not a negotiation point; it is the reason partners trust us. |
| Exclusivity without a volume commitment | Exclusivity is a commercial term with a price. It can be discussed inside an MSA with a volume commitment, not before. |
| A platform licence rather than an operated system | We do not sell licences. We build, operate and transfer. If you want a licence, we can name vendors. |
Section 4 — who we work with
The seat range and the regions come from the brief. Refusals are written down so that nobody has to discover them in a call.
Questions partners ask
Who owns the model and the outputs after a pilot?
You do. Weights where they exist, prompts, rules, outputs and the evaluation set transfer to you at acceptance. We keep nothing that identifies your client.
Will your engineers ever speak to our client?
No. Every call, email and status report goes through your team. If your client asks for a technical session, we brief your people or join under your name.
What happens when extraction confidence is low?
The field goes to the human review queue with the source region highlighted. Your reviewer approves, corrects or escalates, and corrections feed the next evaluation run.
Who sets the price to our client?
You do. We quote you a fixed fee per pilot and per SOW, and a monthly retainer. What you charge your client is your decision and we never see it.
Where does our client's data sit?
In a per-partner environment in the region the SOW names: India, the EU or the US. Deletion within thirty days of exit, with a certificate. The DPA says the same.
Section 5 — questions
Anything not answered here: partners@entailmentlabs.com.