A person is better than this at four things, and this page says which four. It is worth being exact about the rest: what a seat actually buys you, when it starts, and which hours of the week it is awake for.
Every square is one hour of one week. The lit ones are when a full-time specialist in one timezone is at their desk.
45 of 168, and they are the hours your user is at work doing the job they are actually paid for.
The evening a trial finally gets opened, the Saturday somebody migrates their data, the 23:41 import that fails — every one of those lands in the dark squares. A second seat lights forty-five more, in the same timezone, if they are not on holiday.
Nothing here is a criticism of hiring. It is the timetable, which is the part a headcount plan tends to leave out.
Writing it, screening, four rounds, notice period. The gap you are hiring against is doing whatever it was already doing throughout.
Knowing your category, not your product. The first months are spent learning what your software actually does, which is exactly what Discovery does in an afternoon.
Deal-ready, product-fluent, trusted in front of a customer. Real, and worth it — but it is nine months after the quarter you needed it in.
And the product knowledge leaves with them, because it lived in one head. The next hire starts the same nine months over.
Amvio has no ramp because it does not learn your product from you. It reads it. That is the only line on this page where the comparison is not close.
This is not a page arguing you should have fewer people. It is arguing that the people you have are spending their week on the wrong five thousand.
Whether to give this account the credit, whether the relationship survives the outage, whether to escalate to the founder. Nothing here should be deciding that.
Price, terms, the roadmap promise. Amvio is instructed to refuse all three and hand them to you with the transcript attached.
Somebody who wants a person to be accountable to them. That is a person's job and it always will be.
In a book of six thousand, a handful each week genuinely need the specialist. The problem was never that they existed — it was finding them under everybody else.
The argument is not headcount versus software. It is that the nine accounts that need a person this week are currently invisible, and the specialist who should be on them is answering the same import question for the fortieth time.
Bring your account count and your ratio. The interesting number is not what a seat costs — it is how many of your users neither the seat you have nor the seat you are about to open will ever reach.
Your users are already having the conversation. Right now it is with nobody.