Spellbook's Dependence on Word Add-in

This risk matters because Spellbook is not just renting Microsoft for distribution, it is building on the exact screen where Microsoft is now adding native legal workflow. Spellbook works because lawyers already live inside Word, but that also means Microsoft controls discovery, admin permissions, billing rails, and increasingly the default AI experience for contract review, redlining, and playbook based checking inside Word itself.1 2 3 4 5

• Spellbook’s wedge is real because contract lawyers still do core drafting and markup in Word. Prior research on Spellbook describes legal work as historically stuck in unstructured Word documents, which made a Word native assistant the fastest path to adoption versus asking firms to move into a new system.6 7
• The platform risk is becoming more concrete because Microsoft now offers legal skills inside Copilot for Word, including redlining with tracked changes and playbook based contract review. That means the baseline product a buyer gets from existing Microsoft 365 spend is moving closer to Spellbook’s core workflow.1 2 3
• Competitors show the two escape routes. DraftWise stays in Word but differentiates with firm specific precedent retrieval from systems like iManage and NetDocuments. Ironclad goes the other direction, bundling review into a larger contract system that already owns intake, approvals, signature, and storage.8 9 10

Going forward, the winners in contract AI will be the ones that own something Microsoft does not. For Spellbook, that likely means deeper legal specific data, better clause level judgment, and expansion into adjacent workflows where value comes from proprietary context rather than simply occupying the Word sidebar.1 3 8 10