GFE KPI Deep Dive Template
Template Type: KPI Definition & Analysis
Source: GFE Skill System KPI Definitions (/spec/metrics/kpi-definitions.json)
Goal: Transform KPI schemas into authoritative metric guides with reverse links to tasks, processes, and OKRs.
Use with: .agent/workflows/create-kpi-post.md
0. SCHEMA EXTRACTION GUIDE
Before writing, extract these fields from the KPI definition:
Required Fields
{
"id": "KPI-CF-001",
"name": "Operating Cash Flow",
"category": "cashflow_ops",
"description": "Net cash generated by core operations over a period.",
"unit": "currency",
"formula": "Operating Cash Flow as reported in cash flow statement",
"frequency": "monthly",
"data_sources": ["cashflow_statement", "bank_feeds"],
"owner": "CFO or Financial Controller",
"valuation_link": "cashflow"
}Auto-Fetch Related Data
1. Related Tasks (reverse lookup in /spec/tasks/): Search all task JSONs where kpi_links[] contains this KPI ID:
- Extract:
id,title,domain,level,description
2. Related Processes (reverse lookup in /spec/processes/): Search all process JSONs where primary_kpis[] contains this KPI ID:
- Extract:
id,name,description,valuation_link
3. Related OKRs (reverse lookup in /spec/okrs/): Search all OKR JSONs where key_results[].kpi_id matches this KPI ID:
- Extract:
id,objective,owner_role, target from matching key result
4. ValuationOps Layer (from category): Map KPI category to layer:
revenue_ops→ Revenue Opsebitda_ops→ EBITDA Opscashflow_ops→ Cash Flow Opsfree_cashflow_ops→ Free Cash Flow Opsstory_ops→ Story Opsvaluation_ops→ Valuation Ops
1. ARTICLE STRUCTURE
Frontmatter
---
title: '[KPI Name]: The [Domain] Metric That Drives [Valuation Impact]'
slug: kpi-[id-lowercase]
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
[KPI description + why it matters for valuation in 1-2 sentences]
author: GFE Strategy Lab
image: /images/blog/kpi-[id-slug]-hero.png
alt: [Hero image description]
tags:
- kpi
- [category-name]
- [domain if applicable]
- metrics
sections:
- gfe-systems
- kpis
featured: false
aside: true
footer: true
traceability:
valuationLayer: [category]
kpiId: [this KPI ID]
relatedTasks: [array of task IDs]
relatedProcesses: [array of process IDs]
relatedOKRs: [array of OKR IDs]
head:
- - meta
- name: robots
content: 'index, follow'
- - meta
- property: 'og:title'
content: '[KPI Name]: The [Domain] Metric'
- - meta
- property: 'og:description'
content: >-
[KPI description]
- - meta
- property: 'og:image'
content: '/images/blog/kpi-[id-slug]-hero.png'
- - meta
- property: 'og:type'
content: 'article'
- - script
- type: 'application/ld+json'
- |
{
"@context": "https://schema.org",
"@type": "Article",
"@id": "[KPI ID]",
"name": "[KPI Name]",
"description": "[KPI description]",
"about": {
"@type": "DefinedTerm",
"name": "[KPI Name]",
"description": "[KPI description]"
}
}
---Section 1: Hook — Why This KPI Matters (100-150 words)
Purpose: Connect the metric to business outcomes and valuation
Template:
# [KPI Name]: The [Category] Metric That Drives [Valuation Impact]
Most [practitioners] track [KPI name] as a reporting requirement.
That misses the point: this metric measures [what capability], which determines [business outcome], which capital markets price into [valuation multiple/WACC/cash flow].
[One sharp observation about current state or why this KPI is misunderstood]
This guide breaks down **[KPI ID]: [KPI Name]** — what it measures, how to calculate it, how to improve it, and which tasks and processes move it.
::: tip Quick Facts
- **Category**: [Category Name]
- **Owner**: [Owner]
- **Frequency**: [Frequency]
- **Unit**: [Unit]
- **Valuation Link**: [Valuation Link]
:::

---Variables:
[practitioners]: "CFOs", "RevOps teams", "COOs"[what capability]: "how efficiently you convert inputs to cash", "customer retention strength"[business outcome]: "cash runway", "revenue predictability"[valuation multiple/WACC/cash flow]: Pick based onvaluation_link
Section 2: What This KPI Measures (150-200 words)
Purpose: Define the metric precisely
Template:
## What This KPI Measures
**Definition:** [KPI description from schema]
**Formula:**[KPI formula]
**Plain English:**
[Explain the formula in non-technical terms]
**Example Calculation:**
[If formula is complex, show worked example with real numbers]
### Why This Formula Matters
[Explain WHY the formula is structured this way — what it reveals about the business]
**Example:**
For Cash Conversion Cycle (CCC = DIO + DSO - DPO):
- Higher DSO = customers pay slowly = cash tied up
- Higher DPO = you pay vendors slowly = cash retained (short-term)
- The net shows how long cash is locked in operations
---Section 3: How to Measure It (100-150 words)
Purpose: Tactical measurement guidance
Template:
## How to Measure It
**Data Sources:**
[For each data source in schema, explain where to pull it:]
- **[Data Source 1]**: [Where this lives — e.g., "QuickBooks P&L", "Salesforce Reports"]
- **[Data Source 2]**: [Where this lives]
**Measurement Frequency:** [Frequency]
**Recommended Tooling:**
- **Manual (< $10M ARR)**: [Excel template, Google Sheet]
- **BI Dashboard ($10M-$50M)**: [Metabase, Tableau, Looker]
- **Automated (> $50M)**: [Adaptive Planning, Anaplan, NetSuite SuiteAnalytics]
**Common Measurement Errors:**
- [Error 1: e.g., "Mixing accrual and cash accounting"]
- [Error 2: e.g., "Not adjusting for one-time events"]
---Section 4: How to Improve This KPI (200-300 words)
Purpose: Actionable improvement levers
Template:
## How to Improve This KPI
[Frame based on whether higher or lower is better]
### Lever 1: [Improvement Strategy]
**What to do:** [Tactical action]
**Impact:** [Expected improvement — be specific if possible]
**Example:** [Real-world scenario]
### Lever 2: [Improvement Strategy]
**What to do:** [Tactical action]
**Impact:** [Expected improvement]
**Example:** [Real-world scenario]
### Lever 3: [Improvement Strategy]
**What to do:** [Tactical action]
**Impact:** [Expected improvement]
**Example:** [Real-world scenario]
---Example (for DSO improvement):
- Lever 1: Automate invoice delivery (reduces DSO by 5-10 days)
- Lever 2: Offer 2% discount for Net 10 payment (reduces DSO by 15 days)
- Lever 3: Implement collections escalation process (reduces DSO by 10 days)
Section 5: Valuation Impact (150-200 words)
Purpose: Close the loop to enterprise value
Template:
## Valuation Impact
This KPI rolls up into the **[ValuationOps Layer]** layer of the GFE ValuationOps stack.
**How It Connects:**
[Based on `valuation_link`, explain the chain]
**For `cashflow` link:**[KPI Name] improves → Operating Cash Flow increases
→ Free Cash Flow increases → DCF valuation increases
**For `revenue` link:**[KPI Name] improves → Revenue predictability increases
→ Revenue multiple expands → Enterprise value increases
**For `margin` link:**[KPI Name] improves → EBITDA margin expands
→ Multiple expands + cash flow increases → EV increases
**For `risk` link:**[KPI Name] improves → Internal Risk Index decreases
→ WACC decreases → Discount rate decreases → EV increases
**Magnitude:**
[If possible, quantify — e.g., "Improving DSO from 60 to 45 days releases $250K for a $5M ARR company"]
---Section 6: Related Tasks (Reverse Links)
Purpose: Show which tasks move this KPI
Template:
## Tasks That Move This KPI
These GFE Skill System tasks directly influence [KPI Name]:
[For each related task:]
### [Task ID]: [Task Title]
**Domain:** [Domain] | **Level:** [Level] | **Category:** [Category]
[Task description]
**How it moves this KPI:**
[Explain the causal link — e.g., "Building a cash flow forecast exposes DSO trends, enabling collections process improvements"]
::: tip Learn How
See the full guide: [How to [Task Title]](/blog/posts/[task-slug])
:::
---
[If no tasks found:]
*No tasks currently linked to this KPI in the skill system. This metric is typically measured at the process or OKR level.*
---Section 7: Related Processes (Reverse Links)
Purpose: Show which workflows measure this KPI
Template:
## Processes That Measure This KPI
These processes use [KPI Name] as a primary success metric:
[For each related process:]
### [Process ID]: [Process Name]
[Process description]
**Why this KPI matters here:**
[Explain why this process tracks this KPI]
::: tip Process Walkthrough
See the full workflow: [[Process Name]](/blog/posts/[process-slug]) *(coming soon)*
:::
---
[If no processes found:]
*No processes currently measure this KPI as a primary metric. Check related tasks for tactical execution.*
---Section 8: Related OKRs (Reverse Links)
Purpose: Show strategic objectives tied to this KPI
Template:
## OKRs Targeting This KPI
These quarterly objectives include [KPI Name] as a key result:
[For each related OKR:]
### [OKR ID]: [Objective]
**Owner:** [Owner Role]
**Target:** [Key result target for this KPI]
[Brief explanation of why this OKR targets this KPI]
::: tip OKR Breakdown
See the full objective: [[OKR ID]](/blog/posts/[okr-slug]) *(coming soon)*
:::
---
[If no OKRs found:]
*No current OKRs targeting this KPI. This metric may be tracked at the operational level rather than strategic level.*
---Section 9: Traceability Chain
Template:
## Traceability Chain
**ValuationOps Layer:** [[Layer Name]](/blog/posts/[layer-slug]) *(coming soon)*
**Related Tasks:**
[For each task:]
- [[Task ID]: [Task Title]](/blog/posts/[task-slug])
**Related Processes:**
[For each process:]
- [[Process ID]: [Process Name]](/blog/posts/[process-slug]) *(coming soon)*
**Related OKRs:**
[For each OKR:]
- [[OKR ID]: [Objective]](/blog/posts/[okr-slug]) *(coming soon)*
---Section 10: FAQ (8-10 Questions)
Template:
## FAQ
**Q: What's a good benchmark for [KPI Name]?**
A: [Industry benchmarks if available, or framework for setting targets]
**Q: How often should I measure this?**
A: [Frequency] — [explain why this cadence matters]
**Q: What if I can't access [data source]?**
A: [Alternative data sources or proxy calculations]
**Q: Is higher or lower better?**
A: [Direction + explanation of why]
**Q: How does this differ from [similar KPI]?**
A: [Clarify the distinction]
**Q: Can I improve this KPI without [some capability]?**
A: [Yes/No + workaround or prerequisite]
**Q: What's the fastest way to move this metric?**
A: [Highest-leverage lever from Section 4]
**Q: Who should own this KPI in a [company size] company?**
A: [Owner recommendation based on scale]
---2. WRITING GUIDELINES
Tone Strategy
Balance: KPI posts are ANALYTICAL, not tactical. Less wit, more precision.
Hook (100 words): Contrarian take on why this metric matters
Body (500 words): Clinical definition, measurement, improvement levers
Links (200 words): Reverse lookups to tasks/processes/OKRs
Voice:
- Precise, not vague: "Reducing DSO from 60 to 45 days" not "improving collections"
- Diagnostic, not prescriptive: "This reveals X about your business" not "You must do Y"
- Analytical, not tactical: Explain WHY the formula matters, not HOW to execute
Wit Level: LOW
- Hook: Light contrarian framing
- Body: Zero wit (pure analysis)
- FAQ: Helpful, direct
3. IMAGE GENERATION
Subject Formula:
- For flow metrics (cash flow, revenue): "Flowing arrows converging into metric dial"
- For cycle metrics (CCC, CAC payback): "Circular timeline with labeled phases"
- For ratio metrics (margins, multiples): "Stacked layers with highlighted metric"
Base Prompt:
Minimalist 3D relief illustration on off-white background. Muted teal (#1AA8A0) accent. Subject: [SUBJECT]. Composition: centered, balanced, negative space, shallow depth, gentle gradients. Typography: "[KPI Name]" in clean sans, dark slate. Lighting: soft top-front. 16:9 aspect ratio.Save To: docs/public/images/blog/kpi-[id-slug]-hero.png
4. SEO & AEO OPTIMIZATION
Target Keywords
- Primary: "[KPI Name]", "[KPI Name] formula", "[KPI Name] calculation"
- Secondary: "what is [KPI Name]", "how to improve [KPI Name]"
- Long-tail: "[KPI Name] benchmark", "[KPI Name] for [industry]"
JSON-LD
Use @type: Article with about: DefinedTerm (already in frontmatter template)
FAQ
8-10 questions targeting:
- Definition queries
- Calculation queries
- Benchmark queries
- Improvement queries
5. FINAL CHECKLIST
- [ ] KPI schema data extracted
- [ ] Formula explained in plain English
- [ ] Related tasks identified (reverse lookup)
- [ ] Related processes identified (reverse lookup)
- [ ] Related OKRs identified (reverse lookup)
- [ ] ValuationOps layer mapped correctly
- [ ] Improvement levers are actionable
- [ ] Hero image generated
- [ ] FAQ includes benchmarks
- [ ] All links use relative paths (start with
/)
End of Template

