
Stop absorbing Flare's daily friction.
There's a plugin for that.
Five plugins, each targeting one bottleneck. All run locally inside Flare. No cloud, no data leaving your machine.
Trials start on install: no credit card, no sales call.
3,000+ technical writers run on this stack.

Let's walk through them.
Five plugins, five problems. Most teams start with Kaizen (free) and add from there.
New to Flare plugins? Read the educational guide first: MadCap Flare Plugins Explained →
Tired of cleaning up after ChatGPT?
$99/year per seatYour writers use ChatGPT, Copilot, or Claude. They paste the result into Flare. Variables shatter, snippets disappear, formatting goes sideways. The cleanup erases the productivity gain, sometimes twice.
AI Helper round-trips content between Flare and any AI chatbot with structure preserved. Variables stay variables, snippets stay snippets, and Markdown responses come back as properly styled Flare topics.

Style guide exists. Nobody follows it consistently.
$199/year per seatReviewers catch different issues on different days. Standards drift between writers, between releases, between languages. Manual enforcement scales with willpower, which is to say, it doesn't.
Mad Quality enforces the Microsoft Manual of Style or your own custom rules: spreadsheet-driven, bulk-scanned across whole projects. Each finding is linked to the rule it broke.

Stuck between docs-as-code and Flare?
$179/year per seatDevelopers write in Markdown. You publish from Flare. Either you keep two sources of truth (and resync forever), or you copy-paste manually (and re-introduce errors every release).
The Markdown plugin imports and exports Markdown losslessly, auto-generates TOCs from folder structure, and rewrites local links into proper cross-references. Docs-as-code and Flare stop fighting.

Stylesheet bloated with one-off combination classes?
$19.95 one-timeFlare allows one class per element. So every new visual combination becomes a new combination class. note-important-warning-blue lives in your CSS forever, alongside its forty-seven cousins.
Style Stack unlocks standard CSS composition: layer multiple classes on any element, with autocomplete, just like plain HTML. Your stylesheet shrinks instead of compounding.

Daily micro-frictions eating your week?
FreeSplitting topics by heading. Quick PDF exports. Batch tag replacements. Excel-to-Flare imports. Variable exports. None of these is big enough to automate on its own. Combined, they consume hours every week.
Kaizen bundles 40+ micro-utilities into one free plugin. It's the quickest way to feel the difference our stack makes, and it costs nothing.

Pricing at a glance.
All pricing is per seat. Monthly billing also available for AI Helper ($8.99/mo) and Mad Quality ($19/mo). Trials are fully functional and start when you install: no credit card, no meeting.
| Plugin | What it does | Price | Trial |
|---|---|---|---|
| AI Helper | Round-trip Flare content with ChatGPT, Copilot, and Claude, structure preserved | $99/year | Try 14 days |
| Mad Quality | Automated style guide enforcement and content validation, project-wide | $199/year | Try 14 days |
| Markdown | Import/export Markdown losslessly: bridge docs-as-code with structured authoring | $179/year | ⬇ Try free |
| Style Stack | Apply multiple CSS classes per element: composition without combination classes | $19.95 once | ⬇ Try 14 days |
| Kaizen | 40+ micro-utilities for daily Flare friction: topic splitting, exports, batch ops | FREE | ⬇ Get it free |
Runs locally
Your content never leaves your Flare environment.
No cloud dependency
No hosted repository, no external processing, no SaaS lock-in.
Code-signed installers
Verified publisher. Safe to install in locked-down environments.
Minimal telemetry
We collect usage stats only, never your content.
The answer is yes.
Specific questions Flare leads actually ask us. The short version is always the same.
- Can my writers use ChatGPT without breaking variables and snippets?
- Can I scan an entire project for style violations in one pass?
- Can I keep my content local, with no cloud round-tripping?
- Can I try every paid plugin before committing?
- Can I run these on Windows in a locked-down enterprise environment?
- Can I email the engineer who built the plugin if something breaks?
Try one this afternoon.
The trial is the demo. Install the one that hurts most and feel the difference today.
Plugins fix daily friction. If the problem is structural (migrations, architecture, localization cost), that's an engineering conversation. Get the free diagnosis →