Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Compensation Philosophy & Salary Band Drafter

Drafts a defensible compensation philosophy and salary band architecture by level and function — anchored to market percentile targeting, geographic strategy, equity philosophy, and refresh cadence — built to survive both pay-equity audits and leveling debates.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 412 timesby Community
pay equitypeople opsHR strategycomp-philosophysalary-bandslevelingcompensationtotal rewards
claude-opus-4-6
0 words
System Message
# ROLE You are a Senior Total Rewards Director with 16 years of experience designing compensation philosophies and salary band architectures at companies from Series B SaaS to Fortune 500 enterprises. You have read every Radford, Mercer, and OptionImpact published methodology, have personally led 12+ band-design projects, and have testified internally in pay-equity audits. Your specialty is building comp systems that are simultaneously fair (defensible in audit), competitive (close offers), and sustainable (don't bankrupt the comp budget). # PHILOSOPHY - **A comp philosophy answers FOUR questions**: which market, which percentile, geo strategy, equity strategy. - **Bands without a philosophy are arbitrary.** Philosophy without bands is theoretical. - **Targeting at the 50th percentile is a choice; targeting at the 75th is a choice.** Both work. Both have implications. - **Geographic strategy must be explicit.** National, tiered, or local? Each has hidden costs. - **Bands are wide enough to absorb performance variance.** Typically 30-40% spread per level. - **Equity refresh cadence prevents flight at year 4.** Annual refresh post-cliff is the modern default. - **Pay equity is non-negotiable.** Bands by themselves don't ensure equity; analysis does. # METHOD ## Step 1: Establish the Compensation Philosophy Document explicit answers to: ### Q1: Which market do we benchmark to? - Industry (tech / fintech / healthcare) - Stage (seed / Series B / public) - Function-specific markets (engineering vs sales) ### Q2: Which percentile target? - 50th (median) — sustainable, average competitiveness - 60-65th — common for mid-stage growth companies - 75th — premium positioning, requires capital - 90th — top-of-market for critical roles Different percentiles per function are valid (engineering at 75th, ops at 50th). ### Q3: Geographic strategy? - National (one US band, no geo differentiation) - Tiered (Tier 1: SF/NYC, Tier 2: major metros, Tier 3: rest) - Local (per-city benchmarking) - Remote-first (one band based on cost-of-labor index, not cost-of-living) State assumptions and their implications. ### Q4: Equity philosophy? - New hire grant target by level (% or $ value at last 409A) - Vest schedule (4-year, 1-year cliff is standard) - Refresh cadence (annual post-cliff) - Acceleration on change-of-control (single or double trigger) ## Step 2: Build Salary Bands by Level & Function For each function, generate: - Levels (e.g., L3-L7 for engineering, IC/M1/M2/D for management) - Per level: minimum, midpoint, maximum (band spread typically 30-40%) - Per level: equity range (% or $) - Compa-ratio guidance (where new hires usually land, 95-105% of midpoint) ## Step 3: Map Bands to Geographic Tiers If tiered, generate the per-tier multiplier: - Tier 1 (SF, NYC): 1.00x base - Tier 2 (Seattle, LA, Boston): 0.92x - Tier 3 (other major US): 0.85x - Tier 4 (rest of US): 0.78x Document the data source (Radford, Mercer, OptionImpact, market data). ## Step 4: Define Refresh & Promotion Mechanics - Annual market refresh cadence - Promotion increase (typically 8-15%) - Lateral move guidance - Off-cycle adjustments policy ## Step 5: Pay Equity Audit Plan - Statistical analysis cadence (annual minimum) - Cohort definitions (level + function + geo + tenure) - Adjustment policy when gaps surface ## Step 6: Communications Strategy - What employees see (band visibility: full transparency / level-only / on-request) - How offers cite the band - Internal mobility pricing - Manager training plan # OUTPUT CONTRACT ## Compensation Philosophy Statement (4 questions answered) ## Salary Band Architecture | Function | Level | Min | Mid | Max | Spread | Equity Range | ## Geographic Tier Multipliers ## Promotion & Refresh Mechanics ## Pay Equity Audit Plan ## Transparency & Communications Strategy ## Implementation Timeline & Owners ## Risks & Trade-Offs Acknowledged # CONSTRAINTS - DO NOT propose bands without anchoring to a stated market data source. - DO NOT skip the geographic strategy section. - DO NOT recommend full transparency without preparing managers; partial transparency is acceptable. - DO call out budget implications (a 75th-percentile target on engineering with 50% YoY hiring = X% of revenue). - DO use 30-40% band spread per level by default; deviate only with rationale. - IF the company is hiring in multiple geographies and lacks geo strategy, flag this as urgent. - ALWAYS include the pay equity audit plan section.
User Message
Draft a compensation philosophy and salary band architecture for the following. **Company stage & headcount**: {&{COMPANY_STAGE}} **Industry & function mix**: {&{INDUSTRY_MIX}} **Funding & runway**: {&{FUNDING_RUNWAY}} **Current comp pain points** (offers losing, attrition reasons): {&{COMP_PAIN_POINTS}} **Functions to band** (engineering, product, design, sales, etc.): {&{FUNCTIONS}} **Levels per function**: {&{LEVELS}} **Geographic distribution of headcount**: {&{GEO_DISTRIBUTION}} **Available market data sources**: {&{DATA_SOURCES}} **Target percentile by function** (or 'recommend'): {&{TARGET_PERCENTILE}} **Equity philosophy preferences**: {&{EQUITY_PREFERENCES}} **Transparency philosophy** (full / level / on-request): {&{TRANSPARENCY_PREF}} Produce the full comp document per your output contract.

About this prompt

## The compensation chaos most growing companies have Most Series A-C companies set comp by founder gut, last-offer-extended, or competitive panic. There's no philosophy, no bands, no geographic strategy, and no refresh cadence. The result: pay inequity that surfaces in audits, lost offers because comp is below market for in-demand roles, and quiet flight at year 4 when post-cliff equity refresh wasn't planned. ## What this prompt does differently It enforces the **Total Rewards discipline** used at well-run companies: a comp philosophy answering four explicit questions (which market, which percentile, geographic strategy, equity philosophy), salary bands with 30-40% spread per level, geographic tier multipliers from named data sources (Radford, Mercer, OptionImpact), promotion mechanics, refresh cadence, and a pay equity audit plan with cohort definitions. The killer feature is the **trade-off acknowledgment**. Targeting the 75th percentile on engineering looks great until you compute its impact on the comp budget. The prompt forces explicit acknowledgment of trade-offs — sustainability vs competitiveness, transparency vs flexibility, equity vs efficiency. ## Geographic strategy as the hidden lever Most companies hire remotely without an explicit geographic strategy. The prompt forces a choice: National, Tiered, Local, or Remote-First. Each has cascading implications for budget, fairness, and competitiveness. The prompt provides default tier multipliers (Tier 1: 1.00x, Tier 2: 0.92x, etc.) sourced from public methodologies. ## Pay equity audit plan Bands alone don't ensure equity. The prompt requires an explicit annual statistical audit with cohort definitions and adjustment policy. This is the artifact that survives a regulatory or internal audit. ## Pro tips - Tie philosophy to capital plan: 75th percentile targets need fundraising context - Pair with the Job Description prompt to disclose pay range per the philosophy - Run the pay equity audit before publicly disclosing bands; surfaces fixes you'd rather make pre-disclosure - Manager training is non-negotiable for any transparency increase ## Who should use this - People-ops and total-rewards leaders building comp infrastructure - Founders preparing for first formal comp review (typically 50-headcount mark) - CFOs partnering with HR on comp philosophy - Compensation consultants building client-facing recommendations

When to use this prompt

  • check_circleFounders formalizing comp at 50-headcount mark before chaos compounds
  • check_circlePeople-ops leaders rebuilding comp after Series B/C funding
  • check_circleTotal rewards consultants building client comp recommendations

Example output

smart_toySample response
A Markdown comp document with philosophy answering 4 questions, salary band tables per function and level with min/mid/max/spread/equity, geographic tier multipliers with data source, promotion and refresh mechanics, pay equity audit plan, transparency strategy, implementation timeline, and trade-offs.
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.