Meridian Freight Pvt Ltd
Plot 14, Bhiwandi Logistics Park, Thane 421302
GSTIN 27AAECM4821K1Z5
Bill to
Halcyon Retail Group, accounts payable, Pune
| Description | Qty | Unit | Amount |
|---|---|---|---|
| Container handling, 20ft | 12 | 850.00 | 10,200.00 |
| Customs documentation | 3 | 420.00 | 1,260.00 |
| Freight surcharge, fuel | 1 | 1,240.00 | 12,400.00 |
Amounts in USD. Synthetic document.
This is a synthetic invoice. Real pilots use your documents.
Human review
Your system
SAP, accounts payable
We build the AI layer your clients think you built.
Document, voice and back-office AI for BPO partners. Built, run and reported under your brand.
The question you’re being asked
Your clients are asking whether you have AI. They ask in RFPs, in quarterly reviews and in renewal calls, and a slide is no longer an answer. They want invoices read, tickets triaged and calls summarised inside the service they already buy from you.
Buying AI as a customer does not fix this. A platform licence sits on your cost line, the vendor’s brand sits on the output, and the margin you were meant to protect moves to them.
Running models yourself is a different business. Evaluation sets, drift, exception queues, security questionnaires: an operations burden your delivery teams were not hired for.
Section 2 — the question you're being asked
We are not a platform you subscribe to. We are the engineering team behind your AI line.
What we build
Document intelligence
Extraction, validation and human review for the documents your clients send you.
Invoices, KYC packs, claims intake
Voice and chat agents
Agents that take the first tier of calls and chats, and hand off to your people when they should.
Order status, appointment scheduling, collections reminders
Back-office automation
Whole processes across the systems you already run, with a person in the loop where the rules end.
Accounts payable, employee onboarding, reconciliations
AI operations
Monitoring, evaluation and retraining for every model we ship, reported monthly under your name.
Accuracy reports, drift alerts, exception SLAs
- We never contact the BPO's client.
- The BPO sets the price.
- Everything we build transfers to the BPO.
Section 3 — what we build
Every build ships with the operations retainer. We do not hand over unmonitored models.
The three numbered lines are our commitments. They appear, in this form, wherever we describe the offer.
How it runs
Client
Sends invoices, calls and tickets to the service they buy from you. Sees your brand, your reports, your people.
Your BPO
Owns the client, the contract and the price. Your reviewers clear the human review queue. Results land in your systems.
Entailment
Builds and runs extraction, agents and monitoring behind your line. Reports to you monthly, under your name.
| Step | Stage | Who does it | What you see | Typical duration |
|---|---|---|---|---|
| 1 | Discovery | Your COO or transformation lead, our engineer | A written scope after the call | placeholder |
| 2 | NDA | Both legal teams | Our mutual NDA, or yours | placeholder |
| 3 | Paid pilot | Our engineers, your ops lead | Extraction running on your documents, and an accuracy report | 2 weeks |
| 4 | Empanelment | Your procurement, our operations | Registration, GST, insurance certificate, security questionnaire pack | placeholder |
| 5 | MSA and SOW | Both legal teams. One MSA, then one SOW per project | Fixed fee, acceptance criteria, ownership of outputs | placeholder |
| 6 | Build and UAT | Our engineers, your QA | Weekly demos, then acceptance sign-off | placeholder |
| 7 | Run and expand | Our operations team, your delivery leads | Monthly SLA report, exception queue, the next process scoped | Ongoing |
Section 4 — how it runs
Yellow marks the step the machine does. Red marks the step a person does. Hairlines are system boundaries.
Numbered because it is a sequence. The pilot is two weeks by design. Every other duration is a placeholder — replace with data from the first engagements.
Built by people who ship security products.
| Control | What it means for your client | Status | Evidence available |
|---|---|---|---|
| Per-partner isolation | Their data never shares infrastructure with another partner's | implemented | Policy 01, information security |
| Encryption in transit | Documents are unreadable on the wire | implemented | Policy 03, encryption |
| Encryption at rest | Documents are unreadable in storage and in backups | implemented | Policy 03, encryption |
| No training on partner data | Their documents improve no one else's model | implemented | Policy 09, ai model monitoring and drift |
| Append-only audit logging | Every extraction, correction and export is attributable to a person or a system | implemented | Policy 04, logging and monitoring |
Section 5 — security
Status as of 2026-09-01, from the same file that feeds the security page. SOC 2 Type II: not started. Target: placeholder.
Shipped
CanaryVaults
An AI security suite: honeypots, decoy identities, RAG trap facts, a prompt-injection firewall, tamper-evident audit and agent monitoring. canaryvaults.com
ChainPay
Payments, built and run by the same team. chainpay.network
Section 6 — shipped
Things we built and run ourselves.
How we would like to be measured
Containment and accuracy are quoted without saying what was counted, so two numbers that look comparable are not. We publish four benchmark suites that define the metric tightly enough to put in a contract, with the data and the scorer public so anyone can check the definition was followed.
Messy Scan
What degradation does to extraction, and how much of the volume survives without a person.
Honest Containment
Whether a contact was resolved, or only ended.
Exception Economics
What automation costs when it is wrong, in reviewer minutes and money.
Day-60
Whether the system is still trustworthy two months after go-live.
What the four suites measure, or go straight to the benchmark site.
Section 7 — how we would like to be measured
No system has been scored yet. The tables are empty, and each row says why it is empty.
Our own system will sit in the same table as everyone else’s, under the same definitions.
Notes from the lab
26 Aug 2026
5 Aug 2026
14 Jul 2026
Section 8 — notes from the lab
Working notes, dated. No figures until a pilot report supplies them.