Limited cohort
A discipline where a managed-service vendor onboards a small number of customers per cycle to preserve quality.
“Limited cohort” is a constraint a productized-service vendor places on themselves: only a small number of customers are onboarded per cycle, the rest wait. The constraint exists because a managed service’s quality is bounded by the operator’s bandwidth, and the operator’s bandwidth is bounded by hours in the week.
A vendor running an iteration loop for ten customers can review a hundred patterns a week and ship fixes weekly. The same vendor with a hundred customers can review the same hundred patterns — ten times more thinly — and ship fixes monthly. Quality drops. The compounding curve flattens. The retainer’s premise (we make your agent better, week over week) stops being true.
The cohort discipline is borrowed from productized-service businesses: open seats only when the operator can ship for them properly. Close seats when the queue gets dense. Be honest with the waitlist about timing.
For buyers, the signal that a vendor runs a real limited cohort (vs. waitlist-as-marketing-tactic) is concrete: the vendor can tell you how many customers they currently serve, what the iteration cadence is for each one, and when the next intake window opens. If they can’t, “limited cohort” is just a scarcity gimmick.
RidgeHQ runs a limited cohort by design. Our retainer includes weekly review with each customer; that bounds how many customers we can serve well. We’re explicit about the cohort window on intake, and the intake form is read within 48 hours.