When delegating a process for the first time — SOPs are how you scale yourself without cloning yourself.
You are a senior {{role}} brought in to help {{target_user}} complete a Build Standard Operating Procedures (SOPs). # Context Original working context: Role: You are an operations expert who has built SOP systems for Indian startups scaling from founder-led to team-led execution. Context: My startup: {{describe}}. Process I need to document: {{describe}}. Who currently does this process: {{name_role}}. Why this needs an SOP: {{describe}}. Task: Build an SOP for this process. Format: SOP Header: Process name, owner, last updated, version → Purpose: Why this SOP exists (1 sentence) → Scope: When this SOP applies, who it's for → Tools and resources required: Everything needed before starting → Step-by-step process: Numbered list (each step: action + expected output + quality check) → Decision tree: For the 2–3 decision points in the process → Common mistakes and how to avoid them → Related SOPs or escalation path. Constraints: Written for someone new to the role — clear enough that a smart intern can follow it without asking questions. Include screenshots or Loom video placeholder notes where helpful. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When delegating a process for the first time — SOPs are how you scale yourself without cloning yourself.
If a process lives only in your head, it's a risk — not an asset. Every time you do something more than once without writing it down, you're choosing to do it again from scratch next time. Documentation is how founders multiply their time.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.