21 example Ops · 7 roles · every one human-gated
Use-case gallery

Before & after: an Op for every desk

A cross-functional pass at concrete Ops — one set per role, deliberately not status roll-ups. Each turns a painful manual ritual into a Frame-oriented workflow that drafts the work and leaves the judgment with a human.

These are candidates, not commitments. Skim by role, flip to "Just the win" to see only the after-state, and when one fits, it can be built step-by-step the same way the weekly-status guide was.

7
functions covered
21
candidate Ops
100%
keep a human gate
Marketing

From blank page to on-brand draft

Brand voice and messaging discipline stop living in a style guide nobody reads and start orienting every draft automatically.

01

Campaign brief → launch kit

● Today
  • A one-line idea sits in a queue; an agency round-trips for a week.
  • Drafts come back off-voice, with the wrong product names.
  • Blog, social, email, and landing copy are written separately and drift apart.
▶ With the Op
  • One brief in → a full kit out: blog post, 5 social variants, email, landing copy.
  • All in the brand voice and approved terminology, because the Frame carries them.
  • You edit the angle and approve — no re-briefing the voice every time.
Powered byFrame · Brand VoiceCog · Campaign-WriterOp · launch-kityou approve copy
02

Webinar recording → repurposed content

● Today
  • Someone re-watches a 60-minute recording to find the good moments.
  • Clips, recap, and posts get written by hand, days after the event.
  • Most of the content value evaporates before anything ships.
▶ With the Op
  • Reads the Drive transcript → drafts a recap, 8 social posts, a clip list, and a nurture email.
  • Quotes are pulled verbatim with timestamps so nothing is misattributed.
  • You pick the clips and hit publish.
Powered byFrame · Brand VoiceCog · Transcript-MinerCog · WriterOp · repurposeyou pick clips
03

Pre-publish brand & claims check

● Today
  • One person eyeballs everything; off-voice phrasing and risky claims slip through.
  • Legal-sensitive language is caught late, if at all.
▶ With the Op
  • Scans any team's draft against the brand and claims/legal Frames.
  • Flags off-voice lines and unsupported claims inline, with the rule cited.
  • You accept or override each flag before it ships.
Powered byFrame · Brand VoiceFrame · Claims/LegalCog · Brand-GuardOp · brand-reviewyou resolve flags
Sales

More selling, less assembling

Your methodology, pricing rules, and approved answers orient every rep's AI — so prep and paperwork stop eating the day.

01

Account research → pre-call brief

● Today
  • The rep spends 45 minutes googling and digging through the CRM before each call.
  • Prior touches and open threads are scattered across email and notes.
▶ With the Op
  • Assembles a one-page brief: company, recent news, stakeholders, our history, a tailored talk track.
  • Framed in your sales methodology's stages and language.
  • You skim it on the way into the call.
Powered byFrame · Sales MethodologyCog · Account-ResearchCog · CRM-ReaderOp · pre-callyou run the call
02

Security questionnaire / RFP drafting

● Today
  • A 200-question questionnaire eats days of copy-paste and SME chasing.
  • Answers come out inconsistent across deals and reps.
▶ With the Op
  • Drafts every answer from the approved-answer library and current docs.
  • Routes only the genuine gaps and exceptions to an SME.
  • Security reviews the exceptions, not all 200.
Powered byFrame · Approved AnswersCog · RFP-DrafterOp · questionnaireSME clears exceptions
03

Approved quote → tailored proposal

● Today
  • The rep hand-builds a proposal from an old deck, often with stale terms.
  • Discount and term mistakes slip past until deal desk catches them.
▶ With the Op
  • Composes a proposal from the pricing, brand, and legal-terms Frames.
  • Out-of-policy discounts are blocked at a manager approval gate.
  • The rep personalizes the narrative; the numbers are already right.
Powered byFrame · PricingFrame · Legal TermsCog · Proposal-BuilderOp · deal-deskmanager approves discount
Accounting & Finance

Reconcile and explain, with the rule cited

Policies, chart-of-accounts conventions, and the CFO's format orient the work — and every number traces back to its source.

01

Budget-vs-actual variance narrative

● Today
  • An analyst reconciles the GL and hand-writes the commentary each month.
  • The "why" behind a variance gets thinner the closer it is to the deadline.
▶ With the Op
  • Drafts the variance narrative with drivers, in the CFO's exact format.
  • Every explanation cites the GL lines and journal entries behind it.
  • The controller reviews and signs off.
Powered byFrame · Reporting StandardsCog · Variance-AnalystOp · variance-narrativecontroller signs off
02

Invoice 3-way match & exception triage

● Today
  • AP manually matches each invoice to its PO and receipt.
  • Discrepancies trigger a chase across email threads.
▶ With the Op
  • Auto-matches invoice ↔ PO ↔ receipt and clears the clean ones.
  • Drafts an exception note explaining each mismatch and likely cause.
  • The clerk approves payment batches at the gate.
Powered byFrame · AP PolicyCog · Match-EngineOp · 3-way-matchclerk approves payment
03

Expense report policy review

● Today
  • Managers rubber-stamp reports or miss quiet policy violations.
  • Enforcement is inconsistent from approver to approver.
▶ With the Op
  • Checks each report against the T&E policy Frame.
  • Flags violations with the specific rule and threshold cited.
  • The approver decides; consistent standard every time.
Powered byFrame · T&E PolicyCog · Expense-AuditorOp · expense-reviewapprover decides
Project Management

Capture, assess, and chase — without the busywork

Beyond the status roll-up: the recurring coordination work that quietly consumes a PM's week.

01

Meeting → decisions & action items

● Today
  • The PM re-watches the recording, types notes, and creates tickets by hand.
  • Decisions get lost; action items land without owners or dates.
▶ With the Op
  • Turns the transcript into logged decisions, owners, due dates, and a recap.
  • Drafts the tracker tickets and a channel summary.
  • The PM confirms before anything is written to the board.
Powered byFrame · ProgramCog · Transcript-MinerCog · Tracker-WriterOp · meeting-recapPM confirms tickets
02

Scope-change impact assessment

● Today
  • A change request lands; the PM scrambles to assess schedule and cost impact.
  • Assessments vary in depth and rarely surface hidden dependencies.
▶ With the Op
  • Drafts an impact assessment: affected milestones, cost delta, dependency ripple.
  • Framed in the program's terms and critical-path logic.
  • PM and sponsor make the call at the change-control gate.
Powered byFrame · ProgramCog · Change-ImpactOp · change-controlsponsor approves
03

Cross-team blocker & dependency sweep

● Today
  • The PM manually hunts boards and channels for stale dependencies and blockers.
  • Escalations go out late, after the blocker has already cost time.
▶ With the Op
  • Sweeps boards and channels for cross-team blockers and aging dependencies.
  • Drafts an escalation list with owners and the ask, ready to send.
  • The PM reviews and fires the escalations.
Powered byFrame · ProgramCog · Blocker-ScoutOp · blocker-sweepPM sends escalations
Executive · VP / Division Lead

Synthesis, on tap and on-message

The org's narrative, decision framework, and your voice orient the heavy synthesis work so you can spend time deciding, not assembling.

01

QBR / board pack assembly

● Today
  • Weeks of wrangling slides and chasing teams for inputs each quarter.
  • The story arrives late and reads like stitched-together fragments.
▶ With the Op
  • Composes a draft pack from the quarter's accumulated program memory.
  • In the exec-narrative and investor framing your org already uses.
  • You shape the story and the asks; the assembly is done.
Powered byFrame · Exec NarrativeCog · Pack-ComposerOp · qbr-packyou shape the story
02

Messy question → decision brief

● Today
  • A build-vs-buy or vendor choice means reading five docs and synthesizing by hand.
  • Tradeoffs are framed differently each time, hard to compare.
▶ With the Op
  • Drafts a one-page brief: options, tradeoffs, recommendation, risks.
  • Structured in the org's standard decision framework.
  • You decide; the prep is consistent and fast.
Powered byFrame · Decision FrameworkCog · Decision-BriefOp · decision-briefyou decide
03

Org-wide comms draft

● Today
  • All-hands and reorg messages take many revisions to hit the right tone.
  • Drafts wander off-voice and need heavy rewrites.
▶ With the Op
  • Drafts the message in your voice and the company Frame's tone.
  • Sensitive phrasing routes through the comms/legal Frame first.
  • You approve before it goes wide.
Powered byFrame · Company VoiceCog · Comms-WriterOp · org-commsyou approve send
Software Engineering

Less archaeology, faster to root cause

Team conventions, runbooks, and the service map orient the AI so the grunt work of reconstruction and triage drafts itself.

01

Incident → blameless postmortem

● Today
  • On-call reconstructs the timeline from alerts, logs, PRs, and the incident channel.
  • The postmortem lands days later, with gaps.
▶ With the Op
  • Drafts a postmortem: timeline, contributing factors, action items — in the team template.
  • Every event in the timeline links to its evidence.
  • The incident commander reviews and owns the conclusions.
Powered byFrame · Incident RunbookCog · Timeline-BuilderCog · Log-ReaderOp · postmortemIC owns conclusions
02

Red build → triage & fix proposal

● Today
  • A dev digs through CI logs and recent diffs to figure out what broke.
  • Flaky-vs-real failures waste cycles before anyone starts fixing.
▶ With the Op
  • Gathers the failure, recent diffs, and flaky history → drafts a root cause + proposed fix.
  • Distinguishes a real regression from a known flake.
  • The dev reviews the diagnosis and applies the patch.
Powered byFrame · Eng ConventionsCog · CI-TriageOp · build-triagedev applies fix
03

CVE → remediation PRs

● Today
  • A new CVE means manually auditing every repo for the affected dependency.
  • Upgrades and test plans are pieced together service by service.
▶ With the Op
  • Finds affected services and drafts the upgrade PRs plus a test plan for each.
  • Respects the team's versioning and review conventions.
  • The engineer reviews and merges — the gate stays on the merge.
Powered byFrame · Eng ConventionsFrame · Security PolicyCog · RemediatorOp · cve-remediateengineer merges
CEO

The narrative and the signal, every day

The strategic narrative and investor framing are the highest-leverage context in the company — and the one most prone to drift. These keep it coherent.

01

Investor update draft

● Today
  • The CEO writes each update from scratch and pulls the metrics by hand.
  • The narrative subtly shifts month to month and across audiences.
▶ With the Op
  • Composes the update from org memory in the investor Frame — metrics, narrative, asks.
  • The strategic story stays coherent across every update.
  • The CEO sets the message and approves.
Powered byFrame · InvestorCog · Update-ComposerOp · investor-updateCEO approves
02

Morning signal brief

● Today
  • The CEO scans dashboards, escalations, email, and competitor news across many tabs.
  • The important signal is buried in the noise.
▶ With the Op
  • Synthesizes overnight signals into a one-page brief: key metrics, escalations, must-reads, competitor moves.
  • Prioritized by what the strategic Frame says matters most.
  • The CEO reads it with coffee; decides where to lean in.
Powered byFrame · Strategic PrioritiesCog · Signal-SynthOp · daily-briefCEO directs focus
03

Rough thinking → strategy memo

● Today
  • Turning a half-formed idea into a crisp memo takes many drafts and late nights.
  • The framing rarely matches how the company already talks about strategy.
▶ With the Op
  • Shapes notes and dictation into a structured strategy memo in the company voice.
  • Grounded in the strategic Frame's language and prior decisions.
  • The CEO refines the argument; the scaffolding is there.
Powered byFrame · Strategic NarrativeCog · Memo-DrafterOp · strategy-memoCEO refines
One pattern, every desk

Different work, same shape

Every example above is the same three pieces: a Frame carrying the role's context, one or more Cogs doing the drafting, and an Op that orchestrates them and stops at a human gate. The role changes; the architecture doesn't.

Pick any one and it can be built step-by-step the same way as the weekly-status walkthrough →  ·  New to the ideas? Start with the concepts.