10 ChatGPT Prompts Every Solo Service Owner Should Steal

I used ChatGPT wrong for my first three months. I'd type "write me a client proposal" and get back something that could have been for a bakery, a SaaS company, or a dog walker. Technically correct, universally useless.

The unlock was realizing prompts are less like search queries and more like briefs for a very fast intern. Give the intern no context and they write something generic. Give them a name, a scenario, a tone, and a deadline — and they write something you can actually send.

These are the ten prompts I come back to every week. Each one follows the same structure: role, context, task, constraints, format. Steal them.

1. The client proposal generator

You are a proposal writer for a [your profession — e.g., brand designer, fractional CMO, fitness coach]
with 5+ years experience working with [your niche, e.g., DTC founders doing $1-5M/yr].

Write a proposal for a new client named [Name] whose business is [one-sentence business description].
Their goal is [their stated outcome]. Their current obstacle is [problem they described on the call].
My package is [package name, price, timeline, 3-5 deliverables].

Structure the proposal with: opening line that references their specific situation,
a 2-sentence "what I heard," deliverables, timeline, investment, and a clear next step.
Keep it under 400 words. Professional but warm. Avoid corporate filler.

Why it works: the "what I heard" section forces the model to mirror back their situation, which is the single most persuasive move in a proposal.

2. The discovery call follow-up

Write a follow-up email after a discovery call with [Name] from [company/business].
They said they're struggling with [specific problem]. We discussed [solution].
They mentioned a concern about [objection].

Address the objection gently, reiterate the solution in plain language,
and suggest one clear next step. Under 200 words. Tone: confident, warm, specific.
End with a question that invites a reply.

The trick here is naming the objection explicitly. Most follow-ups ignore the thing the client is actually worried about. This one doesn't.

3. The scope creep response

Write a short, polite, firm email to a client who has requested work outside our agreed scope.

Original scope: [scope].
The new request: [request].
I want to offer it as an add-on at [$price] with a [timeline].

The email should acknowledge what they asked for, restate the original scope in one sentence,
frame the add-on as a solution rather than a rejection, and end with a clear yes/no question.
No apologies for the original scope. Warm but unambiguous.

"No apologies for the original scope" is the line that changes the output most. Take it out and the email grovels.

4. The testimonial request

Write a short, friendly email asking a past client for a testimonial.
We worked together on [project]. The outcome they got was [specific, measurable result if possible].

Make it easy for them to say yes. Include 3 specific short questions they could answer in a few sentences each:
one about their situation before, one about what working together was like, one about the result.

Under 150 words. No "I know you're busy" filler. End with "Reply in a few sentences and I'll turn it
into a testimonial you can approve."

That last line is the hack. You're offering to do the work for them, which triples reply rates.

5. The content idea generator

Generate 10 blog post ideas for [your niche] targeting [your specific audience].
Focus on problems they face with [specific pain point].

Mix: 3 how-to posts, 2 comparison posts ("X vs Y"), 2 personal-experience posts ("how I…"),
2 list posts ("N ways to…"), and 1 contrarian take.

For each idea: a working title, a one-sentence hook, and the primary keyword someone would Google
to find it. Avoid generic titles — every one should be specific enough that someone in the niche
would click immediately.

The "primary keyword" field forces the model to think like a searcher, not a thought leader.

6. The email sequence builder

Create a 3-email welcome sequence for new subscribers to my newsletter about [topic].
The audience is [specific audience]. My voice is [pick: witty/direct/warm/analytical].

Email 1 (send immediately): welcome + the #1 resource I promised. Under 250 words.
Email 2 (send day 3): my origin story + the biggest lesson I learned. Under 300 words.
Email 3 (send day 7): a quick win they can implement today + an invitation to reply.

Each email should have a subject line that's 5-8 words and doesn't sound like marketing.
End each email with a PS that does one job: invite a reply, share a resource, or set up the next email.

The "doesn't sound like marketing" constraint is doing most of the work here.

7. The social media repurposer

Take the blog post below and create 5 LinkedIn posts.

Each post should:
- Stand alone (readable without the blog post)
- Start with a hook in the first 1-2 lines that works as a preview on LinkedIn
- Be under 200 words
- Use short paragraphs (1-2 sentences each)
- End with an open question to spark replies
- Include one specific, concrete detail — no vague platitudes

Post 1 should tease the core idea. Posts 2-4 should each pull out one tactic from the post.
Post 5 should be a contrarian take on the topic.

Blog post: [paste here]

Five posts from one blog post is a month of LinkedIn content. I'd do this at a loss even if it took three hours; it takes three minutes.

8. The process documenter (SOP)

Help me turn the rough notes below into a clean Standard Operating Procedure.

Format:
- Header: process name, when it's triggered, estimated time, tools used
- Numbered steps, each with: what to do, which tool, expected output, time estimate
- A quick-reference checklist at the bottom for when I already know the process

Rough notes: [paste your messy steps here]

Where the notes are unclear, flag it with [NEEDS CLARIFICATION] so I can fill it in.
Don't invent steps. Be specific about tool names.

The "flag ambiguity" instruction prevents the model from inventing steps, which is the usual failure mode.

9. The pricing page copy writer

Write copy for my pricing page.

Offer: [services] at [price points].
Target client: [specific description].
The transformation: [what changes in their business when they hire me].

Highlight the outcome, not the deliverables. Lead each tier with who it's for, not what's in it.
Use plain English — no "elevate" or "unlock."

Include:
- A one-line offer promise at the top
- 2-3 tiers with: who it's for, what they get, the price, the CTA button text
- A short FAQ with 3 objections: "is it worth it?", "what if I need more?", "can we do a call first?"

"No elevate or unlock" is a surprisingly powerful constraint for SaaS-adjacent copy.

10. The weekly planning prompt

Help me plan a realistic work week.

Context:
- I have [N] active clients at [project stages].
- This week's hard deliverables: [list].
- Open priorities (not deliverables): [list].
- My deep-work hours are [time of day]. Shallow work hours are [time of day].
- Non-negotiable personal commitments: [list].

Produce a Monday-Friday schedule with 6-hour work days.
Block deep-work hours for creative or hard thinking.
Batch shallow work (email, admin, calls) into the afternoon.
Identify any conflicts up front and flag them as [CONFLICT] with a suggested fix.

I run this every Monday morning. It takes 90 seconds and replaces 20 minutes of planning anxiety.

The meta-prompt (read this if you remember nothing else)

Every one of these prompts follows the same bones:

1. Role ("you are a…")
2. Context (who I am, who the client is, what the situation is)
3. Task (the thing you want done)
4. Constraints (tone, length, what to avoid)
5. Format (structure, sections, word count)

If you can write a prompt that hits those five beats for any task you do more than twice a month, you'll never type "write me a client email" again.

Frequently asked

Should I save these in ChatGPT's custom instructions? Yes. Put the recurring context (your role, niche, tone, client profile) in the custom instructions once. Then the task-specific prompt can be shorter every time.

What about hallucinations in business emails? Keep the AI to language, not facts. Never paste a number, date, or name you haven't personally verified. The prompt can structure the email; the specifics come from you.

Which model should I use for these? GPT-4 class or better for anything client-facing. The smaller models are fine for brainstorming but too loose for the tone-sensitive work. Claude Opus is particularly good at the follow-up and testimonial prompts.

I broke down how I use AI to write full proposals in under 5 minutes using a single-stage version of prompt #1 above — if proposals are your bottleneck, start there.