Supporter plan preview

Simple plans, clear value, no pressure on people already carrying too much.

The free side should help people learn, organize, and prepare. The Supporter side should be reserved for deeper guided drafting, route clarity, source upkeep, privacy controls, and later saved work that costs money to run.

Use Free Tools Compare Supporter Tools

Plan structure

The Supporter offer has to feel useful before it asks for money.

A patient should never feel that basic help is being held hostage. The upgrade has to be about saving time, improving drafts, organizing complicated facts, and funding the expensive parts of the platform.

Always available

Free Tools

For learning, organizing, and building a basic paper trail without an account or payment.

issue education and patient-rights explainers
basic packet builders for records, medication barriers, care delays, complaints, and private stories
copy, short-copy, and print actions after the user reviews the wording
privacy reminders, source pages, and clear limits before anything is shared
plain routing to the existing page or tool that fits the problem

Use Free Tools

Best fit for harder cases

Supporter Tools

planned low yearly access

For people who need deeper guided help turning messy facts into clearer drafts and better-organized advocacy packets.

stronger provider, pharmacy, records, board, agency, insurer, and legislator drafts
route sorting when several offices may be involved and the user is not sure where to begin
direction based on reviewed official sources and maintenance rules are approved
cleaner packets that separate facts, dates, impact, privacy risks, documents, and the exact written request
future saved work only after account, consent, delete, export, and retention controls are ready

Review Supporter Tools

For people who can help more

Sustainer Option

voluntary higher support

For supporters who want the deeper tools and also want to help keep free resources available for people who cannot pay.

the same careful guided-help standards as Supporter Tools
higher fair-use access only if cost controls and safeguards support it
clear renewal, cancellation, and support-contact language before checkout exists
no special medical, legal, complaint, or agency outcome because of support level
mission support that remains separate from patient dignity and basic public help

See Trust Rules

Why pay if the site already has free tools?

The free tools are for starting. Supporter Tools are for the harder work: stronger wording, route guidance, source-guided support, privacy controls, and later saved packets. Supporter access should make a complicated advocacy task easier, not merely unlock a prettier version of the same page.

Value proof

When the facts are scattered

Free: Free Tools help collect the basic facts and create a usable first draft.

Supporter: Supporter Tools can turn those facts into a tighter recipient-specific packet with less rewriting.

Value proof

When offices keep pointing elsewhere

Free: Free Tools help document the loop and name the missing answer.

Supporter: Supporter Tools can help separate which letter belongs to the clinic, pharmacy, insurer, board, agency, or legislator.

Value proof

When wording matters

Free: Free Tools provide safe structure and plain language.

Supporter: Supporter Tools can make the message firmer, cleaner, and less likely to sound emotional, scattered, or easy to ignore.

Value proof

When someone cannot finish in one sitting

Free: Free Tools can be copied or printed from the browser.

Supporter: Future saved packets can help patients and caregivers return later, but only after privacy and account controls are ready.

What the fee is meant to cover

The public explanation should stay plain. Deeper guided help costs money to run because it needs drafting support, source maintenance, privacy safeguards, security, uptime, review work, and platform upkeep.

stronger drafting support for complicated packets
reviewed-source maintenance before source-guided routing goes live
privacy, account, export, deletion, and retention controls
security, uptime, accessibility, testing, and platform maintenance
fair-use limits that keep deeper help affordable instead of unlimited and unstable

Cautious-user trust

The plan language has to work for exhausted patients and careful caregivers.

A clean plan page should reduce fear, not add another confusing system. It should be plain about costs, privacy, limits, and cancellation before any payment flow is built.

For patients on fixed income

The free tools should still provide a usable packet. Supporter access should add depth and convenience, not basic dignity.

For caregivers helping someone else

The plan language should be easy to understand and should make clear that a caregiver may help later without mixing payment data with health details.

For older or cautious users

Buttons, renewal terms, cancellation routes, support contact, and privacy language need to be visible before any payment flow exists.

For credibility

The plan page should say what the tools do and what they do not do. No hype, fake urgency, hidden renewal, or outcome promise belongs here.

Launch rules

The plan page can exist before checkout. The payment system cannot.

This preview explains the business model and value ladder without activating subscriptions, accounts, saved work, official lookup, message delivery, or payment collection.

Payment terms first

No checkout until the value, renewal terms, cancellation route, fair-use limits, and support contact are plain.

Reviewed public sources first

No source-guided routing until official guidance has jurisdiction, route lane, last-reviewed date, and correction channel fields.

Consent before storage

No saved work until users can choose storage, understand retention, export work, and delete it.

Review before delivery

No delivery system until every message is shown to the user first and the user chooses what leaves the browser.

No outcome promises

No plan language should imply better medical care, legal results, agency action, or special influence because of support level.