Quarterly Ops Review

A recurring back-office review: flow, capacity, vendors, spend, and SOPs vs last period and target, with rule-based RAG and top 3 fixes.

Business & Ops / Operationsoperations-reviewbizops
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Map vendor SLA requirements and assess coverage gaps.”
Beforegeneric AI agent
Managing vendors is complex because you need to track contracts, service levels, and whether they're actually meeting their commitments. You could document everything in a spreadsheet, but it's easy to lose track of renewal dates or performance issues. Different vendors have different SLA terms, so comparing them is hard. You might want to categorize by criticality—which vendors are essential to your business? What's your current vendor portfolio size, and which ones are causing problems?
Afterwith Quarterly Ops Review
VENDOR SLA ASSESSMENT

CRITICAL VENDORS (must not fail)
1. Cloud infrastructure provider: 99.95% uptime SLA, 4-hour support response
2. Payment processor: 99.99% uptime, settlement within 24 hours
3. Email delivery: 98% inbox placement, 2-hour support window

SECONDARY VENDORS (impact business but not critical)
1. Analytics platform: 99% uptime, next-business-day support
2. Customer communication tool: 95% uptime, standard ticket support

COVERAGE GAP ANALYSIS
RISK 1 → No backup for cloud provider (single-vendor lock-in)
  ACTION: Evaluate multi-region failover or secondary cloud provider for 10% traffic
  PRIORITY: Q3 2027

RISK 2 → Payment processor has no redundancy
  ACTION: Contract secondary processor for 15% volume spillover
  PRIORITY: Q4 2026

RISK 3 → Email delivery SLA doesn't guarantee sender reputation
  ACTION: Establish dedicated IP pool, requires 3-month warm-up
  PRIORITY: Ongoing

VENDOR SCORECARD (quarterly review)
→ Uptime performance vs committed SLA
→ Support ticket resolution time (target: under SLA max)
→ Cost increases YoY (flag anything >5%)
→ Contract renewal dates (set calendar reminders at 6 months)

MONTHLY FOLLOW-UP
• Track incident reports from each vendor
• Escalate SLA breaches immediately
• Document workarounds if SLA violated

About this skill

Operations problems creep in quietly: cycle times stretch, renewals auto-renew, runbooks go stale. This skill builds a recurring review that compares each metric with last period and a target, so drift shows up before it hurts.

What it does

  • Picks the 8-12 ops metrics that fit your business across flow, capacity, vendors, spend, and knowledge
  • Compares each with last period and target, with source and date
  • Grades red, amber, and green by rules stated up front, not by feel
  • Lists renewal notice deadlines and other dates before the next review
  • Chooses the top three issues with owner, date, and success measure

What you get

A one-page review: headline, scorecard, what changed and why, top 3 actions, upcoming deadlines, deep dives needed, and data gaps.

Best for

Heads of operations, BizOps leads, and founders running monthly or quarterly reviews, or preparing the ops section of a QBR or board pack.

SKILL.md preview

SKILL.md
---
name: quarterly-ops-review
description: Run a recurring operations review (monthly or quarterly) across the whole back office - process flow, team capacity, vendors and renewals, spend, and SOP freshness - from the user's own data, with each metric compared to last period and a target, red/amber/green status that follows stated rules, and the three issues to act on next quarter. Use when the user says "prep our quarterly ops review", "BizOps review", "ops health check", "what should ops fix next quarter", "put together the ops section for the QBR", "monthly ops scorecard", or "how is operations doing overall?".
---

# Quarterly Ops Review

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More business & ops skills

View all Business & Ops skills →