PAXORA.
Paxora is consumer-facing software for Californians navigating divorce. The consumer surface lives at paxora.com, and a separate platform built for legal-document assistants, mediators, and family-law professionals lives at paxora.com/practitioners. Under both is one engine: deterministic document-to-form software anchored to the actual procedure of California family law.
I incorporated Paxora in July 2025, immediately after my run at 8090 ended in June. The technical core shipped in week one, with two decades of building for developers, enterprise, intelligence, and defense underneath it. What sits around that core is the harder story: every function the company needed in year one, run alone at founder altitude, and the four walls that came with it.
[THE WALLS]
Unauthorized practice of law hit first. I came in carrying an assumption that I needed an attorney co-founder, a five-figure retainer, and a legal opinion that takes months to source before software near family law could operate cleanly. Two months passed inside that assumption. I broke the paralysis the morning I called the relevant insurance carrier directly, completed the application that afternoon, and had professional liability coverage in place the same day. Terms drafted, privacy drafted, the boundary between legal information and legal advice mapped on paper. UPL itself stays. It shapes every surface above it.
Cold outbound came after. I treated email at volume as the cheapest signal available, and the early cohorts returned a conversion rate that told me the problem was the message, not the channel. I rebuilt the data infrastructure, deduplicated against prior mailer logs, segmented by ideal customer profile, and rewrote the copy until the founder voice came through cleanly. The fourth cohort broke silence, and a design partner came in inside the week.
A wrong-output failure followed, the kind that does not announce itself. A design partner used the product on her real case, and an output mismatch surfaced that she caught before the system did. She redid the work by hand. I shipped a verification harness across the form pipeline so the same drift surfaces inside the system before any future user has to absorb it. On a deterministic platform, silent drift is the failure mode I cannot tolerate.
Halfway through the run, the sidecar problem arrived. Forms generated in Paxora left the user holding documents to file somewhere else, which meant the product solved one step inside a longer workflow. I spec'd a marketplace, shelved it the same week, and put it behind an explicit gating condition: a marketplace is downstream of an active design partner running real cases. The fourth cohort bought back that condition.
[THE PARALLEL]
The way out started with becoming everything else first. Engineering was the entry point. Every other function I learned on the way and ran in parallel. Product engineering is the native register. Around that core sit product management and product design, brand identity and website front-end build, content strategy and AI-search structured data, business development, cold outbound, cohort segmentation, design-partner relationship management, sales engineering, and demo scheduling. Operations and infrastructure hold it all up: auth, payments, DevOps, performance monitoring, production deployment, and security audits. Investor work happens alongside, with each pitch iteration tightening the narrative. Across the whole run I have closed 900-plus GitHub issues over ten months, working alone.
The functions I held in my head and my hours during year one are becoming an orchestrated process. The infrastructure that absorbs them is described in Operating Mode and The Long Game.
[WHERE THINGS STAND]
Paxora is live. The consumer surface handles intake. Mediator firms, legal-document assistants, and family-law professionals come in through the practitioner surface, the segment where Paxora operates cleanly inside the UPL line. Both surfaces sit on one engine built to carry a single case across the full divorce lifecycle and every professional category that touches it. All 58 California counties have jurisdictional procedure encoded, and 33 Judicial Council forms are covered. Design partners are running active validation on real cases, with iterative releases on a monthly cadence. The same engine fronts any frontier-model marketplace willing to speak MCP, the Model Context Protocol that lets an AI assistant act on it directly. That route already carries a verified triage path, so someone in distress can reach it from inside the chat surface they are already in. The current focus is form coverage and partner validation. Consumer scale comes downstream of professional density.
[WHERE IT GOES]
Paxora is built as a jurisdictional abstraction, with California as the first surface. Adjacent states slot in without touching the core, and the same boundary extends across borders when the conditions earn it.
What carries forward is the operating system around the engine, not the engine itself. Year one built that system: every function the company needed compressed into one operator's hours, and each wall turned into a permanent process. The next substrate inherits the same system.
