Size a GEO program in hours: a monthly budget for Series A-B RevOps
A Series A-B RevOps lead can size a GEO program at roughly 32 hours a month. The number breaks at three visible thresholds, and each one has a date and a test.
Ida Karlsson
Capacity columnist
Writes about selling capacity: how many sellers a number needs and when that stops being true.
Entries
Flat-priced Salesforce DevOps tools: how to size the EUR 99 and EUR 199 tiers
Flat tiers cap users and connections, not changes. Here is the arithmetic for a RevOps lead deciding between a EUR 99 and a EUR 199 plan, and when the answer expires.
HubSpot CRM cleanup: 110 to 180 hours before a capacity model can trust pipeline
A planning range of 110 to 180 RevOps hours for HubSpot CRM cleanup and lifecycle-stage redesign, with the arithmetic, the falsification condition and the split between what an embedded consultant builds and what the revenue leader must decide.
Salesforce to HubSpot migration: how many RevOps hours it needs
A planning model for the RevOps hours a Salesforce to HubSpot migration consumes, why headcount is not capacity, and the conditions under which an embedded consultant beats a hire.
Data pipeline observability: a capacity number is only as good as its last sync
A selling-capacity number that moves with no business event is a pipeline event until the logs say otherwise. The column argues for data pipeline observability, shows the arithmetic, and says what would withdraw the claim.
The milestone that triggers a hire matters more than the headcount number
Most headcount plans fail before a single offer letter goes out. The problem is the trigger milestone, not the target number — and the arithmetic to find the right one is straightforward.
When your Salesforce admin headcount becomes the pipeline ceiling
The traditional model treats Salesforce admin headcount as the direct input to change capacity. AI-assisted DevOps tools are separating change generation from change review, and the arithmetic matters.
Salesforce AI governance has a weekly ceiling, and it is the approvers
Three reviewers approve about 32 AI-drafted Salesforce changes a week in a constructed model. Here is the arithmetic, where it fails, and the date it gets revisited.
The Salesforce audit trail you can keep: a claim that could be wrong
A customer-owned repository with its pull request history is more inspectable than a trail held inside a vendor product. Here is the claim, the arithmetic, and what would make it false.
Approval capacity is the constraint behind an AI marketer
The drafting is cheap and the sign-off is not. Approval capacity, measured in reviewer hours, sets how much an agent's output is worth.
Fractional capacity is about a third of a head
A twenty-hour fractional engagement is priced as half a head. Count ramp and handoff and the first quarter delivers about a third of one.
An AI outbound agent with no added headcount adds close to zero selling capacity
An AI outbound agent that ships with no added headcount is not adding selling capacity — it's adding a maintenance load against a team that was already at capacity before the agent arrived.