How it works
Same request. Two ways to get there.
One road. Seven step-blockers cause the jam. Watch Scope drop in, clear the road, dispatch once, return three priced quotes, and award one vendor. Then it loops.
Without Scope
- Rate variance+15-25%Rack rates
- Leakage+10-15%Hidden admin fees
- Total premium20-30%Blind inflation
With Scope
- Off the blind premium20-30%saved
- Time to first bid10 minThree priced quotes
- Touchpoints1AI calls Scope
You ask your AI.
Inside Claude, ChatGPT, Microsoft Copilot, or any MCP-compatible AI - whatever your team uses. Plain language. Your own words. No form fields.
Your AI calls Scope. Quotes come back.
Integrated agencies expose their calendar, rate cards, capacity, and credentials through APIs. Scope queries them in real time, runs credential and conflict checks, scores against your past engagements, and returns anonymized quotes - in seconds, not days. No bid windows. Watch the dispatch happen below.
The demo below re-runs each time you change this. Reduced-motion users see the final state immediately.
- Scope createdBuyer 0s
- Dispatched to 5 vendorsSystem +3s
- 5 quotes returnedVendors +47s
- Quote awarded to Vendor ABuyer +1m
- Vendor accepted engagementVendor +2m
- Calendar booked for May 28System +3m
The work gets done. The lifecycle is managed.
One reply confirms the booking. Calendar updates auto-sync. Status streams back to your AI as the work progresses - on-site, in progress, complete, delivered. Reschedule, modify, follow up - all through the same AI workflow. Payment closes out automatically. The entire engagement, start to finish, in one AI workflow.
"Reschedule the Bakersfield depo to Wednesday morning."
"Add a videographer to the Tuesday booking."
"What's the status on the records request?"
"Cancel and find a different reporter."
"Open a new scope for the records subpoena from page 47."
"(Automatic - vendor paid via Scope when buyer pays.)"
Three things you used to do.
All replaced by one request.
Whichever surface your team already lives in, Scope kicks in there.
You don't learn Scope's UI. You forward an email, type into your AI, click in Clio, or fill a form. Scope routes the rest the same way every time.
Type into Claude, ChatGPT, Copilot, or any MCP-compatible AI.
The canonical Scope path. Plain language, your own words. Scope MCP returns named quotes inline, conflict-checked, with rates from your roster's locked card. Award in one reply.
Structured form for complex matters or teams not on AI yet.
Multi-vendor sub-scopes, conflict matrices, confidentiality tiers, sealed-vs-named visibility - all on the form. Same backend as AI dispatch, just rendered in our chrome.
Auto-detected from a Clio matter. One click dispatches.
When a depo notice or records subpoena hits a Clio matter, Scope detects it and surfaces a dispatch card right in the matter view. Award flows back as a Clio matter task. Same pattern for Filevine, Litify, iManage.
Notice of Deposition uploaded to LP-2026-441. Bakersfield · Tue 9 AM. Dispatch a court reporter from your Scope roster?
Forward an inbound notice to dispatch@scope.bid.
Lowest-friction path for paralegals or assistants who don't use AI yet and aren't in Clio. Forward the depo notice; Scope's parser extracts the matter, replies with a quote table, one-click awards in the email thread.
Counsel,
Please find attached the formal Notice of Deposition for Plaintiff in the above-referenced matter. Date: Tuesday at 9:00 AM, Bakersfield Superior Courthouse. Video record will be required.
Best regards, J. Smith
Your matter remembers, even when your AI doesn't.
Every scope has a human-readable slug, a last-touch timestamp, and an append-only activity log. Your AI assistant in Cowork, ChatGPT, Claude.ai, or Claude Code can call the same scope_briefing tool at session start and learn what changed since your last view - quote received, vendor accepted, calendar booked. Same Scope account across every MCP-compatible AI client. No re-explaining.
Hire your next vendor in one request.
No card required. Sign up, connect your AI, and your next request becomes an instant quote.
Firms pay zero. Vendors pay only on awarded work - automatically, at the rail.
When a dispatch is awarded and the work is done, the firm pays the vendor through Scope's Stripe Connect rail. Scope's take rate comes off the top of that payment automatically. No separate invoice, no AP cycle, no platform fees billed to firms. The vendor receives the net deposit on Stripe's payout schedule.
The vendor is the merchant of record for the underlying service. Scope never holds the lawyer-client fee in escrow; the payment passes through Stripe Connect with the platform fee deducted at the rail. That structure is the load-bearing answer to ABA Rule 5.4 (fee-sharing with non-lawyers): the commission comes from the vendor's revenue, not from a lawyer's professional fee.
Deploy Scope inside your perimeter if you need to.
Most firms use Scope through the public MCP endpoint - their AI assistant calls scope.bid over HTTPS, vendors return bids, work gets done. Firms with stricter network requirements (privileged client data flowing through internal-only AI tooling, carrier-imposed network policies, CISO-mandated zero-trust posture) can run Scope's MCP gateway inside their own perimeter via Anthropic Managed Agents tunnels.
The gateway makes a single outbound connection to Scope's vendor network. No inbound firewall rules. No public endpoints. Same dispatch flow, same vendor bids, same Stripe Connect payment rail.
Beta available. Reference deployment verified on Render in under five minutes. Deployment guide ->
Now installable in Cowork, ChatGPT, Claude.ai, Claude Code, and any MCP-compatible AI client.
/plugin marketplace add github.com/scope-bid/scope-platform