Introducing Praesensus.
The paralegal problem, the category we're building, and the founding thesis.
After nine months of building, we're making Praesensus public.
The problem
Every in-house legal team owns a stack of point tools. A contract lifecycle platform. An eDiscovery system. Matter management. Outlook. Increasingly, a drafting AI. Sometimes a docket-alert service, a compliance tracker, a research subscription.
Each tool is competent in isolation. None of them talk to each other in a meaningful way.
The reconciliation happens in a paralegal's head. Or in a spreadsheet. Or in Slack messages exchanged at 9pm on a Tuesday. Or not at all — and the cost of not at all shows up as missed deadlines, unknown obligations, undetected conflicts, and preventable regulatory exposure.
A GC we spoke with last week captured the whole market in a sentence:
"We have Ironclad. We have Relativity. We have Clio. We have Harvey. We have a paralegal spending half her day copying between them."
The point tools work. The reconciliation between them doesn't.
The category we're building
Praesensus is not another point tool. It's not a better CLM, a better eDiscovery, a better drafting AI. Each of those categories has strong incumbents, and we don't compete with them.
Praesensus is the substrate — the layer above the point tools you already own. It reads what they produce. It resolves identity across them. It maintains a live typed 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 spelled out.
The unified operating picture doesn't exist as a product category today. Not because it isn't needed — every GC we speak to describes the pain in the first 90 seconds — but because no single point-tool vendor owns enough of the data planes to build it. Ironclad has clauses but not matters. Relativity has documents but not contracts. Harvey drafts but doesn't reconcile.
The category we're building is the layer that sits above all of them.
The three invariants
Every claim we make reinforces three architectural invariants that hold at every layer, in every deployment mode, for every customer. Break any one, and we break the brand.
- Insight-only. Praesensus advises. It never actuates on legal matters. Every action is human-approved. This is permanent, not a phase — it is the regulatory and professional-responsibility posture that keeps Praesensus on the safe side of unauthorized-practice-of-law risk.
- 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. When the system doesn't know, it stops.
- Federate patterns, not privileged content. The network moat is built without waiving privilege. Raw privileged material never leaves the firm. Only derived typed structure and outcome patterns move across the network, always with consent, differential privacy, and evidence-grade audit trail.
Foundations already tested
A thing we've never seen said in a legal-tech launch: we didn't write our own spine.
Praesensus is the fifth vertical instance of the Atlas platform family. Every core module — the seven-stage spine, the governance gate, the transition detector, the deadline forecaster, the validation harness, the runtime, and the plugin surface — is lifted intact from four production-tested siblings serving buildings, biopharma manufacturing, genetics, and critical facility infrastructure.
What we built new is the layer legal specifically needed: the Combining Layer + Knowledge Graph that produces conclusions no single legal source can reach.
Composition beats invention. We chose composition.
The evidence gate
An honest thing: every commercial claim we make about Praesensus's product performance is currently gated on one thing — closing what we call the "evidence gate."
That means: extraction precision and recommendation quality proven on real firm data with partner-labeled ground truth. Public surrogate data validates plumbing but doesn't close the gate. We won't overpromise, and we're currently pursuing design partners to close the gate honestly.
If your team owns the reconciliation pain we described up top, and you're willing to run a structured 12-week engagement with contractual success criteria, we should talk.
What comes next
Over the coming weeks and months, we'll be publishing more here on:
- The Combining Layer in technical depth
- Federated pattern intelligence and how it preserves privilege
- The two gates (evidence + privilege) and why they matter
- Insight-only as a permanent architectural commitment
- How composition across the Atlas family compressed 24 months of engineering into 12
Subscribe to the blog or find us on LinkedIn.
— The Praesensus team