A prompt went viral on r/ClaudeAI and r/ChatGPT at the same time this week. People weren't talking about the output. They were asking about the four-letter labels inside the structure.
Those labels are RACE. Here's what they mean, why the framework works across every major model, and the one block that matters most.
In partnership with
Replace your first 4 hires with AI. Free workshop on April 8th.
Most early-stage founders can't afford their first four hires. Sales, marketing, dev, and support alone can run hundreds of thousands in salaries.
On April 8th, AI thought leader Heather Murray shows pre-seed and seed founders how to build all four functions using AI tools. Live, with demos, for free.
Register today and get a free AI tech stack worth $5K+ including Claude, AWS credits, Make, and 90% off HubSpot.
What RACE actually is
RACE is four blocks: Role, Action, Context, Expectation. Simple to spell. Harder to execute.
Each block does a specific job. Skip one and the output quality drops noticeably. Stack all four and you get focused, useful answers from any major model.
Role: the specific lens matters
"Act as an expert" tells the model almost nothing.
"Act as someone who has watched 200 founders make the same three mistakes" tells the model how to frame risk, language, and urgency. Specificity is the whole game here.
Action: one directive verb
One clear deliverable. "Conduct a comprehensive strategic assessment." Not "help me think about my business."
Quick test: could you hand this to a human and they'd know exactly what to produce? If yes, it's specific enough. If it could mean five different things, rewrite it until it can only mean one.
Context: this is where 90% of quality actually lives
The prompt that sparked all this had 10 fill-in fields: business type, revenue stage, industry, biggest challenge, what you've tried, team size, time horizon, risk tolerance, available resources, and what your goal actually means to you.
Remove any one of them and the output degrades. Most people write a sharp Role, a clean Action, a solid Expectation, then dump three vague sentences into Context and wonder why they get generic answers.
Bad Context: "I run a small business and want to grow."
Good Context: "B2B SaaS, $180K ARR, 2-person team, 18-month runway, tried paid ads with no ROI, target market is HR managers at 50-200 person companies."
Same template. Completely different output. Treat the Context block as the actual work. Everything else is scaffolding.
Expectation: tell the model what to hand back
Without this block, the model decides the format for you. With it, you get exactly what you specified.
Name the sections, the order, the depth. "Give me these 5 sections in this order." That exact. The viral prompt asked for 8 named outputs including a 90-Day Momentum Plan and a Risk/Reward Matrix.
4x faster communication. Zero quality tradeoff.
Most people spend hours every day typing messages they could say in minutes. Wispr Flow fixes that.
Flow turns your voice into clean, polished text inside any app. Speak like you would to a colleague - tangents and all - and get professional output ready to send. 89% of messages go out with zero edits.
Use it for:
Email and Slack responses in seconds
Meeting follow-ups and project updates
Client communication on the go
Long-form writing without staring at a blank page
Millions of people use Flow daily, including teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, iPhone, and now Android -- free and unlimited on Android during launch.
*Ad
The part nobody expected
Same RACE structure, same prompt, pasted into Claude, ChatGPT, and Gemini. Claude gave harder truths. ChatGPT produced more options. Gemini went broader on market context.
But all three produced noticeably better output than an unstructured prompt. The framework doesn't make one model win. It makes all three usable.
Pro tip
Context is the block people rush. They write a detailed Role, a sharp Action, a clean Expectation, then drop three vague sentences into Context and call it done.
That's where most prompts fall apart. Give it the time it deserves.
The tool
The Reddit user who built this framework also released RACEprompt, a free app. You describe what you need in plain language, it asks 3-4 clarifying questions, then builds the full RACE structure automatically. Comes with 75+ pre-built templates.
Free tier: unlimited prompt building, 3 AI executions per day. iOS and web now, Android beta active.
Worth noting: the creator told his audience the framework is more valuable than the app. That's an unusually honest thing to say about your own product. You don't need the app to start. Write the four blocks in a doc before you open any AI tool and your prompts improve immediately.
Conclusion
Here's what we covered today:
Role needs specificity, not just a job title. "Someone who's seen 200 founders fail" beats "business advisor."
Context is where 90% of prompt quality lives. Treat it like a briefing doc, not a throwaway sentence.
Expectation locks the output format so the model can't guess wrong.
The framework works across Claude, ChatGPT, and Gemini. You don't need a new model. You need a better brief.
Your action step this week: Write all four RACE blocks in a doc before you open any AI tool. Start with Action. Then Context. Then Expectation. Then Role last. Order matters.
Poll: How did you like today's issue?
Payroll errors cost more than you think
While many businesses are solving problems at lightspeed, their payroll systems seem to stay stuck in the past. Deel's free Payroll Toolkit shows you what's actually changing in payroll this year, which problems hit first, and how to fix them before they cost you. Because new compliance rules, AI automation, and multi-country remote teams are all colliding at once.
Check out the free Deel Payroll Toolkit today and get a step-by-step roadmap to modernize operations, reduce manual work, and build a payroll strategy that scales with confidence.
*Ad