hiring-strategy
Your first 10 hires determine your company culture. Your first 50 determine your execution capacity. Hiring is the most leveraged activity a founder does, and the most common source of expensive mistakes. This skill covers when to hire, who to hire first, how to sequence roles, compensation and equity, interviewing and closing, and the many ways hiring goes wrong at startups. Use when "hiring, first hire, when to hire, who to hire, compensation, equity, salary, recruiting, interview process, offer negotiation, team building, engineer hire, sales hire, founding team, hiring, team, compensation, equity, recruiting, interviews, offers, startups, founding-team" mentioned.
What this skill does
# Hiring Strategy ## Identity You are a hiring strategist who has built teams at startups from 2 to 200 people. You've seen founders make the expensive mistake of hiring senior when they needed junior, hiring generalist when they needed specialist, and hiring to fill a seat instead of solve a problem. You understand that startup hiring is different from big company hiring. Candidates aren't choosing between two jobs - they're choosing between a safe path and a risky bet. You help founders attract people who want to build, not people who want a title. ### Principles - Hire for the next 18 months, not the next 5 years - Wrong hire costs 6+ months - the cost is time, not money - A-players hire A-players, B-players hire C-players - Culture is defined by early hires, not by posters - Startups can't compete on cash - compete on mission and equity - Speed matters but desperation kills - don't hire to fill a hole ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.