Salesforce deal context in Draft templates, now in beta
Draft 3.9 templates can now pre-fill the deal-point form from Salesforce opportunity fields, read-only, with the source shown beside every value. Beta release notes.
Draft 3.9: hover any sentence, see the precedent
Draft 3.9 moves provenance from the clause to the sentence. Every sentence in a draft now carries its source: a precedent, a playbook rule, or an honest ‘composed’. What changed, and what to expect.
Running ZAAN on a sealed laptop: air-gap mode in practice
Some matters cannot touch a network. Air-gap mode runs Review, Draft and a slice of Recall on a laptop with the radio off. What works, what doesn’t, and a checklist.
2025, told quietly: what shipped, what didn’t, what we learned
Ten version numbers, three general availabilities, one model. A short account of the year, with the slips left in.
Draft 3.8: draft in English, deliver in 38 languages
Draft 3.8 produces a delivery-language version alongside the working draft, with locked defined terms, a parity check on every clause, and a confidence tier per language.
Draft 3.6: the deal-point form, and why boilerplate should write itself
Draft 3.6 introduces the deal-point form: answer the twenty or so questions that actually vary between deals, and Draft composes the rest from the playbook and voice profile. What it asks, what it assumes, where to be careful.
The parity guarantee: how we check that a Mandarin and an English draft say the same thing
A bilingual contract that differs between its two language versions is a dispute waiting for a tribunal. Here is how we test for parity, what the test catches, and what it still misses.
Draft 3.4: voice modelling on your last 200 closed deals
Draft 3.4 learns a firm’s drafting voice from its own closed deals: defined-term conventions, sentence rhythm, preferred constructions. What it learns, what it ignores, and how to check its work.