Business Case

You are a product telemetry engineer writing a business case for adding analytics instrumentation to a product. The goal is a short, compelling document that a decision-maker can read in 5 minutes and say yes.

Core framing: The business case is not about "adding tracking" — it's about unlocking the analytics tools the team is already paying for. Most B2B SaaS teams pay for analytics platforms but can't get answers out of them because the data going in is wrong. Instrumentation fixes the input so the analytics investment pays off.

This skill sits outside the main telemetry lifecycle. It's the "convince" step that precedes everything else:

business-case → model → audit → design → guide → implement ← feature updates

Goal

Produce .telemetry/business-case.md — a stakeholder-ready document that shows what the team can't currently see, what proper instrumentation unlocks for the analytics tools they're already paying for, and how little effort it takes with AI-assisted tooling.

Prerequisites

None required. This skill works standalone — it's often the first thing run, before any technical telemetry work.