TextEvidence: I Shipped a Legal Tech Platform Because I Couldn't Stop Thinking About It

3,000 screenshots. One week of paralegal time. A grocery bag full of printed texts. Here's how that problem became a production legal tech platform with 46 database tables and 432 attorneys in active outbound.

A family law attorney told me about a client who showed up to a meeting with a grocery bag full of printed screenshots. Three thousand text messages. One week of paralegal time just to sort them chronologically. And the attorney still couldn't cite a specific message in her filing because nothing was numbered.

I couldn't stop thinking about it.

The Problem That Wouldn't Leave Me Alone

Text message evidence is everywhere in family law. Custody disputes, divorce proceedings, protective order cases — the critical evidence lives in iMessage threads and WhatsApp conversations. But getting that evidence into court-ready format is a manual nightmare.

Here's what the process looks like without purpose-built tools: clients send attorneys hundreds of disorganized screenshots. Sometimes they email them. Sometimes they drop them into a Google Drive folder. Sometimes — and I'm not making this up — someone's aunt prints them out at Staples.

Paralegals spend entire afternoons organizing messages chronologically. There's no way to cite specific messages in filings because nothing has line numbers. And the attorney has to spot patterns across thousands of messages by reading every single one.

The alternative is forensic extraction software like Cellebrite — which costs $6,000+ and is overkill for family law. It's built for criminal investigations, not custody disputes.

There's a massive gap between "400 screenshots in a Google Drive folder" and "$6,000 forensic extraction." That gap is where TextEvidence lives.

What I Built

TextEvidence lets attorneys upload text message screenshots. The platform uses OCR to extract message content, automatically assigns sequential line numbers for court citation, organizes messages chronologically, and runs AI analysis to identify communication patterns relevant to the case.

The AI — powered by Claude Sonnet — looks for the specific patterns family courts care about: hostility and contempt, manipulation tactics, co-parenting cooperation or the lack of it, scheduling compliance, and financial discussions. The output is a clean, numbered exhibit for court plus an analysis summary highlighting relevant patterns.

Upload screenshots. Get court-ready exhibits. In under 60 seconds.

That last number matters. I've tested the processing pipeline against datasets of 100,000+ messages. It handles them. The platform wasn't built for small cases — it was built to scale.

46 Database Tables in Production

I'm a firm believer that the complexity of your database reflects the seriousness of your product.

TextEvidence has 46 tables in production. Organizations, users, cases, message archives, conversations, messages, AI conversation threads, AI analysis results, communication insights, emotional timelines, behavioral patterns, key moments, message sentiment, contact connections, plan limits, monthly usage tracking — and 28 more supporting tables. Full Row Level Security policies across all of them.

This isn't a wrapper around an API call. It's an enterprise-grade data model built for attorney-client privilege considerations, multi-user access within law firms, and the kind of nuanced analysis that family courts actually need.

I built the full SaaS platform — authentication, billing, AI analysis, PDF export, client portal — in approximately three weeks. That's the velocity that AI-assisted development enables when you have clear specs and know what you're building.

The 7-Agent Content Engine

Here's where TextEvidence became more than just a product. It became a proving ground.

I built an autonomous content engine on OpenClaw — my multi-agent framework — with five specialized AI roles: Keyword Researcher, Content Writer, SEO Editor, Publisher, and Performance Monitor. Each role has its own skill file, its own tools, and its own quality gates. The system runs on cron schedules and produces 3 to 5 SEO-optimized blog posts per week without human intervention.

But this isn't "AI writing blog posts." It's a complete pipeline. The Keyword Researcher identifies clusters. The Content Writer drafts based on brand voice guidelines and a target SEO score of 94/100. The SEO Editor refines. The Publisher deploys. The Performance Monitor tracks and feeds learnings back into the system.

The agents can update their own skill files based on performance data. The system gets better over time without me touching it.

A companion social media agent repurposes blog content into platform-native posts — triggered automatically when a blog publishes. The whole system compounds.

Everything I learned building this engine for TextEvidence now powers content operations across multiple ventures. The product shipped, but the methodology shipped even harder.

Claudia: The AI SDR Who Handles Replies

When it came time to go to market, I didn't want to hire an SDR. I wanted to build one.

Claudia Reyes — claudia@textevidence.ai — is an AI sales development representative who handles all reply management from the outbound campaign. She operates under a comprehensive Standard Operating Procedure with eight response categories, CRM integration through GoHighLevel, escalation protocols, a daily workflow schedule, and answers to frequently asked questions.

What makes Claudia different from most AI sales agents: the "What I Do Not Know" section. I explicitly defined the boundaries where the AI should escalate to me rather than make something up. Claudia doesn't hallucinate pricing. She doesn't invent features. She doesn't promise things I can't deliver. She handles what she can and routes the rest to a human.

That's the part most people get wrong with AI sales agents. They try to make the AI handle everything. The real skill is defining what it should not do.

The 432-Attorney Campaign

The outbound campaign targets 432 Texas family law attorneys across LinkedIn, email, and Twitter/X — five touches over 23 days. Each touch has a distinct purpose and personality. The product isn't mentioned until Touch 3. Free licenses are held back until the reply conversation.

This is the Delightful Outbound approach in action — earn the right to pitch through observational humor, genuine curiosity, and understanding their daily reality. The empathy research for this campaign went deep: what their Tuesday at 2pm looks like, things clients do that drive them quietly crazy, inside jokes about evidence preparation, specific scenarios that became campaign hooks.

The campaign launched February 18, 2026. Goal: 10 to 15 demos, 2 to 5 conversions.

The Numbers

Here's where TextEvidence stands:

The market opportunity is real: 1.1 million divorces filed in the US annually. 47 million divorce-related online searches in 2024 — the highest ever recorded. The co-parenting app market is projected to hit $1.12 billion by 2032.

And there's a distribution play I'm watching closely: Clio's platform has 150,000+ users, and their App Directory provides a direct channel to the exact attorneys who need this.

What TextEvidence Taught Me

Every venture I build teaches me something that compounds into the next one. TextEvidence taught me that the go-to-market methodology is as valuable as the product.

The Delightful Outbound approach I developed for this campaign? It's now a codified AI skill file I use across every venture. The PRD Builder skill I created for writing specs? Same thing. The LinkedIn Profile Optimization methodology? Codified.

TextEvidence is both a product and a methodology laboratory. Every framework I develop for one engagement gets extracted, documented, and deployed across the whole ecosystem.

The platform processes text evidence for attorneys. But the real output is a set of repeatable systems that make the next thing I build faster and sharper.

That's the part I love most about being a builder — the compounding.

← Back to Writing Work With Me →