Module 3\u2022Lesson 8

Plug-and-Play Prompt Patterns

Real-world prompts for Sales, Support, Operations, and Engineering.

Now that you understand the 4 elements (WHO, WHAT, INFO, HOW), here are complete prompts you can copy, customize, and use immediately. Each one follows the framework from the previous lesson.

Sales — Closing the Deal

Scenario: You need psychological triggers and trial-close questions to win over a COO.

Act as a high-ticket sales closer. I am selling a $5,000 AI Automation Audit to mid-sized manufacturing companies. List 7 psychological triggers that would make a COO want to buy this immediately, and draft a 3-sentence "trial close" question for each. Format as a numbered list.

Framework Breakdown

WHO

High-ticket sales closer

WHAT

7 psychological triggers + trial close questions

INFO

$5,000 AI Audit, mid-sized manufacturing, targeting COOs

HOW

Numbered list, 3-sentence trial close per trigger

Customer Support — Turning Heat into Loyalty

Scenario: A long-term subscriber is threatening to cancel over a UI change.

Act as a senior retention specialist. A long-term subscriber is threatening to cancel because our latest software update moved their favorite dashboard button. Draft a reply that validates their frustration, explains the "why" behind the change (efficiency), and offers a 15-minute 1-on-1 optimization call instead of a refund. Use a professional but empathetic tone.

Framework Breakdown

WHO

Senior retention specialist

WHAT

Draft a reply that validates, explains, and offers alternative

INFO

Long-term subscriber, UI change moved dashboard button

HOW

Professional but empathetic tone

Product & Ops — Efficiency Audit

Scenario: Projects take too long to move from Design to Client Review.

Act as a Lean Six Sigma operations consultant. We are a remote digital agency where projects are currently taking 14 days to move from "Design" to "Client Review." Identify 5 potential "bottlenecks" in a standard Slack/Asana workflow and suggest one AI automation for each to cut that time by 50%. Format as a table: Bottleneck | AI Solution | Expected Result.

Framework Breakdown

WHO

Lean Six Sigma operations consultant

WHAT

5 bottlenecks + AI automation for each

INFO

Remote digital agency, 14-day Design→Review cycle, Slack/Asana

HOW

Table format: Bottleneck | AI Solution | Expected Result

Engineering — The Pre-Mortem

Scenario: You're launching a referral feature and need to anticipate failures.

Act as a Lead QA Engineer. We are launching a new "Refer-a-Friend" feature that triggers a discount code via email. List 10 edge cases where this could fail (e.g., duplicate emails, expired codes, database lag) and provide the specific logic for a "fail-safe" to ensure the user experience isn't ruined. Rank them by "Probability of Occurrence".

Framework Breakdown

WHO

Lead QA Engineer

WHAT

10 edge cases + fail-safe logic for each

INFO

Refer-a-Friend feature, discount code via email

HOW

Ranked by Probability of Occurrence

Key Takeaway

Notice how every prompt follows the same 4-element structure? WHO + WHAT + INFO + HOW. Once you internalize this pattern, you can generate high-quality prompts for any situation—not just the four examples above.

← Previous Lesson Next: Master Prompt + Workflow →