The Leo suite

Products, organized by the problem they solve.

Each product starts the same way: a real, painful workflow that still runs on spreadsheets, email, and copy-paste — and a small, AI-assisted build that replaces it with something fast, auditable, and pleasant to use. Several share one engine: structured document understanding, AI agents that do real work, and clean audit trails.

Status — labeled honestly
Pilot In the hands of early real users.
Building Active development; not yet open to outside users.
Problem space · Industry-specific

Deep, narrow, regulation-shaped

Leo for Deathcare

Pilot

A compliance workspace that checks a funeral home's price lists against the FTC Funeral Rule before a regulator does.

The problem

Independent funeral homes must comply with the FTC Funeral Rule — mandatory disclosures and itemized price lists (GPL, CPL, OBCPL). Most do it by hand, with no software and real penalty exposure.

What it does

Audits pricing documents with in-browser PDF parsing, runs mandatory-disclosure and pricing-math checks, applies state-specific checklist profiles, and exports corrected templates.

Built on the FTC Funeral Rule, a published federal regulation, plus publicly available state requirements. Public law, made operational for small operators.  ·  Next.js · Clerk · Neon · Stripe

Problem space · Document & evidence automation

Turn public frameworks into software

A lot of compliance work is just reading documents and checking them against a known standard — exactly what AI is now good at, and exactly what's still done by hand today.

SOC Delta

Building

Upload a vendor's SOC 2 report and get a structured review — plus exactly what changed since last year.

The problem

SOC 2 reports are long, dense PDFs that get read by hand once a year and then forgotten. Comparing this year's to last year's is tedious and easy to get wrong.

What it does

Page-aware AI extraction with citation validation surfaces scope and exceptions, then runs year-over-year delta analysis so changes between two reports are obvious at a glance.

Built from public report structures and published criteria — the AICPA SOC 2 / Trust Services Criteria every SOC 2 report follows by definition — not from any employer-specific workflow, checklist, or confidential process.  ·  Next.js · Clerk · Neon · Drizzle · Claude API

Leo

Building

The platform behind the suite — AI-native compliance automation built on public frameworks.

The idea

The shared engine that powers the editions: structured document understanding, AI agents that do real work, and clean, citable audit trails — generalized so a new vertical is cheaper to build than the last.

How it's grounded

Encodes how published, industry-standard frameworks — SOC 2, ISO 27001, and NIST — say this work should be done, the same standards documented openly by AICPA, ISO, and NIST.

Leo for Deathcare is the first edition built on the Leo platform; more editions follow as the suite grows.  ·  Next.js · TypeScript · Claude API · Postgres

Where this is going

Directions, not products yet

The same document-understanding engine extends naturally into adjacent problem spaces. These are honest directions on the roadmap — not products with users, and I won't pretend otherwise.

Direction

Workflow automation

Generalizing the "read a document, decide, route it" pattern into a configurable layer.

Direction

Business operations

Board- and investor-ready reporting for founders without a finance or ops team.

Direction

AI productivity

Packaging the reusable agent patterns and scaffolding behind every product in the suite.

Building something adjacent? Let's talk.

Early-stage means there's room to shape what gets built. If you're a potential design partner, collaborator, or just curious, reach out.

Get in touchFollow the build