C

ClaimMaster

ClaimMaster's core is rule based. Proofreading of claims, specifications and office action responses, template drafting of sections and flowcharts, office action shells, USPTO forms and patent data downloads all run without a language model. The +Drafting and +Shells add ons bring the generative tools: drafting and rewriting text, figure descriptions, an LLM chat, office action analysis and, since version 2026.5, optional LLM proofreading with custom prompts.

Drafting tools can run retrieval augmented generation over a local workspace of selected sections from earlier applications, retrieved by meaning, and users can supply example documents to reduce hallucinations. Users are told to review responses for factual correctness, especially at higher creativity settings. Output does not cite the passages it drew on, and no accuracy figure or test is published.

Every LLM feature in ClaimMaster sends data only after the user presses a button, and the user controls exactly what is sent. Drafted text can be previewed and edited before insertion, and each prompt carries a creativity setting. LLM proofreading in version 2026.5 needs an explicit opt in at both the administrator and the user level, and all GPT features can be switched off for a whole firm on request. Nothing limits what the output may be used for or describes a review step before filing.

Thousands of patent professionals use the product, ClaimMaster says, at some of the largest corporations and law firms as well as smaller firms and solo practices, and the site quotes satisfied users without names. It was built by a practicing patent attorney and a former USPTO examiner. No named firm, dated result or method is published.

ClaimMaster warrants that the add in collects and transmits no user data, apart from patent number lookups, term definitions and LLM prompts sent at the user's request. It gives the risk of waiving attorney client privilege in cloud processing as the reason for running locally. LLM prompts go straight to the chosen provider with no intermediate server, ClaimMaster trains no models on customer data, and it has not opted in to OpenAI data sharing and says it never will.

Each user's documents stay on that user's machine, private endpoints and local models are available, and all GPT features can be turned off for a firm. These commitments sit on the security and help pages, not in the license agreement.

The license agreement makes the user solely responsible for content created with the software, which sells to patent attorneys, agents and paralegals. The help pages tell users to review LLM responses for factual correctness and to decide whether each provider's policies meet their obligations. Nothing states whether the product gives legal advice, and nothing addresses competence or supervision duties, USPTO guidance on AI use, or jurisdiction.

No AI governance position is published. It uses base models from OpenAI, Azure OpenAI and Anthropic, or local models, without fine tuning them. Nothing describes how its prompts and AI features are tested before release, who answers for them, or how output quality varies across technologies.

The add in runs locally, keeps proofreading reports on the user's computer and collects no work product. Prompts go from the user's machine straight to the configured model over HTTPS, with no ClaimMaster server in between. ClaimMaster says data sent through the API is processed and not retained, while its summary of OpenAI's policy notes that provider's 30 day abuse monitoring retention. Files uploaded to a provider during a chat are deleted when the session ends and can be deleted earlier from the add in.

Private Azure endpoints, a customer's own API keys and local models change who processes the data. No breach notification or incident practice is published.

Conformance to specifications at purchase and freedom from known malware are warranted in ClaimMaster's license agreement. Bugs are repaired, the software updated or replaced at no charge during the subscription, and a prorated refund applies when a defect cannot be fixed. Indirect and consequential damages are excluded, including any loss of confidentiality from sending data to a third party model service, and no aggregate cap is stated.

The user is solely responsible for content created with the software and indemnifies ClaimMaster against misuse, and no vendor indemnity covers output.

Microsoft Word, where drafting happens, is where ClaimMaster runs. Its help files document downloading bibliographic data, file wrappers, family trees and PDFs from the USPTO Open Data Portal, Patent Center and EPO, with background downloads for large patent and IDS lists. They also cover configuring OpenAI, Azure OpenAI, Anthropic and local LLM endpoints, and LLM summaries in the patent viewer. Bibliographic data for forms and shells can be imported from Private PAIR XML or from docketing tools as CSV, and no live connection to a docketing, document management or IP management system is described.

Installation is per user, on each Windows computer, with documents processed locally, and installs on shared servers need separate licenses. LLM calls go from the user's machine to OpenAI, to Azure OpenAI or a customer's own Azure endpoint, to Anthropic, or to a model running locally through Ollama. OpenAI's servers are stated to be in the United States. Where the private OpenAI, Azure and Anthropic models that ClaimMaster configures for subscribers run is not stated.

No SOC 2 report, ISO certification or audit is named for ClaimMaster. Its security page rests on local execution, and the API keys users store for private models are encrypted.

OpenAI's GPT models (GPT-5 among them), Azure OpenAI, Anthropic's Claude models and local models through Ollama all connect to ClaimMaster, which runs no proprietary models. It configures private, stateless OpenAI, Azure and Anthropic models for subscribers, and customers can bring their own keys or Azure endpoints. Calls go directly from the user's computer to the provider. Model support changes appear in release notes, such as the October 2026 updates for recent Anthropic, OpenAI and Ollama API changes, and no notice of changes is committed.

ClaimMaster publishes per user prices for every tier, billed monthly or annually with 20 percent off annually. Lite costs $20 a month on annual billing ($24 monthly), or $30 with shells and forms; QA costs $30; Pro costs $35, $45 with shells, $65 with drafting and $75 with both ($90 monthly). Volume discounts are 5, 10 and 15 percent at 5, 16 and 41 seats, checkout is self service through SoftwareKey, and auto renewal can be cancelled at any time.

Users download and activate the add in themselves after a 30 day trial of the full version, and firms deploying widely can get a custom installer and online training by arrangement.

Patent attorneys, agents and paralegals at firms and companies of every size use ClaimMaster, and in house attorneys use it to check outside counsel's work. Drafting covers electrical, software, mechanical and biochemical technologies. Its shells and forms are built for USPTO practice, office action analysis now reads non United States and non patent citations, and EPO data can be downloaded. It runs in Word on Windows. Where the generative tools perform less well is not stated.