Download for macOS
Skill

product-tracking-business-case

@accoil Updated 2026-10-20

Write a business case for adding product telemetry and analytics to a product. Produces a concise, stakeholder-ready document explaining what telemetry enables, what you're currently blind to, what's involved in implementation, and the business value. Sits outside the main telemetry lifecycle — use before committing to the technical work. Use when the user asks to 'write a business case,' 'justify analytics,' 'make the case for tracking,' 'telemetry brief,' 'why add analytics,' 'convince leadership about tracking,' or 'analytics ROI.'

accoilai-pluginsai-skillsamplitudeanalyticsb2bclaude-codemixpanel

Install

With your agent

Install OMGSkills skill "accoil/product-tracking-skills:skills/product-tracking-business-case" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/Accoil/product-tracking-skills /tmp/product-tracking-skills && ln -s /tmp/product-tracking-skills/skills/product-tracking-business-case ~/.claude/skills/product-tracking-business-case

From README

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: 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.