“How do lawyers use AI without hallucinating a client into trouble?
- How do lawyers use AI without hallucinating a client into trouble?
- How do you digitize a workflow without killing the judgment that made it work?
- What's the MVP for a tool three partners will actually open twice?
- How do you ship a product that has to survive a subpoena?
- How do you design for a user whose worst day is your average Tuesday?
- How do we ship public-interest software on a non-profit budget?
Three lanes.
One bridge.
- I
Legaltech for lawyers
Tools that fit real legal work.
Intake, evidence, drafting, AI where it can be trusted. I build for the person whose name is on the filing — not for the dashboard in the deck.
- §intake
- §evidence
- §drafting
- §ai with guardrails
- II
Civic tech in the public interest
Accountability tooling that has to ship.
Enforcement-adjacent products for NGOs, watchdogs, and regulators. Built to survive a non-profit budget, a public audit, and a user having their worst day.
- §enforcement
- §moderation
- §compliance
- §public interest
- III
Product strategy for regulated domains
Thinking partner when regulation bites.
Scoping, sequencing, and MVPs for founders and teams operating where the law, the user, and the engineering all pull in different directions.
- §discovery
- §scoping
- §mvp
- §sequencing
Half a career on each side
of the same gap.
I've spent the years since 2019 building production software inside industries where regulation actually bites — ERP and indirect-tax compliance, security operations, and now civic accountability and legaltech. The pattern repeats: every regulated domain shares the same problem shape, and the engineers who can cross between them are rare. I bridge legal and tech because I've operated in both halves of that gap long enough to know which questions kill a product before they're asked.
Today I build civic-tech enforcement tooling out of Berlin under a public-interest mandate, take on selective legaltech work for law firms, and advise founders shipping in regulated domains. I don't make legal decisions. I build what the people who do need to make them well.
Selected matters.
Problem narratives from the field — public domain, no client names, no internal tools. The thinking behind the work.
- IMatter
The Illegal Comment Problem
Detecting criminally illegal speech in comment threads without drowning the humans who have to sign off on removal.
- §Filed 2026-03
- §DE · StGB
- §6 min
Read - IIMatter
Shipping Civic Tech on a $30 Budget
What changes when your entire production stack has to fit on a 4GB box, survive a public audit, and cost less than lunch.
- §Filed 2026-04
- §EU · NGO
- §6 min
Read - IIIMatter
Evidence That Holds
Building artifact pipelines where every record has to be traceable, timestamped, and reviewable by someone who wasn't there.
- §Filed 2026-04
- §DE · Evidentiary
- §7 min
Read
Latest filings.
Field notes on the problems I'm working through — product, process, and the places where law and software refuse to agree.
Open a file.
Four questions. No marketing follow-ups. I read every one myself.