Role-Context-Task-Format Examples: 10 Prompts for Real Small Business Jobs

The role-context-task-format framework is easy to agree with and hard to sit down and write. The framework post walks through why it works and how to diagnose output that misses; this one is the other half: ten finished briefs for jobs a small business has on the desk this week. Copy the one closest to your job, swap the [SQUARE BRACKETS], and you have a working prompt in two minutes.

A thirty-second recap for anyone landing here first. Role is who the AI should be. Context is what it cannot know about your situation. Task is the specific thing to produce, with a number where one fits. Format is the shape of the finished output, including what to leave out. The full framework post covers each part in depth.

Hiring and people

1. The job ad that sounds like your shop.

Role: You write job ads for small businesses that sound like a
person, not an HR department.
Context: We are [BUSINESS, SIZE, CITY]. Hiring a [ROLE]. The last
person left because [HONEST REASON]. What makes this job good:
[REAL PERKS]. What makes it hard: [REAL DOWNSIDES].
Task: Write the ad. Include the hard parts; I want fewer, better
applicants, not more.
Format: 250 words max. Pay range stated plainly. No "rockstar,"
no "fast-paced environment," no exclamation marks.

2. The awkward performance conversation, planned first.

Role: You are a calm manager who has run hundreds of feedback
conversations at small companies without HR support.
Context: My employee [FIRST NAME] has been [SPECIFIC BEHAVIOR,
WITH TWO EXAMPLES]. They are good at [STRENGTH]. I have not
raised it before, which is on me.
Task: Give me an opening line, three talking points anchored to
my examples, and the question I should ask before advising.
Format: One page. Behavioral language only, no labels like
"attitude problem."

Sales and quoting

3. The quote follow-up that isn't a nag.

Role: You write follow-ups for a [TRADE] owner who hates
pushiness more than lost revenue.
Context: Quote sent [N DAYS] ago for [JOB, AMOUNT]. The customer
said [WHAT THEY SAID]. We can hold the price until [DATE].
Task: Write one follow-up email that adds something useful (a
detail, an option, a date) instead of "checking in."
Format: Under 90 words, one question at the end, no "just
following up."

4. The price question you keep fumbling on the phone.

Role: You are a sales coach for owners who do their own selling.
Context: I sell [OFFER] at [PRICE]. When callers open with "how
much," I quote a number, they say thanks, they vanish.
Task: Give me a 3-sentence phone answer that gives a fair range,
attaches it to what changes the number, and ends with a
qualifying question back to them.
Format: Spoken language. Write it the way I would say it, not
the way a website would.

Money

5. The invoice chase, escalating politely.

Role: You handle receivables for a small business that needs the
money and the relationship.
Context: Invoice [NUMBER] for [AMOUNT] is [N] days overdue.
Customer history: [GOOD / FIRST OFFENSE / REPEAT]. Payment terms
were [TERMS].
Task: Write the day-7 nudge, the day-21 firm note, and the
day-40 final notice before I stop work.
Format: Each under 80 words. Friendly, plain, zero apology for
asking to be paid.

6. Reading the monthly numbers without an accounting degree.

Role: You are a bookkeeper who explains numbers to owners in
plain language and flags what deserves a question.
Context: Here are my last 3 months of [P&L / bank export]:
[PASTE]. My business is [ONE LINE]. Rent and payroll are fixed.
Task: Tell me the three numbers that moved most, the likeliest
reason for each, and the one question I should take to my
accountant.
Format: Five bullet points, then the question. No jargon without
a bracket translation.

Marketing

7. The job-photo social post.

Role: You write social captions for a [TRADE] business. Proud
craftsman voice, never salesy.
Context: Photo attached from today's job: [WHAT IT SHOWS]. The
interesting part a customer would not notice: [DETAIL]. We serve
[AREA].
Task: Write the caption telling that one detail as a story.
Format: Under 60 words, no hashtag pile (two max), no "DM us."

8. The newsletter blurb people don't skip.

Role: You write short newsletters for a local [BUSINESS TYPE]
with an open rate worth protecting.
Context: This month's one thing worth saying: [NEWS / TIP /
OFFER]. Audience: [WHO THEY ARE]. Last month we wrote about
[TOPIC], so no repeats.
Task: Write the blurb and three subject lines to pick from.
Format: Blurb under 120 words with one link. Subject lines under
45 characters, no clickbait, no emoji.

Operations

9. The meeting agenda that ends on time.

Role: You run tight meetings for small teams and protect
everyone's morning.
Context: Weekly team meeting, [N] people, 30 minutes. Standing
problems: [WHAT DERAILS IT]. Decisions needed this week:
[LIST].
Task: Build the agenda with minutes assigned per item, decisions
first, updates last and written-only if possible.
Format: A table I can paste into the calendar invite, then two
ground rules at the bottom.

10. The vendor comparison before you sign.

Role: You are a skeptical operations advisor who has watched
small businesses overbuy software.
Context: Choosing between [OPTION A] and [OPTION B] for [JOB].
Costs: [BOTH]. Our non-negotiables: [LIST]. Team's tech comfort:
[HONEST LEVEL].
Task: Compare them on my non-negotiables only, name the switching
cost if I am wrong, and recommend one with the reason.
Format: Short table, then a 3-sentence recommendation. If the
honest answer is "neither, keep the spreadsheet," say that.

Where these break

Copied briefs inherit your honesty. Every example above has a slot where the truth goes (the downside of the job, the reason the customer went quiet, the derailers in your meeting), and filling it with something polite instead of something true is the main way these fail. The other failure is scale: a brief you find yourself rewriting weekly for the same job has outgrown hand-prompting, which is a systems problem, not a wording problem.

Two shortcuts

If you have a rough prompt in hand and want it restructured into this shape, the Prompt Rewriter does the conversion, and our free prompt improver does it in the browser. And once a few of these briefs earn a permanent place in your week, the Prompt Library Builder skill turns them from scattered notes into a maintained library your whole team pulls from. The prompt engineering courses teach the craft from the ground up if you would rather build the skill than borrow the briefs.