Great prompts follow a consistent structure. While there are many ways to write an effective prompt, the most reliable approach uses five key components that can be mixed and matched based on your needs. Understanding these components and how they work together transforms you from someone who writes random prompts and hopes for good output to someone who intentionally crafts prompts that deliver.

This isn't complicated. You've been thinking about these elements intuitively your whole career. We're just naming them and showing you how to use them deliberately.

The Five Components: RCFCF Framework

The five components spell out RCFCF (which we also call "Role, Context, Task, Format, Constraints"). Let me show you what each does and why they matter.

Component 1: Role—Who Should the AI Be?

When you assign a role, you're telling the AI what lens to look through. "You are a financial analyst" produces different output than "You are a business growth consultant" for the same request. The role shapes everything.

Here are examples of roles you might assign:

• Business strategist experienced in SaaS
• Project manager with 10+ years of enterprise experience
• Marketing copywriter specializing in B2B lead generation
• Customer success expert focused on retention
• Financial analyst reviewing P&L statements

Notice these aren't generic. "Business strategist" is better than "expert." "SaaS experienced" is better than nothing. "Project manager with 10+ years of enterprise experience" is better than just "project manager." The more specific the role, the more tailored the thinking.

Component 2: Context—What Should the AI Know?

Context is where you bridge the gap between general AI knowledge and your specific situation. Without context, the AI can only offer generic advice. With context, it can offer advice tailored to you.

Here's what context typically includes:

• Company information: Size, industry, stage (startup, growth, mature), business model
• Market position: Who you compete with, your target customer, your differentiation
• Current situation: What's working, what's not, key challenges, recent changes
• Constraints: Budget limits, team size, technical capabilities, time constraints
• Goals: What you're trying to achieve, how success is measured, timeline
• User context: Who will use this output, what they know, what they care about

Let's see context in action. Compare these two requests:

The second prompt will produce vastly more useful output because the AI understands your reality—your customer type, your scale, your constraints, your goals. It can now suggest solutions that actually fit your situation rather than generic cost-cutting ideas that might break your business.

Component 3: Task—What Exactly Do You Want?

This is the core of your prompt—the actual work you want done. Be specific. "Write an email" is less effective than "Write a follow-up email to a prospect who attended our webinar." The more specific, the better.

Good task specifications include:

• Action verbs (write, analyze, create, suggest, compare, evaluate)
• Object (what you're acting on—email, plan, analysis, list, etc.)
• Specificity (follow-up to unresponsive prospect, not generic email)
• Scope (comprehensive list of 10 ideas, not vague suggestions)

Task examples:

• "Analyze these three customer support interactions and identify the most common objection"
• "Create a 90-day onboarding plan for a new VP of Sales joining a 30-person company"
• "Write three different subject lines for a product launch email to our existing customers"
• "Compare the pros and cons of hiring a full-time accountant versus using a fractional CFO service"

Component 4: Format—How Should the Output Look?

Many people skip this component, then spend 15 minutes reformatting the output to what they actually needed. Specify format upfront and you get immediate utility.

Format specifications include:

• Structure: Bullet points, numbered list, outline, table, paragraph prose, JSON, HTML
• Headers: Main sections, subsections, specific heading names
• Length: Word count, number of items, level of detail
• Style: Formal vs. casual, technical vs. business language, with examples or without
• Organization: Chronological, by priority, by category, nested structure

Examples of format specifications:

Component 5: Constraints—What Are the Limits?

Constraints are often the most overlooked component, yet they dramatically improve output quality by forcing the AI to be disciplined. Constraints might include:

• Length: Under 200 words, 1,000-1,500 words, approximately 5 pages
• Tone: Professional but friendly, authoritative, conversational, empathetic
• Audience: CFOs, entry-level employees, technical experts, non-technical decision makers
• Perspective: From the CEO's point of view, as an outside consultant, from customer perspective
• What to avoid: No jargon, no fear-based messaging, no tactics already tried, no solutions over $100k
• Time period: Actionable in next 30 days, 90-day initiatives, long-term strategic
• Reading level: 8th grade reading level, post-graduate, specific industry knowledge assumed
• Scope: Only ideas the team can execute ourselves, solutions under $50k implementation, etc.

Constraints prevent AI from going off-track. Without constraints, an AI might produce a 3,000-word treatise when you need a quick 150-word summary. It might adopt a tone that's too casual for a board presentation. It might suggest solutions beyond your budget.

Putting the Components Together: The Complete Prompt Structure

Here's how these components work together in a complete prompt:

Notice how this prompt guides the AI systematically. The role establishes credibility of perspective. The context explains the situation. The task specifies what work to do. The format describes how output should be structured. The constraints keep everything realistic and focused.

Building Prompts Component-by-Component

You don't need to memorize a rigid structure. You don't even need all five components for every prompt. Quick questions might only need Task. But for any significant work, following this framework produces better results.

Here's a process:

Step 1: Start with your Task. What do you want the AI to do? Be specific.

Step 2: Add Context. What should the AI know about your situation to give you relevant advice rather than generic advice?

Step 3: Specify Format. How should the output be structured to be most useful to you?

Step 4: Add Constraints. What limits or parameters should shape the output?

Step 5: Assign a Role (optional but high-impact). What expertise or perspective should the AI adopt?

You can build prompts in any order, but this progression often works well. Start with what you need, add context to make it specific, specify format for utility, add constraints for focus, and crown it with a role for perspective.

Practical Exercise: Prompt for Business Tasks

Let's build a complete prompt for a real business scenario: drafting a job description.

Step 1 - Task: "Write a job description for a Customer Success Manager"

Step 2 - Add Context: "We're a 35-person B2B SaaS company selling project management tools to teams of 10-50 people. Our CSM team has two people managing 60 customers. Average customer pays $1,500/month. We're losing customers at 5% annual churn. Our goal is to reduce churn to 2% and increase upsell revenue. This new CSM hire will own 30 customers and focus on reducing churn and identifying upsell opportunities."

Step 3 - Format: "Format as: Company Overview (1 paragraph), Role Purpose (1 paragraph), Key Responsibilities (bullet list), Required Skills (bullet list), Nice-to-Have Skills (bullet list), What Success Looks Like (3-4 bullets). Keep the entire job description under 400 words."

Step 4 - Constraints: "Focus on retention and upsell, not just support. Assume the role requires someone who can have strategic conversations with customers, not just reactive support. Avoid generic CSM job description language. Emphasize the business outcomes this role owns (churn reduction, expansion revenue). Suitable for posting on LinkedIn and tech job boards."

Step 5 - Role: "You are an experienced Head of Customer Success who has built world-class CS teams at venture-backed SaaS companies."

That's a complete, structured prompt. It will produce a job description far more aligned with what you actually need than a generic "write a job description" request.

What You'll Learn Next

Now that you know the structure of effective prompts, the next lecture shows you proven patterns for common business tasks. teaches you reusable templates you can adapt for email, reports, analysis, brainstorming, and strategic work.