X
The Sales Nerd
GTM Framework
The exact lifecycle, pipeline, and attribution model we use to design scalable revenue systems.
X
.png)
Most companies don’t intentionally decide to ignore expansion. In fact, almost every leadership team will say expansion is a top priority. Net retention is celebrated. Expansion revenue shows up in board decks. Everyone agrees it matters.
Yet when you look inside the CRM at how expansion is actually represented, it becomes clear that most organizations don’t truly have an expansion funnel at all.
What they usually have is renewals, some ad hoc upsell activity, and a handful of sales-driven opportunities that appear when an account executive decides something looks promising. There is rarely a consistent lifecycle, rarely a shared definition of what qualifies as expansion demand, and almost never a reliable way to measure how much expansion interest exists before a salesperson gets involved.
This gap exists because of the order in which companies naturally build their systems.
First comes new business. The company is trying to survive, so everything revolves around acquiring customers. Lead stages, MQL definitions, pipeline stages, routing, and attribution are all designed around net-new acquisition.
Next comes customer support and customer success. The focus shifts to onboarding, ticketing, renewals, and account health. Tools get layered in. Fields get added. Automation grows.
Only later does expansion become a serious strategic focus.
By the time that happens, the CRM architecture is already committed. Core objects exist. Lifecycles are defined. Automation chains are fragile but relied upon. Reports are deeply embedded in leadership workflows. The roads are paved.
So when leadership finally says, “We need to focus on expansion,” the system itself quietly pushes back. Not maliciously, but structurally.
Most CRMs were never designed to understand expansion demand in the same way they understand new business demand. They don’t have a native concept of an expansion-qualified lead. They don’t have expansion lifecycle stages. They assume opportunities are created by sales, not by downstream qualification from marketing, product, or customer success.
As a result, expansion signals live outside the system of record.
- They live in product usage dashboards.
- They live in support tickets.
- They live in CS notes.
- They live in Slack threads and meetings.
Some of those signals eventually turn into opportunities, but only after a human decides to act. Everything before that moment is invisible.
And invisible demand cannot be measured, optimized, or scaled.
This is why expansion so often feels “hard,” even for companies with great products and strong customer relationships. The problem isn’t motivation. It isn’t even strategy.
It’s architecture.
A real expansion funnel does not start when a salesperson opens an opportunity.
It starts earlier, at the moment the business identifies a meaningful expansion signal.
That signal might come from marketing engagement, product behavior, customer success validation, or even automated scoring models. But regardless of source, the system must be able to record that signal, classify it, and move it through defined stages toward pipeline.
At a minimum, a company with an expansion funnel can answer:
If your CRM cannot answer those questions, you don’t have an expansion funnel. You have anecdotal expansion.
Not every organization needs the same level of sophistication on day one. There is a natural progression. What matters is understanding where you are and what you’re optimizing for.
Below are three common maturity levels.
At the most basic level, the goal is visibility.
You introduce a small set of fields on the Contact record that capture expansion-related information. For example:
When an expansion opportunity is eventually created, those values are copied from the Contact onto the Opportunity.
This approach creates a simple audit trail. You can begin to see which opportunities had expansion interest beforehand and where that interest originated.
The upside is that this is lightweight and minimally disruptive. You don’t need to redesign lifecycles or overhaul opportunity creation.
The downside is that expansion is still fundamentally sales-driven. Marketing, product, and CS can influence expansion, but they don’t truly generate pipeline inside the system. You gain attribution, but not a funnel.
This is a solid starting point, but it should be viewed as a stepping stone.
The next level is acknowledging that expansion deserves to exist inside your lifecycle model.
Instead of lifecycle stages being strictly new-business oriented, you introduce expansion-aware stages such as:
You also allow opportunities to be created from more than one place. A qualified expansion contact can create an opportunity. A contract or subscription amendment can create an opportunity. Sales is still involved, but they are no longer the only entry point.
Contact status and lifecycle stages are automatically updated based on defined qualification rules rather than manual edits.
This approach treats expansion as a real motion, not a side effect.However, most companies at this stage still only create opportunities once sales has engaged. Expansion demand that never gets picked up remains invisible.
You have a better funnel, but it still starts late.
The highest-maturity model flips a long-standing assumption: opportunities do not only exist because sales created them.
They exist because qualified demand exists.
In this model, the company defines what a Qualified Expansion Lead actually is. For example:
When one of these conditions is met, the system automatically creates an Expansion Opportunity and places it into a pre-pipeline or “Expansion Qualified” stage.
The opportunity is sourced to the originating team (marketing, product, CS). Ownership is assigned via routing rules. Sales now works opportunities that already exist rather than deciding when something deserves to exist.
This unlocks something powerful: true top-of-funnel expansion reporting.
You can see how much expansion demand is created, how much converts to pipeline, how long it takes, and where it dies.
Expansion becomes measurable.
Measurable becomes optimizable.
Optimizable becomes scalable.
For years, companies have slowly accepted that new business opportunities can be created by systems and qualification logic, not only by humans.
Expansion often hasn’t made that leap yet.
As long as expansion opportunities only appear when a salesperson manually creates them, your funnel will always start too late.
And as long as your funnel starts too late, expansion will always feel unpredictable.
Most companies did not “forget” to build expansion funnels.
They built CRMs that structurally excluded expansion.
That’s understandable. It’s common. But it’s also fixable.
The earlier you make expansion a first-class citizen in your architecture, the less painful it is. The longer you wait, the more expensive it becomes to reroute those paved roads.
Ask your CRM one question:
“How many expansion-qualified leads did we generate last month?”
If the answer is “we don’t track that,” you don’t have an expansion funnel.
You have renewals and hope.
And hope is not a strategy.
