A prompt with a job.

Rewrite the email below to be clearer and warmer. Audience: [CLIENT_OR_PROSPECT_ROLE]. Keep all facts identical. Target length: [N] words. Tone: professional and friendly. Ask me clarifying questions if anything is ambiguous.
EMAIL:
[PASTE_DRAFT]

Try it with fake data. A long-time client, about 150 words. Paste a clumsy draft you wrote yourself, with the name and any numbers taken out.

Check it: Names, dates, requests unchanged; no new offers invented; tone not overly casual.

Using ONLY the notes below, create: (1) 5-bullet summary, (2) action items with owners/dates only if stated (else TBD), (3) a draft follow-up email with [PLACEHOLDERS] for any missing facts. Do not invent account values or recommendations.
NOTES:
[PASTE_NOTES]

Try it with fake data. A few rough bullets you invent: who met, what was discussed, and one next step. No real client.

Check it: No invented deadlines; email clearly marked DRAFT; placeholders visible.

Draft a [DURATION]-minute annual review agenda for a fictional client profile. Use only provided facts. Leave dollar amounts and recommendations as [BRACKETS]. Include prep checklist for the advisor.
PROFILE:
[PASTE_PROFILE]

Try it with fake data. Jordan & Avery Nguyen fictional profile; 45 minutes.

Check it: No fabricated performance; compliance-sensitive topics flagged for human review.

I need a plain-English explainer about [TOPIC] for [AUDIENCE]. Before drafting, ask me 5 clarifying questions. After I answer, write at a [GRADE_LEVEL] reading level in [LENGTH]. Label anything that is general education vs. something that would need personalized advice from a human professional. Do not invent rules or figures.

Try it with fake data. TOPIC=required minimum distributions (general education); AUDIENCE=busy client who likes plain English; GRADE_LEVEL=8th; LENGTH=250 words.

Check it: Not personalized advice; facts verified by advisor; firm policy on educational content — compliance officer to confirm.

Act as a careful, skeptical reviewer. List: unclear claims, missing information, tone risks, and anything that sounds like a guarantee or advice beyond the draft's intent. Do not rewrite yet — critique only.
DRAFT:
[PASTE]

Try it with fake data. Sample renewal/thanks letter with one vague promise.

Check it: Human decides which critiques to accept; no client data in paste.

Turn these rough advisor notes into a clean CRM note with sections: Summary, Client goals mentioned, Open items, Next step. Use only information present. Mark unknowns as Unknown.
NOTES:
[PASTE]

Try it with fake data. Rough bullets about Nguyen household fictional review.

Check it: No invented goals; suitable for firm CRM field lengths.

Help me prepare for a conversation about [TOPIC] with [ROLE]. Ask me 5 questions first. Then provide: talking points, questions to ask them, and phrases to avoid. This is preparation for a human conversation — not advice to the client.

Try it with fake data. TOPIC=timeline for paperwork; ROLE=fictional prospect Casey Brooks.

Check it: No manipulative scripts; stays factual.

Compare Draft A and Draft B for clarity, warmth, and risk of overclaiming. Recommend which to use as a base and what to edit. Do not invent new content.
DRAFT A:
[A]
DRAFT B:
[B]

Try it with fake data. Two short educational blurbs on the same fictional topic.

Check it: Recommendation is editorial, not product endorsement.

From this transcript, extract requests, deadlines (only if spoken), and questions. Output a checklist. Do not guess unspoken details.
TRANSCRIPT:
[PASTE]

Try it with fake data. Fake voicemail: "Hi Alex, it's Sam Patel… need the form by next Friday if possible…"

Check it: Names correct; "next Friday" not converted to a calendar date unless provided.

Create a 20-minute team huddle agenda from these priorities. Include timeboxes and an owner column. Priorities:
[LIST]

Try it with fake data. Reviews due, prospect follow-ups, ops checklist update.

Check it: Internal only; no client PII.

Draft a short thank-you email after an annual review. Tone: [TONE]. Include: thanks, 2–3 topics we covered as [TOPICS], and clear next steps as [NEXT_STEPS]. Leave any personal financial details as placeholders.

Try it with fake data. TONE=warm professional; TOPICS=goals check-in, paperwork, scheduling; NEXT_STEPS=send summary by Friday.

Check it: No performance claims; placeholders for anything firm-specific.

Turn my rough concerns into a clear list of questions for our compliance officer about using AI for [USE_CASE]. Do not answer the policy questions — just organize them.
CONCERNS:
[LIST]

Try it with fake data. USE_CASE=drafting client emails; concerns about what data is allowed.

Check it: Output is questions only; answers are for compliance officer to confirm.

Rewrite this engagement/onboarding email to be clearer and friendlier while remaining professional. Keep all factual requirements. Flag any sentence that sounds like legal advice for human review.
DRAFT:
[PASTE]

Try it with fake data. Clunky "documents we need" email for fictional client.

Check it: Deadlines accurate; no new legal promises.

Create a client-facing checklist titled [TITLE] from this internal list. Plain English. Group by category. Add a note that the list may change after review by our team.
INTERNAL LIST:
[LIST]

Try it with fake data. ID, prior year return, bank statements sample list.

Check it: No overbroad demands invented; human reviews before send.

Summarize this PUBLIC article in 5 bullets for a busy partner. Then list 3 questions we should verify with primary sources. Do not invent citations.
ARTICLE TEXT:
[PASTE_PUBLIC]

Try it with fake data. Public IRS page excerpt or news blurb (user pastes public text).

Check it: Every bullet traceable; verification questions retained.

Explain what this spreadsheet shows in plain English for a non-expert. Ask me 5 questions first about what "done" means. Do not provide tax or accounting advice — describe structure and fields only.
COLUMNS/DESCRIPTION:
[PASTE]

Try it with fake data. Invent column names such as Invoice, Amount, and Status. Do not paste a real report.

Check it: No advice; formulas labeled unverified if proposed later.

Draft a status update email about [PROJECT] to [AUDIENCE]. Include completed items [DONE], in-progress [WIP], blockers [BLOCKERS], and ask [ASK]. Tone: calm and clear. No guarantees of outcomes.

Try it with fake data. PROJECT=fictional books cleanup; AUDIENCE=business owner client.

Check it: Dates realistic vs input; no invented completion claims.

Turn this procedure narrative into a numbered checklist an admin can follow. Note any missing steps as questions back to me.
PROCEDURE:
[PASTE]

Try it with fake data. How we onboard a new bookkeeping client (fictional).

Check it: Questions captured; no silent assumptions.

From these internal meeting notes, produce tasks with owners and due dates only when stated. Add a "Decisions" section.
NOTES:
[PASTE]

Try it with fake data. Partner meeting notes sample.

Check it: TBD for missing dates.

Critique this draft for clarity, missing attachments mentioned, tone, and anything that could be read as a guarantee. Critique only first.
DRAFT:
[PASTE]

Try it with fake data. Draft requesting missing 1099s (fictional).

Check it: Human edits after critique.

Turn this FAQ into a one-page "What to expect working with us" handout. Friendly, accurate, no promises not in the source. Flag risky lines.
FAQ:
[PASTE]

Try it with fake data. A short fake FAQ: office hours, and how a client sends documents.

Check it: Compliance/marketing review before publishing — officer to confirm.

Suggest a spreadsheet formula for [GOAL] given columns [COLUMNS]. Label the suggestion UNVERIFIED — user must test on sample rows. Explain in one sentence what it does. Do not claim tax correctness.

Try it with fake data. GOAL=sum of AmountUSD where Status=Open; COLUMNS from sample.

Check it: Test on known numbers before use.

Rewrite this reminder to be firm but kind. Keep the deadline [DEADLINE] and document list [LIST]. Offer a clear way to ask for help.
DRAFT:
[PASTE]

Try it with fake data. DEADLINE=April 2, 2026 (sample); LIST=W-2s, 1099s (sample).

Check it: Deadline unchanged; tone respectful.

Create a half-page partner briefing from these bullets: priorities, risks, asks. Max 200 words. No client names if not provided.
BULLETS:
[LIST]

Try it with fake data. Busy-season staffing, software renewal, training interest.

Check it: Internal; no confidential client details.

Draft a renewal explainer email for a policyholder using ONLY the change bullets provided. Do not add coverage advice. Invite them to call with questions. Tone: clear and calm.
CHANGES:
[BULLETS]
OTHER FACTS:
[FACTS]

Try it with fake data. Fictional Morgan Ellis homeowners; deductible sample change.

Check it: No advice; changes match bullets; compliance review before real send.

Create a comparison table from the two descriptions below. Columns: Topic | Option A | Option B. Do not invent differences. Add a row "Needs human review" for unclear items.
A:
[TEXT]
B:
[TEXT]

Try it with fake data. Two fictional coverage blurbs.

Check it: No fabricated coverage; agent verifies.

Rewrite our FAQ answers into a short claims "what happens next" handout. Use only provided answers. Flag gaps as questions for our team / compliance.
FAQ:
[PASTE]

Try it with fake data. Sample FAQ about contacting agency first, timelines TBD by carrier.

Check it: No carrier rule invention.

Write 3 variants (email, SMS ≤160 chars, voicemail script) reminding [NAME] about appointment on [DATE] at [TIME] regarding [TOPIC]. No advice content.

Try it with fake data. NAME=Morgan Ellis (fake); DATE/TIME sample; TOPIC=renewal review.

Check it: Opt-out/compliance for SMS — firm policy / compliance officer to confirm.

Draft a short thank-you for a referral. Warm, professional, no exaggeration about services. Placeholders for names.

Try it with fake data. Referrer and new client fictional first names only.

Check it: Gift policy not discussed unless firm provides rules.

From notes, list follow-ups with owners. Draft one email to the client with placeholders for quotes/numbers.
NOTES:
[PASTE]

Try it with fake data. Sample review meeting notes.

Check it: Numbers only if in notes.

Review this blurb for overclaims, absolute language, and unclear terms. Suggest safer rewrites without inventing new offers.
BLURB:
[PASTE]

Try it with fake data. "We always find you the lowest price" type bad blurb (sample to fix).

Check it: Marketing/compliance review required before use.

Create 5 multiple-choice questions from this internal handout to train new CSRs. Include an answer key. Do not add facts not in the handout.
HANDOUT:
[PASTE]

Try it with fake data. Office hours + portal FAQ.

Check it: Answer key matches source.

Given these email subject lines and snippets, suggest a category label and a draft reply from templates. Categories: [LIST]. Do not auto-send language — drafts only.
EMAILS:
[LIST]

Try it with fake data. Sample subjects: billing question, COI request, claim status.

Check it: Human sends; sensitive items flagged.

From these sample approved sentences, extract a voice card: tone words, phrases we use, phrases we avoid.
SAMPLES:
[PASTE]

Try it with fake data. 3 short approved sample sentences from firm.

Check it: Voice card reviewed by principal.

Using ONLY these feature bullets, write 3 listing description variants: factual, warm, and brief. Avoid exclusionary or fair-housing-risk language. Do not invent amenities.
FEATURES:
[BULLETS]

Try it with fake data. 123 Birch Lane sample features.

Check it: Fair housing review by human; no invented sqft.

Draft a 3-email status update series for a buyer transaction using milestones [MILESTONES]. Leave dates as placeholders. Calm tone. No promises about approval or closing.

Try it with fake data. MILESTONES=application received, docs requested, appraisal scheduled (sample).

Check it: No credit/underwriting advice.

Create a friendly document request checklist for [TRANSACTION_TYPE] from this internal list. Explain why each item is needed in one short phrase if provided; otherwise ask me.
LIST:
[ITEMS]

Try it with fake data. Pay stubs, ID, bank statements (sample mortgage docs).

Check it: List matches lender requirements as provided by human.

Draft a follow-up text and email after an open house. Mention property [ADDRESS] only as given. Invite questions. No pressure tactics.

Try it with fake data. ADDRESS=123 Birch Lane (fake).

Check it: TCPA/SMS policy — compliance/firm to confirm.

Turn these notes into a TC checklist with owners and TBD dates when missing.
NOTES:
[PASTE]

Try it with fake data. Sample contract-to-close huddle notes.

Check it: No invented contingencies.

Explain this closing timeline in plain English for a first-time buyer using only the steps given. Ask 3 clarifying questions first if gaps exist.
STEPS:
[LIST]

Try it with fake data. Sample steps with placeholders.

Check it: Not legal advice; brokerage review.

Flag any absolute claims, unverifiable superlatives, or potentially sensitive language in this blurb. Suggest safer alternatives without adding new amenities.
BLURB:
[PASTE]

Try it with fake data. "Best schools / perfect for young families" style risky sample.

Check it: Fair housing awareness — human/legal review as needed.

Draft an intro email connecting [CLIENT_ROLE] to [VENDOR_TYPE]. Neutral tone; no endorsement beyond firm's allowed language [ALLOWED_LINE].

Try it with fake data. CLIENT_ROLE=buyer; VENDOR_TYPE=inspector; ALLOWED_LINE=provided by firm.

Check it: Follow firm vendor policy.

Summarize this pipeline list into: new, in-process, stuck, closing soon. Do not invent statuses.
PIPELINE:
[LIST]

Try it with fake data. Fictional deals with statuses.

Check it: Internal only.

Write a next-steps email from this checklist. Numbered. Encourage questions. No rate or approval predictions.
CHECKLIST:
[LIST]

Try it with fake data. Sample pre-contract steps.

Check it: Numbers/dates only if provided.

Rewrite this internal announcement for clarity and kindness. Keep facts. Max [N] words.
DRAFT:
[PASTE]

Try it with fake data. New AI tool access instructions (sample).

Check it: IT facts unchanged.

Produce decisions, actions (owner/date), and parking lot from notes. No invented owners.
NOTES:
[PASTE]

Try it with fake data. A few fake huddle bullets: reviews due, a software question, and who owns the follow-up.

Check it: TBD when missing.

Turn these bullets into a simple SOP with Purpose, Steps, Owners, Exceptions. Ask questions if critical gaps.
BULLETS:
[LIST]

Try it with fake data. How we schedule annual reviews (sample).

Check it: Ops owner approves before publish.

Categorize each message snippet into [CATEGORIES] and draft a reply using tone [TONE]. Flag anything sensitive for human-only handling. Drafts only — no auto-send.
MESSAGES:
[LIST]

Try it with fake data. Categories: scheduling, documents, billing, other.

Check it: Sensitive → human; firm policy on automation.

Draft an email proposing times for [MEETING] with agenda bullets [AGENDA]. Offer 3 time options as [OPTIONS].

Try it with fake data. MEETING=PACE 30 check-in; sample options.

Check it: Timezone clear.

Rewrite this new-hire checklist so a nervous new employee can follow it on day 1. Keep all required steps.
CHECKLIST:
[LIST]

Try it with fake data. Badge, laptop, tool logins sample.

Check it: Security steps not weakened.