Conduit
Open for founding partners

You sell it. We build it. Nobody upstream ever says hello.

Conduit is the white-label delivery layer behind independent AI consultants. You keep the client, the contract and the markup. We ship the automation under your name, on your letterhead, inside your SLA.

NDA + MSA in 24h Named sub-processor No client contact, ever
patch bay — live ch 01 / 09
inbound · workloads routing · live upstream · labs
Your client
What you keep

Contract, relationship, and renewal stay with you.

Your margin
What you keep

Flat delivery fee. It doesn't move when you raise your price.

Your name
What you keep

Commits, docs, deploys and email are yours.

The build
What we take

Scoped, tested, documented, handed over.

01 What we route

Four workloads that sell themselves and hurt to build.

We deliberately don't do everything. These four have a scope you can quote in an email, a demo you can run in twelve minutes, and a failure mode we already know.

Workload A

Inbox & ticket triage

Classify, route, draft. Sits on their existing helpdesk, writes back through the API, hands anything ambiguous to a human queue with the reasoning attached.

  • REST API
  • Webhook
  • CSV / SFTP
  • Human review
Workload B

Document extraction

Invoices, POs, statements, scanned contracts. Structured output with a confidence score per field and a review screen for anything under threshold.

  • REST API
  • Webhook
  • CSV / SFTP
  • Human review
Workload C

Call & meeting intelligence

Transcript in, structured record out: next steps, objections, risk flags, CRM fields. The one where the client sees value on day one and renews without a conversation.

  • REST API
  • Webhook
  • CSV / SFTP
  • Human review
Workload D

Internal knowledge answers

Retrieval over their own mess — SharePoint, Drive, a decade of PDFs. Cited answers only, permissions respected, and an honest "not in the corpus" instead of a guess.

  • REST API
  • Webhook
  • CSV / SFTP
  • Human review

02 The stack

Six labs. One patch bay. You never pick.

We're not resold to a single lab. Every workload gets routed to whichever upstream model fits the job — chosen for a stated reason, not a benchmark we ran and aren't publishing.

AnthropicRT-21

Claude

The pick when a workload can't tolerate a wrong turn — used for anything client-facing that has to hold up under scrutiny.

  • Careful reasoning
  • Long instructions held
OpenAIRT-22

GPT

The most widely deployed option — the safe second opinion when a build has to hold up against scrutiny from a client's own team.

  • Broadly deployed
  • Well-documented
GoogleRT-23

Gemini

Aggressive pricing on the lighter tiers makes this the default for workloads that just need to run constantly and cheaply.

  • Aggressive pricing
  • Runs constantly
MetaRT-24

Llama

Open weights mean the marginal cost per request can approach zero once it's running on infrastructure we already pay for.

  • Self-hosted
  • Open weights
xAIRT-25

Grok

Built into a live platform that has to respond in real time — the pick when a visitor is waiting on the answer right now.

  • Real-time platform
  • Live data
Mistral AIRT-26

Mistral

Smaller, leaner models built to respond fast — useful when latency matters more than raw capability.

  • Lightweight
  • Low latency

Labs suited to quality: Claude, GPT

03 The line

How a job moves through the bay.

Four positions. You only ever touch the first and the last — the middle two are the part you're outsourcing, and the part your client never needs to know about.

Position 01 · you

Forward the brief

Paste the client's problem in whatever state it arrived — a Slack thread, a bad transcript, three bullet points. We scope it back to you within one business day as a fixed quote you can mark up.

Your input: 10 minutes. No discovery call required.

Position 02 · us

We build it dark

Engineering happens in a repo you own, under commits authored by your org. No Conduit branding, no Conduit domains, no Conduit email in the thread. If your client greps the codebase, they find you.

Named as sub-processor in your DPA. That's the only trace.

Position 03 · us

Handoff pack

You get the deploy, the runbook, the eval results, and a demo script written for you to present. Plus the three questions your client is most likely to ask, answered, so you're never caught out on a call we're not on.

Rehearsal call with your team if you want one. We stay off camera.

Position 04 · you

You invoice. We invoice you.

Your client pays your rate on your terms. We bill you flat, monthly, net 15 — never a percentage, so the better you sell, the wider your spread gets.

Escalations route to us within SLA. Your client still only ever emails you.

04 Margin meter

What the spread actually looks like.

Move the sliders. This is arithmetic, not a projection — your billed retainers minus what you pay us, before your own costs.

6

How many client retainers you're modelling.

$4,500

What you'd bill each client per month.

$1,400

Flat delivery fee. Doesn't move when you raise your price.

Billed / month$27,000
Paid to Conduit$8,400
Margin rate68.9%
You keep Delivery cost
Your gross, annually $223,200

05 Rates

Flat fees. Never a percentage of your invoice.

Founding-partner pricing, held for the first cohort. Priced per active client, not per seat or per call. Annual is billed up front and holds the rate for twelve months.

Single line

One client, one workload. The way most partners find out whether this works for them.

$ [TODO] / client / mo
  • One workload from A–D
  • Handoff pack + runbook
  • Escalation response: [TODO: response commitment]
  • Named sub-processor agreement
Start here
Recommended

Patch bay

Up to five active clients across any workloads, with a shared build queue you control the order of.

$ [TODO] / mo, up to 5
  • Any mix of workloads A–D
  • You set queue priority
  • Escalation response: [TODO: response commitment]
  • Rehearsal call before each handoff
  • Quarterly rate review, capped
Open a line

06 The awkward questions

Asked in the first call, every time.

You're reselling someone else's delivery. Here's exactly where that's fine, and the one place it isn't.

Q1 Will my client ever find out you exist?

They'll see us named as a sub-processor in your data processing agreement, because hiding that would be a legal problem rather than a branding one. Everywhere else — commits, docs, deploys, email, calls — it's your name.

Q2 What happens if it breaks at 2am?

Your client contacts you, because you're the vendor. You forward it to the escalation channel and we work it under whichever SLA your tier carries. You stay the single point of contact throughout, which is the whole product — you're selling accountability, and accountability can't be subcontracted in front of the customer.

Q3 Do you work with my competitors?

Possibly — assume so, given how few workloads we cover well. What's contractual either way: your client list, your pricing, and your scoping documents never move between partners. If you need guaranteed exclusivity in a named vertical, ask — that's a conversation, not a default.

Q4 Can I just hire an engineer instead?

Eventually, yes — once the fixed cost of a salaried hire is smaller than the variable delivery fees you're paying us. Early on, when revenue is still uneven, that trade tends to run the other way. Use us to get past the point where hiring is boring rather than terrifying.

Q5 Where does this arrangement actually go wrong?

When the partner sells something they don't understand. If you can't explain the failure modes of what you've sold, the handoff pack won't save you on the call — the client will ask one layer deeper and the whole thing unravels. We'll turn down a brief if it looks like you're quoting outside your own comprehension. That's not us being precious; it's the only version of this that survives a renewal.

Q6 How many partners do you have right now?

Right now, none — you'd be one of the first. This is a founding cohort: direct access to the person actually building your work, founding-partner pricing held for as long as you stay, and real influence over which workloads we prioritize next. That won't be true once this is an established roster, which is exactly why the terms are what they are today.

Channel open

Send one brief. See what comes back.

No pitch deck, no discovery sequence. Forward a real client problem and you'll have a fixed quote and a delivery date within one business day.

hello@conduitdelivery.com