Your AI asks. Scope sources, hires, and governs.

Your AI agent, or you, names the work. Scope checks conflicts, returns named vendors priced from their rate cards, books one, and runs the job to completion - logged, governed, and paid - without leaving your tools.

You do
What Scope runs
Try it

Type a vendor request. See instant prices.

Same flow you would see inside your AI. The prices below are real, computed from each vendor's standing rate card.

The demo below re-runs each time you change this. Reduced-motion users see the final state immediately.

Step 1Type your scope
>
Step 2Scope parsed
CategoryProcess serving
JurisdictionCook County, IL (Chicago)
DeadlineMay 29, 2026
ServiceRush + affidavit return
Step 3Prices computed from rate cards
Vendor A
computing price...
Vendor B
computing price...
Vendor C
computing price...
Vendor D
computing price...
Vendor E
computing price...
Step 4Activity log
  • Scope createdBuyer 0s
  • Qualified 5 vendorsSystem +1s
  • 5 prices computed from rate cardsSystem +2s
  • Vendor A selectedBuyer +1m
  • Vendor A acceptedVendor +2m
  • Server dispatched, affidavit to followSystem +3m
Want to run this from your AI?
Install Scope in Claude, ChatGPT, Cowork, or Cursor. Two-step setup.
Install Scope ->
How the price gets there

Each price is computed, not collected.

Each vendor sets a rate card once. A base rate plus a small set of modifiers (rush, distance, after hours, skip trace) that fire conditionally on your job's attributes. Scope evaluates the formula per job. Different jobs, different prices, all from the same card. See how rate cards work.

What you don't see, but Scope handles

Behind every dispatch.

Behind every dispatch: conflicts are checked before routing, approvals are enforced when set, every matter is encrypted the moment it lands, and the system retries if a vendor doesn't respond. Status updates propagate to your CMS as the work moves. The four-step flow above is the visible surface. The protocol layer handles the rest.

Conflicts

Conflicts are a gate, not a guess.

Every Scope dispatch carries a conflict check flag. Routing halts until the check runs against your firm's client and matter database, where the ground truth lives. Scope does not replace your CMS conflict screen. It ensures the screen happens before the vendor's name leaves your firm.

The corporate-affiliation tier (vendor parent companies, VC backers, related-entity holdings) stays a separate disclosure obligation between you and your client. Scope surfaces vendor ownership data on the vendor card so that disclosure is easier to do, not harder.

Delivery

The record comes back in the format each system expects.

When the work completes, the deliverable lands back where your firm already works: status synced to your case management system, a LEDES 1998B file ready for billing, and a signed audit-and-spend link for the carrier or client. No re-keying, no PDF shuffling, no copying numbers between systems.

The same governance trail rides along: who was hired, what was paid, and when it cleared, all queryable from your AI. The job finishes the way it started - inside the tools you already use.

Try Scope on any matter. Firms pay nothing.

Explore the breadth:Workflows ->Platform ->