Title: The two prompts in this pack that people keep asking about

Got a few comments and DMs asking specifically about the Bottleneck Finder and SOP Generator, so here's both in full, straight from the pack.

---

PROMPT: The Bottleneck Finder

You are a business systems analyst specializing in constraint theory and throughput optimization.

Context: My business is generating activity but not converting it to revenue at the rate it should. Something is the constraint — I may not be seeing it clearly.

Task: Analyze my business flow below and identify the single constraint that, if removed, would have the highest downstream impact on revenue. Do not give me a list of problems. Give me the one.

My current flow: [describe leads to sales to delivery to revenue cycle]

Current conversion rates or drop-off points: [paste what you know]

Format: (1) Identified constraint — one sentence. (2) Why this is the constraint, not a symptom. (3) Three actions to break it, ranked by speed of impact.

Constraints: No generic advice. If you don't have enough data, ask one specific question to get it.

---

PROMPT: The SOP Generator

You are an operations architect specializing in turning founder knowledge into repeatable systems.

Context: I have a process I do manually and inconsistently. I need it documented as a standard operating procedure so it can be handed off, automated, or run without me.

Task: Interview me to extract the full process. Ask me the questions needed to document it completely. Then produce a finished SOP.

Format: SOP structure — Purpose, Trigger, Inputs Required, Step-by-Step Process (numbered), Decision Points, Output/Deliverable, Tools Used, Common Errors to Avoid.

Constraints: Write at an 8th grade reading level. Assume the person following this SOP has never done it before. No jargon unless defined.

Process to document: [describe the process]

---

These two are part of a 10-prompt set I built (SOP Generator's actually one of them too — different version, more detail than what's used here). Happy to talk through any of the others in the comments if useful.

reddit.com
u/Frank_Eventus — 5 days ago

Title: Built 10 prompts that replace a $500/mo consultant — sharing the full breakdown

I run a one-man operation and got tired of reinventing the wheel every time I needed to delegate thinking to AI. So I built out 10 structured prompts — each with full Role/Context/Task/Format/Constraints — covering the stuff that actually eats time: SOP generation, pricing audits, bottleneck diagnosis, cold outreach, weekly strategic briefs.

These aren't "write me a blog post" prompts. They're built to make AI think like an operator, not a chatbot.

Happy to share the structure of any one of these in the comments if it's useful — drop what you're working on and I'll tell you which prompt fits, or just comment and I'll send the full set.

reddit.com
u/Frank_Eventus — 6 days ago
▲ 2 r/agency+1 crossposts

Sharing the AI prompt framework I use to run my business — two full examples inside

I run multiple ventures and AI is embedded in how I operate daily. The biggest unlock wasn't finding better tools — it was learning to write prompts that actually produce usable output.

The structure I use on every prompt:

Role — who the model is playing
Context — what situation it's in
Task — what I need
Format — how to structure the output
Constraints — what to avoid

Two examples I use weekly:

---

THE WEEKLY WAR ROOM BRIEF

You are an executive briefing AI that runs a weekly operating review for a solo founder.

Context: I am a solo operator across multiple ventures. I need a structured weekly review that forces honest accounting of progress, flags drift, and resets priorities.

Task: Run my weekly war room. Ask me the questions needed to produce a complete brief. Then generate the full output.

Questions to ask me: (1) What were last week's three commitments? (2) What actually happened? (3) What's the number one bottleneck right now per venture? (4) What am I avoiding?

Format: War Room Brief — Last Week Score (%), Wins, Misses, Active Bottlenecks by venture, This Week's Three Non-Negotiables, One Honest Observation.

Constraints: No encouragement. No positive framing of a miss. Call it what it is.

---

THE OFFER SHARPENER

You are a direct response strategist who has built and launched over 50 productized service offers.

Context: I have a service or product that isn't converting as well as it should. The market exists — the positioning may be off.

Task: Analyze my current offer below. Identify the single biggest positioning weakness. Rewrite the offer from scratch with a sharper ICP, a clearer result, and a more specific proof mechanism.

My current offer: [paste your offer description, price, and target customer]

Format: (1) Diagnosis — what's weak and why. (2) Rewritten offer — headline, one-sentence result, three bullet deliverables, price anchor, ideal client sentence. (3) One A/B test to run immediately.

Constraints: No buzzwords. No generic language. Every claim must be specific and provable.

---

Both work with Claude or ChatGPT. Run the War Room one on a Sunday night and you'll see what I mean.

Built 8 more in the same structure if anyone wants them — drop a comment.

reddit.com
u/Frank_Eventus — 6 days ago

Built a prompt structure that actually gets usable output on the first pass — sharing two

Most prompts fail because they give the model nothing to work with. No role, no context, no constraints. You get a generic wall of text you have to edit into something yourself.

I've been using a five-part structure — Role, Context, Task, Format, Constraints — and the difference is significant. Here are two from a pack I built:

---

PROMPT: The Decision Pressure Test

You are a strategic advisor who specializes in pre-mortem analysis and decision stress-testing.

Context: I am about to make a significant business decision. Before committing, I want to pressure-test it from every angle.

Task: Run a full decision audit on the choice below. Argue both sides with equal force. Then identify the three assumptions my decision depends on that, if wrong, would make it a mistake.

Decision: [describe the decision and your current lean]

Format: (1) Case FOR — 4 strongest arguments. (2) Case AGAINST — 4 strongest arguments. (3) Three critical assumptions I'm making. (4) One question I haven't asked that I should.

Constraints: Do not tell me what to do. Do not soften either side. Your job is clarity, not comfort.

---

PROMPT: The Bottleneck Finder

You are a business systems analyst specializing in constraint theory and throughput optimization.

Context: My business is generating activity but not converting it to revenue at the rate it should. Something is the constraint — I may not be seeing it clearly.

Task: Analyze my business flow below and identify the single constraint that, if removed, would have the highest downstream impact on revenue. Do not give me a list of problems. Give me the one.

My current flow: [describe leads to sales to delivery to revenue cycle]

Format: (1) Identified constraint — one sentence. (2) Why this is the constraint, not a symptom. (3) Three actions to break it, ranked by speed of impact.

Constraints: No generic advice. If you don't have enough data, ask one specific question to get it.

---

Got 8 more built the same way if anyone wants them — drop a comment and I'll share.

reddit.com
u/Frank_Eventus — 6 days ago