Content production ramp calculator

Models how adding content hires changes monthly output (written, video, design) and what that's worth in organic sessions, conversions and ARR, against the current no-new-hires plan. Every rate below is a real, cited figure or a clearly labelled estimate you can adjust; this is a planning tool, not a locked forecast.

Add hires

Assumptions

Value chain (real, cited)
Current baseline (real + latest confirmed)
Output per hire, per month (estimate, editable)
Traffic value per piece (estimate, editable)
Baseline monthly cadence, no new hires (from the hero-month plan)
Extra pieces / month
+0
vs 2 today (1 written, 1 video)
Extra ARR booked, 12mo
£0
cumulative vs no-new-hires plan
Fully-loaded hire cost
£0/mo
salary + 18% on-cost
Payback
—
month value overtakes cost

Organic sessions, 12-month trajectory

Sitewide CVR, no-hires plan vs with design capacity

Monthly output by type

TypeNo new hiresWith this scenarioDifference
Written pieces–––
Video packages–––
Fully-designed pieces–––

How this is worked out

Value per non-brand organic session = non-brand CVR × lead-to-Closed-Won rate × average contract value. With the defaults: 1.21% × 8.21% × £6,675 ≈ £6.63 per session. This is the real, cited conversion path (GA4 key events via AirOps, 21 Jul 2026 cross-check; close rate and ACV from the CVR-to-ARR scenario model, 15 Sep 2026), not an estimate.

Current non-brand sessions/month is derived from the last confirmed GSC figure (10 Aug 2026: ~50.2k clicks over the trailing 6 months, ≈8,370/month) split by the 12 Sep 2026 brand/non-brand ratio (86% branded, so 14% non-brand ≈1,170/month). Edit this if you have a fresher pull.

Output-per-hire and traffic-per-piece figures are estimates, not measured facts: we don't yet have a locked baseline for how many organic sessions a typical new piece drives once mature. The written-piece default (80 sessions/month at maturity) sits well below our best-performing individual non-brand page (≈177/month over the last confirmed 90-day window), which is a deliberate margin of caution. Adjust every one of these to match what you and Liv believe is realistic, and the whole model recalculates.

Design isn't modelled as its own traffic source. Design capacity is treated as a conversion-rate multiplier on pieces it fully supports (default +15%), since a well-designed page converts better rather than ranks differently. Pieces beyond current design capacity still publish, just without that uplift.

Hire cost uses the midpoint of each role's researched UK salary band plus 18% on-cost (employer NI + pension), the same on-cost assumption used across this year's cost-breakdown workbooks.

This is a planning estimate to stress-test the case for hiring, built from real conversion and traffic data plus clearly editable assumptions about content output and ramp. Treat the headline numbers as directional, not as a committed forecast, until a few months of real post-hire data let us tighten the estimate ranges above.