The People Operating Model Playbook

The People function as a system

Most fintechs at Series A have a People function that exists by accident. Someone became "the HR person" because they were good at calendars. Someone owns comp because they used to work in finance. Onboarding happens because the EA built a Notion doc once. The operating model isn't designed; it's the residue of a hundred small decisions made under pressure.

That residue costs you. Not in any single quarter — in the compounding effect over 24 months. A People function that's a series of improvisations becomes a People function that's blocking the next fundraise: comp is uneven, leveling is undocumented, perf cycles are rituals, and the founders can't answer the questions an investor or acquirer asks about the workforce.

This playbook gives you the architecture. It's anchored in three public frameworks — McKinsey's 7-S, Jay Galbraith's Star Model, and BCG's Target Operating Model framing — and adapted for the 30–300 employee range that most fintechs occupy through Series B. The synthesis is FlexHR's; the foundations are publicly published scholarship.

Section 1 — The 8-block People Function Canvas

A People Function Canvas is a single page that documents how the function operates. The eight blocks force you to be specific about choices that most companies leave implicit.

Block 1 — Strategy. What is the People function trying to enable? For a Series A fintech: enable the company to grow from 50 to 200 people in 18 months without losing the management coherence that got us here. For a Series C: retain the top 25% of performers through the next round and pre-IPO transition. Strategy is downstream of company strategy; if you can't write yours, you don't have one yet.

Block 2 — Capabilities. What does the function need to be good at? At Series A: hiring, onboarding, comp design, basic ER. At Series B: add perf cycle, manager development, leveling. At Series C: add talent reviews, succession, exec comp. Match capabilities to stage — don't try to build everything at once.

Block 3 — Structure. Who does what? At Series A, this is usually 2–3 people: a People lead (often part-time or fractional CHRO), a People Ops generalist, a recruiter. At Series B, you split into COE roles (comp, perf, recruiting) and HRBPs assigned to business units. At Series C, you add Shared Services for operational scale.

Block 4 — Processes. The four core process loops: hiring, onboarding, performance, exit. Document each end-to-end. Anti-pattern: skipping documentation because "everyone knows how it works." They don't. New hires don't.

Block 5 — Technology. Your HRIS, ATS, perf tool, comp tool, engagement survey tool. Decision discipline: integrate aggressively or accept data debt. At Series A, the minimum viable stack is HRIS + ATS integrated. At Series B, add perf + comp.

Block 6 — Data. What metrics do you measure, and who owns them? Headcount, hires, attrition, time-to-hire, offer-acceptance rate, engagement, comp ratio. Each metric needs an owner. Ownerless metrics go uncalibrated.

Block 7 — Talent. Who's on your People team? Skills, levels, gaps. The team itself needs leveling.

Block 8 — Outcomes. What does success look like? We hit 75 hires this year with offer-accept >80%. Engagement scores hit 75+. Annual perf cycle ran on time. No pay-equity remediation surprise.

Print the canvas. Fill it out. Update quarterly.

Section 2 — McKinsey 7-S applied to fintech

The 7-S Framework (Waterman & Peters, 1980) is a diagnostic, not a design tool. Use it after you've sketched the canvas to check for internal alignment.

Strategy: What's the company strategy? People strategy must serve

it directly.

Structure: How is the company organized? People structure

mirrors org structure.

Systems: What processes run the company? People systems must

integrate with finance, ops, eng systems.

Shared values: What does the company actually believe? Comp,

hiring, perf decisions are observed-values broadcasts.

Skills: What does the company need to be good at? Recruiting and

manager development must build those skills.

Style: How do leaders behave? People function reflects and

reinforces leadership style.

Staff: Who's on the team? Composition is the hardest 7-S

dimension to change.

The diagnostic question: are the 7 dimensions aligned, or are they pulling in different directions? Misalignment is where the People function ends up firefighting forever.

Section 3 — Galbraith Star applied to fintech

The Star Model (Jay Galbraith, Designing Organizations, 1995) is more practical for design. Five points:

Strategy drives Structure, which determines Processes,

which require Rewards alignment, which depends on People.

For a Series A fintech building the People function:

• ·Strategy: scale headcount from 50 to 200 in 18 months while
• ·Structure: People lead + Ops generalist + recruiter (3 ppl).
• ·Processes: Quarterly hiring forecast → monthly cycle → weekly
• ·Rewards: Comp band v1, leveling matrix v1, annual refresh,
• ·People: Hire a People lead with operating-model design experience.

When the Star is consistent, the function operates. When points are misaligned (e.g., a strategy that says "scale fast" with a structure that says "1 People person per 100 ppl"), something breaks.

Section 4 — COE / HRBP / Shared Services

Dave Ulrich's tripartite model (HR Champions, 1996) is still the operating standard for People functions at scale. The transition points:

At <50 ppl: No formal split. One person (or a fractional CHRO) holds everything.

At 50–100 ppl: First split. Recruiting becomes its own discipline. Comp + perf + ER live in a single People generalist. Onboarding owned by Ops or People depending on who's strongest.

At 100–200 ppl: Three roles emerge. People Operations Lead runs the platform (HRIS, payroll, benefits, compliance). HRBP assigned to business units (Eng, GTM, G&A) handles strategy and ER. Recruiting Manager runs the talent acquisition function.

At 200–300 ppl: Add COE specialization. Comp lead, perf lead, L&D lead. Shared Services emerges — typically tier-1 employee questions ("how do I update my address?") routed away from HRBPs to a dedicated team.

At 300+: Full enterprise model. CHRO + COE leads + HRBPs across business units + Shared Services tier-1/tier-2 escalation.

The most common failure mode: scaling structure faster than the underlying processes. A 75-person company that hires three HRBPs has created political headcount, not capability. Process maturity lags structure by 6–12 months; design accordingly.

RACI for the most-disputed handoffs (template):

| Decision | Hiring manager | HRBP | People Ops | CFO |

|---|---|---|---|---|

| Open a new req | A | C | I | C |

| Approve final offer comp | C | A | R | C/I |

| Performance-rating finalization | A | C | I | – |

| Comp adjustment outside cycle | C | A | R | I |

| PIP decision | A | C | – | – |

| Termination decision | A | C | I | – |

A=Accountable, R=Responsible, C=Consulted, I=Informed.

Section 5 — Stage-by-stage org charts

At 50 ppl:

CEO

├── VP Eng (1 EM, 12 ICs)

├── VP Sales (1 sales mgr, 6 AEs, 2 SDRs)

├── Head of Product (3 PMs, 2 designers)

├── CFO (1 finance analyst)

├── COO (often founder; owns ops + people part-time)

└── People lead (fractional CHRO + 1 ops generalist + 1 recruiter)

At 150 ppl:

CEO

├── CTO (3 EMs, 1 director, ~50 eng + product)

├── CRO (sales + CS + marketing, ~40)

├── CFO (finance + legal + ops, ~15)

├── Head of People (HRBP + recruiting mgr + ops, 6 ppl)

└── Compliance / Risk (CCO + 4 ppl, fintech-specific)

At 250 ppl:

CEO

├── CTO + CTO direct reports (5 directors, ~120 eng + prod)

├── CRO (~70 GTM, with regional layers)

├── CFO (~25, finance + ops + legal)

├── CHRO (4 COE leads + 3 HRBPs + Shared Services lead, ~10–12 ppl)

└── CCO (compliance + risk + audit, ~10–12 ppl)

These are templates, not prescriptions. The variance comes from revenue model (sales-led vs PLG), regulatory burden (consumer fintech vs B2B SaaS), and geographic distribution.

Section 6 — The first People hire 30/60/90

This applies whether you're hiring an in-house People lead or engaging a fractional CHRO.

Days 1–30: listen, map, quick-win. - 1:1s with every leader (CEO, CTO, CRO, CFO, CCO). - 1:1s with 6–10 ICs across functions. - Audit the existing artifacts: hiring practices, comp spreadsheet, onboarding doc, perf history. - Identify 3 quick wins (visible improvements deliverable in 30 days). Examples: standardized offer letter template, 30-day onboarding checklist, calibration on the next 3 hires. - Document everything currently held in someone's head.

Days 31–60: foundation. - Comp bands v1 (use the Compensation Playbook). - Leveling matrix v1. - Hiring playbook v1 (use the Recruiting Playbook). - First-time-manager curriculum cohort kick-off (use the Manager Development Playbook).

Days 61–90: roadmap + first board package. - 12-month People function roadmap with quarterly milestones. - First board people-metrics page: headcount actuals vs. plan, hiring metrics, attrition, engagement baseline if available. - Decision: what's the structure look like at headcount 100, 200, 300? Lock the next layer's hires.

By day 90, the People function is no longer accidental. It's documented, instrumented, and on a roadmap.

Section 7 — The People-function operating cadence

The cadence is the discipline. Without it, the function reverts to firefighting.

Weekly (30 min): People lead + CEO 1:1. Hiring pipeline, ER flags, top-of-mind risks. Brief.

Bi-weekly (60 min): People-team standup. Recruiting metrics, cycle progress, escalations.

Monthly (90 min): People-metrics review. Full leadership team. Headcount actuals vs plan, hiring funnel metrics, attrition by team, comp ratio, engagement deltas if collected.

Quarterly (4 hours): Talent review + comp review + risk register. Senior leadership team. Top 20% / middle 60% / bottom 20% on each leader's team. Comp adjustments outside cycle. ER flags across the company.

Annually (full day): Workforce plan + strategy review + board package. Board prep. Year-ahead headcount, comp budget, perf cycle calendar.

Anti-pattern: doing the cadence sporadically. The cadence works because it's predictable. The first quarter of consistency feels heavy; by quarter four it's the rhythm of how the company runs.

Section 8 — US-specific governance considerations

Audit-readiness from day 1. As fintechs grow, audits become inevitable: SOX 404 readiness pre-IPO, regulatory exams (CFPB, NYDFS, OCC), SOC 2 Type II (every B2B fintech sale), ISO 27001 in some markets. Each requires People-function audit trails — comp decision logs, perf documentation, training records, access logs. Build for audit from day 1, not when the auditor arrives.

Documentation discipline. Federal employment law (Title VII, ADEA, ADA, EPA, FMLA) and state equivalents require documented decision-making for hires, promotions, terminations, comp changes. A simple decision log — "On [date], [decision-maker] decided [X] because [reason]" — is the difference between a defensible employment-practice and one that gets you sued.

Board package essentials. A People page in every board deck covers: headcount actuals vs plan, hiring metrics, attrition by team and tenure cohort, engagement signal (or its absence and why), comp budget and any deviations. Quarterly addition: pay-equity status, top-talent flight risk, key open roles. Pre-IPO addition: comp benchmarks vs peer group, equity pool runway, exec comp committee preparation.

Risk register. Quarterly review of People-function risks: key- person dependencies, comp-equity exposure, regulatory compliance gaps, ER patterns suggesting culture risk. The register is read by the audit committee in mature companies; institute it before they ask.

Closing

The operating model is the system that produces all your other People outcomes. Hiring quality, retention, performance management, culture — they're all downstream of whether the function is designed or accidental. The 90-day investment in this playbook is the highest-ROI architectural decision in the first three years of the company.

When you're ready to install — diagnose the gaps and build the canvas with a partner — the FlexHR Diagnostic Sprint runs the canvas + 7-S + Star alignment in 10 working days. We surface the misalignments and ship a 90-day roadmap. Book a call when timing's right.