Files
claude-skills-reference/c-level-advisor/chro-advisor/references/comp_frameworks.md
Alireza Rezvani 466aa13a7b feat: C-Suite expansion — 8 new executive advisory roles (2→10) (#264)
* feat: C-Suite expansion — 8 new executive advisory roles

Add COO, CPO, CMO, CFO, CRO, CISO, CHRO advisors and Executive Mentor.
Expands C-level advisory from 2 to 10 roles with 74 total files.

Each role includes:
- SKILL.md (lean, <5KB, ~1200 tokens for context efficiency)
- Reference docs (loaded on demand, not at startup)
- Python analysis scripts (stdlib only, runnable CLI)

Executive Mentor features /em: slash commands (challenge, board-prep,
hard-call, stress-test, postmortem) with devil's advocate agent.

21 Python tools, 24 reference frameworks, 28,379 total lines.
All SKILL.md files combined: ~17K tokens (8.5% of 200K context window).

Badge: 88 → 116 skills

* feat: C-Suite orchestration layer + 18 complementary skills

ORCHESTRATION (new):
- cs-onboard: Founder interview → company-context.md
- chief-of-staff: Routing, synthesis, inter-agent orchestration
- board-meeting: 6-phase multi-agent deliberation protocol
- decision-logger: Two-layer memory (raw transcripts + approved decisions)
- agent-protocol: Inter-agent invocation with loop prevention
- context-engine: Company context loading + anonymization

CROSS-CUTTING CAPABILITIES (new):
- board-deck-builder: Board/investor update assembly
- scenario-war-room: Cascading multi-variable what-if modeling
- competitive-intel: Systematic competitor tracking + battlecards
- org-health-diagnostic: Cross-functional health scoring (8 dimensions)
- ma-playbook: M&A strategy (acquiring + being acquired)
- intl-expansion: International market entry frameworks

CULTURE & COLLABORATION (new):
- culture-architect: Values → behaviors, culture code, health assessment
- company-os: EOS/Scaling Up operating system selection + implementation
- founder-coach: Founder development, delegation, blind spots
- strategic-alignment: Strategy cascade, silo detection, alignment scoring
- change-management: ADKAR-based change rollout framework
- internal-narrative: One story across employees/investors/customers

UPGRADES TO EXISTING ROLES:
- All 10 roles get reasoning technique directives
- All 10 roles get company-context.md integration
- All 10 roles get board meeting isolation rules
- CEO gets stage-adaptive temporal horizons (seed→C)

Key design decisions:
- Two-layer memory prevents hallucinated consensus from rejected ideas
- Phase 2 isolation: agents think independently before cross-examination
- Executive Mentor (The Critic) sees all perspectives, others don't
- 25 Python tools total (stdlib only, no dependencies)

52 new files, 10 modified, 10,862 new lines.
Total C-suite ecosystem: 134 files, 39,131 lines.

* fix: connect all dots — Chief of Staff routes to all 28 skills

- Added complementary skills registry to routing-matrix.md
- Chief of Staff SKILL.md now lists all 28 skills in ecosystem
- Added integration tables to scenario-war-room and competitive-intel
- Badge: 116 → 134 skills
- README: C-Level Advisory count 10 → 28

Quality audit passed:
 All 10 roles: company-context, reasoning, isolation, invocation
 All 6 phases in board meeting
 Two-layer memory with DO_NOT_RESURFACE
 Loop prevention (no self-invoke, max depth 2, no circular)
 All /em: commands present
 All complementary skills cross-reference roles
 Chief of Staff routes to every skill in ecosystem

* refactor: CEO + CTO advisors upgraded to C-suite parity

Both roles now match the structural standard of all new roles:
- CEO: 11.7KB → 6.8KB SKILL.md (heavy content stays in references)
- CTO: 10KB → 7.2KB SKILL.md (heavy content stays in references)

Added to both:
- Integration table (who they work with and when)
- Key diagnostic questions
- Structured metrics dashboard table
- Consistent section ordering (Keywords → Quick Start → Responsibilities → Questions → Metrics → Red Flags → Integration → Reasoning → Context)

CEO additions:
- Stage-adaptive temporal horizons (seed=3m/6m/12m → B+=1y/3y/5y)
- Cross-references to culture-architect and board-deck-builder

CTO additions:
- Key Questions section (7 diagnostic questions)
- Structured metrics table (DORA + debt + team + architecture + cost)
- Cross-references to all peer roles

All 10 roles now pass structural parity:  Keywords  QuickStart  Questions  Metrics  RedFlags  Integration

* feat: add proactive triggers + output artifacts to all 10 roles

Every C-suite role now specifies:
- Proactive Triggers: 'surface these without being asked' — context-driven
  early warnings that make advisors proactive, not reactive
- Output Artifacts: concrete deliverables per request type (what you ask →
  what you get)

CEO: runway alerts, board prep triggers, strategy review nudges
CTO: deploy frequency monitoring, tech debt thresholds, bus factor flags
COO: blocker detection, scaling threshold warnings, cadence gaps
CPO: retention curve monitoring, portfolio dog detection, research gaps
CMO: CAC trend monitoring, positioning gaps, budget staleness
CFO: runway forecasting, burn multiple alerts, scenario planning gaps
CRO: NRR monitoring, pipeline coverage, pricing review triggers
CISO: audit overdue alerts, compliance gaps, vendor risk
CHRO: retention risk, comp band gaps, org scaling thresholds
Executive Mentor: board prep triggers, groupthink detection, hard call surfacing

This transforms the C-suite from reactive advisors into proactive partners.

* feat: User Communication Standard — structured output for all roles

Defines 3 output formats in agent-protocol/SKILL.md:

1. Standard Output: Bottom Line → What → Why → How to Act → Risks → Your Decision
2. Proactive Alert: What I Noticed → Why It Matters → Action → Urgency (🔴🟡)
3. Board Meeting: Decision Required → Perspectives → Agree/Disagree → Critic → Action Items

10 non-negotiable rules:
- Bottom line first, always
- Results and decisions only (no process narration)
- What + Why + How for every finding
- Actions have owners and deadlines ('we should consider' is banned)
- Decisions framed as options with trade-offs
- Founder is the highest authority — roles recommend, founder decides
- Risks are concrete (if X → Y, costs $Z)
- Max 5 bullets per section
- No jargon without explanation
- Silence over fabricated updates

All 10 roles reference this standard.
Chief of Staff enforces it as a quality gate.
Board meeting Phase 4 uses the Board Meeting Output format.

* feat: Internal Quality Loop — verification before delivery

No role presents to the founder without passing verification:

Step 1: Self-Verification (every role, every time)
  - Source attribution: where did each data point come from?
  - Assumption audit: [VERIFIED] vs [ASSUMED] tags on every finding
  - Confidence scoring: 🟢 high / 🟡 medium / 🔴 low per finding
  - Contradiction check against company-context + decision log
  - 'So what?' test: every finding needs a business consequence

Step 2: Peer Verification (cross-functional)
  - Financial claims → CFO validates math
  - Revenue projections → CRO validates pipeline backing
  - Technical feasibility → CTO validates
  - People/hiring impact → CHRO validates
  - Skip for single-domain, low-stakes questions

Step 3: Critic Pre-Screen (high-stakes only)
  - Irreversible decisions, >20% runway impact, strategy changes
  - Executive Mentor finds weakest point before founder sees it
  - Suspicious consensus triggers mandatory pre-screen

Step 4: Course Correction (after founder feedback)
  - Approve → log + assign actions
  - Modify → re-verify changed parts
  - Reject → DO_NOT_RESURFACE + learn why
  - 30/60/90 day post-decision review

Board meeting contributions now require self-verified format with
confidence tags and source attribution on every finding.

* fix: resolve PR review issues 1, 4, and minor observation

Issue 1: c-level-advisor/CLAUDE.md — completely rewritten
  - Was: 2 skills (CEO, CTO only), dated Nov 2025
  - Now: full 28-skill ecosystem map with architecture diagram,
    all roles/orchestration/cross-cutting/culture skills listed,
    design decisions, integration with other domains

Issue 4: Root CLAUDE.md — updated all stale counts
  - 87 → 134 skills across all 3 references
  - C-Level: 2 → 33 (10 roles + 5 mentor commands + 18 complementary)
  - Tool count: 160+ → 185+
  - Reference count: 200+ → 250+

Minor observation: Documented plugin.json convention
  - Explained in c-level-advisor/CLAUDE.md that only executive-mentor
    has plugin.json because only it has slash commands (/em: namespace)
  - Other skills are invoked by name through Chief of Staff or directly

Also fixed: README.md 88+ → 134 in two places (first line + skills section)

* fix: update all plugin/index registrations for 28-skill C-suite

1. c-level-advisor/.claude-plugin/plugin.json — v2.0.0
   - Was: 2 skills, generic description
   - Now: all 28 skills listed with descriptions, all 25 scripts,
     namespace 'cs', full ecosystem description

2. .codex/skills-index.json — added 18 complementary skills
   - Was: 10 roles only
   - Now: 28 total c-level entries (10 roles + 6 orchestration +
     6 cross-cutting + 6 culture)
   - Each with full description for skill discovery

3. .claude-plugin/marketplace.json — updated c-level-skills entry
   - Was: generic 2-skill description
   - Now: v2.0.0, full 28-skill ecosystem description,
     skills_count: 28, scripts_count: 25

* feat: add root SKILL.md for c-level-advisor ClawHub package

---------

Co-authored-by: Leo <leo@openclaw.ai>
2026-03-06 01:35:08 +01:00

12 KiB
Raw Blame History

Compensation Frameworks Reference

Salary bands, equity design, total comp modeling, comp philosophy, and raise/refresh processes.


Comp Philosophy — The Foundation

Before building bands, define your philosophy. Ambiguity in comp philosophy = pay equity lawsuits and trust erosion.

The five decisions:

1. What market percentile do you target?

  • P25 (below market): Only viable with exceptional mission, equity, or growth opportunity. Flight risk is high after 18 months.
  • P50 (market median): Standard for most Series AB companies. Competitive without premium.
  • P75 (above market): Premium talent strategy. Used by high-margin or talent-intensive businesses. Netflix model.
  • P90+: Top-of-market for specific functions (ML at AI companies, senior engineers at FAANG feeders).

Common hybrid: P50 base + above-market equity = total comp at P6575.

2. What's in your total comp package?

Define each component explicitly:

  • Base salary — cash, market-benchmarked
  • Variable / bonus — % of base, tied to what criteria
  • Equity — options vs. RSUs, vesting schedule, refresh cadence
  • Benefits — health, retirement, PTO policy
  • Learning & development budget
  • Remote/location allowances

3. Are bands public internally?

Recommended: Yes. Pay transparency reduces equity complaints, builds trust, and forces you to maintain clean bands.

4. How often do you refresh bands?

Minimum: annually. High-growth markets: every 6 months (engineering specifically in hot markets).

5. How do you handle individual negotiation?

Options:

  • Fixed bands, no negotiation (Buffer model) — simple, fair, loses some candidates
  • Band range with manager discretion — most common, requires calibration guardrails
  • Individual negotiation within band — flexible, creates pay equity drift over time

Salary Bands: Construction

Step 1: Define levels

Standard IC levels (adapt to company):

Level Title example Scope
L1 Junior / Associate Execution with guidance
L2 Mid-level Independent execution
L3 Senior Leads workstreams, mentors L1-L2
L4 Staff / Principal Cross-team technical leadership
L5 Distinguished / Fellow Company-wide technical direction

Management track:

Level Title Scope
M1 Manager Team of 48 ICs
M2 Senior Manager Manager of managers or larger team
M3 Director Function or large org
M4 VP Business unit, company-wide
M5 SVP / C-Suite Executive

Step 2: Gather market data

Data sources (by quality):

  1. Radford / Aon — Gold standard. Expensive ($10K+/year). Worth it at Series B+.
  2. Levels.fyi — Excellent for engineering. Free. Self-reported but large sample.
  3. Glassdoor Salary — Broad coverage. Less precise for startups.
  4. Pave / Carta Total Comp — VC-backed companies. Good peer benchmarking.
  5. LinkedIn Salary — Free tier. Reasonable signal for G&A roles.
  6. Offer letter data — What candidates are bringing from other companies. Real-time signal.

What to pull: P25, P50, P75, P90 for each role × level × geography.

Step 3: Set band structure

Band width (range within a level):

  • IC bands: 80120% of midpoint (i.e., ±20% from center)
  • Manager bands: 85115% of midpoint
  • Wider bands allow room for differentiation within level; narrower bands reduce pay equity drift

Band overlap between levels:

  • 1020% overlap is normal (top of L2 overlaps with bottom of L3)
  • 30% overlap: your levels are too close together

  • No overlap: new hires jump too much between levels (compression risk)

Example engineering band structure (US, Series B company, P50 target):

Level Band Min Midpoint Band Max
L1 Software Engineer $90K $105K $125K
L2 Software Engineer $115K $135K $160K
L3 Senior SWE $150K $175K $205K
L4 Staff SWE $195K $225K $260K
M1 Eng Manager $175K $205K $235K
M2 Sr Eng Manager $215K $250K $285K
M3 Director, Eng $255K $300K $345K

Adjust by 1525% for non-SF/NYC markets. Adjust -40% to -60% for European markets.

Step 4: Place employees in bands

Compa-ratio = Employee salary / Band midpoint

Compa-ratio Interpretation
< 0.85 Below range — immediate risk
0.850.95 Developing in role
0.951.05 Fully performing (target zone)
1.051.15 Senior/expert in role
> 1.15 Above range — flag for review

Audit report: Run quarterly. Flag anyone below 0.85 (flight risk) or above 1.15 (overpaid for level, or needs promotion).


Equity Frameworks for Startups

Option Basics

ISO vs NSO:

  • ISO (Incentive Stock Options): For employees. Favorable tax treatment if held 1+ year post-exercise.
  • NSO (Non-Qualified Stock Options): For advisors, contractors, sometimes employees. Taxed as ordinary income on exercise.

Strike price: Set to 409A valuation at grant. Lower is better for employees. Early employees win on strike price.

Vesting schedule standards:

  • 4-year vest, 1-year cliff: Standard
  • 4-year vest, 6-month cliff: Startup market adapting to faster pace
  • 1-year cliff means: nothing until 12 months; monthly or quarterly after

Post-termination exercise window (PTEW):

  • Standard: 90 days. Often too short for employees who can't afford exercise.
  • Better: 15 years or until IPO. Use as a talent differentiator.
  • Companies extending PTEW: Stripe, Airbnb (pre-IPO), Square, most employee-friendly startups.

Equity Grant Ranges by Stage and Level

Expressed as % of fully diluted shares at grant. Ranges vary significantly by market, stage, and funding.

Seed stage:

Role Equity %
Co-founder 2040%
First engineering hire 0.51.5%
First non-technical exec hire 0.250.75%
IC (L2-L3) 0.10.4%
IC (L3-L4) 0.20.6%

Series A:

Role Equity %
VP / Head of function 0.30.75%
Director 0.10.3%
Senior IC (L3) 0.050.15%
Mid IC (L2) 0.020.08%
Junior IC (L1) 0.010.05%

Series B:

Role Equity %
VP / Head of function 0.10.3%
Director 0.050.15%
Senior IC (L3) 0.020.07%
Mid IC (L2) 0.010.03%

At Series B+, equity is increasingly expressed in dollar value (grant value = X shares × current 409A). Use Carta or Pulley to model dilution.

Equity Refresh Program

Why it matters: Employees hired at Series A with 4-year vesting will be fully vested by Series B. No unvested equity = no retention hook.

When to refresh:

  • After every significant funding round
  • Annually for high performers (top 20%)
  • After promotion (role-commensurate top-up)
  • Counter-offer situations (use carefully — signals you underpaid initially)

Refresh models:

  1. Anniversary grant: Annual cliff-free refresh for all employees above a performance threshold
  2. Evergreen model: Continuous vesting maintained — refresh annually so employee always has 23 years remaining
  3. Event-based: Refresh tied to milestones (promotion, funding, annual review cycle)

Dilution awareness: Every refresh dilutes existing shareholders. Model pool usage quarterly. Replenish option pool before it drops below 1012% of fully diluted shares.


Total Comp Modeling

Components of Total Comp

Total Compensation = Base Salary
                   + Annual Bonus (target %)
                   + Equity Value (annualized grant / vesting period)
                   + Benefits (employer-paid premiums, retirement match)
                   + Allowances (home office, internet, L&D, commuter)

Annualizing Equity Value

For comparison to cash compensation:

Annual equity value = (Grant shares × Current 409A price) / Vesting years

Example: 10,000 options at $2 strike, current 409A = $8, 4-year vest

  • Grant value at current 409A = 10,000 × $8 = $80,000
  • Annual value = $80,000 / 4 = $20,000/year
  • If base is $150K, total comp is ~$170K/year

Note: For recruiting purposes, you can use last preferred share price (VC price) to show upside — but be transparent about the difference between 409A and preferred.

Benefits Valuation

Frequently undervalued in offers. Quantify explicitly:

Benefit Typical employer cost
Health insurance (employee) $4K8K/year
Health insurance (family) $15K25K/year
401K match (4% of salary) $5K10K/year
L&D budget ($2K/year) $2K/year
Home office stipend ($500) $500/year

A $140K offer with family health coverage + 4% 401K match is worth $165K+ total.


Raise and Refresh Process

Annual Compensation Review Cycle

Recommended cadence:

  • October/November: Market data refresh, band updates
  • November/December: Manager merit recommendations
  • December/January: Calibration and approvals
  • January/February: Effective date for new salaries + equity grants

Budget allocation:

  • Merit budget (performance-based raises): 35% of total payroll typically
  • Market adjustment budget (fixing below-band salaries): Separate from merit. Non-negotiable to avoid attrition.
  • Promotion budget: Separate. Promotions should not come from merit pool.

Merit Increase Guidelines

Performance Rating Merit Increase Range
5 Exceptional 815%
4 Exceeds 58%
3 Meets 24%
2 Needs improvement 01%
1 Underperforming 0% (PIP active)

Adjust based on compa-ratio. A high performer at P90 of their band gets a smaller increase than a high performer at P50.

Compa-Ratio Adjustment Matrix

Performance \ Compa-Ratio < 0.90 0.901.00 1.001.10 > 1.10
Exceptional (5) 1215% 812% 58% 35%
Exceeds (4) 812% 58% 35% 13%
Meets (3) 58% 35% 23% 02%
Needs impr (2) 02% 01% 0% 0%

Promotion vs. Merit — Keep These Separate

Common mistake: Using merit budget to fund promotions. This forces a choice between rewarding performance and recognizing level change.

Promotion increase guidelines:

  • One level (e.g., L2 → L3): 1020% increase, new equity grant
  • Two levels (rare): 2035% increase, new equity grant at new level
  • Manager track (IC → M1): 1525% increase, new equity grant

Promotion criteria process:

  1. Manager nominates with written business case
  2. Calibration committee reviews cross-functionally
  3. HR validates against band (no off-band exceptions without CHRO sign-off)
  4. Employee informed before annual review — never surprised at review meeting

Off-Cycle Adjustments

When to do them:

  • Counter-offer situations (see below)
  • Competitive intelligence reveals underpay for a specific role
  • New market data shows a role significantly under-benchmarked
  • Internal equity audit reveals unexplained gaps

Counter-offer policy: Three options:

  1. Match — Risk: signals you underpay; sets precedent
  2. Partial match — "We can do X, which is the top of your band" — cleaner
  3. Decline — Accept the attrition, improve the band for the next hire

Rule: If you're regularly in counter-offer conversations, your bands are stale. Fix the bands.


Pay Equity Audit

Run annually. Non-negotiable at Series B+.

What to audit:

  • Pay gap by gender within each level and function
  • Pay gap by ethnicity within each level and function
  • Compa-ratio distribution across demographics
  • Time-to-promotion by demographic group

Methodology:

  1. Pull all employee data: level, function, salary, tenure, performance ratings, gender, ethnicity
  2. Run regression controlling for level, tenure, and performance
  3. Unexplained gap after controls = the problem to fix
  4. Flag and remediate within the same review cycle

Legal exposure: In many jurisdictions, documented pay gaps without remediation plans are litigation risk. The audit creates a record of intent; remediation closes the risk.

Remediation budget: Set aside 0.51% of payroll annually for equity adjustments. If you're doing it right, this shrinks over time.