The internal operations category is the one nobody markets. Customer Ops has obvious revenue tie-in. Marketing and Sales gets the budget. Strategy and Research gets the executive attention. Internal Ops is the work that quietly determines whether the rest of it runs — and it is also the work that founders, ops managers, and fractional leaders procrastinate on the longest because the artifacts (compliance policies, contract reviews, raw thinking turned into tasks) are tedious to produce and easy to defer. This week's three templates are calibrated to that exact pile. The unglamorous work. The stuff that gets shoved to Friday afternoon and then to next Friday and then to "after the launch" and then it is six months later and there is a customer asking for your SOC 2 report or a renewal date you missed by a week. ## What's New This Week **SOC 2 / Compliance Policy Drafting Prompt** (Internal Ops, Advanced) — Paste in a 1–2 page plain-English description of how your business actually performs a practice (access control, change management, vendor management) and get back a structured first-draft policy section with every control statement mapped to specific Trust Services Criteria (CC6.1, CC6.2, etc.), known gaps flagged honestly in their own section, and values the model could not invent (dates, frequencies, employee counts) marked as `[NEEDS_INPUT]` ready for you to fill in. Built for the moment a prospect asks for your SOC 2 report and you have a blank policy template open. **Vendor Contract Summary Prompt** (Internal Ops, Intermediate) — Paste in a full vendor contract package — MSA, order form, DPA, schedules — and get back a one-page summary in ten sections covering obligations, money, renewal and termination, data and IP, liability, and a triaged red-flag list calibrated to the deal size. Every risk-bearing term is quoted exactly with section citations, so you can verify before you sign. The template is the bridge between reading every word yourself (slow) and sending every contract to outside counsel (expensive). **Voice Memo to Task List Converter** (Internal Ops, Beginner) — Paste in the transcript of a 2–5 minute voice memo and get back a prioritized task list bucketed into Today / This Week / Next Week / Backlog, with owners matched to your team roster, absolute dates resolved from relative references ("by Thursday" → 2026-05-15), and an index of every customer or project mentioned so you can spot pile-ups before they become fire drills. For the operators who think out loud and end every week with a notes app full of meandering audio that never becomes action. ## Why These Three Together These three templates look unrelated on the surface — a compliance policy, a contract review, a voice memo cleanup. The thread connecting them is the shape of the input. Each one starts with messy, unstructured material that you have in front of you anyway (how your business actually operates, a stack of contract PDFs, the audio of your own thinking) and produces a structured, citable, operator-ready output. The category we keep deferring is rarely deferred because the work is hard — it is deferred because the gap between unstructured input and shippable artifact feels too wide to cross in a single sitting. This is also the category where the model has to be most disciplined about not inventing things. A made-up control on a SOC 2 policy gets caught in audit. A misremembered liability cap loses you tens of thousands of dollars at renewal. A fabricated task owner means someone shows up to a meeting that was never on their calendar. All three templates are written with explicit "if the input does not contain this, say so — do not invent" rules, and they preserve quoted source language wherever risk is at stake. The point is not to replace the operator's judgment — it is to get the structural work done in 5 minutes so the operator's judgment can spend its time on the parts that actually require it. ## A Note on Model Choice The three templates this week sit at different points on the model-tier curve. The Voice Memo converter runs cleanly on Haiku 4.5 or GPT-4o mini — the work is structural cleanup and the cheaper models do it well. The Vendor Contract Summary needs a long-context model (100K+ tokens) because contract packages routinely run 30+ pages and lower-context models silently truncate the back half where the worst clauses hide. The SOC 2 Policy Drafting needs a frontier-tier model (GPT-4o or Claude Sonnet 4 or higher) because the TSC control-ID mapping breaks on cheaper models — they hallucinate CC numbers and invent criteria that do not exist. Each template's frontmatter lists the supported tools and the difficulty rating signals the model class. When in doubt, the rule is: structural cleanup on cheap models, document-length work on long-context models, anything involving named identifiers or codes (compliance criteria, contract sections, regulatory frameworks) on frontier models. ## Get Started All three templates are available now for Pro members: - **SOC 2 / Compliance Policy Drafting Prompt** — in [Internal Operations](/internal-operations) - **Vendor Contract Summary Prompt** — in [Internal Operations](/internal-operations) - **Voice Memo to Task List Converter** — in [Internal Operations](/internal-operations) Pick the one that maps to the unglamorous work currently sitting at the top of your "I will do this on Friday" list. The compounding wins in operations come from clearing those piles before they grow, not from optimizing the work you already enjoy doing.