Best PromptsSOP From a Process Walkthrough
Turn a rambling explanation or transcript of how you do a task into a follow-able SOP with decision points, screenshots slots, and a QA check.
Turn my process walkthrough into a real SOP. The process, as I actually do it (talk it out: messy is fine, include the "oh and sometimes..." parts): """ [PASTE: a voice-memo transcript, a Loom transcript, or just type it out stream-of-consciousness] """ Who will follow this SOP: [NEW HIRE / VA / TEAMMATE COVERING FOR ME, and what they can be assumed to know] How often it runs + what triggers it: [e.g. "every Monday" / "when a refund request arrives"] Tools involved: [THE APPS/SYSTEMS + who has access] Build the SOP: 1. **Header block**: purpose (why this process exists, in one sentence: people skip steps they don't understand the point of), owner, frequency/trigger, time it should take, tools + access needed. 2. **The steps**: numbered, one action per step, each starting with a verb, concrete enough that the stated audience can execute without asking me. Where my walkthrough said "then I just sort of...", that's where the real knowledge hides: unpack it or mark [DETAIL NEEDED: what exactly happens here?]. 3. **Decision points as forks**: every "it depends" in my walkthrough becomes an explicit IF/THEN: "IF the amount is under $100 → step 7. IF over → escalate to [ROLE], stop here." Undocumented judgment calls are why SOPs fail their first real-world contact. 4. **[SCREENSHOT] markers**: at every step involving a UI: what the screenshot must show. I'll capture them; you place them. 5. **The edge cases and landmines**: from my "sometimes..." asides: the known weird cases, each with its handling. Plus the DON'T list: the 2-3 mistakes that cause real damage in this process, stated with why. 6. **Done-right check**: how the person verifies their own output before finishing (the QA step), and what "done" triggers next (notify whom, update what). 7. **The gaps list**: everything my walkthrough left ambiguous, as questions back to me. An SOP with silent guesses is worse than no SOP. Rules: write at the assumed-knowledge level of my stated audience, a VA needs the login step; a teammate doesn't. Keep it under 2 pages; if the process genuinely needs more, propose splitting it into linked SOPs at the natural seams. Plain language, no corporate process-speak.
More business prompts
Build me a monthly budget and a debt payoff plan from these numbers. Take-home income per month: [AMOUNT, and note if it varies] Fixed costs: [RENT/MORTGAGE, UTILITIES, INSURANCE, SUBSCRIPTIONS, TRANSPORT, CHILDCARE, with amounts] Variable spending, last 3 months if known: [GROCERIES, DINING, SHOPPING, ETC.] Debts: [FOR EACH: name, balan
Budget and Debt Payoff Plan
Turn your real income, bills, and debts into a monthly budget and a payoff schedule with the math shown and the tradeoffs named.
Businessbeginner
Build a 13-week cash flow forecast. Cash on hand today: [AMOUNT, and which accounts] Any restricted or committed cash: [AMOUNT AND WHAT IT IS FOR] Expected inflows: - Receivables outstanding: [CUSTOMER, AMOUNT, INVOICE DATE, TERMS, and how reliably each pays] - Recurring revenue: [AMOUNT, BILLING DATE, CHURN ASSUMPTION] - New sales expe
13-Week Cash Flow Forecast
Build the rolling weekly cash forecast operators actually run on: opening balance, timed inflows and outflows, and the week you run short.
Businessadvanced
Help me set pricing for [PRODUCT/SERVICE]. What it does and who buys it: [PRODUCT + BUYER] The alternative if they do not buy: [COMPETITOR, IN-HOUSE, SPREADSHEET, DOING NOTHING] What that alternative costs them: [MONEY, TIME, RISK. Estimate if needed and say so.] Value we create, quantified if possible: [TIME SAVED, REVENUE GAINED, COST
Pricing Strategy
Work out what to charge and how to package it: value basis, tier structure, the metric you meter on, and how to test before committing.
Businessadvanced