Use-case library
Real, cross-tool examples — most pulling in an outside signal as well. Search by tool or outcome, or filter by area. Every example uses sample data.
Showing 52 of 52
Blocked issues in Linear, no merges in GitHub, a design still moving in Figma and an unanswered “who owns QA?” in Slack — for a date two customers were promised in HubSpot and a competitor just shipped.
Champion quiet in HubSpot and Gmail, usage down in Amplitude, tickets turning negative in Zendesk — and a restructure in the news that puts their budget in question.
A new EU data-retention rule maps to a year-old policy in Notion, a Logging project in Linear that doesn’t cover it, and two enterprise deals in HubSpot waiting on a compliance answer.
A dependency advisory matched against your GitHub SBOM hits a customer-facing service in Datadog — while the patch task in Linear is still sitting open.
A capability being pitched in Gong calls and live HubSpot deals was quietly deprioritised in Linear last sprint — a collision heading straight for a renewal.
A departure in BambooHR matched against GitHub CODEOWNERS shows the sole approver on a core service is leaving in two weeks, with no cover lined up.
A renewal in HubSpot, an exec change on LinkedIn and a stuck Zendesk ticket all point at the same account — and one clear move to save it.
A signed agreement in DocuSign commits to an uptime SLA your Statuspage history doesn’t hit — with no reliability work in Linear to close the gap.
Committed spend in Ramp plus the hiring plan in Rippling, weighed against cash in QuickBooks, pushes runway past your threshold sooner than the board thinks.
A rival shipped a feature you have in beta — surfaced against your roadmap in Linear and your GTM plan in Notion so leadership can respond on purpose, not in a panic.
An epic in Linear is silently blocked by a ticket in another team’s Jira — surfaced before the deadline instead of at it.
Overlapping epics in Linear and parallel work in two GitHub repos, discussed in separate Slack channels — duplicated effort no one had connected.
A leaked credential in a GitHub commit, with the rotation task in Linear open for three days — and the clock running the whole time.
A call made in Slack three weeks ago still conflicts with the plan in Notion and the active roadmap in Linear — and work is moving on the old assumption.
A spike in failed Stripe payments concentrated in one plan tier — real revenue leaving quietly, with no dunning follow-up logged in HubSpot.
A project marked complete in Linear still has open errors in Sentry and rising tickets in Zendesk — shipped, but not finished.
The same Datadog alert paged three times this month and was closed each time without a fix surviving in Linear — a pattern, not a blip.
60% of in-flight Linear issues, on-call in PagerDuty and three interviews in Greenhouse all land on the same engineer.
A contract in Ramp renews next week at a higher rate, the cancellation window closing, and no one looking at it.
A commitment captured in a Gong call has no matching item in Linear — a trust problem waiting quietly for the next QBR.
An acquisition in the news matched to an open account in HubSpot — expansion or churn, surfaced to the account lead while there’s still time to shape it.
A mention in the news spikes traffic in GA4 and tickets in Zendesk — surfaced in time to staff the queue, not after the one-star reviews.
A promise in the board deck on Drive has no matching project or anyone responsible in Linear — a commitment slowly being forgotten.
An offboarding in BambooHR with lingering admin access across three tools in Okta — access that should already be gone.
A new logo closed in HubSpot, no activation in PostHog after two weeks and no kickoff booked in Calendar — a churn risk born on day one.
An epic’s issue count in Linear is up 40% in a fortnight — against a delivery date written into a HubSpot contract.
A tagged release in GitHub with no changelog in Notion and no customer note in Gmail — value shipped that nobody knows about.
A dip in PostHog activation lines up with a specific GitHub PR — a regression the metrics caught before any human reported it.
A Looker dashboard has had no fresh data for five days, and decisions in Slack are being made on numbers that stopped updating.
SLA slipping in Zendesk for your top three accounts, each with a quarterly review booked in Calendar next week.
A discount in a HubSpot deal pushes below the margin floor in your finance model — flagged before it’s signed, not after.
A dependency posted degraded service on its status page, matched to your SSO rollout in Linear that relies on it.
A flag still live in LaunchDarkly for a PostHog experiment that finished weeks ago — shipping untested behaviour to everyone.
A company goal in Notion has no active projects in Linear this quarter — a priority that exists on paper only.
Seat reductions in Stripe across three accounts in the same segment this month — an early pattern, not three coincidences.
A run of G2 reviews about a problem your Zendesk queue already shows — the same issue, now out in public.
A bet leadership cares about has gone quiet across Linear, Slack and GitHub for a month — drifting without anyone noticing.
A freeze in the board doc on Drive, with many requisitions still live in Greenhouse — a costly, avoidable misalignment.
A TLS certificate set to expire days before a launch booked in Calendar — a self-inflicted outage, caught well ahead.
Two leaders set different top priorities in different Slack channels this week — surfaced so it’s settled once, not re-fought in every standup.
Top no-result help searches in Zendesk line up with your most-used features in PostHog — exactly where docs would cut tickets fastest.
A pricing-page experiment in GA4 is sending signups to a plan being deprecated in Linear — money and goodwill into a dead end.
A data-residency request from a prospect in HubSpot, checked against where data actually sits in your infra docs in Notion.
A rival raised a round targeting your segment, surfaced against the at-risk renewals in HubSpot it’s most likely to threaten.
The same “we should…” keeps appearing in retros in Notion and never turns into a Linear task — a lesson the team keeps not learning.
Leadership calendars sit at 80% booked while the quarter’s top project has no working time blocked anywhere.
A detractor in your latest survey is also the logo on a reference slide in Notion — a reputational risk surfaced before it’s used.
A start date in Rippling lands before laptop and access provisioning in Okta — a wasted first day, caught in advance.
A competitor changed their pricing page, surfaced against your live pricing experiment in Stripe so you’re not testing against stale assumptions.
A competitor announced a partnership with one of your key vendors — a supply risk surfaced against your contracts in Ramp.
A feature waitlist in Airtable for something that just shipped in GitHub — warm, ready-to-convert demand sitting unanswered.
Three of the four people on a Linear launch are out the week it ships, according to Calendar — a slip you can still avoid.
An ops risk audit turns a handful of your tools into your first brief — without a full rollout.