Skip to main content

Use Cases

Operations

For BizOps, IT, BD, COO staff, EAs, chiefs of staff — the people the rest of the company depends on to keep track of everything that isn't a deal or a feature. Vendors, contracts, renewals, incidents, internal projects, headcount.

If your day looks like this​

  • You're the human spreadsheet for vendor renewals, contract dates, and recurring obligations.
  • Incidents happen across systems and someone has to compile the report after.
  • You're CC'd on more threads than anyone in the company.
  • Internal projects span multiple teams and the status lives in your head.

Set up first​

  1. A Vendors project — every vendor contract, SLA, renewal date, and contact.
  2. An Incidents project — every Sentry/PagerDuty/Datadog alert, every status-page post-mortem.
  3. Delegate your assistant address as a recipient for status alerts, billing notifications, vendor newsletters, and GitHub/Linear digests.

Use cases worth setting up​

Renewal calendar that surfaces itself​

Forward every signed vendor contract into Vendors. Set a scheduled task on the 1st of every month: "list every vendor renewal in the next 90 days. Sort by spend. Flag any with notice periods that fall inside the window."

You stop missing notice periods. Procurement stops being a fire drill.

Incident digest that writes itself​

Subscribe Deck to your incident alert email (Sentry, PagerDuty, Datadog) — add your assistant address to each tool's notification list. Friday afternoon: "summarize this week's incidents. Group by system, list owners, and flag any that recurred."

You walk into Monday's ops review with the recap already written.

SLA and SLO tracking​

If your vendors report SLAs via monthly emails, Deck reads them as they arrive. Ask: "which vendors missed SLA last quarter? Which improved?"

You'd never compile this by hand. Now you don't have to.

Internal-project status digest​

Each project owner CCs Deck on weekly status emails. End of week: "give me a one-pager across every active internal project — owner, status, blockers, what's needed from me."

The same idea that powers exec briefs, applied to operational work.

Onboarding checklists from threads​

CC Deck on the long onboarding email thread for a new hire or new vendor. Ask: "what's still outstanding from the onboarding for [X]?"

Threads turn into accountable next-step lists without anyone manually maintaining a doc.

Contract Q&A​

Forward a signed contract into Vendors. Months later: "what's the notice period on the [Vendor] agreement? What's the price escalator clause? When does it auto-renew?"

Contracts you never have to re-read.

Monthly board / ops review prep​

Once a month: "give me everything that changed in Vendors, Incidents, and Internal Projects in the last month. Group by category, flag what needs a decision."

The prep doc writes itself; you edit and present.

What good looks like after two weeks​

  • No renewal sneaks up on you.
  • The Friday ops summary writes itself; you read and send.
  • Vendor questions are answered in seconds, not by hunting through Drive.
  • Internal-project status across the org is a one-sentence query away.