All posts

ProductApril 26, 2026·4 min read

Why we built CheckMyDoc

Most founders we know have a stack of unsigned contracts in a tab labeled "need to read". The MSA from a vendor. The side letter from a new investor. The employment offer for the engineer they're trying to hire next week. The privacy policy template they grabbed off a competitor and never quite adapted.

These contracts have risk hiding in plain sight. Auto-renew clauses with 90-day notice windows. Liability caps that don't survive confidentiality breaches. IP assignment language that quietly claims your prior art. Termination-for-convenience clauses that only run one way. Stuff a lawyer would catch in 20 minutes — but the lawyer costs $600 and won't get to it until next week, and the contract needs to be signed today.

So founders sign anyway, and pretend they read it.

What we wanted

Two minutes from upload to redline. Plain English. Cite the clause. Suggest the change. Make it good enough that you'd actually use it before forwarding to your lawyer — not as a substitute, but as a way to walk into the attorney conversation already knowing what to push back on.

How we built it

CheckMyDoc is built on Anthropic's Sonnet 4.5 for deep review and Haiku 4.5 for fast classification. The classifier reads roughly the first 1,500 words and routes the doc to the right deep-review prompt — NDA, MSA, employment, ToS, vendor agreement, and so on. Sonnet then runs a purpose-built analysis prompt for that type, returns risk-scored findings, and proposes redlines as paired original / proposed / why objects.

We never train on your contracts. They go to the Anthropic API with team and user metadata for traceability and live in encrypted Cloudflare R2 storage. Hard-delete on request, within 30 days.

What's next

Phase 4 is Stripe (we're building this in public). Phase 6 ships the AI pipeline. Phase 11 is when we deploy to Railway and you can actually use it.

Until then — sign the next contract carefully.