Workforce Strategy and Headcount Planning

Introduction

A startup’s workforce is not simply a collection of employees. It is a system of capabilities that converts strategic intent into products, customer value, revenue, compliance, and learning. Founders therefore face a central design problem: how can a limited amount of cash be converted into the capabilities required to reach the next business milestone?

This problem is more demanding than preparing an organization chart. Early-stage firms operate with uncertain demand, incomplete information, changing priorities, and severe financial constraints. Hiring too early increases burn and coordination costs; hiring too late creates bottlenecks, quality failures, founder overload, and missed opportunities. Workforce strategy connects business strategy, operating design, talent decisions, and financial planning.

This chapter presents a systematic approach to translating strategy and funding constraints into capability maps, organization structures, role priorities, headcount plans, workforce scenarios, budgets, and build–buy–borrow–automate decisions.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Translate a startup’s strategic objectives into a capability map.
2. Design a proportionate early-stage organization structure.
3. Prioritize roles using milestones, bottlenecks, risk, and economic constraints.
4. Construct headcount and workforce scenarios.
5. Calculate hiring cost, loaded employment cost, burn, runway, and hiring affordability.
6. Evaluate whether a capability should be built internally, bought, borrowed, or automated.
7. Identify governance, ethical, legal, and implementation risks in startup workforce planning.

1. Workforce Strategy as an Execution System

Workforce strategy is the deliberate alignment of people, capabilities, work design, and employment arrangements with business objectives over a defined planning horizon. It differs from reactive recruitment. Recruitment asks, “Whom should we hire?” Workforce strategy first asks:

• What must the business accomplish?
• What capabilities are necessary?
• Which capabilities already exist?
• What work is recurrent, strategic, regulated, or temporary?
• What can be obtained through employment, contracting, partnerships, software, or process redesign?
• What can the company afford before the next financing or revenue milestone?

A useful planning chain is:

Strategy → milestones → capabilities → work activities → roles → capacity → workforce options → cost and risk → decision.

This sequence prevents a common error: hiring for titles rather than for outcomes. For example, “hire a marketing manager” is weak reasoning. “Generate 400 qualified enterprise leads per quarter through two measurable channels while preserving brand and regulatory compliance” is a capability and outcome statement.

Workforce strategy and competitive advantage

The resource-based view of the firm argues that sustained advantage can arise from resources that are valuable, rare, difficult to imitate, and organizationally embedded. In startups, this may involve proprietary technical knowledge, trusted customer relationships, exceptional product-learning routines, or a distinctive culture of experimentation. However, not every activity should be treated as a source of strategic advantage. Payroll administration, routine bookkeeping, and standard legal filings may be important but not differentiating.

The strategic question is therefore not whether a task matters. It is whether ownership of the capability creates learning, control, speed, trust, or defensibility sufficient to justify internal investment.

2. From Strategy to Capability Maps

2.1 Strategic milestones

Headcount planning should begin with a milestone horizon, commonly the next 6–18 months. Milestones should be observable and time-bounded. Examples include:

• launching a minimum viable product;
• achieving a defined number of active or paying customers;
• reaching a target level of monthly recurring revenue;
• completing a security certification;
• reducing customer onboarding time;
• proving unit economics;
• completing a regulatory approval;
• preparing for a financing round.

A milestone is useful only if it identifies what must be true, by when, and how achievement will be assessed.

2.2 Capability mapping

A capability is the organizational ability to perform an outcome reliably. It is broader than a task and more stable than a job title. “Data governance” is a capability; “upload a spreadsheet” is a task. Capabilities normally combine people, knowledge, processes, technology, and decision rights.

A capability map can be organized into four levels:

1. Strategic outcomes: what the firm must achieve.
2. Core capabilities: abilities directly connected to value creation or defensibility.
3. Enabling capabilities: abilities that support reliable operation.
4. Work activities: recurring actions through which capabilities are delivered.

A capability inventory should record the required proficiency, urgency, current ownership, degree of strategic importance, and consequences of failure. A simple assessment scale is useful: 0 = absent, 1 = ad hoc, 2 = repeatable, 3 = scalable, and 4 = leading or strategically distinctive. The scale is ordinal, not a precise measurement; it supports disciplined discussion rather than false numerical precision.

2.3 Capability gap analysis

A gap exists when the required future capability exceeds the capability available through current employees, founders, systems, or external providers. Gaps should be assessed on more than headcount. A firm may have enough people but lack senior judgment, domain expertise, decision rights, or reliable processes.

For each material gap, ask:

• Is the gap urgent for the next milestone?
• Is it a bottleneck for other teams?
• Is it difficult to acquire externally?
• Is it a source of competitive advantage or material risk?
• Is demand sufficiently predictable to justify fixed employment?
• Can technology or process redesign reduce the requirement?

3. Organization Structures for Startups

3.1 Structure follows work, not status

Early startups often use a functional structure because scarce specialists need close coordination. A product engineer may work directly with a founder, designer, and early customers. As the organization grows, functional expertise may be supplemented by cross-functional product squads.

Common structures include:

• Founder-centered structure: founders make most decisions; suitable for very early validation, but vulnerable to overload.
• Functional structure: people are grouped by expertise, such as engineering, sales, and finance; efficient for professional development but may create silos.
• Cross-functional squad structure: product, design, engineering, and commercial roles collaborate around a customer or product outcome; strong for speed and learning.
• Matrix structure: employees have both functional and project accountability; useful at greater scale but potentially confusing for a small firm.

The appropriate structure depends on uncertainty, interdependence, regulatory exposure, product complexity, and growth stage. A startup should not copy the structure of a large corporation merely because its titles appear professional.

3.2 Span, layers, and decision rights

A startup’s organization should make accountability visible. For every important outcome, identify:

• the accountable decision-maker;
• the people responsible for execution;
• those consulted before a decision;
• those informed afterward.

A lightweight responsibility matrix can use the RACI convention: Responsible, Accountable, Consulted, and Informed. RACI is not a substitute for judgment. Excessive consultation can slow decisions, while multiple “Accountable” parties can mean that nobody is truly accountable.

Early structures should minimize management layers. A manager is justified when coordination, coaching, decision quality, or risk control exceeds the cost of management. Creating managers solely to reward tenure can produce hierarchy without capacity.

3.3 Designing roles around outcomes

A well-designed role includes:

1. purpose;
2. measurable outcomes;
3. recurring responsibilities;
4. decision authority;
5. required knowledge and behaviors;
6. interfaces with other roles;
7. indicators of success;
8. constraints, including legal or security requirements.

Role design should distinguish “must-have” criteria from “trainable” criteria. Requiring every desirable skill reduces the candidate pool and can reproduce biased hiring patterns. Conversely, understating a role’s complexity creates false expectations and early attrition.

4. Prioritizing Roles

Founders rarely have enough resources to hire every desirable role. Prioritization should combine strategic value, urgency, bottleneck effects, risk, and cost.

A practical role-priority assessment can rate each proposed role from 1 to 5 on:

• milestone contribution;
• bottleneck removal;
• risk reduction;
• learning value;
• scarcity or hiring difficulty;
• time sensitivity.

The ratings should not be treated as an objective formula. They provide a structured comparison, followed by qualitative review. A role with a moderate total score may still be mandatory if it controls a legal or safety risk.

Critical-role categories

Milestone-critical roles directly enable the next strategic result. A security engineer may be critical before enterprise launch even if not needed during initial prototyping.

Bottleneck roles unlock the productivity of several people. A product operations specialist may allow engineers and sales staff to work effectively by improving requirements, implementation, and feedback loops.

Risk-control roles manage legal, financial, safety, privacy, or security exposure. These roles may be part-time or external at first, but responsibility cannot be ignored merely because the organization is small.

Learning roles accelerate validated learning. Customer research, analytics, and experimentation may be more valuable than adding execution capacity when the primary uncertainty is product–market fit.

Sequencing hires

A sound sequence often follows this logic:

1. fill a capability that is both essential and difficult to outsource;
2. remove a bottleneck constraining existing staff;
3. add capacity when demand is demonstrated;
4. add specialization when complexity or risk justifies it;
5. add management when coordination costs exceed the founder’s span of control.

The sequence is not universal. A regulated health startup may need compliance expertise before commercial expansion, whereas a consumer prototype may need customer discovery before formal operations.

5. Headcount Planning and Workforce Scenarios

5.1 Headcount definitions

Headcount is the number of people engaged by an organization under a specified definition. It must be distinguished from full-time equivalent (FTE). One FTE represents the workload of one full-time position, but part-time employees or contractors may contribute fractional capacity.

If three people each work 0.5 of the reference full-time schedule, their combined capacity is:

where h_i is the fraction of full-time capacity supplied by person i. This measure assumes that fractions are comparable and that work quality and coordination effects are not being modeled. Two half-time individuals do not necessarily provide the same output as one full-time individual because handoffs and context switching may reduce effective capacity.

Headcount plans should state whether they include founders, employees, interns, contractors, agency workers, and open requisitions. Ambiguous definitions produce unreliable budgets.

5.2 Capacity-based planning

The basic capacity question is whether available productive capacity covers required workload. If required workload is W hours and one FTE provides P productive hours during the planning period, the approximate FTE requirement is:

P is not the employee’s paid hours. It should account for leave, meetings, training, administration, and unavoidable coordination. The formula assumes workload can be aggregated and that the work is sufficiently divisible. It is less reliable for highly creative, interdependent, or unpredictable work.

For example, suppose customer implementation requires 1,200 hours over a quarter. If one implementation employee can provide 360 productive hours in that quarter, the requirement is:

The firm may need four employees, external capacity, process automation, or a reduced implementation commitment. Rounding up is prudent when service obligations cannot be partially fulfilled, but the decision should also consider timing and demand uncertainty.

5.3 Hiring plans and timing

A headcount plan is a time-phased schedule rather than a final number. It should show opening headcount, planned starts, planned exits, vacancies, and closing headcount by month or quarter.

The expression uses “headcount” consistently. For FTE planning, the same logic applies only if starts and exits are expressed as FTE values. Hiring lag matters: an approved requisition is not productive capacity. The plan should include sourcing, selection, notice periods, onboarding, and ramp-up.

A more realistic capacity forecast is:

where RampFactor ranges from 0 to 1 and represents expected productive contribution during period t. This is a planning assumption, not a universal law. Ramp factors should be based on role complexity, onboarding quality, manager availability, and historical evidence.

5.4 Workforce scenarios

Because startup forecasts are uncertain, a single plan creates false confidence. At least three scenarios are useful:

Each scenario should specify trigger conditions. For example, an upside hiring trigger might be three consecutive months of demand exceeding service capacity, while a downside trigger might be funding delayed beyond a defined date.

Scenario planning is stronger when it identifies reversible and irreversible commitments. A short-term specialist contract may be reversible; a senior executive hire, office lease, or large permanent team is less reversible.

6. Workforce Budgeting and Runway

6.1 Total employment cost

Salary is only one component of workforce cost. A planning estimate may include base pay, employer taxes, benefits, bonuses, equity-related cash costs, recruiting fees, equipment, software, workspace, travel, and onboarding.

For an employee, a simplified annual cost estimate is:

The categories must be defined according to the jurisdiction and accounting policy. Equity is economically important but may not be a cash expense in the same way as salary; it should nevertheless be modeled separately for ownership and incentive analysis.

If annual cash employment cost is 96,000 monetary units, the monthly average is:

This average does not capture hiring fees, severance, bonuses, or timing differences. A cash-flow plan should use actual payment timing where liquidity is tight.

6.2 Burn and runway

Net cash burn is cash outflow minus cash inflow over a period. If cash expenses are 180,000 per month and cash receipts are 60,000 per month, net burn is:

A simple runway estimate is:

If available cash is 1,200,000 and monthly net burn is 120,000, runway is 10 months. This calculation assumes burn remains constant, an assumption that is often unrealistic. It excludes financing inflows, working-capital timing, taxes, one-time costs, and nonlinear growth. A monthly cash-flow model is preferable for actual decisions.

Hiring affordability should be tested against the milestone and financing plan, not merely against current cash. A new employee costing 12,000 per month may appear affordable under a static calculation but become dangerous if the hire also requires equipment, recruiting fees, management capacity, and additional support staff.

6.3 Budget sensitivity

A sensitivity analysis changes one assumption at a time or uses combinations of assumptions. Important variables include start date, compensation, hiring speed, attrition, revenue conversion, collection timing, and funding date. Decision-makers should identify which assumptions have the greatest effect on runway and milestone probability.

7. Build–Buy–Borrow–Automate Decisions

Not every capability requires a permanent employee. The four-way framework is:

• Build: develop capability internally through employees, training, and organizational learning.
• Buy: acquire capability through recruitment, acquisition, a vendor, or a packaged service.
• Borrow: access capability temporarily through contractors, advisors, fractional executives, agencies, partners, or secondments.
• Automate: use software, workflow redesign, or artificial intelligence to reduce manual work or improve consistency.

These choices are not mutually exclusive. A startup may borrow specialist legal expertise, buy accounting software, build product knowledge, and automate routine reporting.

Decision criteria

Evaluate each option against:

1. strategic distinctiveness;
2. required speed;
3. cost and cash timing;
4. quality and reliability;
5. confidentiality and data sensitivity;
6. regulatory accountability;
7. reversibility;
8. knowledge transfer;
9. vendor dependency;
10. scalability.

A low-cost vendor may create lock-in or expose sensitive data. A contractor may deliver quickly but fail to transfer knowledge. Automation may reduce transaction costs while increasing model, cybersecurity, or oversight risks.

Automation and AI

Automation is most suitable when work is repetitive, rules are stable, inputs are structured, and errors can be detected. AI tools can support drafting, classification, search, forecasting, customer-service triage, and coding assistance. They should not be treated as a substitute for accountability.

Before deploying AI in workforce processes, assess:

• privacy and lawful data use;
• discrimination and disparate impact;
• explainability and appeal procedures;
• accuracy and human review;
• intellectual-property and confidentiality risks;
• cybersecurity and vendor controls;
• records needed for auditability.

Using an algorithm to screen candidates does not remove the employer’s responsibility for fair and lawful selection. Automation should improve work design, not conceal a decision that management has failed to define.

8. Applied Case: Northstar Health Analytics

The following is an illustrative case, not a report of an actual company.

Background

Northstar Health Analytics has developed a software platform that helps outpatient clinics identify patients at risk of missing follow-up care. The company has 12 employees, including five engineers, two founders, one product designer, one sales lead, one customer implementation specialist, one finance administrator, and one part-time clinical advisor. It has 14 paying clinics and 900,000 monetary units in cash. Monthly cash expenses are 170,000 and monthly receipts are 50,000.

The next 12-month milestones are to reach 50 clinics, complete an information-security certification, reduce implementation time from six weeks to three weeks, and prepare for a financing round.

Problem

The founders propose hiring four engineers, two sales representatives, a head of marketing, a compliance manager, and a customer-success team immediately. The plan would increase fixed cost substantially, but the business has not yet demonstrated repeatable sales or implementation capacity.

Analysis

The capability map identifies four urgent gaps:

1. security and compliance ownership;
2. implementation process design;
3. repeatable enterprise sales;
4. product prioritization based on clinic outcomes.

The analysis shows that engineering capacity is not yet the primary constraint. Customer onboarding is slow because requirements are inconsistent and implementation knowledge is concentrated in one employee. Sales conversion is uncertain, so adding two representatives before improving the sales process may increase activity without improving revenue.

Current net burn is:

A static runway estimate is:

This is already shorter than the 12-month milestone horizon. It therefore would be imprudent to approve a large permanent hiring wave without financing or revenue triggers.

Approach and solution

Northstar adopts the following plan:

• borrow a fractional healthcare compliance specialist for certification preparation and control design;
• appoint the implementation specialist as process owner and hire one experienced implementation lead;
• build product-management capability by training a founder and hiring one product manager after the first implementation process is documented;
• test one additional sales representative only after a defined pipeline and qualification process exists;
• automate standardized data-import checks and implementation reporting;
• defer a head of marketing until customer acquisition economics are clearer;
• retain the clinical advisor but formalize decision rights and conflict-of-interest disclosure;
• create downside and upside triggers tied to signed clinic contracts, implementation backlog, and financing progress.

Outcome

The plan reduces immediate fixed commitments and addresses the actual bottleneck. It also creates evidence for later hiring. If implementation backlog exceeds a defined service threshold for two consecutive months, Northstar can add a second implementation employee. If qualified pipeline and conversion rates support sustainable sales capacity, the sales hire becomes justified. If certification risk increases, the fractional specialist can be converted to a permanent role or supported by a specialized firm.

Learning points

The case illustrates five principles:

1. The largest team is not necessarily the most valuable team.
2. Capability gaps may be more important than headcount gaps.
3. Temporary expertise can be appropriate for urgent, specialized, or uncertain work.
4. Hiring should be linked to observable triggers rather than optimism.
5. Compliance and clinical accountability cannot be outsourced conceptually, even when tasks are outsourced operationally.

9. Governance, Ethics, and Legal Considerations

Workforce planning has consequences for fairness, privacy, safety, and organizational legitimacy. Startups should establish basic controls early because informal practices become difficult to correct later.

Classification and employment compliance

The legal distinction between employee and independent contractor depends on jurisdiction and the actual relationship, including control, economic dependence, integration, and mutual obligations. Misclassification can create liability for wages, taxes, benefits, leave, and penalties. A contract label alone does not determine legal status.

Equal opportunity and structured selection

Role criteria should be job-related and consistently applied. Structured interviews, documented evaluation criteria, diverse sourcing, and review of selection outcomes can reduce arbitrary decisions. “Culture fit” should be translated into observable, job-relevant behaviors; otherwise it can become a proxy for similarity to existing founders.

Compensation and equity

Compensation decisions should reflect market conditions, role scope, internal equity, affordability, and legal requirements. Equity is not free compensation. It involves dilution, vesting, tax consequences, information asymmetry, and future-value uncertainty. Candidates should receive clear explanations and appropriate documentation.

Health, safety, and psychological climate

Startups often normalize excessive hours and emotional pressure. Sustainable performance requires workload monitoring, respectful conduct, anti-harassment processes, reasonable leave practices, and channels for raising concerns. Psychological safety supports learning, but it does not eliminate accountability for poor performance or misconduct.

Data governance

Personnel data, customer data, health information, and proprietary product information should be collected and accessed according to legitimate business need and applicable law. External providers and AI systems require due diligence, contractual safeguards, access controls, and incident procedures.

10. Implementation: From Plan to Operating Rhythm

A workforce plan should be reviewed as an operating instrument, not filed as an annual document. A practical rhythm includes:

• monthly review of actual versus planned headcount and cash cost;
• quarterly review of capability gaps and strategic milestones;
• post-hire review of time to productivity and role clarity;
• analysis of regretted attrition, offer acceptance, and hiring-source quality;
• review of scenario triggers and whether assumptions remain credible.

Useful indicators include:

• time to fill, interpreted alongside hiring quality;
• time to productivity;
• voluntary and regretted attrition;
• labor cost as a share of revenue or gross margin, where meaningful;
• capacity utilization and service backlog;
• milestone achievement per FTE;
• employee engagement and workload signals;
• diversity and selection-stage outcomes.

Metrics should support decisions rather than encourage gaming. For example, reducing time to fill by lowering selection standards can damage quality. A metric should be paired with its possible unintended consequences.

Challenges and Limitations

Workforce planning is inherently uncertain. Revenue forecasts may be wrong, role productivity may vary, and startup priorities may change. Quantitative models can create an illusion of precision when assumptions are weak. Capacity formulas generally treat work as divisible, but innovation, leadership, and collaboration are not perfectly divisible.

Scenario planning also has limits. Three scenarios may not capture a severe shock, and triggers can be ignored when founders become emotionally committed to a hiring plan. External labor markets can change rapidly, especially for scarce technical or regulated talent. Finally, capability maps can become bureaucratic if they are too detailed for the organization’s stage.

The appropriate response is not to abandon planning. It is to make assumptions explicit, use ranges where appropriate, link commitments to evidence, and preserve the ability to revise decisions.

Best-Practice Checklist

Before approving a role, ask:

1. Which milestone or risk does this role address?
2. What capability and outcomes are required?
3. Is the gap truly a people gap, or a process, technology, or decision-rights gap?
4. Why is permanent employment preferable to buying, borrowing, or automating?
5. What is the fully loaded cash and non-cash cost?
6. How long will the role take to become productive?
7. What scenario trigger authorizes or pauses the hire?
8. Who will manage, coach, and evaluate the person?
9. What legal, privacy, security, or ethical issues arise?
10. What evidence will show that the decision was successful?

Chapter Summary

Workforce strategy translates business ambition into organizational capability. The process begins with strategic milestones and a capability map, not job titles. Capability-gap analysis identifies what the startup must learn, build, control, or access. Organization structure should reflect uncertainty, interdependence, and decision rights, while roles should be defined through outcomes and accountability.

Headcount planning is time-phased and scenario-based. It distinguishes headcount from FTE, recognizes ramp-up time, and connects hiring decisions to capacity, cash cost, burn, runway, and funding constraints. The build–buy–borrow–automate framework helps startups obtain capability without assuming that every need requires a permanent employee. Automation and AI can improve efficiency but do not remove managerial, legal, or ethical accountability.

Effective plans combine quantitative discipline with judgment. They use explicit assumptions, trigger-based decisions, milestone review, and governance controls. The central managerial principle is simple: hire to create the capabilities required for the next important outcome, at the time and in the form that the startup can responsibly sustain.

Key Terms

Capability: An organizational ability to produce an outcome reliably.

Capability map: A structured representation of the abilities required to execute strategy.

Capacity: The amount of productive work an available workforce can perform.

FTE: Full-time equivalent; a standardized measure of workforce capacity.

Headcount: The number of people engaged under a stated organizational definition.

Milestone: A time-bounded, observable strategic result.

Bottleneck: A constraint that limits the performance of a process or system.

Role design: Specification of a role’s purpose, outcomes, responsibilities, authority, and requirements.

Functional structure: An organization grouped by areas of expertise.

Cross-functional squad: A team combining different specialties around a shared outcome.

RACI: A responsibility framework identifying Responsible, Accountable, Consulted, and Informed parties.

Ramp factor: An estimate of a new or transitioning worker’s productive contribution during a period.

Loaded employment cost: Compensation plus employer burdens, benefits, variable pay, and relevant role costs.

Net burn: Cash outflow minus cash inflow over a defined period.

Runway: The time current available cash can support the organization at an assumed burn rate.

Build: Develop a capability internally.

Buy: Obtain capability through recruitment, vendors, acquisition, or packaged services.

Borrow: Access temporary or fractional external capability.

Automate: Use technology or redesigned processes to reduce or augment manual work.

Workforce scenario: A coherent set of assumptions about business conditions and the resulting workforce response.

Review Questions

5 Short Answer Questions

1. What is the difference between a task, a role, and a capability?
2. Why should startup hiring be linked to milestones?
3. Define FTE and explain one limitation of using it as a capacity measure.
4. What costs should be considered in addition to base salary?
5. State one situation in which borrowing capability may be preferable to building it internally.

5 Long Answer Questions

1. Explain how a startup can translate strategy into a capability map and then into role priorities.
2. Compare founder-centered, functional, and cross-functional squad structures for an early-stage company.
3. Discuss the assumptions and limitations of runway calculations in workforce planning.
4. Explain the build–buy–borrow–automate framework, using examples from a technology startup.
5. Discuss the ethical, legal, and governance issues associated with algorithmic hiring and workforce data.

3 Analytical / Application Questions

1. A startup has 1,000,000 monetary units in cash, monthly expenses of 210,000, and monthly receipts of 70,000. It is considering a hire costing 15,000 per month. Calculate current runway, revised runway after the hire, and discuss whether the decision should be made using only the revised runway.
2. An organization expects 1,440 hours of implementation work in a quarter. Each FTE provides 360 productive hours, but a new hire is expected to operate at a 0.5 ramp factor for the quarter. Determine the approximate capacity implications and recommend a workforce response.
3. Using the Northstar case, evaluate whether the company should prioritize engineering, implementation, sales, compliance, or marketing. Justify the recommendation using milestone contribution, bottleneck effects, risk, reversibility, and cash constraints.

Multiple Choice Questions with Answers

Question 1

Which sequence best represents disciplined workforce planning?

A. Titles → salaries → interviews → strategy

B. Strategy → milestones → capabilities → roles → workforce options → cost and risk

C. Budget → office space → titles → capabilities

D. Recruitment agencies → interviews → organization chart → strategy

Correct Answer: B. Strategy → milestones → capabilities → roles → workforce options → cost and risk

Question 2

A capability is best understood as:

A. A single task completed by one employee

B. A job title used in an organization chart

C. An organizational ability to produce an outcome reliably

D. A temporary staffing arrangement

Correct Answer: C. An organizational ability to produce an outcome reliably

Question 3

A startup needs 1,200 hours of work, and one FTE provides 360 productive hours during the period. What is the approximate FTE requirement?

A. 2.33 FTE

B. 3.00 FTE

C. 3.33 FTE

D. 4.50 FTE

Correct Answer: C. 3.33 FTE

Question 4

If a startup has 900,000 monetary units in cash and monthly net burn of 120,000, its simple estimated runway is:

A. 5.5 months

B. 7.5 months

C. 9.0 months

D. 10.5 months

Correct Answer: B. 7.5 months

Question 5

Which item is most likely to justify a permanent internal capability?

A. A one-week need for generic presentation design

B. A strategically distinctive capability requiring continuous learning and control

C. A temporary workload spike with highly predictable requirements

D. A standard service available from multiple reliable vendors

Correct Answer: B. A strategically distinctive capability requiring continuous learning and control

Question 6

What does a ramp factor represent in workforce planning?

A. The employee’s legal employment classification

B. The fraction of expected productive contribution during a period

C. The percentage of salary paid as equity

D. The number of interview stages completed

Correct Answer: B. The fraction of expected productive contribution during a period

Question 7

Which scenario is a downside workforce response?

A. Accelerating all discretionary hiring immediately

B. Adding management layers before demand is demonstrated

C. Freezing discretionary hiring while protecting critical controls and customer roles

D. Replacing milestone planning with annual hiring targets

Correct Answer: C. Freezing discretionary hiring while protecting critical controls and customer roles

Question 8

Which statement about runway is most accurate?

A. It is always exact if cash is measured precisely

B. It ignores cash inflows by definition

C. It is a simplifying estimate that depends on burn and cash assumptions

D. It measures employee productivity directly

Correct Answer: C. It is a simplifying estimate that depends on burn and cash assumptions

Question 9

In the build–buy–borrow–automate framework, borrowing refers to:

A. Developing a capability through internal training only

B. Accessing temporary or fractional external expertise

C. Purchasing a permanent office

D. Removing a capability from the business

Correct Answer: B. Accessing temporary or fractional external expertise

Question 10

Why should AI-supported hiring processes include human review and governance?

A. Because automation eliminates all useful data

B. Because employers remain responsible for fairness, accuracy, privacy, and lawful decisions

C. Because algorithms can never process structured information

D. Because human review guarantees that every hiring decision is correct

Correct Answer: B. Because employers remain responsible for fairness, accuracy, privacy, and lawful decisions