Northstack

Guides

47 ChatGPT Prompts for Small Business Owners (By Function)

19 min read

Most prompt lists fail for the same reason: they hand you one sentence and no context. “Write a marketing email” gets you generic slop, because the model doesn’t know what you sell, who buys it, or what you’ve already tried.

The 47 prompts below are built differently. Each one carries the context you fill in and a defined output shape, so you get something usable on the first pass instead of something you have to rewrite. They’re grouped by the job they do — sales, marketing, content, support, operations, money — not by which AI feature they use.

How to use this page. Pick one prompt. Fill every bracket. Paste it into ChatGPT, Claude or Gemini. If the output is close but not right, reply with what’s wrong in one sentence (“too formal, cut the adjectives”) rather than starting over. One correction beats three rewrites.

Sales

1. Qualify an enquiry before you spend a call on it

Someone writes “tell me more.” You need to know in three minutes whether they’re a buyer.

You are helping me qualify an inbound enquiry for a one-person business.

What I sell: [one sentence]
Price point: [price]
Typical buyer: [role, company size, situation]

Their message:
"""
[paste the enquiry verbatim]
"""

Give me:
1. What they actually want, in one sentence
2. Three signals they are ready to buy, quoting their own words
3. Three signals they are tire-kicking, quoting their own words
4. The single question I should ask next, and why that one
5. A 60-word reply that answers their question and asks mine

Do not be encouraging. If the enquiry is weak, say so.

2. Write a follow-up that doesn’t sound like a follow-up

Most follow-ups read as pressure. This one reads as usefulness.

Context: I quoted at [price] on [date]. They went quiet after [what happened last].

Write a follow-up email under 90 words that:
- Adds one piece of value they did not have before (not a discount)
- Does not ask "just checking in" or "circling back"
- Ends with a question they can answer in one line
- Gives them a clean way to say no

Tone: direct, no exclamation marks, no "hope this finds you well."

3. Handle the “it’s too expensive” objection

This prompt refuses to let you discount your way out of it.

My product: [name, what it does]
Price: [price]
What it replaces: [the alternative, with its cost in money or hours]
The prospect said: "it's too expensive"

Give me three different responses:
1. Reframe against the cost of the alternative
2. Split the price into a per-use or per-month figure
3. A genuine downsell to a smaller option, if I have one

For each: the exact words I should say, and the risk that it backfires.
Do not suggest discounting.

4. Turn a testimonial into a case study

You have one sentence from a happy customer. This turns it into proof.

Customer said: "[exact quote]"
What they bought:
What they were doing before: [their prior situation]

Write a 250-word case study with:
- A headline stating the outcome, not the product
- Before / after, in concrete numbers if I give them to you, otherwise in concrete actions
- The one thing that made the difference
- Their quote, placed where it carries most weight

Do not invent numbers. If a number is missing, write [MISSING] so I know to fill it.

5. Build a proposal outline from a discovery call

Paste your messy notes; get a structure a client can approve.

Here are my raw notes from a discovery call:
"""
[paste notes, including the messy parts]
"""

Produce a proposal outline with:
1. Their problem, in their words
2. What success looks like, in measurable terms
3. Scope: three deliverables, each with a definition of done
4. What is explicitly out of scope
5. Price and payment terms as placeholders
6. Two risks and how we handle each

Flag anything in my notes that is ambiguous enough to cause a scope dispute later.

6. Write the “no” email that keeps the door open

Declining badly costs you referrals. This one doesn’t.

I need to decline this project: [what it is]
Reason I can share: [capacity / not my expertise / budget mismatch / other]
Relationship: [how we know each other]

Write a 70-word email that:
- Says no in the first sentence, not the last
- Gives the honest reason without over-explaining
- Names one alternative (a person, a resource, or a time when I could)
- Leaves them glad they asked

7. Price a custom request

Custom work is where solo operators lose money. This forces the math.

A client asked for: [the request]
My normal rate: [rate and unit]
Hours I estimate: [estimate]
What usually goes wrong on this kind of work: [past experience]

Calculate:
1. Three scenarios: best case, likely case, worst case, in hours and money
2. A fixed price that survives the likely case, not the best case
3. Three scope boundaries I must write into the quote
4. The sentence I use to present the price without apologising

8. Draft a referral ask

Most people never ask. The ones who do make it effortless to say yes.

I just finished work for [client] and the result was [outcome].
Write a 50-word message asking for a referral that:
- Names the exact type of person who benefits (role, situation, not "anyone who needs help")
- Makes the ask take under 30 seconds to fulfil
- Offers to write the introduction myself so they only have to forward it

Marketing

9. Find your actual positioning

Not a brand exercise. A sentence you can use in a cold email.

Here is what I sell: [description]
Here is who buys it: [customer description]
Here are three competitors: [names and what they claim]

Give me:
1. The positioning statement my competitors could not credibly copy
2. Three reasons to believe it, that I can actually prove
3. The one customer segment I should stop marketing to
4. A 12-word version for a website headline

If my positioning is generic, tell me which word is doing no work.

10. Write five subject lines and predict which wins

Subject line advice is usually vague. This forces a prediction.

Email goal: [what the email asks for]
Audience: [who, how they know me]
Email body:
"""
[paste the email]
"""

Write five subject lines using five different mechanisms (curiosity, specificity, loss, question, plain statement).
For each: predicted open rate relative to the others, and why.
Rank them. State which one you would send and what would make you wrong.

11. Turn one product into a week of social posts

Not “repurpose content” advice — an actual seven-day plan.

Product: [name and what it does]
The single most interesting thing about it: [your answer]
Platform: [LinkedIn / X / Instagram / other]

Give me seven posts, one per day:
- Each takes a different angle (problem, mistake, behind-the-scenes, customer moment, contrarian take, how-to, offer)
- Each is written for that platform's format, not copy-pasted
- Each ends with something other than "buy now"

Day 7 is the only one that mentions price.

12. Write a landing page headline that survives a five-second test

If a stranger can’t tell what you do in five seconds, the page is dead.

What I sell: [description]
Who it is for: [specific person in a specific situation]
The outcome they get: [measurable result]
Current headline: [paste it]

Write 10 headline options:
- 3 outcome-first
- 3 problem-first
- 2 audience-first
- 2 contrarian

For each, name the reader who would click and the reader who would bounce.
Then tell me which of my current headline's words are load-bearing and which are filler.

13. Build a competitor teardown you can act on

Not a feature comparison. A list of openings.

Competitor: [name]
What they sell: [description and price]
What their customers complain about: [paste reviews or your notes]
What I do differently: [your honest answer]

Produce:
1. Three things they do better than me, and whether I should copy them
2. Three gaps in their offer I can occupy this month
3. The customer segment they are ignoring
4. One message I can use that they cannot

14. Write a launch sequence for a small product

For when you have an audience of 40 people, not 40,000.

Product: [what it is, price]
Audience size and channel: [e.g. 400 email subscribers, 900 followers]
Time until launch: [days]

Give me a sequence of five messages over that period:
- For each: channel, purpose, and the exact copy
- Include one message that is pure value with no ask
- Include one that assumes they will not buy, and still helps them

No countdown timers, no fake scarcity.

15. Diagnose why a page isn’t converting

Paste the copy; get a diagnosis, not a rewrite.

Page copy:
"""
[paste the full page text]
"""
Traffic source: [where visitors come from]
Conversion rate: [current]
What conversion means here: [purchase / signup / reply]

Diagnose in order of likely impact:
1. Is the offer clear in the first screen?
2. Is there proof, and is it in the right place?
3. What objection is left unanswered?
4. What is the single change with the highest expected lift?

For each finding, quote the exact line that causes the problem.

16. Write the FAQ that removes the real objection

Not “how does it work” — the question they’re too polite to ask.

Product: [name, price, what it includes]
The objection I hear most: [e.g. "I could do this myself"]
What I actually know about that objection: [your honest view]

Write 6 FAQ entries:
- 2 that answer the stated objection directly
- 2 that surface objections buyers have but don't say
- 2 that disqualify the wrong buyer

Answers under 60 words each. No hedging.

Content

17. Find ten topics your buyers actually search

Based on their situation, not your product features.

My buyer: [role, company size, what they are trying to do]
What they are stuck on right now: [your observation]
What I sell:

Give me 10 topics they would type into a search engine, phrased as they would phrase it.
For each: the search intent (learn / compare / buy), and whether I should answer it or ignore it.
Rank by how close the searcher is to buying.

18. Build an article outline that argues something

Outlines that summarise rank badly. Outlines that argue get read.

Topic: [topic]
My actual position: [what I believe that most people get wrong]
Reader: [who]
What I can prove: [data, experience, examples]

Build an outline where:
- Section 1 states the common belief and why it fails
- Sections 2-4 build the case, each with one piece of evidence
- Section 5 handles the strongest counter-argument honestly
- Section 6 says what to do on Monday

Flag any section where I have no evidence. Do not let me bluff.

19. Rewrite a paragraph so it stops sounding like AI

The tells are specific. This removes them.

Text:
"""
[paste paragraph]
"""

Rewrite it and:
- Remove every instance of "delve," "landscape," "leverage," "robust," "seamless," "it's important to note"
- Break any sentence with more than two clauses
- Replace abstract nouns with concrete ones
- Cut any sentence that only restates the previous one
- Vary sentence length: at least one under 8 words

Show me the rewrite, then list what you removed and why.

20. Turn a customer question into a piece of content

You already have the topics. They’re in your inbox.

A customer asked me:
"""
[the question, verbatim]
"""
My answer at the time: [what I said]

Turn this into:
1. A blog post title
2. A 400-word answer that goes deeper than what I said
3. Three social posts, each taking one part of the answer
4. One line for the FAQ page

Keep my voice: [describe it, or paste something you wrote]

21. Write an intro that doesn’t start with a definition

“In today’s fast-paced world” is where readers leave.

Article topic: [topic]
What the reader is doing right now instead of reading this: [their situation]

Write 5 opening paragraphs (max 60 words each):
1. Start with a specific scene
2. Start with a number
3. Start with the reader's mistake
4. Start with a short story about me
5. Start with a claim I'll spend the article defending

No definitions. No "in today's world." No "have you ever wondered."

22. Build a content calendar from three pillars

Enough structure to stop staring at a blank page, not so much it becomes a job.

My three content pillars: [pillar 1], [pillar 2], [pillar 3]
Publishing capacity: [e.g. 2 posts per week]
Platform: [where]

Build a 4-week calendar:
- Each week rotates the pillars
- Each entry has: title, format, the one idea it delivers, and the CTA
- Include two "easy" slots per month for when I'm busy
- No entry may duplicate another's idea

23. Edit your own writing like an editor

Run this before you publish. It catches what you can’t see.

Draft:
"""
[paste draft]
"""

Edit in three passes and report each separately:
Pass 1 - Structure: does the argument hold? What's out of order?
Pass 2 - Cut: what can go without losing meaning? Target 15% reduction.
Pass 3 - Line: fix rhythm, remove hedging, kill clichés.

Give me the final version, plus a list of the three cuts that hurt most but should stay cut.

24. Write a case study without a big client

You can use yourself. This is how.

What I did for myself: [the project]
Before: [the state, with numbers if possible]
After: [the result]
Time taken: [duration]
What I'd do differently: [honest answer]

Write it as a 300-word story that:
- Opens with the problem, not the solution
- Shows one decision point where it could have failed
- States the result plainly, without inflation
- Ends with what a reader should take from it

Do not call it a case study in the text.

Customer support

25. Answer an angry email without escalating

The instinct is to defend. That’s what makes it worse.

Customer wrote:
"""
[paste their message]
"""
What actually happened: [the facts]
What I can offer: [refund / replacement / fix / nothing]

Draft a reply that:
- Opens by naming their frustration accurately, in one sentence
- States the facts without defensiveness or apology theatre
- Says what I will do, specifically, with a date
- If I'm wrong, says so plainly
- Under 120 words

Then tell me what I should change about my process so this email doesn't happen again.

26. Write the response to “I never got my download”

The most common support ticket for digital products. Make it a template.

Product: [name]
How delivery works: [email + link, expiry, etc.]
Common failure points: [spam folder, wrong email, expired link]

Write a reply template that:
- Solves it in the first message for 80% of cases
- Includes the three checks they should do, in order
- Gives them a re-issue path without asking them to explain again
- Takes under 20 seconds to read

Then write the one-line version for a chat widget.

27. Turn five complaints into a fix list

Support is free product research. This extracts it.

Recent complaints:
"""
[paste 5-10 messages]
"""

Group them by root cause, not by wording.
For each root cause:
1. How many customers it affects (estimate from what I gave you)
2. Whether the fix is copy, process, or product
3. The cheapest fix that removes 80% of the volume
4. What I should stop promising on the sales page

Rank by cost of doing nothing.

28. Set expectations before they buy

Most support volume is created on the sales page, not after it.

Product: [name]
What buyers expect: [based on your support tickets]
What actually happens: [reality]
Gap: [where expectation and reality differ]

Write 3 sentences for the product page that close the gap without reducing sales.
Each sentence must be specific enough that a buyer could hold me to it.
Then write the one that should go directly above the buy button.

29. Draft a refund response that keeps the customer

Sometimes the right answer is yes. This makes it cheap.

Customer asked for a refund because: [reason]
My policy: [terms]
Whether I want to keep them as a customer: [yes / no / unsure]

Write two versions:
A - Approve immediately, no friction, no questions
B - Approve but ask one question that helps me improve

For each: exact copy, and what it costs me in goodwill if I get the tone wrong.

30. Write a proactive email that prevents tickets

One email now beats forty replies later.

The problem my customers hit: [e.g. link expired, wrong file, can't open PDF]
When they hit it: [after how long, at what step]
What I want them to do instead: [the correct action]

Write a 100-word email I send on day [X] that:
- Assumes they haven't read anything I sent before
- Leads with the action, not the explanation
- Contains one link, to the thing they need
- Has a subject line that doesn't look like marketing

31. Build your support macro library

Ten replies that cover 90% of what you actually get asked.

Here are the messages I get most often:
"""
[list them]
"""

For each, write a macro that:
- Answers in the first line
- Fits under 80 words
- Sounds like a person, not a help desk
- Ends with what happens next

Then tell me which three messages should be prevented by changing the product page instead of answered.

Operations

32. Design your week around one constraint

Solo operators don’t have a time problem. They have a priority problem.

What I do: [business description]
Revenue per month: [amount]
Hours available per week: [number]
Everything currently on my plate: [list it all, unsorted]

Identify:
1. The one activity that produces most of the revenue
2. Everything that could stop tomorrow without revenue dropping
3. A weekly structure that protects #1 and kills #2
4. What I should say no to this week, in exact words

33. Write a process document you’ll actually follow

Most SOPs are written once and never opened. This one isn’t.

Process: [e.g. publishing a product, onboarding a client]
How I do it now, roughly: [describe it messily]

Turn this into a checklist where:
- Every step starts with a verb
- Every step has a definition of done
- Steps that can fail have a "if this breaks, do X"
- Total steps under 12

Then tell me which two steps I could automate or delete.

34. Decide what to automate first

Most automation projects start in the wrong place.

Tasks I do every week:
"""
[list them, with rough minutes each]
"""

Score each on:
1. Frequency
2. Whether it's identical every time
3. Cost of it going wrong
4. Whether a customer would notice if it broke

Rank by automation value. For the top three, tell me the simplest tool that would do it, and the one that would be over-engineering.

35. Write a handover brief in 15 minutes

For when you bring in a contractor and don’t want to explain everything twice.

Task I'm handing over: [task]
Who is taking it: [role, experience level]
Deadline: [date]
What "done" looks like: [your standard]

Write a brief with:
1. The outcome, stated first
2. Constraints that are non-negotiable vs. preferences
3. Two examples of good work, one of bad
4. Who to ask when stuck, and what counts as stuck
5. What they should not touch

Under 400 words. No background section unless it changes the work.

36. Run a weekly review in 20 minutes

The meeting you have with yourself. Make it count.

This week's numbers: [revenue, traffic, signups, whatever you track]
This week's work: [what you did]
What went wrong: [honest answer]

Give me a review structure with 5 questions that:
- Separates activity from outcome
- Identifies the one decision that mattered most
- Names what I avoided doing
- Ends with exactly one thing to change next week

Ask the questions, then answer them using what I gave you.

37. Write your pricing page logic

Three tiers, or one? This decides it on evidence.

What I sell:
What buyers ask for most: [from support and sales conversations]
What costs me most to deliver: [time or money]

Recommend:
1. One price, or tiers? Justify from what I told you.
2. If tiers: what actually differs between them (not feature padding)
3. The price anchor and where it sits
4. What to remove entirely because it confuses the choice

Give me the number, not a range.

38. Build a simple dashboard

Five numbers. Not twenty.

My business model: [how money comes in]
What I can measure: [available data sources]
What I currently look at: [list]

Pick the five numbers that would tell me if the business is healthy this week.
For each: why it matters, what "bad" looks like, and what I'd do if it went bad.
Then tell me which of my current metrics are vanity and should go.

39. Write the “we’re changing something” email

Price change, policy change, product retirement. All the same problem.

What is changing: [change]
Effective date: [date]
Who is affected: [segment]
What they can do about it: [options]
Why it is happening: [honest reason, even if unflattering]

Write the announcement:
- State the change in the first two lines
- Give the reason without corporate language
- List exactly what they need to do, or say "nothing"
- Include the deadline, in a date not a duration

Under 150 words.

Money

40. Find your break-even in one page

Most solo operators don’t know this number. It changes every decision.

Monthly fixed costs: [list them with amounts]
Average revenue per customer: [number]
Variable cost per sale: [number]
Current customers per month: [number]

Calculate:
1. Break-even customers per month
2. Break-even revenue
3. How many sales per week that means
4. The gap between now and break-even, in customers
5. The two levers that close the gap fastest

Show the arithmetic. Do not round away the difficulty.

41. Decide whether to raise your price

Not a gut call. A calculation with a threshold.

Current price: [number]
Current volume: [units per month]
Proposed new price: [number]
What buyers say about the price now: [from conversations]

Calculate:
1. How much volume I can lose at the new price and still break even
2. Whether that volume loss is likely, based on what I told you
3. The three things I should improve before raising it
4. The exact words for announcing it to existing customers

Give me a yes/no recommendation with the reasoning exposed.

42. Build a simple cash forecast

Revenue is not cash. For a one-person business, that difference kills.

Starting cash: [number]
Expected income next 3 months: [amount and when it actually lands]
Expected outgoings next 3 months: [amount and when they leave]
Payment terms: [when customers pay, when platforms pay out]

Build a 13-week cash forecast.
Flag the week with the lowest balance.
Tell me the earliest week I could hit zero, and what I'd do about it today.

43. Price a bundle without losing money

Bundles feel like discounts. Sometimes they are.

Products: [name and individual price for each]
Cost to deliver each: [time or money]
How often each sells alone: [units per month]
Proposed bundle price: [number]

Calculate:
1. Revenue per bundle vs. expected revenue from the same customers buying separately
2. Whether the bundle cannibalises my best seller
3. The price that increases total revenue, not just units
4. Which product should never be in a bundle, and why

44. Write an invoice that gets paid on time

Late payment is usually a design problem, not a client problem.

What I invoiced for: [work]
Amount: [number]
Payment terms: [current terms]
How late they usually are: [days]

Rewrite my invoice to include:
1. A due date, not a term
2. One line stating what happens after the due date
3. A payment link, above the fold
4. A single sentence that makes paying the path of least resistance

Then write the reminder email for day 1, day 7, and day 14 past due.

45. Decide what to stop selling

The product that eats your week and pays the least.

My products/services:
"""
[name, price, hours per month it consumes, support load, how much I enjoy it]
"""

Calculate revenue per hour for each.
Rank them.
Identify the one that should go, even if it sells well.
Then write what I tell existing customers, and what I replace the revenue with.

46. Set a revenue target that means something

Not a number you pick. A number derived from how you want to work.

Hours per week I want to work: [number]
Weeks off per year: [number]
Income I need after costs: [number]
What I sell and at what price: [list]

Work backwards:
1. Revenue required
2. Units required per month
3. Hours per unit that this implies
4. Whether that is compatible with the hours I said

If it isn't compatible, say so and tell me which assumption has to change.

47. Write your own quarterly review

One page, four questions, once every three months.

Last quarter's numbers: [revenue, customers, traffic, whatever you have]
What I shipped: [list]
What I planned but didn't do: [list]

Give me four questions that force an honest review, then answer them:
1. What worked that I under-invested in?
2. What did I keep doing out of habit?
3. What did I avoid because it was uncomfortable?
4. What is the one thing next quarter that would make the other three irrelevant?

Why 47 and not 500

Because a prompt you never use is worth nothing. Most people who download a 500-prompt pack use three of them and forget the rest. The 47 here map to jobs that actually come up in a one-person business, and each one is specific enough that you can tell within one output whether it worked.

The pattern underneath all of them is the same, and it’s worth naming: context in, shape out. Tell the model what you sell, who buys it, and what the output should look like. That’s the difference between a prompt that saves you twenty minutes and one that costs you twenty minutes of editing.

If you want the version of this that covers marketing, sales, content, support, ops and productivity in one file — 80 prompts in the same format, written to be pasted rather than read — that’s what the AI Prompt Vault is. The 47 on this page are a subset of it.

Keep reading