一键导入
business-value-case
Use when a seller needs to generate a Business Value Case (BVC) for a dbt Labs prospect, iterate on an existing BVC, or publish a BVC to Notion
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when a seller needs to generate a Business Value Case (BVC) for a dbt Labs prospect, iterate on an existing BVC, or publish a BVC to Notion
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user needs more local disk space, hits ENOSPC or disk full errors, asks to clean stale worktrees, caches, target dirs, Trash, or says to preserve running agents, active worktrees, or PR-specific worktrees during cleanup under /Users/dataders/Developer.
Use when the user asks to clean up, prune, remove, or "get rid of" stale, old, merged, or unneeded git worktrees (worktrunk `wt` / `git worktree`).
Use when quantifying dbt Labs ROI for a Business Value Case — needed for benchmark data, business initiatives definitions, or classifying discovery pain points into value pillars and Ref IDs
Use when scanning the data ecosystem for content opportunities, generating a daily content brief, or populating the Content Pipeline Notion database with ranked content ideas tied to dbt Labs content pillars
Draft a Fusion Diary post — the periodic community update for dbt's Fusion compiler project. Use this skill whenever the user says "fusion diary", "write a diary", "draft a diary", "new diary post", or asks to summarize what's new in Fusion for the community. Also trigger when the user asks to compile Fusion release notes, Fusion progress updates, or a community-facing summary of dbt-fusion changes. The skill handles finding the baseline (most recent prior diary), pulling from GitHub, Slack, and Notion, and producing a structured draft in the correct voice.
Generate clean, data-focused charts and dashboards from compact JSON specs
| name | business-value-case |
| description | Use when a seller needs to generate a Business Value Case (BVC) for a dbt Labs prospect, iterate on an existing BVC, or publish a BVC to Notion |
Builds quantified, 5-page business value cases for dbt Labs prospects. Maps discovery pain points to the 3-pillar Value Framework, quantifies exactly 6 use cases using consistent Ref IDs, and publishes to Notion after seller confirmation.
REQUIRED BACKGROUND: Use bvc-benchmarks for all benchmark data, business initiative definitions, and use case taxonomy when quantifying.
salary ÷ 2,080Gather all [BRACKET] fields before starting. If any are missing, ask for them.
DEAL BASICS
- Company: [Company name]
- Champion: [Name, Title]
- Industry: [e.g., Healthcare, Finance, Insurance]
- Company Size: [e.g., 500 employees, $2B revenue]
TEAM & ENVIRONMENT
- Sr. Data / Software Engineers: [exact count]
- Analysts / Analytics Engineers: [exact count]
- Current tools: [e.g., Snowflake + Airflow + dbt Core]
- Annual warehouse spend: [$X — or "unknown"]
- % of warehouse spend driven by dbt models: [e.g., 60% — or "unknown"]
TOP PAIN POINTS FROM DISCOVERY
1. [Pain point 1 — direct quote or paraphrase]
2. [Pain point 2]
3. [Pain point 3]
GONG / DOCS (optional)
- Gong link 1: [URL]
FINANCIAL ASSUMPTIONS
- Sr. Engineer salary: $[e.g., 175,000]/yr
- Analyst salary: $[e.g., 150,000]/yr
- dbt contract value: $[e.g., 126,720]/yr
- Term: [e.g., 3 years]
4 blocks: Revenue Impact | Cost Savings | AI Readiness | Risk & Modernization
Each block contains: Initiative | Evidence | How dbt Supports It Max 40 words per block. Tag with Revenue / Cost / AI / Risk. Include source and 1 discovery question.
3 tables:
Columns: Value Pillar | Use Case | Business Problem | How dbt Solves
Main table (exactly 6 rows):
| Ref | Pillar | Use Case | Formula | Hours Saved | $ Saved/Yr |
|---|---|---|---|---|---|
| A1 | T&M | ... | ... | ... | ... |
| A2 | T&M | ... | ... | ... | ... |
| B1 | WH Opt | ... | ... | ... | ... |
| C1 | OE | ... | ... | ... | ... |
| C2 | OE | ... | ... | ... | ... |
| C3 | OE | ... | ... | ... | ... |
Then: "Use Cases Discussed in Discovery" (max 3, with business initiative ties) Then: "Metrics Still Needed" (anything that needs seller follow-up)
3-year summary table:
| Row | Year 1 | Year 2 | Year 3 | 3-Yr Total |
|---|---|---|---|---|
| T&M (A1 + A2) | ||||
| Warehouse (B1) | ||||
| OE (C1 + C2 + C3) | ||||
| Total Annual Savings | ||||
| dbt Cloud Cost | ||||
| Net Savings |
Then: Connecting to Business Initiatives | Why Now section (3-5 sentences, company-specific signals)
Header format: USE CASE [Ref ID] — [Name] (Pillar | feeds Page 4 [row] [with other refs])
Each toggle contains:
This is where agents break — triple-check these before presenting the confirmation summary:
Run this BEFORE showing the confirmation summary. Fix mismatches at the source (Appendix) then propagate up.
$ Saved/Yr for that Ref IDAfter reconciliation, post exactly this format:
[Company] BVC | Annual Savings: $[X] | 3-Yr ROI: [X]% | Payback: ~[X] months
Followed by a bulleted list of all 🔴 benchmarked assumptions to validate before the exec meeting.
Then ask: "Does this look right? Reply publish to send to Notion, or tell me what to change."
Do not write to Notion until seller types "publish".
Once seller confirms with "publish":
https://www.notion.so/7c16742721684eaa9f7db2c4ad3345f8After publishing, fetch the live Notion BVC page and verify:
If any number is mismatched, correct immediately and confirm the fix before sharing the link.
| Change | Command |
|---|---|
| Update dbt cost | Update dbt cost to $[X]/yr over [N] years and recalculate |
| Update salaries | Update Sr Engineer to $[X] and Analyst to $[Y], recalculate |
| Update assumption | Update assumption: [describe]. Recalculate all affected use cases and update Notion. |
| Move to potential | Move "[Use Case]" from confirmed to potential. Update all numbers. |
| Add use case | Add use case: [describe]. Champion said: "[quote]". Estimate [X hrs/wk] saved. |
| Remove use case | Remove "[Use Case]" from the BVC and update all numbers |
| Sync Notion | Update the Notion page with the latest version of the BVC |
| Exec summary | Write a 3-sentence executive summary of the ROI story |
| Objection prep | What are the 3 most likely objections to this BVC and how should I respond? |
Loop in a VE before the exec meeting → #ask-biz-value channel. Standard deals can use this skill without a VE.