If you think in systems, SEO agency growth is a throughput problem. Revenue going up while delivery cost goes up proportionally is linear growth, not scale.
The capacity model
python
available_hours = 400 # monthly delivery hours
hours_per_client = 20
rework_and_blocked = 60
naive_capacity = available_hours / hours_per_client # 20
real_capacity = (available_hours - rework_and_blocked) / hours_per_client # 17
Feed it your own time data. It's a working model, not an industry benchmark.
Find the constraint
Work piles up in one of four queues: onboarding, content production, approvals, or reporting. Measure where tasks wait, not where they finish. The longest queue is your constraint.
A blocked-work log schema that's surprisingly effective:
reason | owner | next_action | client_dependency
Separate roles like services
strategy -> keyword mapping, briefs, technical recs
production -> drafting, on-page, CMS publishing
review -> fact checks, voice, final approval
accounts -> client comms, approvals, reporting
One person can hold two roles. The point is that each handoff has an owner.
What to automate
Rule: automate tasks that are repetitive, reversible, rules-based, and reviewable.
Typical manual pipeline:
research_tool -> export CSV -> sheet
content_tool -> copy brief -> doc
doc -> paste -> CMS
CMS -> manual -> index submission
GSC -> copy -> client report
Every arrow is latency and an error surface. Connecting those steps usually beats generating more content.
Escalation rules (keep these human)
Unverified claims, stats, or regulated topics -> senior reviewer
Redirects, robots rules, templates -> approval required
Repeated rework on one deliverable -> workflow review
Metrics to log per client
revenue_per_client, gross_margin, delivery_hours,
utilization, rework_hours_per_deliverable,
blocked_days, retention, lead_to_client_rate
Full playbook: https://keytomic.com/blog/how-to-scale-an-seo-agency
