One console. Every client. Your Conductor learns each of them separately.
Exsel Partner is for VAs and agencies who operate other people's stores. Multi-client switching, isolated memory per client, a PartnerConductor that coordinates across your book.
EXSEL Partner is the VA and agency tier: three plans (EP-S $149/mo, EP-P $299/mo, EP-A $499/mo) that let virtual assistants and agencies manage EXSEL on behalf of multiple merchant clients. Partners inherit the same ScopeManifest safety layer — no action a partner can take on a client account falls outside what the client's own manifest permits. EXSEL Partner is designed to power VAs, not replace them.
The tier ladder (ADR-053)
| Tier | Price | Seats | Designed for |
|---|---|---|---|
| EP-S — Solo VA | $149/mo | 1 seat, up to 3 clients | Freelance VA / part-time operator |
| EP-P — Partner | $299/mo | Up to 5 seats, up to 15 clients | Boutique agency / small team |
| EP-A — Agency | $499/mo | Up to 15 seats, up to 50 clients | Established agency |
Multi-client discipline — the part the other tools get wrong
- Per-client tenant isolation. Each client is a separate tenant with its own Qdrant namespace, its own LoRA adapter, its own audit trail (ADR-055 rule 6).
- Your PartnerConductor coordinates — it does not blend. When you switch clients, the console re-binds to that client's ClientConductor. The PartnerConductor's own memory (your workflows, your preferences) lives at the agency tenant, not any client's.
- Audit per client. Every action is logged to the client's
companionauditlog_v2. When a client asks "what did your agency do this week?", you download their signed bundle and hand it over.
PartnerConductor — your coordination agent
- See cross-client KPIs for stores you operate (aggregate view across your book).
- Surface workflows ("4 of your 12 clients have unreplied reviews ≥24h — open each?").
- Coordinate via A2A protocol (ADR-087) with each client's own ClientConductor when you hand off tasks.
- Run scheduled routines per client ("every Monday at 09:00 Eastern, check Account Health on client A").
- Export client-branded monthly deliverables (PDF reports, screencaps, numbers).
- Read one client's data while acting on another's (fail-closed
TenantIsolationError). - Train on one client's approvals and apply patterns to another. Per-client LoRA adapters are strictly isolated.
- Access a client's account outside its ScopeManifest + ModeGate (the same gates apply — agency status does not grant elevated scope).
The VA workflow — morning to close
One concrete day, EP-S tier, 3 clients:
09:00 — Console morning brief: "Client A: 2 suppression-risk reads to acknowledge. Client B: TikTok review reply SLA window closing in 3h. Client C: inventory reorder threshold hit on SKU-88."
09:05 — Switch to client A. PartnerConductor drafts the ACK reply; you approve. Switch to client B. PartnerConductor shows the review reply draft with sentiment context ("negative, mentions shipping delay"); you edit one line and approve. Switch to client C. PartnerConductor shows the reorder proposal (quantity, supplier, cost); you push to review with client C.
12:00 — Content generation run for client A's Amazon listings — you queue 6 SKUs. PartnerConductor drafts; saves to client A's Content Gen unlock queue (note: client A pays for D-CG; your Partner seat does not unlock it). You review and approve in batch.
16:00 — Client B's weekly report: one-click export with client branding. 4 pages: Account Health trend, review sentiment, PPC ROAS, recommended next actions.
17:30 — Tomorrow's queue: PartnerConductor schedules next-day routines.
What the Partner auto-runs, across every managed client on one dashboard: review response queue, inventory reorder triggers, PPC bid adjustments, listing compliance checks, ad-creative variants. You approve, the Conductor acts, every action signed to each client's audit log.
Beta partners log 4–14h/week reduction — methodology at /partner/methodology (coming soon, 2026-Q3).
---
What your clients see
- Their own ClientConductor — named, memory-bound to them.
- Their own unlock SKUs (they pay).
- Their own audit log of every action — including yours, timestamped, attributed to "Agency: [your name]".
- Transparent posture: they can verify at any time that your PartnerConductor has not crossed into their data beyond what they authorized.
White-label posture (honest)
Exsel Partner is not a white-label — you cannot resell Exsel branded as your agency.
What you can do:
- Co-brand client reports (your logo next to Exsel attribution).
- Own the relationship — you are the client's contact; Exsel is infrastructure.
- Custom domain for client-facing dashboards: EP-A tier only (CNAME to *.client.exsel.ai).
If true white-label (full brand removal) is a blocker for your agency, talk to us — enterprise-custom contracts exist for ≥50 client books.
---
Pricing math (for your agency, at a typical book)
- Your Partner seat: $299/mo
- 10 clients × their own unlocks (their bills, not yours): not your cost
- Your per-client operating cost: $29.90/mo Partner allocation
- Your per-client revenue (agency markup): typical $500-$1,500/mo management fee
Onboarding a new client
1. Client signs up at Exsel themselves (free plan, 90 seconds) OR you refer them via your partner link.
2. Client approves your agency as a partner_operator role on their account — 2FA-gated invitation.
3. Your console shows them in the client switcher.
4. Client or you choose which unlocks to activate (client pays for their own).
5. You start operating; every action logged to their audit trail with your agency's attribution.
Offboarding: client revokes partner access at /settings/integrations/partners. Effective immediately. Your PartnerConductor retains aggregated workflow knowledge (your own tenant) but loses access to client data.
---
Architectural proof (2026-04-19 founder directive — strips, not agency quotes)
Three architectural proof strips, not borrowed logos. Every claim maps to public code:
1. Per-client ScopeManifest — each client audits their own allowlist. Your Partner role does not elevate scope. [/security#scope-manifests](/security#scope-manifests)
2. Tenant isolation via AggregateOnly wrapper — your PartnerConductor cannot compose a query across your book. That's a type rule, not a policy (ADR-055 rule 6). [/security#tenant-isolation](/security#tenant-isolation)
3. Hash-chained audit log per client (ADR-044) — when your client asks "what did your agency do this week?" you hand them a signed evidence bundle. [/security#audit](/security#audit)
Design-partner cohort: 25 seats open through 2026-Q2. When the first beta agency signs off on a public quote + dollar number + screenshot permission, it replaces strip 3's footnote. Never the first two.
---
Exit-intent drawer
> Before you go — the per-client audit example.
> A 1-client-week signed evidence bundle. See how your client sees it.
>
> [ you@agency.com ]
> [ Send me the sample → ]
---
Close
3 numbered steps: 1. [ Start free on your own account ] — get your agency tenant. No card. 2. [ Invite your first client ] — 2FA-gated, 2-minute setup. 3. [ Upgrade to EP-S ] — when you have 3+ clients and want the PartnerConductor.
---