The True Cost Per Story Point of Your Engineering Team

Your team delivered 150 story points last quarter. Is that good? Bad? Expensive? Cheap? Without knowing what those points actually cost, the number is meaningless. Yet most engineering teams track velocity religiously while ignoring the cost side of the equation entirely.

Understanding your true cost per story point isn't just accounting trivia. It's the foundation for making informed trade-offs between speed, quality, and investment. It's how you answer questions like "Should we hire another engineer?" or "Is this contractor worth the premium?"

What Goes Into Fully-Loaded Cost

To calculate cost per story point, you first need accurate fully-loaded costs. Most engineering leaders underestimate this by 30-50% because they stop at salary.

Direct Compensation

• Base salary: The obvious starting point
• Bonuses: Annual, signing, retention
• Equity: Stock grants, options (use fair value, not face value)

Benefits

• Health insurance: Medical, dental, vision (employer portion)
• Retirement: 401(k) match, pension contributions
• Life/disability insurance: Often forgotten but real cost
• Parental leave: Paid time plus coverage costs
• PTO: Cost of paid time not working

Employer Taxes

• Social Security: 6.2% up to wage base
• Medicare: 1.45% on all wages
• State unemployment: Varies by state
• Workers' compensation: Required insurance

Infrastructure and Tools

• Equipment: Laptop, monitors, peripherals (amortized)
• Software licenses: IDE, tools, SaaS per-seat costs
• Cloud resources: Development environments, CI/CD
• Office space: If applicable, prorated per person

Overhead Allocation

• HR costs: Per-employee HR administration
• Management: Manager time allocated per report
• Training: Onboarding, ongoing development
• Recruiting: Amortized cost of finding and hiring

"A rule of thumb: multiply base salary by 1.3-1.5 to get fully-loaded cost. But actually calculating it is more accurate than rules of thumb."

Calculating Productive Capacity

The denominator matters as much as the numerator. How many story points does your team actually produce?

Productive Hours Reality

Start with 2,080 hours/year (40 hours x 52 weeks). Then subtract:

• PTO: 15-25 days = 120-200 hours
• Holidays: 10-12 days = 80-96 hours
• Sick time: 5-10 days = 40-80 hours
• Meetings: 5-15 hours/week = 260-780 hours/year
• Administrative tasks: 2-5 hours/week = 104-260 hours/year
• Context switching: Studies suggest 20-40% productivity loss

Realistically, an engineer might have 1,000-1,400 hours of focused productive time per year. That's 50-67% of nominal capacity—and that's being optimistic.

From Hours to Story Points

Story points per hour varies enormously based on:

• Codebase complexity and technical debt
• Team experience and cohesion
• How your team calibrates story points
• Mix of work (greenfield vs. maintenance)

The key insight: don't try to standardize story points across teams. Instead, measure each team's historical velocity and cost, then calculate their specific cost per point.

The Calculation

Here's a worked example for a senior engineer:

Fully-Loaded Annual Cost

• Base salary: $180,000
• Benefits: $22,000
• Employer taxes: $14,000
• Equipment/tools: $5,000
• Overhead allocation: $15,000
• Total: $236,000/year

Annual Output

• Sprints per year: 26 (two-week sprints)
• Average velocity: 12 points/sprint
• Availability factor: 85% (PTO, sick, etc.)
• Annual output: 265 story points

Cost Per Story Point

$236,000 / 265 points = $890 per story point

That's the number. Every story point your senior engineer delivers costs roughly $890 in fully-loaded expense.

Comparing Across Scenarios

Cost per story point becomes powerful when you compare scenarios:

Junior vs. Senior

• Junior: $140K fully loaded, 6 points/sprint = $1,008/point
• Senior: $236K fully loaded, 12 points/sprint = $890/point

The senior costs 69% more but delivers twice the velocity. Their cost per point is actually 12% lower. This is why "juniors are cheaper" is often wrong.

In-House vs. Contractor

• In-house senior: $890/point
• Contractor at $150/hr: If they deliver similar velocity, that's ~$1,100/point

The contractor looks 23% more expensive per point. But if they're faster to onboard, have specialized skills, or provide flexibility you value, that premium might be worth it.

Team Composition Effects

Management overhead changes the math. A team of 6 engineers with one manager:

• 6 engineers at $890/point average
• Manager at $280K fully loaded, not delivering points directly
• Team delivers 60 points/sprint = 1,560 points/year
• Total cost: (6 x $236K) + $280K = $1.7M
• Cost per point: $1,090/point

Adding the manager increased cost per point by 22%. That overhead is worth it if the manager makes the team more effective—but it's real and should be tracked.

Benchmarking Your Numbers

What's a "good" cost per story point? It depends on context, but here are rough benchmarks:

By Company Stage

• Early startup (seed/A): $600-900/point (lean teams, high productivity pressure)
• Growth stage (B/C): $800-1,200/point (scaling pains, more overhead)
• Mature company: $1,000-1,500/point (more process, larger teams)
• Enterprise: $1,200-2,000/point (compliance, bureaucracy, specialization)

By Technical Domain

• Web applications: Moderate complexity, moderate cost
• Mobile: Higher due to platform fragmentation
• Infrastructure/DevOps: Higher due to specialization
• ML/AI: Highest due to talent scarcity and compute costs
• Legacy systems: Higher due to complexity and knowledge requirements

Warning Signs

• Cost per point increasing over time: Growing overhead, declining efficiency
• High variance between similar engineers: Inconsistent point calibration or performance issues
• Cost much higher than benchmarks: Process problems, wrong team composition, or technical debt

Using Cost Per Point for Decisions

Hiring Decisions

When evaluating a new hire, estimate their expected velocity and calculate projected cost per point. If a candidate will cost $1,200/point and your team average is $900, they need to bring something else—skills, mentorship, architecture—to justify the premium.

Project Planning

If a feature is estimated at 100 story points and your cost is $900/point, that feature costs ~$90K in engineering time. Is it worth it? Now you can have that conversation with product.

Team Investment

If investing $50K in tooling reduces your cost per point from $900 to $800, that's an 11% efficiency gain. On 1,500 points/year, that's $150K saved—3x return on the tooling investment.

Technical Debt Quantification

Technical debt slows you down, but by how much? If a refactoring project would improve velocity by 20%, you can calculate the payback period in cost-per-point terms.

The Limitations

Cost per story point is useful but not perfect:

• Story points aren't standardized: Comparing across teams is tricky
• Not all work is points: Research, support, mentorship don't show up
• Quality matters: Fast, buggy points cost more in the long run
• Short-term focus: Optimizing for points can hurt long-term velocity

Use cost per point as one metric among several, not the only metric that matters.

Getting Started

If you're not tracking cost per story point today, here's how to start:

1. Calculate fully-loaded costs for each team member (or average by level)
2. Pull velocity data from your project management tool
3. Divide cost by output for the measurement period
4. Track over time to see trends
5. Compare across scenarios when making hiring or investment decisions

The first calculation will probably surprise you. Most teams underestimate their true cost per point by 30-50%. That's not a problem—it's information. And with that information, you can finally make engineering investment decisions based on data rather than intuition.

What gets measured gets managed. Start measuring your cost per story point.