praesensus
Foreseen judgment for legal

The state-aware operating spine for legal work.

Every matter. Every contract. Every deadline. One interpreted state. One recommended next action. One approval spelled out. Insight-only.

The problem

Your team owns a CLM, an eDiscovery platform, matter management, Outlook, and now a drafting AI. And a paralegal spending half their day reconciling data across them. The point tools work. The reconciliation between them doesn't.

The Praesensus difference

Praesensus is the layer that sits above the point tools you already own. It reads what they produce. It resolves identity across them. It maintains a live knowledge graph of your matters, contracts, deadlines, obligations, and counsel. And it produces one unified recommendation per decision — with the named drivers and the required approval.

Not another point tool. The substrate.

What it catches — every day, in the background

30–90 days

Missed statute of limitations

Lead time before the filing deadline lands.

5–30 days

Missed cure or notice window

A triggering event has occurred; the counter is running.

Days–weeks

Missed regulatory filing

SEC, HSR, GDPR, HIPAA reporting windows detected early.

On ingest

Unknown-to-firm obligations

Buried commitments in a portfolio contract, surfaced on first read.

On matter open

Cross-matter conflicts

Discovered before the client learns it from someone else.

Weeks ahead

Standard-form defects

A defect in a widely-used MSA template lights up across users.

Pre-production

Privilege lapse risk

Ambiguous communications flagged before disclosure.

Real-time

Settlement authority exceeded

Fail-closed HALT with reason code and named approver.

The background sentinel. Silent by design. Speaks only when it must.

The three invariants

Every claim we make reinforces three architectural commitments. They hold at every layer, in every deployment mode, for every customer.

1

Insight-only

The system observes, reasons, and advises. It never actuates on legal matters. Permanent, not a phase.

2

Fail-closed governance

Default-deny. Every advisory carries an approval-tier requirement, a reason code, and a HALT path if governance conditions aren't met.

3

Federate patterns, not privileged content

Raw privileged material never leaves the firm. Only derived typed structure and outcome patterns move across the network.

How it plugs in

Standards on one side. Legal-vendor connectors on the other. One appliance in your rack, tenant, or air-gap.

Standards-based

SAML 2.0 · OIDC · SCIM 2.0 · LDAP · syslog · REST · mTLS

Drops into your IT posture without demanding architectural change.

Legal-vendor plugins

M365 · iManage · NetDocs · Ironclad · Icertis · PACER · Westlaw · Lexis · Relativity · Clio · Aderant

Every new source is a plugin. Not a fork.

See the full architecture →

Deploy your way

Cloud tenant

Per-firm namespace, your data residency choice, continuous updates.

On-prem connected

Signed appliance in your datacenter. Federation via mTLS.

Air-gap

Zero automated outbound. Federation via signed daily pull and monthly push.

Same codebase. Same behavior. Deployment posture is a config flag, not a build target.

From day one to density

100 teams → cross-firm benchmarks turn on. 1,000 teams → federated pattern intelligence — the moat lives.

Same platform. Same subscription. Enhancements switch on at density. At scale, the network makes every advisory sharper without touching your privileged content.

Ready to see foreseen judgment in your practice?

Founding design partners: contract-heavy in-house legal teams in one of SaaS · Healthcare payer · Regional financial services · Life sciences · Renewable energy.