Steal these.

I run {{business}}, a {{industry}} business in {{city}}. I'm the {{role}}.

I'm going to describe a process I do regularly, badly and out of order, the way it actually lives in my head. Your job is to turn it into a written SOP someone else could follow.

Ask me one question at a time until you understand it — especially the parts I skip over because they're obvious to me. Don't write anything until you've asked at least five questions.

Then produce:
1. A step-by-step SOP with numbered steps and who does each one
2. The decision points, written as if/then rules
3. The three steps most likely to go wrong, and what "wrong" looks like
4. Which steps a computer could do without me

Here's the process: [describe it here, messily, in one paragraph]

I'm the {{role}} of {{business}}, a {{industry}} business in {{city}}.

Below is an honest account of a normal week. Read it as an operations consultant would — someone who is not impressed by how busy I am.

Tell me:
1. Which single activity is eating the most hours for the least money
2. Which activity only I can do, and which ones I just haven't handed off
3. Where the same information gets typed in more than once
4. What would break first if I doubled my customer count next month
5. The one change that buys back the most hours, and what it would cost me

Be blunt. Do not tell me I'm doing a good job.

My week: [describe it here]

I'm about to hire someone to build custom software for {{business}}, a {{industry}} business in {{city}}. I need to explain how we operate clearly enough that they can scope it properly.

Interview me. Ask one question at a time, and keep going until you could describe my business to a stranger. Cover at minimum:
- Where customers come from and what happens to each one
- Every system, spreadsheet, inbox and notebook we currently use
- Who touches what, and what they're allowed to change
- What we measure, and what we wish we could measure
- The parts of the week everyone complains about

When you're done, produce a one-page brief with: how we work today, the specific problems worth solving, what "done" would look like, and the questions a developer would still need to ask me.

I'm going to paste the header row and a few sample rows from the spreadsheet {{business}} actually runs on.

Work out what real-world things this sheet is secretly tracking. Then give me:
1. The distinct entities (e.g. Customer, Job, Invoice, Technician) and the fields that belong to each
2. How they relate to each other, in plain English
3. Every column that is really two pieces of information crammed together
4. Every column where the same thing is spelled several ways
5. What's missing that a business like mine would normally need
6. A short list of the questions this data cannot currently answer but should

Do not suggest a tool. I just want to understand the shape of my own data.

Here it is: [paste headers and 5-10 rows]

I'm the {{role}} of {{business}} in {{city}}. I quoted a customer and never heard back. I want to follow up without sounding desperate or like an automated sequence.

Write me three options as SMS messages, each under 300 characters:
1. Short and warm — assumes they got busy
2. Useful — gives them a reason to reply that isn't "just checking in"
3. The polite close-out — makes it easy for them to say no, which usually gets a yes

Rules: no "just circling back", no "touching base", no exclamation marks, no emoji. Write the way a person who owns a {{industry}} business actually texts.

Context: [what the quote was for, how long ago, anything they said]

I sell {{industry}} services in {{city}} through {{business}}. My typical customer is: [describe them].

List the eight most likely reasons a customer says no to me — ranked by how often it really happens, not how often they say it out loud. For each one:
- The polite version they actually say
- What they usually mean underneath it
- One question I could ask to find out which it is
- The honest response, not a rebuttal script

Then tell me which of the eight are legitimate reasons I should walk away from the deal.

I run {{business}}, a {{industry}} business in {{city}}. Here's what I charge and what it costs me to deliver: [paste your services, prices, and rough costs].

Act as a pricing analyst who has seen a hundred businesses like mine.

1. Calculate my real margin per service, including my own time at a fair hourly rate
2. Tell me which service I'm effectively doing as a favour
3. Tell me which service is quietly funding everything else
4. Identify where I'm charging one price for two very different amounts of work
5. Propose a revised price list, with the reasoning I could actually say out loud to a customer
6. Tell me what I'd lose if I raised prices 15% and 20% of customers left

Assume my prices are too low unless the numbers say otherwise.

I'm the {{role}} of {{business}}. Below are last month's numbers next to the two months before.

Give me a one-page read, in this order:
1. The single most important thing that changed, and whether it's signal or noise
2. Anything that moved more than 15% in either direction, with a plausible cause
3. What these numbers cannot tell me, and what I'd need to start tracking
4. Three things to check before next month
5. One sentence I could send my accountant

No dashboards, no charts, no encouragement. Just the read.

Numbers: [paste revenue, jobs, leads, costs, anything you have]

A customer of {{business}} complained about the following: [paste the complaint].

Don't help me write an apology yet. First:
1. Tell me what actually broke — the process, not the person
2. Tell me whether this is a one-off or something that will happen again
3. Write the policy or process change that prevents it, in under 100 words, in language my team would actually follow
4. Tell me what this change costs me and what it might make worse

Then write the reply to the customer: honest, specific about what changed, no grovelling, under 120 words.

I'm putting an AI agent in front of customers at {{business}}, a {{industry}} business in {{city}}. Before I write a single line of it, I need the guardrails.

Help me produce:
1. The complete list of things this agent must NEVER do — legal, medical, financial, pricing, promises about timing
2. The exact trigger words or situations that should hand the conversation to a human immediately
3. What it should say when it doesn't know something (write the actual sentence)
4. What information it is allowed to collect, and what it must never ask for
5. The three worst-case conversations for a {{industry}} business, and how the agent should handle each

Assume this thing will be talking to an angry customer at 11pm with no supervision. Write it accordingly.

Here is a list of repetitive tasks at {{business}}, a {{industry}} business: [list them, one per line, with roughly how often each happens].

For each task, tell me:
- Roughly how many hours a month it consumes
- Whether it is rule-based, judgement-based, or both
- What happens if it's done wrong, and who notices
- Automate / partly automate / leave alone — with a reason

Then rank the automatable ones by hours saved per unit of effort to build. Be honest about the ones where automating adds more risk than it removes — a task that quietly fails is worse than a task nobody does.

I run {{business}}, a {{industry}} business in {{city}}, and I'm making my first proper hire. I'm the {{role}} and right now I do everything.

Before writing anything, ask me what a normal week would look like for this person — hour by hour if you have to. Push back if my answer is vague or if I'm describing three jobs.

Then write:
1. A job post that describes the actual work, not an ideal candidate
2. The three things that would genuinely make someone bad at this job
3. Five interview questions that reveal whether they can do the work, not whether they interview well
4. A paid trial task that takes under two hours and looks like the real job

Write the business description for {{business}}, a {{industry}} business in {{city}}.

Constraints:
- Under 750 characters
- First sentence says what we do and who for, with no throat-clearing
- Mention {{city}} and the surrounding areas naturally, not stuffed
- No "we pride ourselves", no "state-of-the-art", no "solutions", no "passionate"
- Sounds like the {{role}} wrote it, not a marketing agency

Give me three versions: plain, warm, and slightly confident. Then tell me which one you'd pick and why.

What makes us different: [two or three real things]

Below is the text from the homepage of {{business}}, a {{industry}} business in {{city}}.

Read it as a busy person who landed here from a search and will leave in eight seconds.

1. In one sentence, what do you think this business does? Guess, don't look for the answer.
2. What is the single clearest thing on the page? What is the vaguest?
3. Which sentences say nothing? Quote them.
4. What question would you still have before calling?
5. Rewrite the first 40 words so a stranger understands us immediately.

Do not be encouraging. I need to know what's actually landing.

The page: [paste it]

Below is a transcript from a meeting at {{business}}.

Extract:
1. Every decision that was actually made — not discussed, made
2. Every commitment, with who made it and by when. If no date was given, say so explicitly.
3. Every open question nobody answered
4. Anything someone raised twice, because that usually means it wasn't resolved
5. What was discussed at length but changes nothing

Then write a follow-up message under 150 words that I could send to everyone who was there.

Transcript: [paste]

Here is every software subscription {{business}} pays for, with monthly cost: [paste the list].

For each one, tell me what it's for in plain English. Then:
1. Group them by what job they do, and flag any two doing the same job
2. Flag anything that's usually bundled free with something else on the list
3. Total the annual spend and tell me what percentage goes to tools I probably touch less than once a month
4. Tell me which ones would be painful to leave, and which would not be noticed
5. Give me a cancellation order, safest first

If you don't recognise a tool, say so rather than guessing what it does.