The Sandstone Theory: Legal Is the Glue. So, Why Does It Keep Breaking?

Ask any General Counsel what their department does, and you'll hear some version of the same answer: we touch everything. Hiring, deals, compliance, product, finance — legal sits at the intersection of every significant decision the company makes. The department isn't a function. It's the glue.

Which makes it all the more puzzling that, for most in-house teams, the internal experience is the opposite of connected. Requests come in through six channels. Context lives in someone's head. Triage happens manually, in someone's inbox. Work gets executed in one tool, reviewed in another, approved in a third. The glue, it turns out, doesn't stick to itself.

This isn't a complaint about lawyers. It's a diagnosis of how legal departments were built — in layers, over time, with tools designed for discrete problems rather than for the department as a whole. The result is a function that is deeply embedded in the business but structurally fragmented from within.

The Four Layers That Have to Work Together

Every legal department, regardless of size or sector, operates across four fundamental layers: intake, triage, context, and work execution. When these work in harmony, legal is fast, consistent, and genuinely strategic. When they don't, legal becomes a bottleneck — not because of the people, but because of the architecture.

Intake.

Fragmentation starts here. A request from Sales arrives via Slack. A question from HR comes through email. A procurement matter gets submitted as a Jira ticket. There is no single front door. The consequence isn't just disorganization — it's invisibility. Legal leaders can't manage what they can't see, and what arrives through six different channels is, by definition, hard to see in full.

Triage.

Once a request lands, someone has to decide what it is, how urgent it is, and who should handle it. In most departments, that decision is made manually — by a senior lawyer, a legal ops lead, or whoever happens to notice the message first. This is among the most expensive uses of legal talent available. Triage is not legal judgment. It is administrative overhead dressed up as process.

Context.

Here is where the real cost compounds. A request arrives, but the context that makes it meaningful — the deal history, the counterparty relationship, the risk decisions made last quarter — is scattered across a CLM, a shared drive, an email thread from eight months ago, and the memory of a lawyer who left the company in January. Before meaningful work can begin, the team has to reconstruct the picture. That reconstruction has a name: the Context Tax. And in most legal departments, it is paid on every single matter.

Work execution.

Even once context is assembled and work begins, execution happens across a patchwork of tools that do not talk to each other. The draft lives in Word. The redline conversation happens in email. The approval sits in a ticketing system. The final version gets uploaded to a CLM that isn't connected to any of the above. Every handoff is a potential break in the chain, and there are many handoffs.

Why This Has Been Tolerated

The honest answer is that legal departments have been remarkably good at compensating for broken infrastructure through individual effort. Senior lawyers carry institutional knowledge in their heads. Legal ops teams build elaborate workarounds in spreadsheets. Teams develop informal intake with business teams that route around the official process.

It works — until it doesn't. Until the lawyer who knows everything about a major counterparty leaves. Until the spreadsheet becomes too complex to maintain. Until request volume grows faster than the team can absorb it. The fragmentation was always there. The consequences just took time to arrive.

The other reason is that, until recently, there wasn't a credible alternative. Point solutions addressed individual symptoms: a CLM for contract storage, an intake form for routing, a research tool for legal questions. But none of these solved the underlying architecture problem. They added more destinations without reducing fragmentation. In many cases, they made it worse.

Building from First Principles

What Sandstone is building is different in kind, not just degree. The premise is that legal departments shouldn't be retrofitted with AI features — they should be rebuilt around AI as a first principle. That distinction matters more than it might initially seem.

An AI-augmented department uses AI to accelerate specific tasks: summarizing a document, drafting a first pass, or flagging a deviation. The underlying architecture — fragmented intake, manual triage, scattered context — remains unchanged. The team is still paying the same taxes; they're just paying them slightly faster.

An AI-native department is structured differently from the ground up. Intake is unified, so every request enters through a system that understands it. Triage is automated, so intelligent routing replaces manual sorting. Context is attached to every matter automatically, surfaced from the systems where business information already lives. Work execution happens with institutional knowledge applied consistently, not reconstructed each time from scratch.

The result is not just a faster legal department. It is a structurally different one, where the four layers work in harmony because they were designed to, not because talented people are compensating for the gaps between them.

What This Actually Looks Like

In practice, building AI-native from the ground up means several things. It means a single intake layer that captures requests wherever they originate — Slack, email, Salesforce, Teams — without forcing business teams to change their behavior. It means triage that uses AI to classify, prioritize, and route based on matter type, deal value, and current team capacity. It means context assembled automatically from integrated business systems, so the lawyer walking into a matter walks in with the full picture already in hand. And it means work execution with living playbooks, positions that reflect the team's current standards, not a static document from two years ago.

Critically, none of this requires rebuilding the legal team's existing tools. The AI-native layer sits above the tech stack, integrating with what's already there and making it coherent. The goal is not change management; it is removing the friction that makes change management necessary.

The Stakes Are Higher Than They Appear

It is tempting to frame this as an efficiency story — save time, reduce cost, increase throughput. Those outcomes are real. But the deeper stakes are strategic.

Legal departments that operate reactively, perpetually catching up with fragmented requests, are not in a position to contribute proactively. They cannot identify patterns across matters, flag emerging risks before they escalate, or advise the business on how to structure deals rather than just reviewing them after the fact. The fragmentation doesn't just slow legal down. It keeps legal from becoming what it has the potential to be.

The companies that will look back on this moment as a turning point are the ones whose legal departments are already thinking in first principles: what should this function look like if we were building it today, with everything we now know? The answer is not more tools layered on top of a broken architecture. It is a foundation designed for the way legal work actually happens — and the way it increasingly needs to.

That foundation is what Sandstone is building. And the legal departments that are serious about being strategic partners to the business are the ones who are building on it.