AGENCYSCRIPT
CoursesEnterpriseBlog
👑FoundersSign inJoin Waitlist
AGENCYSCRIPT

Governed Certification Framework

The operating system for AI-enabled agency building. Certify judgment under constraint. Standards over scale. Governance over shortcuts.

Stay informed

Governance updates, certification insights, and industry standards.

Products

  • Platform
  • Certification
  • Launch Program
  • Vault
  • The Book

Certification

  • Foundation (AS-F)
  • Operator (AS-O)
  • Architect (AS-A)
  • Principal (AS-P)

Resources

  • Blog
  • Verify Credential
  • Enterprise
  • Partners
  • Pricing

Company

  • About
  • Contact
  • Careers
  • Press
© 2026 Agency Script, Inc.·
Privacy PolicyTerms of ServiceCertification AgreementSecurity

Standards over scale. Judgment over volume. Governance over shortcuts.

On This Page

Building the Foundation — Understanding Your NeedsStep One — Define Your Revenue PlanStep Two — Map Revenue to Capacity RequirementsStep Three — Define Your Team Composition ModelStep Four — Identify the GapsStep Five — Prioritize and SequenceThe Twelve-Month Hiring PlanFinancial Modeling for HiringThe Hiring Break-Even CalculationCash Flow ImpactHiring Triggers Versus Fixed TimelinesContingency PlanningIf Revenue Falls ShortIf Revenue Exceeds ExpectationsIf a Key Person LeavesTracking and Adjusting the PlanMonthly ReviewQuarterly AdjustmentYour Next Step
Home/Blog/Patrick Hired Every Time He Felt Overwhelmed, and It Caught Up
General

Patrick Hired Every Time He Felt Overwhelmed, and It Caught Up

A

Agency Script Editorial

Editorial Team

·March 21, 2026·12 min read
hiring planworkforce planningtalent strategyagency growth

CoreLogic AI grew from three to fourteen employees in eighteen months. The founder — Patrick Doyle — hired whenever he felt overwhelmed. When delivery was backed up, he hired an engineer. When sales calls piled up, he hired a business development rep. When the office felt chaotic, he hired an operations coordinator. Each hire seemed reasonable in isolation. But when Patrick looked at his team composition at the fourteen-person mark, the picture was concerning. He had eight engineers, two sales people, an operations coordinator, a designer, a project manager, and himself. Revenue per employee was $105,000 — well below the $180,000 industry benchmark. Three of the eight engineers had overlapping skill sets. The sales team was generating leads, but the project manager was overwhelmed coordinating fourteen people. And nobody was handling client success, leading to churn that wiped out the new revenue the sales team generated.

Patrick had hired tactically — solving today's problem — without a strategic plan that aligned team composition with business needs. The result was an expensive, unbalanced team that was less effective than a smaller, better-composed team would have been.

A strategic hiring plan connects your business goals to your team growth. It answers: What roles do we need, when do we need them, and why? It prevents reactive hiring, ensures balanced team composition, and aligns your largest expense — payroll — with your revenue trajectory.

Building the Foundation — Understanding Your Needs

Step One — Define Your Revenue Plan

Your hiring plan must be grounded in your revenue plan. How much revenue do you expect to generate in the next twelve months? What is the trajectory — steady growth, accelerating, or uncertain?

Revenue scenarios:

Create three revenue scenarios for the next twelve months:

  • Conservative: Revenue grows at the slower end of your expectations. Market conditions are tough, close rates decline, or a major client churns.
  • Expected: Revenue grows at the rate your pipeline and historical performance suggest.
  • Optimistic: Revenue grows faster than expected — a large deal closes, market demand surges, or a new service takes off.

Your hiring plan should align with the expected scenario, with flexibility to scale up (if optimistic materializes) or slow down (if conservative materializes).

Step Two — Map Revenue to Capacity Requirements

For each revenue scenario, calculate the delivery capacity required.

Capacity calculation:

  • Total delivery hours needed: Expected revenue divided by your effective hourly rate (or the average revenue per billable hour across your agency)
  • Available hours per person: Working hours per month (typically 160 for full-time) multiplied by target utilization rate (typically 70% to 80% for engineers)
  • People needed: Total delivery hours divided by available hours per person

Example:

  • Expected annual revenue: $2,400,000
  • Effective hourly rate: $200
  • Total delivery hours needed: 12,000 per year / 1,000 per month
  • Available hours per engineer at 75% utilization: 120 per month
  • Engineers needed: approximately 8 to 9

This gives you the delivery headcount target. But you also need to account for non-delivery roles.

Step Three — Define Your Team Composition Model

A balanced agency team includes delivery roles, revenue-generating roles, and operational roles. The right ratio depends on your agency's size and stage.

Typical team composition by stage:

Five to eight people:

  • 60% to 70% delivery (engineers, data scientists)
  • 10% to 15% revenue (sales, marketing, or founder wearing the hat)
  • 10% to 15% operations (project management, admin)
  • 10% to 15% leadership (founder time on strategy and management)

Ten to twenty people:

  • 55% to 65% delivery
  • 15% to 20% revenue (sales, marketing, business development)
  • 15% to 20% operations (project management, client success, admin)
  • 5% to 10% leadership

Twenty-plus people:

  • 50% to 60% delivery
  • 15% to 20% revenue
  • 20% to 25% operations (including people management, finance, quality)
  • 5% to 10% leadership

Compare your current team composition to these benchmarks. Significant deviations suggest imbalances that your hiring plan should address.

Step Four — Identify the Gaps

With your capacity requirements and team composition model defined, identify the specific gaps between your current team and your target team.

Gap analysis template:

For each role category, answer:

  • How many people do we have now?
  • How many do we need at our twelve-month revenue target?
  • What specific skills or specializations are missing?
  • Which gaps are most urgent (blocking current revenue) versus strategic (enabling future revenue)?

Example gap analysis:

Current team: 9 people

  • Engineers: 5 (need 7-8 at expected revenue)
  • Sales: 1 (need 2 to grow pipeline)
  • Project management: 1 (need 2 at the expected project volume)
  • Client success: 0 (need 1 — churn is a growing problem)
  • Operations: 1 (sufficient for now)
  • Founder: 1

Gaps:

  • 2-3 engineers — one with NLP specialization, one generalist
  • 1 salesperson — business development focus
  • 1 project manager
  • 1 client success manager

Step Five — Prioritize and Sequence

You cannot fill all gaps simultaneously. Prioritize based on impact and urgency.

Prioritization criteria:

  • Revenue impact: Which hire will most directly increase revenue? (Usually sales or delivery roles that are bottlenecking new work)
  • Retention impact: Which hire will most directly reduce client churn? (Usually client success or delivery quality roles)
  • Founder liberation: Which hire will most effectively remove the founder from day-to-day operations? (Usually operations or management roles)
  • Financial feasibility: Can you afford this hire now, or do you need revenue growth first?

Sequencing principle: Each hire should either directly generate revenue (sales, delivery) or create the capacity for others to generate more revenue (operations, management). Avoid hiring roles that add cost without a clear path to increased revenue.

The Twelve-Month Hiring Plan

Structure your plan as a quarterly hiring roadmap.

Q1 — Foundation hires:

The hires that address your most critical current constraints. Typically one delivery person and one operational or revenue person.

Q2 — Growth hires:

The hires that build capacity for your revenue growth trajectory. These should be timed to coincide with expected revenue growth so that utilization remains healthy.

Q3 — Specialization hires:

The hires that add specialized capabilities to your team — a specific technical specialization, a dedicated marketing person, or a senior delivery lead.

Q4 — Strategic hires:

The hires that position you for the following year — leadership development, new service area capabilities, or geographic expansion.

Each hire in the plan should specify:

  • Role title and description
  • Required and desired skills
  • Target start date (quarter or month)
  • Revenue trigger — the revenue milestone that justifies the hire
  • Estimated fully loaded cost
  • Expected impact — how this hire will affect revenue, utilization, or operational efficiency

Financial Modeling for Hiring

The Hiring Break-Even Calculation

For each planned hire, calculate when they will break even — the point at which their contribution to revenue exceeds their cost.

For delivery roles:

  • Fully loaded monthly cost: $12,000
  • Expected billable hours per month: 120
  • Billing rate: $200 per hour
  • Monthly revenue contribution: $24,000
  • Break-even: Month one (if work is available immediately)
  • Ramp-up adjustment: Engineers typically reach full productivity in two to three months. Assume 50% productivity in month one, 75% in month two, and full productivity from month three.

For sales roles:

  • Fully loaded monthly cost: $10,000
  • Expected ramp-up to first closed deal: three to six months
  • Expected annual closed revenue once ramped: $500,000
  • Break-even: Approximately month six to eight (total investment of $60,000 to $80,000 before the hire contributes net revenue)

For operations roles:

Operations roles do not directly generate revenue, but they free up revenue-generating people to be more productive. Calculate the break-even by estimating how many additional billable hours the operations hire frees up across the team.

  • Fully loaded monthly cost: $7,000
  • Hours freed up from billable team members: 40 per month
  • Value of freed hours at blended billing rate: $8,000 per month
  • Break-even: Month one

Cash Flow Impact

Each new hire increases your monthly burn rate. Model the cash flow impact of each hire:

  • How much cash will be consumed before the hire reaches break-even?
  • Do you have sufficient cash reserves to absorb this pre-break-even investment?
  • What happens if the hire takes 50% longer than expected to reach full productivity?

As a general rule, have enough cash reserves to fund each new hire for three months at full cost with zero revenue contribution. This provides a buffer for ramp-up delays, onboarding costs, and market uncertainty.

Hiring Triggers Versus Fixed Timelines

Rather than committing to specific hire dates, consider using revenue triggers — specific revenue milestones that activate the next hire.

Example triggers:

  • "When monthly revenue exceeds $120,000 for three consecutive months, initiate hire for Engineer #7"
  • "When the sales pipeline exceeds $500,000 in qualified opportunities, initiate hire for BDR #2"
  • "When average team utilization exceeds 82% for four consecutive weeks, initiate hire for next delivery person"

Revenue triggers prevent two dangerous scenarios: hiring too aggressively before revenue supports it, and hiring too slowly when demand has clearly justified the investment.

Contingency Planning

Your hiring plan should include contingency plans for scenarios where reality diverges from expectations.

If Revenue Falls Short

  • Which planned hires can be deferred without critical impact?
  • Can any planned full-time roles be filled with contractors instead?
  • What is the minimum team size needed to sustain current operations?

If Revenue Exceeds Expectations

  • Can you accelerate planned hires without compromising quality?
  • Do you have a warm pipeline of candidates who could be engaged quickly?
  • Can contractors fill the gap while you hire full-time roles?

If a Key Person Leaves

  • For each critical team member, who is the backup?
  • How quickly can you hire a replacement? (This is why maintaining a warm pipeline matters)
  • Can responsibilities be redistributed temporarily without hiring?

Tracking and Adjusting the Plan

Monthly Review

Review your hiring plan monthly against actual revenue and capacity data.

  • Is revenue tracking to the expected scenario?
  • Is utilization within the target range?
  • Are there emerging gaps not covered by the plan?
  • Do any planned hires need to be accelerated or deferred?

Quarterly Adjustment

Every quarter, formally update the hiring plan:

  • Revise revenue projections based on actual performance
  • Recalculate capacity requirements
  • Adjust hiring timeline and priorities
  • Update financial models with actual cost data

Your Next Step

Create a simple spreadsheet with four tabs: current team roster (name, role, start date, cost), gap analysis (needed roles and skills versus current capabilities), twelve-month hiring plan (role, priority, target quarter, trigger, estimated cost), and financial model (monthly cash flow projection including hiring costs). Populate the first two tabs this week using the frameworks in this post. Then build the hiring plan and financial model based on your gap analysis. Review it with your accountant or financial advisor to validate the financial assumptions. This document becomes your compass for every hiring decision over the next year.

Search Articles

Categories

OperationsSalesDeliveryGovernance

Popular Tags

prompt engineeringai fundamentalsai toolsthe difference between AIMLagency operationsagency growthenterprise sales

Share Article

A

Agency Script Editorial

Editorial Team

The Agency Script editorial team delivers operational insights on AI delivery, certification, and governance for modern agency operators.

Related Articles

General

Prompt Quality Decides Whether AI Earns Its Keep

Prompt quality is the single biggest variable in whether AI delivers real work or expensive noise. The model matters, the platform matters — but the prompt you write determines whether you get a first

A
Agency Script Editorial
June 1, 2026·10 min read
General

Counting the Real Cost of Every Token You Send

Tokens and context windows sit at the intersection of AI capability and operational cost—yet most business cases treat them as technical footnotes. That's a mistake that costs real money. Every time y

A
Agency Script Editorial
June 1, 2026·10 min read
General

Rolling Out AI Hallucinations Across a Team

Most teams discover AI hallucinations the hard way — a confident-sounding wrong answer makes it into a client deliverable, a legal brief, or a published report. The damage isn't just to the output; it

A
Agency Script Editorial
June 1, 2026·11 min read

Ready to certify your AI capability?

Join the professionals building governed, repeatable AI delivery systems.

Explore Certification