Milja
CEO · Lawyer
Ran customer success and sales at Contract Mill for five years.
For in-house legal teams
Legal self-service that builds itself.
Blanks turns the contracts you already have into playbooks, templates and answers. The business asks in Teams, Slack or email and gets back a lawyer-approved agreement, ready to sign. There is no portal to learn, because nobody was going to log into one anyway.
Setup in hours, not months. Nothing sends without a lawyer's approval.
B
Blanks · Legal control panel
Meridian Oy playbook v3.2 · July 2026
25agreements this month
23handled without legal touching them
11 minof legal time spent
Agreement queue
2 need review
23 auto-handled hidden
Just now
Consultancy — Nordic Advisory
auto-drafted · 3 tailored clauses · in DocuSign
Review
MSA — DataFlow Oy
§12 liability: customer wants uncapped, outside playbook
Review
Review
DPA — Cloudia Oy
sub-processor outside EU · needs GC sign-off
Review
Signed
NDA — Innofactor Oyj
auto-drafted · signed in 2 h
Signed
Consultancy — Vertex Design
auto-drafted · signed same day
How it works
One request in. Signed agreement out.
Someone in the business writes what they need, in plain words. Blanks does the rest and keeps the lawyer in charge of anything that matters.
01
Ask
A message in Teams, Slack or email is enough. "I need a consultancy agreement for a contractor in Germany, six months." No forms, no template hunting.
02
Draft
Blanks matches the request to a playbook built from your own contracts, asks a couple of clarifying questions and prepares the document.
03
Approve
Anything outside the playbook lands in the lawyer's queue with the deviation flagged and a counter already suggested. Approve, amend or reject.
04
Deliver
The finished agreement returns on the channel it came from, ready for signature, with a status link so nobody has to chase legal for updates.
Setup is where other tools lose.
Every legal tool asks lawyers to hand-craft templates and playbooks before anyone can use it. That work takes days nobody has, and it is where adoption dies. We watched it happen for six years. Blanks reads your existing contracts and drafts the playbooks itself. A lawyer reviews them and goes live the same day.
Lawyer control
Agentic, yet predictable.
The obvious worry with AI in legal is trust. Blanks runs on one rule: nothing reaches a business user without a lawyer's approval, and every clause traces back to the contract it was learned from.
The approval gate
Drafts, redlines and playbook changes wait in a review queue until a lawyer signs off. The queue arrives prepared: deviations flagged, counters suggested, one click to decide.
Traceable to source
No raw model output ends up in an agreement. Every position points back to the contract it came from, so the lawyer can check the reasoning, not just the result.
Playbooks that stay current
Blanks collects suggested changes from real usage and queues them for review. Approve or reject. The content stays up to date without a maintenance project.
MSA — DataFlow Oy
⚠ Outside playbook · §12 Liability
Playbook caps liability at 12 months' fees. Customer wants uncapped.
"Strategic customer, €300k ARR. They threatened to walk over this." — Jussi, in Slack
Blanks suggests: counter with a 24-month cap. Accepted in 8 of 9 similar deals.
Why Blanks
Built for the person who drafts two agreements a year.
Most legal software is built for people who use it every day. Most legal requests come from people who don't.
No portal
A sales manager who needs an NDA twice a year will not log into a portal, learn a workflow or remember where anything lives. Blanks answers them where they already work.
The content builds itself
Other tools wait for a lawyer to author every template and playbook. Blanks builds them from your existing contracts and keeps them current from real usage.
A suite, not a chatbot
Behind the single point of contact sits real legal tooling: document automation, redlining, drafting. Outputs are predictable, not free-form generation.
Your positions, not the model's
Foundation models don't know how your company negotiates. That context, maintained and lawyer-approved, lives in Blanks and shapes every output.
Harvey · Legora · Juro · Spellbook
- Built for lawyers and portal power users
- The business must log in and learn a workflow
- A lawyer authors and maintains every template first
- Generic model knowledge, no company positions
Blanks
- Built for the occasional business user
- Requests arrive in Teams, Slack or email
- Playbooks build and maintain themselves from your contracts
- Your lawyer-approved positions, traceable to source
Who's building this
Six years watching this problem.
We're Milja and Andy. We met at Contract Mill, a Helsinki legal tech company, and worked side by side there for five years. Milja ran customer success and sales, Andy built the document editor and export engine.
The same two requests came up the whole time: lawyers wanted tools that build themselves, and business users wanted legal help without learning anything new. Nobody built that, so we are.
Andy
CTO
Built the document editor and export engine at Contract Mill.
See it on your own contracts.
We're onboarding a small number of design partners before the first release. Book a walkthrough with the founders.