Drafting contracts from your own templates with AI

How the bot works

Nine steps. Reading the agreed terms, picking the template, inserting approved clauses, walking the fallback ladder and diffing the result are ordinary code and cost almost nothing to run; the model is only asked to fit approved language to the terms in front of it.

1. It starts from terms somebody agreed. The deal record, the signed proposal, the intake form: parties, dates, amounts, term, renewal, deliverables. A description of the deal in prose is not a set of terms, and a term nobody confirmed is a question rather than a guess.

2. It uses your template of record. The current version of record. The template has a version and a review date, and a draft records which version it came from so two drafts of the same agreement cannot quietly differ.

3. Clauses come out of the library, or not at all. Each clause is an approved block. There is no clause written from general knowledge, no borrowing from an agreement the library does not hold, and no sentence composed to fill an awkward gap.

4. Fallbacks follow the ladder you approved. Preferred position, acceptable alternative, the floor. When the agreed terms call for a fallback, the bot takes the next rung and names it — it does not invent a middle position that nobody has ever agreed to.

5. A blank with no approved answer is held. A cap nobody set, a governing law nobody chose, a schedule that was never written. The draft carries the blank, marked, with the question attached. A filled blank that nobody chose is worse than an obvious hole.

6. Every deviation is a diff a reviewer can read. The draft comes with a comparison against the template: what moved, which rung of which ladder, and why the terms called for it. A reviewer reads the differences instead of re-reading the whole agreement.

7. Your required and forbidden clauses are checked, not assumed. The clauses that must appear in every agreement of this kind are verified present, and the ones you never agree to are flagged if the terms would imply them. Both lists are yours and both are versioned.

8. The person who owns the template approves. The draft waits with the diff, the held blanks and the fallback rungs on top. Somebody named approves the version they read, and that version is the draft that goes to counsel or to the counterparty by a person's hand. The bot sends nothing and requests no signature.

9. It tells you which templates are out of date. The clauses that get edited every time, the fallbacks nobody ever accepts, the blanks that are always held, the templates whose review date has passed. That list is the useful output in the first month, because none of it is visible from inside a single draft.

What you configure

It can be configured to run in any business. This is what that actually means — the list of things that are yours, not ours.

Your templates

Which template is the record for each kind of agreement, its version, its review date, and who may publish a new one.

Your clause library

The approved blocks, what each one is for, which ones are required, and which combinations are not allowed together.

Your fallback ladders

Preferred, acceptable and floor positions for the terms you negotiate, with the rung below the floor marked as a person's decision.

Your limits

Caps, payment terms, notice periods, renewal and termination windows — the numbers a draft may use, and the point past which it is held.

Your forbidden terms

What you never agree to, written down once, so a draft that would imply one of them is flagged before a reviewer sees it.

Your parties and entities

Which legal entity signs what, the names and addresses of record, and which jurisdictions your templates exist for. Choosing one is a person's decision, not the bot's.

Your approvers

Who owns each template, who approves a draft, what needs a second name, and which agreements go to counsel every time.

Your intake

Which fields are required before a draft is allowed to start, and what happens when one of them arrives empty.

Your release switches

Which agreement kinds may be drafted automatically from a completed intake, which wait for somebody to ask, and whether the finished file is delivered anywhere at all. Sending is off, and signature requests are not a feature.

Transparent, and configurable by you

The dark band below is what the system will not do. This is what you can see and change — and it is how we build everything, not something invented for this page.

You see what it did, and why

Every clause in the draft names the library block and version it came from, every fallback names its rung, every held blank says what was missing, and each draft records the terms it read, the template version, the diff against that template and who approved it. A draft can be checked against your own library rather than taken on trust.

Versioned prompts you can tune yourself

The template map, the clause library, the fallback ladders, the required and forbidden lists and the prompts behind fitting language to terms are yours to tune. A change is a reviewable diff, replayed against agreements you have already signed so you can see what it would have drafted differently, and rolled back the same way.

A human in the loop wherever judgment actually matters

Reading the terms, selecting the template, inserting approved clauses and producing the diff are automatic. Whether a position is acceptable, what a clause means for you, what to concede and whether to sign are a person's — that boundary is a property of the system, not a promise about how carefully we'll use it.

Every run logged, along with what it cost

One row per draft and one per held blank: the terms it read, the template version, every clause with its library block, every fallback rung taken, the flags it raised, who approved the draft and where it went — plus token usage and cost for that run.

It can be configured to run in any business. The paper is yours: your templates, your clauses, your fallbacks, your limits, your approvers. The agreements on this page are one configuration of it, not the limit of it.

Works with your tools

This drafts in the document your team already edits, from the systems you already run. We're not selling you a contract platform, and your template library stays the record.

• Microsoft 365 and Word
• Google Workspace and Docs
• Google Drive, SharePoint or Dropbox
• A contract management tool
• A document management system
• DocuSign or a similar e-signature tool
• Salesforce
• HubSpot

Works well for

• Staffing agencies — Client agreements and contractor paperwork, produced over and over from the same handful of templates.
• Property management companies — Management agreements, vendor contracts and leases, each one the same document with different terms.
• Professional services firms — Service agreements and order forms per engagement, with terms that have to match what was sold.
• Software companies — Order forms, NDAs and data terms are routine paperwork, drafted from positions somebody has already settled.
• Restaurant and hospitality groups — Supplier agreements, event contracts and employment paperwork across more than one location.

How a rollout works

Nothing is sent on day one and nothing is signed, ever. The first milestone is agreements you have already executed, redrafted from your own template and library, so you can compare them clause by clause with the version that was signed.

1. 01Discovery

   The quote call, then a working session. We go through the agreements you produce, which template is the record for each one, where the clause library lives, your fallback positions and limits, what you never agree to, which entity signs what, and who owns each template. You get the template map, the clause inventory and a written scope.

2. 02Dry run

   Agreements you have already executed, redrafted. Nothing is delivered. You compare each draft with what was signed and read the held list — and the held list is where the work is, because a blank that is always filled by hand is a clause the library is missing.

3. 03Assisted mode

   Live on one kind of agreement. The bot produces the draft and the diff, the template owner reviews and approves, and the document goes to counsel or to the counterparty the way it always has. Who reviews and who signs does not change.

4. 04Optional limited automation

   Optional, and narrower than it sounds. A short list of agreement kinds you name, drafted from a completed intake, still unapproved and unsent, with every hard stop in force and the kill switch. Plenty of teams stop at step 03, and that's a good place to stop.

What we don't claim

• No numbers we haven't earned. No turnaround claim, no contracts-per-month figure, no accuracy percentage, no legal-cost comparison. We have not drafted your agreements. What a run takes and what it costs come out of the dry run, and they will be your numbers.
• No customer claims on this page. No names, no case studies, no logos.
• We are not your lawyers and this does not replace them. The bot assembles language somebody with a license already approved. It has no opinion on whether a term is enforceable or wise, and a page that implied otherwise would be selling you something nobody should buy.
• The library is the product, and somebody has to own it. A clause library and a fallback ladder are legal work. If yours does not exist yet, building it is the first piece of the engagement and it is worth doing whether or not a bot ever drafts from it.
• A held blank is doing its job. It would be easy to produce a draft with nothing visibly missing, and a draft with nothing visibly missing is how a term nobody chose ends up in a signed agreement. The design would rather show the hole.

Questions people ask

Can AI draft our contracts?

Yes, from your own approved material. An agent can take agreed deal terms, select your template of record, insert clauses out of your approved library, apply a fallback only from a ladder you signed off, hold any blank it has no approved answer for, and hand a draft plus a diff to the person who owns the template. What it will not do is write a clause that is not in the library or tell you what one means.

Where do the clauses come from?

Your clause library, with the block and version recorded on every clause in the draft. Nothing is composed from general knowledge and nothing is borrowed from an agreement your library does not hold.

Is this legal advice?

No. The bot assembles language a licensed person already approved, and it gives no opinion on meaning, enforceability, jurisdiction or risk. The design assumes a lawyer still reviews what matters, and it is built to make that review start further along.

What if the deal needs a clause we don't have?

The draft holds it. You see the term that was agreed, the fact that no approved block covers it, and the name of the person who has to decide. The bot does not write the missing clause.

Does it review the other side's contract?

No, and that is deliberately a different bot with its own page. Reading somebody else's paper and producing questions about it is one job; producing your paper from your own approved templates is this one.

Will it send the contract or get it signed?

No. The approved draft is handed to a person, delivery starts off, and requesting a signature is not a feature. Nothing goes to the counterparty except by somebody's own hand.

Who approves a draft?

Whoever owns the template, plus anyone your thresholds add. The draft arrives with the diff against the template, the fallback rungs it took and the held blanks on top, so the approval is a reading of the differences rather than the whole agreement.

What about governing law and jurisdiction?

Those are configured facts, not judgments the bot makes. It uses the entity, the law and the venue your templates already cover, and a deal that falls outside them is a hard stop for a person.

Is there a record of how a draft was built?

Yes, per draft: the terms it read, the template version, every clause with its library block, every fallback rung taken, the blanks it held, the flags it raised, who approved it and where it went - plus the token usage and cost for that run.