Making Peak Demand Capacity Calls in Operations

11 ownersRick Elmore, Louis Ducruet, Nirmal Gyanwali, Joe Spisak and 7 more

Choose Overtime for Brief Spikes

When demand surges at Simply Noted, my default is overtime first, temporary staff second, and turning away low value work as a last resort. I almost never build backlog intentionally because our customers expect fast turnaround on handwritten notes, especially in real estate and insurance where timing drives results.

The rule of thumb I use is simple: if the surge looks like it will last less than two weeks, I run overtime. My team knows the product inside out and quality stays consistent. Overtime is expensive hourly but cheap compared to onboarding temps who do not understand our robotic handwriting machines or quality standards.

If the surge extends past two weeks, I bring in temporary help for non technical roles like packaging, quality checks, and shipping. I never put temps on machine operation or customer communication. Those areas require too much tribal knowledge and mistakes are costly.

Turning away work only happens when we are genuinely capacity constrained on machine time and I cannot add shifts. When that happens, I prioritize by customer lifetime value. A one time order for 50 cards gets pushed back before a recurring client who sends 500 cards monthly. I am transparent about it too. I call the smaller customer directly, explain the delay, and offer a small discount for patience. Most people respect honesty.

The biggest mistake I made early on was trying to say yes to everything during a holiday surge. Quality dropped, fulfillment times stretched, and I lost two recurring clients over it. Now I would rather turn away 10 small orders than risk damaging relationships with my core accounts.

Rick Elmore, Founder/CEO, Simply Noted (simplynoted.com)

Judge Permanence Before You Commit

Louis DucruetFounder and CEO, Eprezto

The rule of thumb I use when demand surges is to ask whether the spike is temporary or structural, because that single distinction decides everything else.

The instinct is to react to the surge in front of you, throw overtime or temp staff at it, and feel productive. The danger is committing permanent capacity to a temporary spike, or burning out your team on a surge that turns out to be the new normal and needed a real hire.

So I sort first by permanence. If the surge is short and reversible, overtime or building a little backlog is fine, you absorb it without changing your cost base. If it looks structural, the answer is different, you address it with a lasting solution rather than patching it, because patching a permanent problem just makes it recur. The way I separate the two is to run the cheapest short test of the assumption before committing, the same way we decide any build-or-buy question: do not bet permanent resources until you know the demand is permanent.

The other half of the rule is protecting what compounds. When capacity is tight, I do not spread it evenly. I protect the work that builds on itself and I am willing to turn away low-value work that only produces once, because saying yes to everything is how the most important thing falls behind. Turning away low-value work in a peak is not a failure, it is focus.

A related instinct that serves us: when volume strains the team, the better long-term move is often removing the reason for the work rather than adding hands to do it. Automating or simplifying the thing causing the surge beats staffing up to survive it.

The honest part is that judging temporary versus structural is a guess, so I make the cheap, reversible move while I gather evidence, and commit permanent capacity only once.

My advice is to decide by permanence first, protect compounding work, and test before you commit.

Decline Bad Fits and Guard Retainers

Nirmal GyanwaliFounder & CEO, WP Creative

When demand spikes, the first lever I pull is turning away low-value work, well before I'd ever pile overtime on the team. Burning out good people to service a bad-fit rush job is a terrible trade, because you lose the staff long after the busy patch ends.
My rule of thumb is to protect the retainer clients and the team's sanity first, then decide everything else. In our last peak we got asked to take on a big one-off with a brutal deadline, and I said no, because saying yes meant my existing clients got a worse month and my team got a worse fortnight.
We built a short backlog for the good-fit work instead and brought in a trusted freelancer for overflow. Protect quality and your people, and the right work waits for you.

Use a 72 Hour Rule

Joe SpisakCEO, Fulfill.com

Last December, one of our Fulfill.com partner 3PLs faced a brutal choice: a major skincare brand was shipping 4x normal volume while their second-biggest client launched a flash sale. They couldn't staff up fast enough to handle both without breaking promises.

Here's what they did that surprised me. They called the smaller client and said "We can fulfill your sale orders, but delivery will slip three days, or we can route overflow to our sister facility two states away for an extra dollar per box." The client picked the sister facility. Crisis solved, and they actually strengthened the relationship by being honest upfront.

When I ran my fulfillment operation, I learned this the painful way during our first Black Friday. We threw bodies at the problem, paid double overtime, and still built a five-day backlog. Our labor costs spiked 340% that month. Total disaster. The next year we got smarter.

My rule became the 72-hour test: if we can't clear new volume within 72 hours using reasonable overtime (time and a half, not double), we immediately activate temporary staff OR we get on the phone with clients to negotiate delayed ship dates. We never turned away work completely, but we absolutely tiered it. High-value clients with good margins got priority. Low-margin accounts that demanded two-day SLAs during peak? We renegotiated terms or suggested they split volume with a backup 3PL.

The math is simple. Temporary staff cost us about 30% more than regular employees when you factor in agency fees and training waste. Overtime ran 50-100% premium. But a backlog? That costs you in chargebacks, customer service nightmares, and reputation damage that takes years to repair.

The brands that win peak season are the ones planning this conversation in August, not November. They're asking their 3PL "what's your surge capacity protocol" and building backup relationships before they desperately need them. At Fulfill.com, we push brands to have a secondary 3PL on standby just for Q4. Redundancy isn't expensive. Scrambling is.

Prune Low Margin Distractions Early

Rebecca RushtonFounder, Blister Prevention

When demand for our blister kits surged during the peak ultra-marathon and hiking seasons, I used to try and fulfill every single order by working myself and my core team into the ground with relentless overtime. That quickly led to clinical burnout and packaging errors because packing hydrocolloids and gel protectors requires absolute precision.

My rule of thumb now is to use immediate capacity constraints to ruthlessly cull low-value, high-maintenance work before making any operational adjustments. In our last seasonal peak, instead of hiring temporary staff who don't understand our specialized inventory or paying costly overtime, I chose to completely turn away small, ad-hoc retail orders that required custom handling. This cleared the decks, allowing our core team to focus entirely on high-margin, streamlined wholesale fulfillment for our main pharmacy channels.

If you are facing a massive demand bottleneck, do not automatically look to increase labor. Use the pressure to audit your client list, chop out the low-margin clutter that slows down your production line, and prioritize the accounts that keep your business profitable.

Honor Promises and Defer Secondary Channels

Ben FrederickFounder, Dr. Frederick's Original

During our last peak, I filtered every order in the queue with one question. Can we fulfill this at full quality within our promised window? If the answer was yes, it stayed on the schedule. Everything else got sorted by channel priority.
I held my fulfillment capacity steady, let a few lower-priority wholesale orders slide into backlog, and kept my direct-to-consumer commitments locked in. The wholesale accounts got honest timelines upfront, and they were fine with it because they knew exactly when to expect delivery.
Overtime came into play only for my core team on specific days when we could maintain quality checks. I kept those changes targeted so the team stayed sharp through the whole run. Temps were off the table because the ramp-up time exceeded the surge itself, which we expected to cool within a few weeks.
The volume I passed on was all marginal work where fulfillment pressure would have put my core orders at risk. I protected the commitments that mattered to my repeat buyers and gave clear answers to everyone else.

Automate Bottlenecks and Welcome All Traffic

Runbo LiCEO, Magic Hour AI

I'm Runbo Li, Co-founder & CEO at Magic Hour.
The answer is simple: you never turn away demand. You engineer your system so surge capacity is the default state, not an emergency protocol. That's the whole point of building with AI at the core of your operations.
David and I run a platform with millions of users as a two-person team. We don't have the luxury of "hiring temp staff" or "building backlog." When we hit a demand spike, the question isn't who do we call, it's what do we automate next. I call this "surge-proofing through architecture." You design every workflow assuming 10x volume could hit tomorrow.
Here's a concrete example. Earlier this year we saw a massive spike in usage after a viral social moment drove hundreds of thousands of new users to the platform in a matter of days. Our infrastructure auto-scaled on the compute side, but our support queue exploded. Instead of hiring a temp support team, we spent 48 hours building an AI-powered support system that could handle 90% of inbound questions without a human touch. That system still runs today. The spike forced a permanent upgrade.
My rule of thumb: if a demand surge exposes a bottleneck, that bottleneck was already a liability. The surge just made it visible. So I never treat peaks as temporary problems requiring temporary solutions. Every spike is a stress test that reveals where your next automation investment should go.
As for "turning away low value work," I reject the framing. If someone wants to use your product, that's signal. The real question is whether your cost to serve them is low enough to make it worthwhile. When you automate aggressively, your marginal cost per user drops so low that almost no work is "low value" anymore.
The companies that staff up and staff down with every demand cycle are playing a game they'll always lose. The ones that treat every surge as a permanent architecture problem are the ones that compound.

Scale with Thresholds and Safeguard Judgment

Pranjal KukrejaCEO, Optima Bags

At Optima Bags, we experience significant demand surges around Q4 gifting season and travel product peaks, and the decision framework we've settled on for handling them uses two thresholds.

Below 20% above baseline capacity: we use overtime and flex scheduling with our existing team. The team knows the product, quality control stays tight, and the premium cost is manageable relative to the revenue opportunity.

Between 20-40% above baseline: we bring in temporary warehouse staff for pick-and-pack — the most modular, trainable part of our operation. We don't use temps for anything requiring product knowledge, quality judgment, or customer interaction. The temp boundary is strict: if the task requires judgment, it stays with the core team.

Above 40% above baseline (which has happened once): we build controlled backlog for new wholesale orders while protecting all existing committed DTC orders. We communicate estimated delays proactively and offer a small discount for customers willing to wait. We don't turn away business entirely — we manage expectations and sequence fulfillment.

The rule we've learned not to violate: never use temps or overtime to rush orders that require quality verification. The cost of a defective batch reaching customers far exceeds the revenue of filling the order on time. In a recent peak, we had a production run from a new supplier arrive right at surge time. We held that inventory for an extra 4 days of QC review rather than shipping immediately. We shipped one day late on those orders. We had zero returns from that batch.

— Pranjal Kukreja, CEO, Optima Bags

Extend Timelines and Lead with Candor

Hugo GomezCEO, Abogados NOW

I widen the response window before bringing in outside help. I've spent years earning certain client relationships, and the cultural context behind how we work takes time to transfer to a contractor.

So when volume spikes, I extend turnaround times, tell clients exactly how long they'll wait and why, and give them something useful in the meantime, even if it's just a well-timed follow-up call. I keep the communication close so the slower pace feels deliberate.

During one recent busy quarter, I could have justified bringing on a contractor, but I kept the work in-house and managed the cadence myself. A few clients told me they appreciated the transparency about timelines.

Set a Throughput Limit and Cap Bookings

Carolyn VasquezFounder, Ready Rental Cleaning

The rule that drives every surge decision is a quality floor: past 3 turnovers per cleaner per day, our photo-defect rate doubles. That number came from tracking our own work, not instinct. Once a cleaner goes past that in the same day, they start missing corners, bathroom grout, the inside of the microwave, the smell test on entry. In vacation-rental work, a bad guest review from a preventable miss can cost a property manager multiple future bookings. When a holiday weekend fills up, the math is simple. I can add cleaners or I can cap bookings, but I can't push the same crew past that threshold. Temps are an option. But trained temps who know how to spot a mildewed shower liner or count paper goods take time to run reliably on their own. For a same-weekend surge, I cap, waitlist, and offer a priority slot the following weekend. For planned surges, I start recruiting extra staff weeks out. The work you turn away because you don't have the crew is always better than the work you damage because you pushed too hard.

Grow Only as Fast as Feedback

Jeremy MaherCo-Owner, Phoenix Home Remodeling

We focus on the option that protects trust as we grow. A backlog is not always bad when we set clear expectations and keep work organized. We may turn away low value work to protect time for better fit clients. We use overtime with care because tired teams can meet output goals but harm quality, morale, and predictability.

We follow one rule during peak periods. We do not add capacity faster than the system can handle feedback. If communication loops, planning checkpoints, or accountability routines slip, then growth becomes too costly. In a recent peak, we chose to hold our line and avoid adding work that would create chaos for the team and clients.

Q&A

Making Peak Demand Capacity Calls in Operations

Q&A

Making Peak Demand Capacity Calls in Operations

Choose Overtime for Brief Spikes

Judge Permanence Before You Commit

Decline Bad Fits and Guard Retainers

Use a 72 Hour Rule

Prune Low Margin Distractions Early

Honor Promises and Defer Secondary Channels

Automate Bottlenecks and Welcome All Traffic

Scale with Thresholds and Safeguard Judgment

Extend Timelines and Lead with Candor

Set a Throughput Limit and Cap Bookings

Grow Only as Fast as Feedback

Related records

Standing brief