Product · Features
Features
One place for a legal team’s daily work: agents organized the way your department is, workflows that run under human approval, knowledge that answers from your own documents, and the controls and measurement that make it safe to adopt. Here is the tour.
The workspace
A single home for the day’s work. Sonata opens to a launchpad that presents your agents organized by department, so a commercial lawyer and a privacy lawyer each see the work that is theirs. Attach references so an agent works from your documents, download any response as a document, and recover deleted work for thirty days.
Today, your schedule on your home. Connect Google Calendar in one click and the day’s schedule appears on your home, read only, merged across your calendars in time order with a live now-and-next marker. Sonata never writes to your calendar.
Impact, the value you can see. Your home shows your own measured usage: your agent runs and your most-used agent, and once an administrator sets up the productivity calculator, the hours and cost given back. Usage is measured; the return is an estimate you shape, and Sonata labels which is which.
Matters (coming soon). Your active matters and deals will sync from your CLM or matter-management tool, with status, deadlines, and value in flight. Sonata reads your system of record; it never writes to it.
A Desk for the reading you follow. Add the newsletters, podcasts, and news sources you keep up with by pasting a link, and each becomes a card with its latest post. The feeds are personal to you and managed by you. Findings from your team’s watchers appear at the top of the Desk, visible to the whole organization, and dismissing one dismisses it for everyone.
Good afternoon, Olivia.
Agents and departments
Your AI counsel, organized the way a legal team is. Sonata arranges its agents into departments spanning deal work, regulatory and compliance, specialized practice areas, and operations, each holding its agents in four clearly marked tiers: Approved agents your department has vetted and tested; agents powered by Sonata that ship free and you copy to make your own; a curated library of Anthropic’s Claude for Legal agents, imported and governed inside Sonata; and My agents, the ones your own people create. A new user reads the trust model at a glance, and access follows roles, so each person sees the departments that are theirs.
General Tools, the built-ins that ship free. Every Sonata workspace comes with a set of general-purpose agents ready to use and yours to copy: a summarizer, a clause and term extractor, an obligations reviewer, a plain-language rewriter, and more. The first one we built, and the one that proves the idea behind the rest, is Document Comparison: give it an original and a revised document and it returns a plain-language explanation of what changed and a visual redline marking every edit in place. Its changes are found by deterministic code, not guessed by a model, so it cannot miss a change or invent one. It is the first of a deterministic core where the part that has to be right is not left to a model’s judgment. The Regulatory department carries its siblings, Bill Version Comparison, the Legislative History Compiler, Hearing Digest, the Docket Analyzer, and the Coalition and Stakeholder Mapper: name a federal bill and the first fetches two published text versions from Congress.gov, lists every version that exists, compares the pair with the same deterministic engine, and explains what changed, never what it means; the second compiles the bill’s record in code, its version trail, full action timeline, and committee reports with their own text, every item cited, and narrates what the record contains without inventing a citation or presenting a committee’s stated purpose as settled intent; the third digests a congressional hearing from its official record, the published transcript when it exists, or the hearing’s known record with an honest note that printed transcripts publish months after the event, every statement attributed as the record attributes it; the fourth condenses a rulemaking docket’s public comments from Regulations.gov in code, grouping exact and near-identical form letters, then identifies the positions and coalitions in what commenters actually wrote, always honest about the comments that arrive as attachments it does not read; and the fifth maps the lobbying landscape around an issue or organization from public disclosure filings on lda.gov, who filed and for whom on what, with amounts exactly as filed, and never a claim about motive, sides, or opposition, because the record does not state them.
Departments
Practice areas your team works across, each with its agents in clearly marked tiers.
Commercial
Contracts, order forms, and renewals.
Corporate
Entities, equity, and governance.
Privacy
DPAs, DSARs, and data transfers.
Litigation
Holds, disputes, and outside counsel.
Knowledge
Knowledge management without moving your knowledge. Your documents already live across the drives your team uses, and Sonata leaves them there. It reads them where they live, so your files stay a single source of truth: Sonata always works from the current version, which keeps version control intact and means no one is ever reasoning from a copy that has drifted out of sync. Point it at the folders you already use, then ask. Your files never move and their contents are never stored, only a metadata inventory. There are two ways to ask.
Research, for questions that need judgment. Research reads and reasons (non-deterministic: it weighs and interprets like a careful analyst). Ask across the folders you choose and get a clear answer backed by citations, and for each document it draws on it shows you the exact line it used, so you can check the answer against the source yourself.
Structured Query, for questions that need a count. Structured Query answers exactly (deterministic: the same question always returns the same precise, repeatable result). Ask in plain language, like how many agreements expire in 2026 or how many auto-renew, and get a precise count you can check, with a supporting quote from each matching document. And when you ask about something not tracked yet, it says so and lets you suggest it, then an administrator reviews and approves the new field before it becomes permanently queryable.
Knowledge
Keep your documents as a single source of truth. Sonata reads them where they live, always the current version.
How many agreements expire in 2026?
Interpreted as: expiration date falls in 2026.
Workflows
Multi-step legal work, built without code and run under human approval. A workflow chains agents into a repeatable process: you assemble it in a no-code builder, start from a template or from scratch, and run it supervised or autonomously. Either way, any step that would change something outside Sonata pauses for a person to approve before it acts. Every run keeps a complete step-by-step record of what ran, what was approved, and by whom. Some workflows run themselves: adopt a watcher, and it runs on the schedule you set, owned by the person who adopted it, under the same approval rules as any other run. The renewal watcher scans your agreements for upcoming expirations; the Federal Register monitor watches for new rules and notices matching the agencies and terms you choose, and can draft a client alert per finding, grounded in the document’s own data, for a lawyer to review, approve, and download; the legislative monitor watches Congress for new bills matching your policy areas and keywords (a plain text match against bill titles and summaries) and follows the bills it surfaces for new actions; and the Comment-cycle monitor watches Regulations.gov for new rulemaking activity matching your agencies and search terms, follows each rulemaking docket that opens a public comment period, and records new documents, deadline changes, and approaching deadlines, always showing the deadline exactly as Regulations.gov states it. The Federal Register and legislative monitors’ findings can become lawyer-reviewed client alerts, and a Comment-cycle finding can become a comment-letter scaffold with the client’s positions left clearly marked for the lawyer, each drafted on demand and grounded in the source’s own record. Nothing is ever sent by the system.
Review an inbound NDA
A multi-step run that works on its own, and pauses for your call before anything leaves the building.
Review the flagged terms and suggested redlines before the workflow continues.
Three terms are flagged for your attention. Approve to continue, or deny to stop here.
Admin and governance
The control surface that makes the rest safe to use. Administration in Sonata splits into two halves, the same two you see in the product: govern who can do what, and measure what it is worth.
Govern. People are managed with least-privilege roles, invitations, and reversible deactivation. Policy and access sets what the organization allows: which kinds of connections are permitted, which model new agents start with, whether agents act read-only or read-and-write, and how many documents a single research run may read. This is also where connections live: Sonata works with the systems your team already uses, from a pre-vetted catalog covering contract lifecycle, document management, e-discovery, court data, and the productivity tools around them. Google Workspace is verified end to end today; the rest of the catalog is pre-vetted and verified as each customer enables it. Connections reach only official first-party servers or servers your own organization hosts, and reading is open while any action that would change something is built to pause for a person to approve. The Audit log records privileged actions like role changes and deactivations for administrators to read.
Measure. Insights show how the organization is adopting Sonata, who is active and how usage is trending, all from real, measured usage. Productivity estimates the time and cost Sonata saves, combining that measured usage with assumptions you control like salary and time saved per task. Usage is measured; the return is an estimate you shape, and Sonata labels which is which wherever it shows a number. Evals (coming soon) will be how you check that outputs meet your standard.
Admin
Govern how your organization uses Sonata, and measure the value it delivers.
People
Your team, their roles, and the departments they work in.
Policy & access
What’s connected, who can use it, and the defaults everyone starts with.
Audit log
A record of role changes and account activity across your team.
Insights
How your organization uses Sonata, and the time and cost it saves.
Productivity
Estimate the time and cost Sonata saves, from your real usage and your assumptions.
Evals
How you check that outputs meet your standard.
Control on your terms
Sonata shapes itself to how your team already operates, not the other way around. It reaches the systems you already run, connecting to official first-party servers or to ones your own organization hosts. It is model-agnostic by design: use the AI managed through Sonata, or bring your own model-provider account and run the work under your own agreement and data boundary, so you hold the choice of model and your exposure to its cost. And a person with the expertise stays in command of the work: across every autonomy mode, anything that would change something outside Sonata waits for a human to approve. The model is a connection you control, the privacy of your work stays yours, and the expert keeps the final say.
Everything above is shipped capability, except where it is marked coming soon. For the deeper security story, start with the Trust Center; when you want to see it for yourself, get in touch.