product-tracking-business-case

Name: product-tracking-business-case
Author: Accoil

36stars4forks

How to install product-tracking-business-case?

accoil/product-tracking-skills/product-tracking-business-case

$npx -y skills add Accoil/product-tracking-skills --skill product-tracking-business-case

Installs into the current project.

Summary

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 teleme

Files · 1

View on GitHub

SKILL.md

1	# Business Case
2
3	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.
4
5	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.
6
7	This skill sits outside the main telemetry lifecycle. It's the "convince" step that precedes everything else:
8
9	```
10	business-case → model → audit → design → guide → implement ← feature updates
11	```
12
13	## Goal
14
15	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.
16
17	## Prerequisites
18
19	None required. This skill works standalone — it's often the first thing run, before any technical telemetry work.
20
21	Optional context: If `.telemetry/product.md` exists, read it to make the case concrete and specific to the product. If it doesn't exist, gather enough context through conversation.
22
23	## Process
24
25	### 1. Understand the Product
26
27	If `.telemetry/product.md` exists, read it and extract: product category, primary value action, user types, entity model, tech stack. Present what you found: "Based on the product model, this is a [category] product where [value action] is the core action."
28
29	If no product model exists, ask:
30	- "What does your product do, in one sentence?"
31	- "Who is this business case for?" (engineering lead, founder, PM, board)
32	- "Do you have any analytics today, or is this greenfield?"
33
34	Keep it to 2-3 questions. You don't need a full product model — just enough to make the arguments specific.
35
36	### 2. Identify Blind Spots
37
38	This is the most persuasive section. Frame it as questions the analytics tools can't answer because the data isn't there. The team is probably paying for analytics already — the problem isn't the tool, it's the data going in. Tailor to the product type:
39
40	For B2B SaaS:
41	- Which accounts are at risk of churning? (no engagement data)
42	- Which features drive upgrades? (no correlation between usage and expansion)
43	- Are new accounts reaching value, or stalling during onboarding? (no activation tracking)
44	- Which accounts would benefit from outreach? (no engagement scoring)
45
46	For B2C / consumer products:
47	- Where do users drop off in key flows? (no funnel data)
48	- Which features are actually used vs. built but ignored? (no adoption data)
49	- What drives retention vs. one-time usage? (no cohort analysis)
50
51	For any product:
52	- How long does it take new users to reach the core value action?
53	- Which integrations/features correlate with retention?
54	- Are you building features that users actually want, or guessing?
55	- When usage limits are hit, do users upgrade or leave?
56
57	Don't list all of these — pick the 4-6 that hit hardest for this specific product.
58
59	### 3. Frame What Proper Instrumentation Unlocks
60
61	Position this as unlocking the analytics investment the team has already made — not as a new technical project. The analytics tools work fine. The data going in is the problem. Once the right data is flowing, the tools can finally deliver:
62
63	\| What Becomes Possible \| Why It Matters \|
64	\|----------------------\|----------------\|
65	\| Analytics tools can surface at-risk accounts \| CS can act before accounts churn, not after — because engagement signals are finally flowing \|
66	\| Analytics tools can show expansion opportunities \| See which accounts are hitting limits or using power features — data that drives revenue \|
67	\| Onboarding visibility becomes real \| Time-to-value, activation milestones, drop-off points — the data your analytics tool needs to show you where users stall \|
68	\| Feature adoption is visible \| Your analytics tool can finally answer "which features are used, by whom?" — so roadmap decisions are based on data, not gut feel \|
69	\| Account-level segmentation works \| Group accounts by actual behavior — because the usage data powering segmentation is accurate \|
70
71	Select the 3-4 most relevant

AccoilPublisher · 9 listings

Preview

Accoil/product-tracking-skills

# 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

**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 team

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

RepoAccoil/product-tracking-skills

LicenseMIT

TypeSkills

CategoryMarketing

UpdatedMar 2026

Repo stars36

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type