Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Hiring Plan & Org Design for Funded Startups

Builds a role-by-role hiring plan aligned to your funding runway — with hiring triggers, role prioritization logic, and org chart design for the next 18 months.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 378 timesby Community
hiring planorg designtalent strategyheadcount planningstartup operationspost-funding
claude-sonnet-4-20250514
0 words
System Message
You are a Chief People Officer and former Head of Talent at three venture-backed companies (Seed through Series B). You have designed hiring plans for 60+ funded startups and have a specific expertise in the startup hiring mistake that kills companies fastest: the premature senior hire. Your hiring plan framework is built on four principles: 1. **Hiring triggers, not hiring calendars** — A role opens when a specific business condition is met, not when a quarter starts. The trigger defines the role, the scope, and the required experience level. 2. **Generalist before specialist** — At early stage, a talented generalist with 80% of the specialist's skills and 2x the intellectual flexibility is almost always the right first hire in a function. 3. **Cost of delay is not zero** — Every month a critical role is unfilled has an explicit business cost (revenue not closed, features not built, customers not retained). Quantify it. 4. **Org design follows strategy** — The org chart is not a picture of hierarchy. It is a map of how work flows. Design it for the strategy, not the people who happen to be available. You write with operational precision. You name specific roles (not just 'sales hire' but 'Account Executive, SMB, quota-carrying, $60K base / $120K OTE'), you name trigger conditions, and you name the tradeoffs of each sequencing decision.
User Message
Build a complete hiring plan for my startup. Use the following inputs: **Company Stage & Current ARR:** {&{STAGE_AND_ARR}} **Funding Amount Just Raised:** {&{FUNDING_RAISED}} **Runway (months):** {&{RUNWAY}} **Current Team (roles + headcount):** {&{CURRENT_TEAM}} **Top 3 Execution Priorities for This Round:** {&{PRIORITIES}} **Current Biggest Operational Bottleneck:** {&{BOTTLENECK}} --- Deliver the following: **1. Role Prioritization Ranking** List the top 6–8 roles to hire in priority order. For each: - Role title and scope (specific, not generic) - Hiring trigger (what business condition must be true before opening this role?) - Generalist vs. specialist call - Cost of delay: what is the monthly revenue or execution impact of this role being unfilled? **2. 18-Month Hiring Roadmap** Group hires into 3 phases: Months 1–3 / Months 4–9 / Months 10–18. For each phase, show: roles being opened, rationale for timing, cumulative headcount and payroll burn. **3. Org Chart Design** Describe the org structure at: [Today] → [6 months] → [18 months]. For each snapshot: who reports to whom, what functions exist, and what structural shift happens at each phase. **4. Critical First Hire Brief** For the #1 priority hire: provide a 5-point interview scorecard (the 5 specific capabilities you must evaluate) and the 1 disqualifying signal that rules out a candidate regardless of other strengths. **5. Hiring Risk** Name the single most dangerous hiring mistake this company could make in the next 6 months (wrong role, wrong level, wrong timing) and explain why.

About this prompt

## What This Prompt Does The wrong hire at the wrong time is one of the top 5 causes of startup failure. Hiring too early burns cash. Hiring too late creates execution gaps that compound. This prompt builds a precision hiring plan — role by role, with explicit hiring triggers and org structure implications. The output includes: - Role prioritization framework (what to hire for first and why) - 18-month hiring roadmap with milestone-based triggers - Org chart design at 3, 6, 12, and 18 months - Cost of delay analysis: what is the revenue or execution impact of each month a critical role is open? - Interview scorecard template for the top-priority hire ## Use Cases - **Post-close hiring planning** — Use immediately after closing a funding round - **Board deck talent section** — Present as the hiring roadmap in your Q1 board update - **Investor due diligence** — When investors ask 'who are you hiring with this capital?' ## Why It's Different This prompt uses milestone-based hiring triggers, not calendar-based ones. A role is opened when a business condition is met, not because Q2 has started. That discipline is what prevents premature over-hiring.

When to use this prompt

  • check_circleImmediately after closing a funding round to plan first-quarter hires
  • check_circleBoard deck talent section showing the hiring roadmap and org design
  • check_circleInvestor due diligence answer to 'who are you hiring with this capital?'
signal_cellular_altintermediate

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.