Yes. The services agreement is signed and dated March 2022 — program setup, two dedicated sales development representatives, a defined target market of roughly 3,000 companies, and a 30-days-written-notice termination clause. The termination call gave zero days of notice, which the client acknowledged on the call while apologizing. Growth Orbit's founder is happy to take questions about it, on any forum you like.

Why won't you name the client?

Two reasons. They never cleared their name for marketing use, and our rule is that named means permissioned — every named case on this site has it in writing. And second: publicly naming a company whose defining quote is 'we got more business than we could handle' seems like a poor way to thank them for the story.

What should anyone actually learn from this?

That pipeline capacity is a two-sided equation. A demand program has to be sized to the client's ability to absorb what it produces — sales capacity, delivery capacity, onboarding capacity. After this engagement, Growth Orbit got much more diligent about setting expectations for pipeline growth up front — and verifying, before a program starts, that the client is actually equipped to handle what it will produce. It's also part of why the system Growth Orbit runs today governs pacing instead of maximizing volume. Volume you can't process isn't pipeline; it's backlog with a deadline.

Did Growth Orbit enforce the contract terms?

No. The client apologized, explained honestly, and asked out. We released them from the agreement. Reluctantly — but you don't hold a drowning man to his notice period.

NOT OUR TYPICAL CASE STUDY · IDENTITY WITHHELD · CYBERSECURITY

The client broke the contract. To make the pipeline stop.

Every other case on this site ends with an acquisition, an exit, or a market mapped. This one ends with a client apologizing while terminating the agreement early — no notice, terms knowingly broken — because the pipeline-development program Growth Orbit built had buried them in more business than they could handle. We are contractually entitled to be annoyed about it. Mostly we tell the story.

TARGET MARKET BUILT~3,000 accounts

DEDICATED SDRS2

NOTICE REQUIRED30 days

NOTICE GIVEN0 days

THE SETUP

What did they buy?

A cybersecurity services firm came to Growth Orbit in early 2022 for pipeline development — the standard program, by the book: a playbook and messaging built for their buyers, a prospecting cadence, a defined target market of roughly 3,000 companies built to their ideal customer profile, and two dedicated SDRs working it daily. We got them into market and even supported their trade-show efforts. Nothing exotic. It just worked.

THE PROBLEM WE CAUSED

What happens when the pipeline outruns the company?

The call came without warning. The client's leader apologized, said he knew he was ending the agreement with no notice, knew he was breaking its terms — and then explained why: “I can't afford to continue, because it's just more business than we can handle.”

There is no graceful way to put this on a proof page: the program didn't fail, the client's capacity did. Sales, delivery, and onboarding could not absorb what the pipeline was producing, and the honest business decision was to turn off the tap. We released them from the agreement. Reluctantly.

THE LESSON

What did it teach us?

That demand is only half the equation. Pipeline a company cannot process isn't growth — it's backlog with a deadline, and it strains the very team it was meant to feed. The scoping question we now ask every client came directly from this engagement: how much pipeline can you actually handle, per month, with the team you have? It's also part of why the system Growth Orbit runs today is governed — pacing, volume, and targeting are controls to be set, not dials to be maxed. The goal was never the most pipeline. It was the right amount, aimed at the right market, at a rate the business can turn into revenue — run as a system.

Questions we'd ask too

The questions this story invites

Results may exceed capacity

Tell us how much pipeline you can actually handle.

We'll count your market, measure your coverage, and build to your absorption rate — not past it. Start with the coverage-gap analysis: read-only, two weeks to first finding.

Get your coverage gap