ContractKen is a Word-native AI copilot for contract drafting and review aimed at lawyers, legal teams, and contract-heavy in-house groups. Founded in 2021 and based in the United States, it combines Microsoft Word add-in workflow, playbook-driven review, centralized clause libraries, precedent-based drafting, defined-term and formatting checks, and AI-generated surgical redlines. First-party pricing is unusually transparent for this segment: $149/user/month monthly or $119/user/month annually for the core add-in, with no minimums and cancel-anytime terms; custom workflows, SSO, RBAC, and iManage-style integrations sit in a separate 8-12 week proof-of-concept tier. Security posture is more specific than most startups in this band: SOC 2 Type II, AWS hosting, tenant isolation, per-customer encryption keys, no public-model training on customer data, and EU/US residency on request. The strongest fit is transactional legal work where lawyers already live in Word and want playbook enforcement without moving into a full CLM interface. Evidence outside the vendor is still relatively thin: no visible G2/Capterra footprint, but LawSites covered the company, TrustRadius lists it, and Reddit/legaltech snippets show in-house lawyers naming it among actual Word add-ins they use.
Company Info
- Founded: 2021
- Team size: 1-10 employees
- Funding: $100K
- HQ: United States
- Sector: CLM & Contracting
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Contractken is used in these workflows:
Where it fits in your workflow
Before Contractken
A lawyer or in-house counsel opens a draft NDA, MSA, procurement agreement, or customer paper in Microsoft Word after receiving first-party paper, counterparty redlines, or a term sheet. The trigger is usually review pressure: find deviations, compare against playbook, or draft from precedent faster without leaving Word.
After Contractken
After ContractKen flags risks and suggests redlines, the attorney accepts/rejects edits in Word, sends the next draft to the counterparty or business owner, and then either archives the approved clause language or feeds negotiated positions back into the team's clause library and playbooks.
Integrations & hand-offs
Business or deal team -> lawyer in Word -> ContractKen for review/drafting support -> counterparty negotiation in Word/email -> final executed contract stored in DMS/CLM/repository. On larger rollouts, legal ops or KM maintains playbooks and clause bank, then hands usage back to attorneys.
Community Data
Loading practitioner-sourced data…