exploreAIExplore
How to Use Brew for Free vs paid plan planning
Learn Brew free vs paid plan planning with step by step workflows, realistic examples, and verified plan notes.
Brew works well for free vs paid plan planning when you run it like production work: locked brief, SOURCE facts, then review before publish. Brew is an AI email platform for on-brand campaigns, automations, and sends. Free tier is listed in catalog; verify paid tiers on brew.new. Include required facts; do not invent metrics. Start at /explore/brew.
This guide focuses on free vs paid plan planning in detail. Related Brew articles: /blog/how-to-use-brew-for-subject-line-variant-sets, /blog/how-to-use-brew-for-waitlist-launch-emails, /blog/how-to-use-brew-for-on-brand-campaign-drafts.
When this workflow is the right job
Use free vs paid plan planning when the deliverable is specifically this Brew job. Switch to subject line variant sets when that workflow already owns the asset.
Step by step workflow
1. Brief Free vs paid plan planning
Write what must stay true for free vs paid plan planning in Brew before settings or spend.
Brief: Free vs paid plan planning Keep: verified SOURCE facts only Avoid: invented pricing or features Success: one reviewable output
2. Open Brew for Free vs paid plan planning
Use the Brew surface that owns free vs paid plan planning. Do not mix a neighboring workflow in the same pass.
Surface: Free vs paid plan planning Start: pilot with one representative input Plans: brew.new
3. Pilot Free vs paid plan planning
Run a single free vs paid plan planning pilot. Score clarity, grounding, and whether the output is reviewable.
Pilot: Free vs paid plan planning [ ] SOURCE facts match [ ] Output reviewable [ ] Settings logged
4. Refine Free vs paid plan planning
Change one free vs paid plan planning dimension only. Save a template from the best run.
Refine: Free vs paid plan planning Change: one control only Keep: SOURCE and success criteria
Practical free vs paid plan planning examples
Deadline firm polite
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Deadline firm polite". Objective: Rewrite into a firm, professional message for Deadline firm polite without sending. Inputs: - Full angry draft - Recipient relationship for Deadline firm polite - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Deadline firm polite → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Deadline firm polite preserving facts, removing insults, with one clear ask.
Apology limited
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Apology limited". Objective: Rewrite into a firm, professional message for Apology limited without sending. Inputs: - Full angry draft - Recipient relationship for Apology limited - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Apology limited → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Apology limited preserving facts, removing insults, with one clear ask.
Heated thread follow
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Heated thread follow". Objective: Rewrite into a firm, professional message for Heated thread follow without sending. Inputs: - Full angry draft - Recipient relationship for Heated thread follow - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Heated thread follow → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Heated thread follow preserving facts, removing insults, with one clear ask.
Policy cite only
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Policy cite only". Objective: Rewrite into a firm, professional message for Policy cite only without sending. Inputs: - Full angry draft - Recipient relationship for Policy cite only - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Policy cite only → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Policy cite only preserving facts, removing insults, with one clear ask.
No legal invent
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "No legal invent". Objective: Rewrite into a firm, professional message for No legal invent without sending. Inputs: - Full angry draft - Recipient relationship for No legal invent - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for No legal invent → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for No legal invent preserving facts, removing insults, with one clear ask.
Recipient role
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Recipient role". Objective: Rewrite into a firm, professional message for Recipient role without sending. Inputs: - Full angry draft - Recipient relationship for Recipient role - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Recipient role → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Recipient role preserving facts, removing insults, with one clear ask.
Desired outcome
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Desired outcome". Objective: Rewrite into a firm, professional message for Desired outcome without sending. Inputs: - Full angry draft - Recipient relationship for Desired outcome - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Desired outcome → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Desired outcome preserving facts, removing insults, with one clear ask.
Keep facts
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Keep facts". Objective: Rewrite into a firm, professional message for Keep facts without sending. Inputs: - Full angry draft - Recipient relationship for Keep facts - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Keep facts → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Keep facts preserving facts, removing insults, with one clear ask.
Remove insults
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Remove insults". Objective: Rewrite into a firm, professional message for Remove insults without sending. Inputs: - Full angry draft - Recipient relationship for Remove insults - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Remove insults → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Remove insults preserving facts, removing insults, with one clear ask.
One ask CTA
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "One ask CTA". Objective: Rewrite into a firm, professional message for One ask CTA without sending. Inputs: - Full angry draft - Recipient relationship for One ask CTA - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for One ask CTA → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for One ask CTA preserving facts, removing insults, with one clear ask.
CC list review
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "CC list review". Objective: Rewrite into a firm, professional message for CC list review without sending. Inputs: - Full angry draft - Recipient relationship for CC list review - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for CC list review → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for CC list review preserving facts, removing insults, with one clear ask.
Subject line calm
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Subject line calm". Objective: Rewrite into a firm, professional message for Subject line calm without sending. Inputs: - Full angry draft - Recipient relationship for Subject line calm - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Subject line calm → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Subject line calm preserving facts, removing insults, with one clear ask.
Sign-off professional
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Sign-off professional". Objective: Rewrite into a firm, professional message for Sign-off professional without sending. Inputs: - Full angry draft - Recipient relationship for Sign-off professional - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Sign-off professional → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Sign-off professional preserving facts, removing insults, with one clear ask.
Do not send auto
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Do not send auto". Objective: Rewrite into a firm, professional message for Do not send auto without sending. Inputs: - Full angry draft - Recipient relationship for Do not send auto - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Do not send auto → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Do not send auto preserving facts, removing insults, with one clear ask.
Human final edit
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Human final edit". Objective: Rewrite into a firm, professional message for Human final edit without sending. Inputs: - Full angry draft - Recipient relationship for Human final edit - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Human final edit → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Human final edit preserving facts, removing insults, with one clear ask.
Save draft
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Save draft". Objective: Rewrite into a firm, professional message for Save draft without sending. Inputs: - Full angry draft - Recipient relationship for Save draft - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Save draft → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Save draft preserving facts, removing insults, with one clear ask.
Vendor refund firm
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Vendor refund firm". Objective: Rewrite into a firm, professional message for Vendor refund firm without sending. Inputs: - Full angry draft - Recipient relationship for Vendor refund firm - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Vendor refund firm → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Vendor refund firm preserving facts, removing insults, with one clear ask.
Support escalate
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Support escalate". Objective: Rewrite into a firm, professional message for Support escalate without sending. Inputs: - Full angry draft - Recipient relationship for Support escalate - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Support escalate → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Support escalate preserving facts, removing insults, with one clear ask.
HR-sensitive soft
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "HR-sensitive soft". Objective: Rewrite into a firm, professional message for HR-sensitive soft without sending. Inputs: - Full angry draft - Recipient relationship for HR-sensitive soft - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for HR-sensitive soft → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for HR-sensitive soft preserving facts, removing insults, with one clear ask.
Client complaint
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Client complaint". Objective: Rewrite into a firm, professional message for Client complaint without sending. Inputs: - Full angry draft - Recipient relationship for Client complaint - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Client complaint → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Client complaint preserving facts, removing insults, with one clear ask.
Internal disagreement
Scenario: A user pastes a heated draft into Brew for Free vs paid plan planning labeled "Internal disagreement". Objective: Rewrite into a firm, professional message for Internal disagreement without sending. Inputs: - Full angry draft - Recipient relationship for Internal disagreement - Desired outcome - Tone constraints Workflow: Paste draft → Generate polite rewrite for Internal disagreement → Edit facts → Human final review → Send manually if appropriate Requirements: - Stay within verified Brew capabilities; do not invent features. - Confirm live plan notes on brew.new before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Tool does not send email; review legal/HR sensitivity. Expected output: A rewritten email for Internal disagreement preserving facts, removing insults, with one clear ask.
How to improve free vs paid plan planning
Cut noise from free vs paid plan planning by removing extra adjectives while preserving SOURCE facts in Brew.
Raise quality by insisting on a single success check before debating style.
Make review easier by labeling fields that must never change.
Speed iteration by cloning the last good run and altering only one control.
Stabilize outputs by pinning settings after the pilot is approved.
Reduce rework by rejecting drafts that invent claims.
Improve handoffs by recording which control produced the best result.
Harden the workflow by testing an incomplete input before trusting defaults.
Prompting and usage guidance
Name the free vs paid plan planning job, audience, and success check before opening Brew.
Paste only verified facts under SOURCE so Brew cannot invent details.
Specify the deliverable shape up front.
Call out fixed details versus flexible style choices.
Ask Brew to flag unsupported claims before you accept the draft.
Limitations to respect
Check Brew plan gates for free vs paid plan planning on brew.new before you promise timelines.
Keep drafts unpublished until a human confirms SOURCE facts.
Brew can be wrong. Treat free vs paid plan planning as provisional until review.
If documentation is silent on a claim, leave it out rather than guessing.
Practical tips for this workflow
Pilot once before batching free vs paid plan planning in Brew.
Keep a reusable template with variables for free vs paid plan planning.
Separate creative instructions from SOURCE facts.
Log settings from the best run.
Common mistakes
- Skipping the pilot run before scaling volume
- Inventing pricing, quotas, or features not on official pages
- Mixing unrelated workflows in one session
- Publishing without a human review gate
Treat free vs paid plan planning in Brew as a production workflow: brief, pilot, refine, then ship with review. Related reading: /blog/how-to-use-brew-for-subject-line-variant-sets, /blog/how-to-use-brew-for-waitlist-launch-emails, /blog/how-to-use-brew-for-on-brand-campaign-drafts.