In-house legal teams manage six-figure deals across Slack, email, and Jira – with no system of record. Sandstone’s 40x revenue growth in 90 days says they were waiting for one.
ENTRY ANGLES
Build relationship management layer for compliance teams with regulatory deadline enforcement · Build operational layer for infosec access review processing · Build cross-functional request tracking for procurement with counterparty history
VERTICALS
CAPABILITIES
AI workflow automation, Multi-channel intake aggregation, Knowledge graph architecture
SANDSTONE FOUNDER
“Every day, I was buried under Slack pings, procurement tickets, and redlines. Each piece of work depended on some bit of institutional knowledge hidden in someone's head or an outdated doc. — Jarryd Strydom, Co-founder & COO”
In-house legal teams at companies like Wayfair and Mercury have a workflow problem that no amount of hiring fixes. Every business unit – sales, procurement, HR, product – sends requests through different channels: Slack DMs, emails, Jira tickets, sometimes hallway conversations. The legal team triages manually, tracks in spreadsheets, and loses institutional knowledge every time someone leaves.
Sandstone calls what it built "Legal Relationship Management" – a deliberate echo of CRM, because the insight is that legal work is fundamentally relationship work. Every contract sits inside a web of counterparty history, past decisions, internal precedents, and business context. Strip that context away and you get lawyers re-doing analysis they’ve already done, or worse, contradicting positions they’ve taken before.
The platform aggregates intake from Slack, email, Jira, and 50+ other tools, then uses AI agents to triage, route, and build workflows – redlining, drafting, applying institutional knowledge. The key architectural choice: Sandstone sits on top of existing tools rather than replacing them. Nobody has to change how they send requests. The legal team gets structure; everyone else keeps their habits.
Sequoia led the $10M seed in January 2026. Six months later, Lightspeed led a $30M Series A. In the 90 days before the Series A, revenue grew 40x.
The legal AI market is crowded – Harvey, Legora, and now Anthropic’s own Claude for Legal are all competing for law firm budgets. But Sandstone isn’t targeting law firms. It’s targeting the in-house legal departments at mid-sized companies, which is a structurally different problem.
Law firms bill by the hour and need AI that makes legal reasoning faster. In-house teams don’t bill anyone – they’re a cost center trying to process an ever-growing volume of requests without proportional headcount growth. Their bottleneck isn’t legal reasoning. It’s operational: knowing what’s been asked, by whom, what the history with that counterparty looks like, and whether someone on the team already handled something similar last quarter.
This is why Sandstone’s founders chose "relationship management" as the frame instead of "legal reasoning." The 40x revenue growth suggests the diagnosis is correct – in-house teams were waiting for someone to build the operational layer rather than another document analysis tool.
The competitive moat, if there is one, will be the institutional knowledge graph. Every triage decision, every precedent applied, every routing pattern becomes training data for the system. The longer a team uses Sandstone, the more expensive it becomes to switch – not because of lock-in tactics, but because the accumulated context is genuinely irreplaceable.
The underlying pattern – "build a relationship management layer for a professional function that’s drowning in cross-functional requests" – extends well beyond legal.
Compliance teams face an identical problem: requests from every department, tracked in spreadsheets, institutional knowledge lost to turnover. But compliance has a forcing function that legal doesn’t – regulatory deadlines with actual fines. A SOX compliance team that misses a control review because the request was buried in a Slack thread faces personal liability for the compliance officer. That pain is quantifiable, which means the sales cycle is shorter and the willingness to pay is higher.
Information security is the other obvious vertical. Access reviews, vendor risk assessments, incident response triage – each involves the same pattern of cross-functional intake, manual tracking, and lost institutional context. The average enterprise processes 5,000+ access requests per quarter, and most still route them through email.
The entry angle for builders: find the internal function where request volume has outpaced the team’s ability to track it, where historical context has dollar value (a contradicted legal position costs more than a missed Jira ticket), and where the existing tooling is generic. Then build the relationship layer – the system of record that captures not just what was decided, but why, by whom, and what the counterparty history looks like.