Five agents handle the business around legal work. Lawyers keep judgment, client responsibility, and the craft itself.
The five agents
Each card counts the capabilities behind that agent, grouped by state. Select a card to open its capability drilldown.
What each agent can do for each job a firm is trying to get done. Verified counts are capabilities that actually run today; planned counts are prototypes without evidence yet, connected previews, or vision items.
| Job | Marketing | Sales | Admin | Finance | Client Service | Total |
|---|---|---|---|---|---|---|
Capture demand Turn strangers into inbound leads. | 14/40 | 0/1 | — | — | — | 14/41 |
Qualify and book Screen leads and put a consultation on the calendar. | 12/33 | 30/96 | — | — | — | 42/129 |
Onboard clients Sign the engagement and get the client set up. | 2/3 | 3/13 | 0/12 | 1/4 | — | 6/32 |
Run matters Draft documents, run the case, keep the file clean. | 4/10 | 12/23 | 9/57 | 0/1 | 0/1 | 25/92 |
Manage deadlines Never miss a filing, calendar entry, or statute. | 4/3 | 7/15 | 3/23 | 1/1 | 0/1 | 15/43 |
Collect payments Invoice, take payment, get paid. | 10/8 | 7/18 | 2/11 | 4/10 | — | 23/47 |
Trust accounting Keep IOLTA/trust funds clean and auditable. | 1/3 | 1/11 | 0/9 | 5/17 | — | 7/40 |
Serve clients Keep clients informed and responsive between meetings. | 2/12 | 4/13 | 3/16 | 0/5 | 1/7 | 10/53 |
Reputation & referrals Turn happy outcomes into reviews and new referrals. | 1/9 | 0/1 | — | — | — | 1/10 |
Operate the firm Security, integrations, audit, and the operating cockpit. | 6/8 | 3/6 | 1/15 | 1/5 | 1/0 | 12/42 |
| Column total | 56/129 | 67/197 | 18/143 | 12/43 | 2/9 | 155/529 |
One capability can serve more than one job, so row and column totals can exceed each agent's headline capability count.
What exists today
76 capabilities
Reachable prototype demonstrations — illustrative or database-backed, always labeled.
Available in prototype
What is being built
In-flight build step from the V13.1 tracker.
Building
Where this goes
283 capabilities
Vision items in the registry. No dates, no promises — the shape of the destination.
Vision
Roadmap horizon
Sourced from the V13.1 roadmap timeline. No specific dates — waves, outcomes, and guardrails only.
In flight — the atomic steps behind the current build wave.
Create the measurement, trust, and data spine before shipping at scale.
Turn legal demand into booked consults with measurable ROI.
Planned — the next wave after the current one lands.
Turn consults into signed, paid retained clients with less admin.
Vision — direction of travel, not a date.
Move from generic legal intake to the practice-area packs that prove highest economics.
Only build operating-system depth where integration is not enough.
Roadmap swimlane
Each lane is a wave from the V13.1 roadmap. Items show product state, delivery state, dependencies, and — when the community has voted on a matching idea — the current vote weight. Paused items stay visible so kill/defer decisions are auditable.
Create the measurement, trust, and data spine before shipping at scale.
Know exactly where visitors become leads, qualified leads, consults, retained clients, and revenue.
Route leads and ask the right intake questions without pretending all legal work is one workflow.
Make clear what AI is doing, what the lawyer does, and when attorney-client relationship may form.
Create a shared spine for leads before handoff into Clio/MyCase/Filevine/etc.
Measure AI extraction, classification, and routing quality before scaling live traffic.
Make firm/agency/client data safe enough to support legal workflows.
Let ops review bad leads, duplicate leads, failed syncs, and risky AI outputs before customers notice.
Guardrails: No pilot scale without auditability and clear AI/human boundaries.
Capture more high-intent visitors from law firm websites and Pearl/Fount demand surfaces.
Ask adaptive questions by practice area while keeping the user moving toward a consult.
Identify where the legal issue occurred and where representation is needed.
Prioritize leads needing fast response, same-day consults, or human escalation.
Score fit by practice area, firm preferences, lead economics, and disqualifiers.
Prevent firms from paying attention to repeated, fake, or low-quality inquiries.
Send leads to the right lawyer/firm based on practice, geography, value, and availability.
Give lawyers/agencies a simple, visual way to manage leads before matter creation.
Show every chat, call, SMS, email, note, booking, and handoff in one place.
Create follow-up tasks and reminders tied to lead stage and urgency.
Let prospects book consults directly against lawyer/staff availability.
Turn qualified leads into scheduled consults with clear expectations and reminders.
Recover slow responders, no-shows, and partially completed intakes.
Respond instantly when a prospect calls after hours or abandons chat.
Show which channels and campaigns produce qualified, booked, and retained clients.
Make the business case visible: leads, consults, retained clients, revenue, response time.
Push a qualified lead/consult package into the firm's system of record.
Let agencies deploy and manage Fount chat across many law-firm websites.
Capture what each lawyer wants: practice areas, geography, budget/value filters, capacity.
Rapidly test conversation, CTA, qualification, and booking flows against conversion and trust guardrails.
Capture setup barriers, must-have integrations, lost deals, and activation blockers in-product.
Summarize facts, timeline, urgency, questions, and missing info for the lawyer before consult.
Record/transcribe calls where permitted and generate follow-up notes and next steps.
Generate approved engagement letters from structured intake and firm settings.
Send, track, and store signed engagement letters without building e-sign from scratch.
Collect initial deposit/consult fee/retainer through LawPay/Stripe or PMS payment flow.
Let firms configure flat consult fees, deposits, package prices, and payment instructions.
After retainer, guide the client through next steps, documents, deadlines, and expectations.
Ask clients for needed documents and chase missing items automatically.
Provide secure intake status, document requests, messages, and signed docs without replacing PMS portal.
Revive unretained leads, old consults, and incomplete intakes with compliant follow-up.
Keep Fount and PMS aligned enough to measure retained outcomes and avoid duplicate work.
Know if retainer/deposit was paid and trigger onboarding or follow-up.
Show agencies performance across client firms: installs, leads, conversion, ROI.
Escalate uncertain, high-risk, or policy-sensitive intakes for human review before handoff.
Help law firms connect site, calendar, lead preferences, notifications, and PMS with minimal hand-holding.
Charge firms/agencies clearly for lead/workflow products with transparent invoices and cancellations.
Capture accident facts, injuries, insurance, treatment, liability, limitations risk.
Capture parties, children, assets, urgency, court dates, restraining orders, consult fit.
Capture status, forms needed, deadlines, family/work context, country/language needs.
Capture debts, assets, income, household, creditors, urgency, payment-plan fit.
Capture family, assets, beneficiaries, guardianship, plan type, package fit.
Capture charges, jurisdiction, court dates, custody/bail, urgency, conflict risk.
Prompt firms to check conflicts using captured parties before consult/retainer.
Support Spanish and other high-volume languages for legal demand capture and lawyer handoff.
Create standard tasks/checklists after intake/retainer by practice area and firm template.
Suggest next questions, summarize leads, draft follow-up, and identify missing facts.
Show firms performance vs anonymized peers by source, practice area, response time, and conversion.
Let lawyers rate leads, explain bad-fit reasons, and feed scoring/routing improvements.
Support pay-per-lead, pay-per-qualified-lead, booked-consult, subscription, or hybrid tests.
Offer basic matter timeline, tasks, files, notes, and client context after retainer.
Support simple invoices/payment plans without full legal accounting.
Generate reusable documents from intake data by practice area and firm templates.
Sync invoices/payments/customer records to accounting instead of building accounting.
Pass dates/events into a trusted docketing provider rather than calculating court deadlines.
Let lawyers move from intake/matter facts to research in Westlaw/Lexis/vLex/partner tools.
Import contacts/leads/matters from spreadsheets/old systems for no-PMS or switching firms.
Allow lawyers to accept, reject, resell/reassign, or pause leads based on capacity and fit.
Show verified attorney credentials, availability, reputation, and specialty fit.
Do not build until/unless acquiring a regulated accounting capability or deep PMS displacement is proven.
Pause trigger: Build only after explicit executive decision and legal/accounting expertise.
Use InfoTrack/Odyssey/partner ecosystem if needed; do not own fragmented courts early.
Pause trigger: If target ICP is eFiling-heavy and partner unavailable.
Partner with Relativity/Everlaw/DISCO/Filevine; not relevant for first solo/small acquisition wedge.
Pause trigger: If chosen beachhead becomes litigation-heavy/midmarket.
Do not try to clone Westlaw/Lexis/vLex; use summaries/handoff and expert verification.
Pause trigger: If legal research becomes must-have for target ICP.
Do not target full displacement until conversion/retainer OS proves pull and no-PMS segment is validated.
Pause trigger: If integrations are enough or switching costs are too high.
Use Microsoft/Google/Box/Dropbox/NetDocuments/iManage integrations; build only document workflows tied to intake/onboarding.
Pause trigger: If no-PMS/no-DMS segment demands native document storage.
Partner with Smith.ai/Answering Legal until call volume and margin justify owned ops.
Pause trigger: If partner costs exceed margin or quality hurts brand.
Not relevant to solo/small consumer-law wedge; watch enterprise/legal ops market separately.
Pause trigger: If Pearl creates separate Enterprise legal-ops product.
Defer unless Pearl picks IP law as a dedicated beachhead.
Pause trigger: If IP lead volume and willingness to pay are high internally.
Suite treemap
261 tools across 17 suites. Tile size reflects the number of tools in each suite; segment bars show the split between prototype, connected preview, and vision. Tap a tile to see the underlying tools and — in Nerd Mode — the suites it shares platform nodes with.
Aggregate: 72 prototype · 0 connected preview · 189 vision.
| Suite | Total | Prototype | Preview | Vision | Flagship |
|---|---|---|---|---|---|
| Integrations / Ecosystem | 20 | 5 | 0 | 15 | 3 |
| Intake / Qualification | 18 | 6 | 0 | 12 | 5 |
| Convert / Sales Agent | 18 | 9 | 0 | 9 | 7 |
| Documents / Knowledge | 18 | 3 | 0 | 15 | 3 |
| Litigation / Disputes | 17 | 4 | 0 | 13 | 1 |
| Acquire / Demand | 16 | 5 | 0 | 11 | 2 |
| Retainers / Billing / Payments | 16 | 8 | 0 | 8 | 3 |
| Analytics / Reporting | 16 | 3 | 0 | 13 | 1 |
| Client Service | 15 | 4 | 0 | 11 | 1 |
| Practice Management | 15 | 4 | 0 | 11 | 0 |
| Practice-Area Suites | 15 | 3 | 0 | 12 | 3 |
| Trust / Compliance | 15 | 2 | 0 | 13 | 2 |
| Marketplace / Network | 15 | 5 | 0 | 10 | 5 |
| Legal AI / Research / Drafting | 13 | 3 | 0 | 10 | 3 |
| Contracts / Transactional | 12 | 1 | 0 | 11 | 0 |
| Operations / Admin | 12 | 4 | 0 | 8 | 1 |
| Platform / Command Center | 10 | 3 | 0 | 7 | 4 |
| Total | 261 | 72 | 0 | 189 | 44 |
Recent updates
atlas_status_eventsRecent activity is restricted for signed-out visitors.
Sign in to see the live status-change feed across every Atlas item, including who made each change and why.
Community ideas are hidden for signed-out visitors. Sign in to browse, submit, and upvote what firms want next.
Sign inCommunity priorities
No community priorities yet. Sign in to submit or upvote the first idea.
Sign in to upvote or submit an idea.
Reachable demonstration — illustrative or database-backed. Never inferred.
A real provider/adapter path in a controlled preview.
An intended capability, not a current promise.
Actively in an atomic build step in the V13.1 tracker.