Most firms don't decide to bring in overflow delivery support during a calm week. It usually happens reactively, after a deadline is already at risk. The firms that use overflow capacity well tend to notice these signs earlier, and treat them as a planning problem instead of a fire to put out.
1. You've turned down work you were qualified to win
If the reason was capacity, not fit, that's a direct signal — and every turned-down project is also a client relationship you didn't get to start.
2. One person is the only one who understands a cloud you've sold into
Marketing Cloud, CPQ, Data Cloud — if expertise in a given cloud lives in exactly one person's head, that's a single point of failure the moment they're on vacation, sick, or leave.
3. Timelines are slipping because delivery can't keep pace with sales
A healthy sales pipeline that delivery can't absorb isn't a win, it's a liability building quietly in the background — and clients notice the slippage before leadership does.
4. Your team is doing generalist work outside its certified depth
Stretching a Sales Cloud-certified team onto a Marketing Cloud build because there's no one else available is how avoidable mistakes end up in front of a client.
5. You're weighing a hire for a need that might not be permanent
If the gap is for one large engagement rather than a standing need, a full-time hire is a slow, expensive, and hard-to-reverse way to solve a temporary capacity problem.
The reframe
None of these are signs of a firm doing something wrong — they're normal growing pains for a healthy pipeline. The difference between firms that handle them well and firms that don't is usually just timing: lining up overflow capacity before the deadline is already tight, not after.