How long does a typical project take?

Projects ship in 4–8 weeks. We agree on scope and timeline before any code is written.

Do I need a technical team on my side?

No. We handle the integration with your existing tools and train your team on how to adjust things. If you have engineers, we'll collaborate with them.

What about our data and privacy?

Happy to sign an NDA if needed. We build against provider APIs (Anthropic, Bedrock, Vertex) using your own keys — inputs and outputs aren't used to train models by default, and every data flow is documented.

Which tools do you integrate with?

Anything with an API. Common: Gmail, Slack, Notion, Airtable, HubSpot, Salesforce, Stripe, Shopify, Zendesk, Linear, DocuSign. If something's not feasible, we tell you up front.

What happens after launch?

Every project includes 30 days of post-launch support. After that we offer a month-to-month retainer, or a clean documentation handoff so your team can maintain it.

How is pricing structured?

Projects are fixed-price based on scope. Retainers are month-to-month. Numbers are discussed on the intro call once we understand the problem.

all workflows

legal ops·workflow / contract-review

Every incoming contract read, summarized, and flagged for deviations.

Compare against your playbook. Surface risky clauses. Draft redlines. Your legal or ops team reviews a short summary — not a 40-page PDF.

fixed scope·no tech team required·ships in 4–8 weeks

§ flow

inbox

Contract received

→

floworks

Compare to playbook

→

docusign

Draft redlines

→

slack

Route to reviewer

§ problem

Sound familiar?

Every incoming contract gets 'I'll review it later' treatment.
Sales wants to move fast; legal needs 3 days minimum.
Reviewers miss the one clause that actually matters.
No two reviewers flag the same things consistently.

§ what we build

Here's the fix.

Read every incoming contract the moment it arrives.
Compare against your playbook of acceptable terms.
Flag deviations: liability caps, payment terms, IP, termination.
Draft a one-page summary with risks ranked.
Suggest redlines based on your standard positions.

§ what it's worth

review time

3 days → 2 hrs

Summary and redlines ready before a human opens the doc.

deviation catch-rate

95%+

Every playbook violation surfaced — nothing slips.

consistency

Uniform

Same risks flagged every time, regardless of reviewer.

estimates · based on typical engagements · your numbers vary with volume

§ common questions

Things people ask on the call.

NDAs, MSAs, SOWs, DPAs, vendor contracts, and customer contracts — anything in PDF or Word. Scanned PDFs work too via OCR.

No. It does the first-pass review so your lawyer or legal ops team spends time on nuanced decisions rather than reading boilerplate. Final signoff is always human.

Yours. During setup, we extract your standard positions from 20–30 past approved contracts. Your legal team reviews the playbook before we turn it on.

Yes. For each flagged deviation, the system suggests your standard fallback language. Your reviewer edits as needed and exports clean tracked changes.

ready to ship this

30 minutes and a rough idea of your workflow.
That's all we need to scope it.

free · no prep · no sales pitch

Every incoming contract read, summarized, and flagged for deviations.

Sound familiar?

Here's the fix.

Things people ask on the call.

30 minutes and a rough idea of your workflow.That's all we need to scope it.

30 minutes and a rough idea of your workflow.
That's all we need to scope it.