GFE ValuationOps Layer Template

Template Type: System Architecture
Source: GFE Skill System ValuationOps Docs (/docs/valuation-ops/[LAYER]/00-overview.md)
Goal: Define the top-level valuation stack and its component suites.
Use with: .agent/workflows/create-valuation-layer-post.md

---

0. SCHEMA EXTRACTION GUIDE

Before writing, extract these fields from the Layer Overview markdown:

Required Fields

• Layer Name: (e.g., "Revenue Ops")
• Definition: (e.g., "The entire lifecycle of revenue generation...")
• Suites: List of sub-modules (e.g., Lead Gen, Deal Closing, Customer Success)
• Key Metrics: Total flows, KPIs, Tasks (from "Architecture Summary")

Auto-Fetch Related Data

1. Suite Details:

• For each Suite, extract the list of "Completed Flows" (Processes).
• Link: /blog/posts/[process-slug]

2. KPI Map:

• Extract the top 5-10 "North Star" KPIs for this layer.
• Link: /blog/posts/[kpi-slug]

3. Canon Laws:

• Identify which GFE Canon Laws apply to this layer (e.g., Law 5 for Revenue, Law 2 for Cash).

---

1. ARTICLE STRUCTURE

Frontmatter

---
title: '[Layer Name] Architecture'
slug: [layer-slug]-overview
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
  [Definition]. The complete architecture of [Suites Count] suites and [Flows Count] flows driving [Valuation Impact].
author: GFE Strategy Lab
image: /images/blog/[layer-slug]-hero.png
alt: [Hero image description]
tags:
  - valuation-ops
  - [layer-slug]
  - architecture
sections:
  - gfe-systems
  - valuation-ops
featured: true
aside: true
footer: true
traceability:
  valuationLayer: [layer-slug]
  suiteIds: [array of suite names]
  processIds: [array of key process IDs]
head:
  - - meta
    - name: robots
      content: 'index, follow'
  - - meta
    - property: 'og:title'
      content: '[Layer Name] Architecture'
  - - meta
    - property: 'og:description'
      content: >-
        [Definition]. The complete architecture.
  - - meta
    - property: 'og:image'
      content: '/images/blog/[layer-slug]-hero.png'
  - - meta
    - property: 'og:type'
      content: 'article'
---

---

Section 1: Hook — The Valuation Thesis (150-200 words)

Purpose: Define this layer's role in the Enterprise Value equation.

Template:

# [Layer Name] Architecture

**ValuationOps Layer [N]**

In the GFE Skill System, **[Layer Name]** is the engine of [Function, e.g., "Growth", "Profit", "Survival"].

Most companies treat [Layer Name] as a department. We treat it as a **valuation driver**. It encompasses [Scope, e.g., "the entire lifecycle from first touch to renewal"].

If this layer fails, [Failure Mode, e.g., "you burn cash and die"]. If it succeeds, [Success Mode, e.g., "you command a premium multiple"].

::: tip Architecture Stats
- **Suites**: [Count]
- **Flows**: [Count]
- **KPIs**: [Count]
- **Primary Owner**: [Role]
:::

![Layer visualization](/images/blog/[layer-slug]-hero.png)

---

---

Section 2: The Suite Architecture (Visual)

Purpose: Show the sub-modules that make up this layer.

Template:

## The Suite Architecture

We structure [Layer Name] into [Count] distinct suites:

```mermaid
graph TD
    Layer[[[Layer Name]]]
    
    subgraph "Suite 1"
    S1([Suite 1 Name])
    end
    
    subgraph "Suite 2"
    S2([Suite 2 Name])
    end
    
    subgraph "Suite 3"
    S3([Suite 3 Name])
    end
    
    Layer --> S1
    Layer --> S2
    Layer --> S3

---

---

### Section 3: Suite Deep Dives (500-800 words)

**Purpose:** Breakdown each suite and its key flows.

**Template:**
```markdown
## 1. [Suite 1 Name]
**Focus:** [One-line description]

This suite standardizes [Activity]. It replaces ad-hoc work with [Count] canonical flows:

- **[Flow Name]**: [Brief description]
- **[Flow Name]**: [Brief description]

::: info Key Metric
**[KPI Name]**: The primary measure of success for this suite.
:::

---

## 2. [Suite 2 Name]
...

---

Section 4: The KPI Scorecard (200-300 words)

Purpose: List the "North Star" metrics for this layer.

Template:

## The KPI Scorecard

You cannot improve what you do not measure. These are the top KPIs for [Layer Name]:

| KPI | Why It Matters | Owner |
| :--- | :--- | :--- |
| **[[KPI Name]](/blog/posts/[kpi-slug])** | [Reason] | [Role] |
| **[[KPI Name]](/blog/posts/[kpi-slug])** | [Reason] | [Role] |

---

---

Section 5: Canon Law Connection (150-200 words)

Purpose: Tie this layer to the GFE Canon.

Template:

## Canon Law Connection

This layer is governed by **Law [N]: [Law Name]**.

> "[Quote from Law]"

[Explanation of how the law applies to this layer].

---

---

Section 6: Traceability Chain

Template:

## Traceability Chain

**Upstream:** [Enterprise Value / Valuation Model]

**Downstream Suites:**
[For each Suite:]
- [Suite Name]

**Key Processes:**
[For each Key Process:]
- [[Process Name]](/blog/posts/[process-slug])

---

---

Section 7: FAQ (3-5 Questions)

Template:

## FAQ

**Q: Who owns this layer?**  
A: Typically the [C-Level Role, e.g., CRO, CFO].

**Q: How does this connect to [Other Layer]?**  
A: [Explanation of interdependency].

---

---

2. WRITING GUIDELINES

Tone Strategy

Architectural & Systemic:

• Focus on structure and completeness.
• Use terms like "Architecture," "Stack," "Engine," "Lifecycle."
• Emphasize that this is a system, not just a collection of tasks.

Visuals:

• The Mermaid diagram should show the hierarchy (Layer -> Suites).

---

3. IMAGE GENERATION

Subject Formula:

• "Abstract architectural diagram of [Layer Name]"
• "Layered strata visualization"
• "Foundation block of a larger structure"

Base Prompt:

Minimalist 3D relief illustration on off-white background. Muted teal (#1AA8A0) accent. Subject: [SUBJECT]. Composition: layered, structural, solid foundation, negative space. Typography: "[Layer Name]" in clean sans, dark slate. Lighting: soft top-front. 16:9 aspect ratio.

Save To: docs/public/images/blog/[layer-slug]-hero.png

---

4. FINAL CHECKLIST

• [ ] Layer schema extracted
• [ ] Suites defined and mapped
• [ ] Key flows listed per suite
• [ ] North Star KPIs identified
• [ ] Canon Law linked
• [ ] Hero image generated

---

End of Template