Master AI at Work · Prompt Framework
R · C · T · F · C
The 5-Part Formula Behind Every Great AI Prompt

Most people get bad AI output because they give AI a bad brief. This framework fixes that — permanently. Master these five ingredients and you'll get dramatically better results from any AI tool, every time.

Scroll to learn
The Framework

Five ingredients. Infinite results.

Think of AI like a brilliant new hire on their first day. They're capable, fast, and eager — but they know nothing about your business, your customers, or what "good" looks like. Your prompt is their brief. The better you brief them, the better they perform.

R
Role
Tell AI who to be

The Role is the persona you assign to AI before it does anything. It's the single highest-leverage ingredient in the framework — changing the Role alone can completely transform the quality, tone, and expertise level of the output.

"You are a senior B2B sales consultant with 15 years of experience closing deals for professional services firms" produces dramatically different output than a blank prompt asking the same question. AI calibrates vocabulary, depth, framing, and assumptions based entirely on the Role you assign.
Role examples — weak vs. strong
Weak
Write me an email.
Strong
You are a senior account manager who closes deals through empathy and insight, not pressure.
Weak
Help me with HR.
Strong
You are an HR business partner with expertise in performance management at growing SMBs.
C
Context
Tell AI what it needs to know

Context is the briefing. AI knows nothing about your business, your customer, what happened yesterday, or what's at stake — until you tell it. The more specific and relevant context you provide, the more useful and accurate the output.

Context answers: Who is involved? What is the situation? What has already happened? What's at stake? Without this, AI fills the gaps with generic assumptions — which is exactly why so much AI output feels generic.
Context examples — weak vs. strong
Weak
A client is upset.
Strong
A 3-year client ($24K/year) is threatening to cancel after a missed delivery. They've emailed twice with no response. This is our highest-value relationship.
Weak
I need to write a proposal.
Strong
I'm proposing $8,500 in workflow automation to a 40-person accounting firm whose main concern is ROI timeline. They're comparing us to a competitor at $6K.
T
Task
Tell AI exactly what to do

The Task is the specific action you want AI to perform. Most people make their Task too vague — they ask for a "summary" when they mean a "3-bullet executive brief" or ask AI to "help with the email" when they mean "write a follow-up that reopens a stalled conversation."

The more specific your Task, the more specific the output. "Write a follow-up email" is not a task. "Write a 4-sentence follow-up that acknowledges their budget concern, offers a smaller first engagement, and ends with a specific question" is a task.
Task examples — weak vs. strong
Weak
Write a job description.
Strong
Write a job description that emphasizes culture fit and day-to-day reality over credentials. Lead with a punchy intro, then use two short bullet sections.
Weak
Summarize this data.
Strong
Turn this financial data into a 3-paragraph executive narrative: what happened, why, and what we're doing about it.
F
Format
Tell AI how the output should look

Format controls the structure, length, tone, and style of what AI produces. Without explicit Format instructions, AI defaults to its own preferences — which are often too long, too formal, or structured in a way that doesn't match your actual use case.

Format answers: How long? What structure? What tone? What should it look like? Bullets or prose? Table or narrative? 3 sentences or 3 paragraphs? Professional or conversational? Specify it, and you'll never have to manually reformat AI output again.
Format examples — weak vs. strong
Weak
(No format specified)
Strong
Under 100 words. Subject line included. Warm and direct tone. End with a yes/no question. No bullet points.
Weak
Make it professional.
Strong
3 sections: Problem, Solution, ROI. Each section: 1 heading + 2–3 sentences. Executive audience. No jargon. Under 300 words.
C
Constraints
Tell AI what to avoid

Constraints are the guardrails. They protect your brand voice, prevent AI from using language you hate, and stop it from making assumptions that undermine the output. Most beginners skip this step. Experts never do.

Constraints are where you regain control. "Never say 'just checking in'" — "Don't mention price" — "Avoid corporate jargon" — "Don't start with I" — these small guardrails make the difference between output that sounds like AI and output that sounds like you.
Constraint examples — weak vs. strong
Weak
(No constraints)
Strong
Never start with "I". Don't say "I hope this finds you well." No "synergy" or "value-add." Avoid sounding salesy.
Weak
Keep it short.
Strong
Maximum 4 sentences. Do not include bullet points. Do not mention our pricing. This email should feel human, not templated.
Framework in Action

Same task. Completely different results.

Here's the same request — a sales follow-up email — with and without R·C·T·F·C. Read both outputs and decide which one you'd actually send.

❌ Without R·C·T·F·C

The Prompt

"Write a follow-up email to a client."
What you get
Dear [Client Name],

I hope this email finds you well. I wanted to follow up on my previous email regarding our services. Please let me know if you have any questions or would like to discuss further.

I look forward to hearing from you.

Best regards,
[Your Name]
✓ With R·C·T·F·C

The Prompt

"You are a senior B2B sales consultant. I sent a $6,500 proposal to a 25-person accounting firm 5 days ago — no reply. They mentioned budget concerns. Write a 4-sentence follow-up that reopens the conversation without pressure. Include a subject line. Never say 'just checking in.' Don't mention price."
What you get
Subject: One question before you decide

Hi Sarah, wanted to check in before the quarter closes — I know Q2 is when firms like yours tend to feel the reporting squeeze most. Rather than the full engagement, would it be worth a 20-minute call to walk through which piece delivers the fastest ROI? Happy to work backwards from your timeline. Would Thursday work?
How to Use It

Build your first prompt
in 5 minutes

Follow these steps every time. After about 20 prompts, the framework becomes instinctive — you'll stop thinking about the letters and start thinking directly in terms of what AI needs to know.

1
RStart with the Role
Before you type anything else, decide who AI should be. Think about what expertise you actually need. A 15-year CFO? A UX copywriter? A labor attorney? The more specific the role, the more calibrated the output.
2
CDrop in your Context
Brief AI like you'd brief a new hire. Who is involved? What's the situation? What's already happened? What's at stake? Give AI the specifics it needs to stop guessing and start knowing.
3
TDefine the Task precisely
Be specific about the action. Not "help me write an email" — "write a 4-sentence follow-up that reopens a stalled conversation and ends with a yes/no question." The difference in output quality is dramatic.
4
FSpecify the Format
Tell AI exactly how you want the output structured. Length, tone, voice, structure — all of it. Think about how you'll actually use the output and work backward to the format that serves that use case best.
5
CAdd your Constraints
What should AI avoid? Think about the phrases you hate, the tone that's wrong for this situation, the topics to stay away from, the length limits. Two or three sharp constraints protect everything you've built in the first four steps.
6
↻ Iterate, don't restart
The first output is a draft, not a final. Say "make it shorter," "redo the opening in a warmer tone," or "remove the second paragraph." AI holds the full context in the conversation — build on it instead of starting over.
Prompts by Role

Real prompts for real work

Every prompt below is fully built using R·C·T·F·C. Copy it, fill in the brackets, and run it. Then tweak one variable and run it again.

Proposal Drafting⏱ Saves 2–3 hrs per proposal
R — Role
You are a senior B2B consultant with 15 years of experience winning proposals for professional services firms.
C — Context
Client: [company name, size, industry]. Their pain point: [specific problem]. Our solution: [what you offer]. Their main concern: [price/ROI/timeline].
T — Task
Write a 1-page executive summary proposal that leads with their pain, not our capabilities.
F — Format
1 punchy intro paragraph + 3 specific ROI bullets + 1 risk mitigation sentence + confident closing CTA. Under 400 words.
C — Constraints
No jargon. Don't lead with our company name or history. Don't mention price unless specifically asked.
Full prompt to copy
"You are a senior B2B consultant with 15 years of experience winning proposals. Client: [company name, size, industry]. Their pain point: [specific problem]. Our solution: [what you offer]. Write a 1-page executive summary proposal that leads with their pain, not our capabilities. Use: 1 punchy intro paragraph, 3 specific ROI bullets, 1 risk mitigation sentence, confident closing CTA. Under 400 words. No jargon. Don't lead with our company name."
Follow-Up Email⏱ Saves 20 min per follow-up
Full prompt to copy
"You are a senior sales consultant who closes deals through warmth and insight, not pressure. I sent a [price] proposal to [prospect description] [X] days ago — no response. Context: [any relevant details]. Write a follow-up email that reopens the conversation without desperation, ends with a specific easy question. Under 4 sentences. Include a subject line. Never say 'just checking in' or 'I hope this email finds you well.'"
SOP Writing⏱ Saves 1–2 hrs per process
R — Role
You are an operations director who writes clear, usable standard operating procedures.
C — Context
Process: [name]. Who does it: [role]. How often: [frequency]. Tools involved: [list].
T — Task
Write a complete SOP with purpose statement, numbered steps, responsible party for each, and a "watch out for" notes section.
F — Format
Max 8 steps. Each step: action verb + who + what + any tools used. Add a "Definition of Done" at the end.
C — Constraints
Plain language only. No internal acronyms without explanation. No steps longer than 2 sentences.
Full prompt to copy
"You are an operations director who writes clear, usable SOPs. Process: [name]. Who does it: [role]. How often: [frequency]. Tools: [list]. Write a complete SOP with: 1-sentence purpose statement, numbered steps (max 8), responsible party for each, 'watch out for' notes, and a Definition of Done. Plain language only. No internal acronyms. No steps longer than 2 sentences."
LinkedIn Post⏱ Saves 1 hr of ideation
Full prompt to copy
"You are a B2B social media strategist who writes LinkedIn posts that get real engagement. Topic: [topic]. Audience: [who follows this account]. Write 3 post variations — each with a different hook: (1) counterintuitive statement, (2) specific data point, (3) short story lead. Each under 150 words. No hashtags. No 'Excited to share...' openings. End each with 1 engagement question."
Email Campaign⏱ Saves 3–4 hrs of sequence planning
Full prompt to copy
"You are an email marketing specialist. Campaign goal: [goal]. Audience: [describe]. Offer: [what we're promoting]. Write a 3-email nurture sequence: Email 1 (welcome/value — no pitch), Email 2 (education + social proof), Email 3 (soft CTA). For each: subject line (under 8 words), preview text, body (under 120 words), CTA button text. Conversational, not salesy."
Job Description⏱ Saves 1–2 hrs per open role
Full prompt to copy
"You are an HR director who writes job descriptions that attract great people, not just qualified ones. Role: [title]. Company culture: [2 sentences]. Day-to-day reality: [what they'll actually do]. Must-haves: [3 real requirements]. Write with: 1 culture-forward intro, 'What you'll own' (5 bullets), 'What we're looking for' (4 bullets — behaviors not credentials), short human CTA. Under 350 words. No 'rockstar' or 'ninja.' No 'competitive salary.'"
Performance Review Language⏱ Saves 30–60 min per review
Full prompt to copy
"You are an HR business partner. Employee role: [role]. My raw feedback notes: [paste bullet points]. Rewrite this as professional, specific, growth-oriented performance review language. For each point: describe the observed behavior, state the business impact, give a specific developmental suggestion. No vague praise. No personality statements. No 'great attitude.' Keep the honest assessment intact."
Executive Financial Summary⏱ Saves 1 hr of board prep
Full prompt to copy
"You are a CFO-level financial communicator. Raw data: [paste your figures]. Audience: non-finance executives. Write a 3-paragraph executive summary: (1) What happened — key result in plain language, (2) Why it happened — 2–3 root causes, (3) What we're doing about it — concrete actions and timeline. Under 180 words. Flag the ONE number that demands their attention. No acronyms. No hedging."
All-Hands Communication⏱ Saves 1–2 hrs of careful drafting
Full prompt to copy
"You are an experienced CEO communicator. Situation: [describe — growth news, hard news, change, vision update]. Tone needed: [transparent / energizing / honest-about-challenges]. Write an all-hands email (200–300 words) that: opens with a headline humans want to know, tells the full story without spin, acknowledges what's hard, ends with a clear call to action. Leadership voice, not PR voice. No 'exciting opportunity.' No 'transformation.'"
Decision Memo⏱ Saves 2 hrs of strategic writing
Full prompt to copy
"You are a chief of staff writing for a CEO audience. Decision: [describe]. Context: [what's driving this, what's at stake]. Write a 1-page strategic memo with: 1-paragraph situation summary, 3 genuine options with trade-offs, a recommendation with clear rationale, implementation dependencies, metrics for success. Concise. No waffling. The reader should be able to decide after reading this once."
What Not to Do

The 6 mistakes
everyone makes at first

Every one of these is fixable with one more line in your prompt. Recognizing them is half the battle.

01
Being too vague
The fix
Add Role + Context before your Task. Specificity is the single highest-leverage change you can make to any prompt.
02
Accepting the first output
The fix
The first output is a draft. Say "make it more [X]" or "redo the opening with [Y]." Iteration is the game, not perfection on attempt one.
03
Skipping the Format
The fix
Always specify structure, length, and tone. If you'll spend more than 30 seconds reformatting the output, you forgot the Format block.
04
No Constraints
The fix
Constraints protect your brand voice. "Never say X" and "avoid jargon" turn generic AI output into something that sounds like you.
05
Restarting instead of iterating
The fix
AI holds the full conversation context. Build on what's there — "now make it shorter" or "add a version for LinkedIn" — don't start fresh every time.
06
Pasting sensitive data
The fix
Never paste client names, financial records, or PII into public AI tools. Use placeholders like [client name] and fill them in after you copy the output.
Quick Reference

Your desk reference card

Save this. Print this. Screenshot this. The R·C·T·F·C Framework in the smallest possible format.

R·C·T·F·C Framework — Master AI at Work
R
Role — Who AI should be
"You are a senior [role] with [X] years of experience in [domain]..." Assign specific expertise before anything else.
C
Context — What AI needs to know
Who is involved, what the situation is, what has happened, and what's at stake. Don't make AI guess.
T
Task — Exactly what to do
Specific action with specific parameters. Not "write an email" — "write a 4-sentence follow-up that reopens a stalled conversation."
F
Format — How it should look
Length, structure, tone, voice, style. Bullets or prose? How many sections? What word count? What register?
C
Constraints — What to avoid
Phrases to exclude, topics to skip, tone guardrails. "Never say X." "Avoid Y." "Don't start with Z."
Go Deeper

Put the framework
to work for your team.

The R·C·T·F·C Framework is just the beginning. Our Role-Based Prompt Engineering Workshops build this into your team's muscle memory — with prompts built for your specific roles, workflows, and business.

Book a Workshop → Join the Community Free ← Back to Home