Expansion and upsell. Two items on the shelf.

What expansion actually was

Our expansion revenue consisted of exactly two levers: plan upgrades and seat expansion. That was the whole menu, because in an SMB market that's often all you have. And it was smaller than the playbooks pretend — not a meaningful slice of revenue. The truth is simple: if you don't have additional products to sell, your expansion won't be that meaningful, no matter how well you run the motion.

Each lever had a ceiling we kept hitting. Seat expansion sounds easy until you remember who you sold in the first place — we'd usually already sold most or all of the sales team. So growing seats meant finding another sales team inside the company, or a team that wasn't sales at all. That's real work, not a usage curve that compounds on its own. Plan upgrades were the more likely path, but for roughly the first seven years of the business we only had one or two plans. There's not much of an upgrade ladder when the ladder has two rungs.

The grocery store with two items

Here's the picture I'd hand any founder thinking about NRR. Imagine your customer walks into your grocery store — a customer who already knows you, trusts you, and is ready to spend — and you have two items on the shelves: more seats, and an upgraded plan. That was us. We could have had three to five more products on those shelves to sell to the existing customer. We never quite got there.

That distinction matters, because most expansion advice assumes the problem is motion — better triggers, better playbooks, better comp plans. Sometimes the problem is inventory. And inventory is a product-strategy decision you make years before the expansion conversation ever happens. So ask early: what additional problems could you solve for your ICP? What could you sell to them once they're in the store? Think early and often about that NRR number — in year one, not year ten.

The three add-ons that should have existed

In retrospect, I wish we had developed at least three add-on solutions for ancillary problems in the CRM space: a de-duping product, a data-enrichment service, and a sales coaching product. Every one of those sits right next to the core job a CRM does, every one is a problem our customers visibly had, and every one would have been another tool in the success team's toolkit. The more tools in the toolkit for the success team, the better — we were just too limited with a plan upgrade as the only real conversation.

And here's the validation that stings a little: I believe the team at PipelineCRM did build the data-enrichment add-on after my time, and they're selling it now. The shelf space was always there. We just didn't stock it.

Your best expansion reps are your CSMs

Who should sell expansion? We answered this one the hard way. Our CSMs were responsible for expansion — they owned those numbers, the same way they owned churn. Over the years we ran a few experiments where we took a salesperson and had them drive expansion, both solo and in partnership with the CSMs. Those experiments mostly failed.

It sounds good on paper: dedicated hunters working the install base. In reality, it was awkward having someone involved in selling who wasn't involved in the relationship — someone wearing a pure sales hat walking into an account they didn't know. The customer feels the difference immediately.

This is the same one-owner logic that runs the renewal motion: the person who knows the account is the person who should be having the commercial conversation. Splitting relationship and revenue across two people manufactures the awkwardness, then asks the customer to sit through it.

How the motion actually ran

Mechanically, expansion happened three ways. The first was the quiet one: when a customer's sales team grew, their admins would simply add new seats to the account on their own. No conversation required — the product expanded with the org. The second was the deliberate one: in QBRs we'd ask about other teams in the business, and when the answer was yes, we added them to the account. The third was ambient — expansion conversations got triggered at almost any customer touchpoint, sometimes initiated by the customer, sometimes by our CSMs.

On the product side, we did some in-app messaging to market the next plan up, and we feature-gated a bit — but not as aggressively as we should have. That's an honest admission, not a humble-brag: a clearer ladder of gated value would have given the upgrade conversation more to stand on.

One aside on pricing, since it always comes up next to expansion: we raised prices rarely, and it didn't really cost us expansion revenue — and it won't cost you any, as long as you communicate clearly about the change. What investments you made, and why your product is worth more. The communication is the mechanism; the increase is just the number.

The expansion push that flopped

Not every attempt to widen the shelf works, and ours didn't. We had several expansion pushes flop over the years; the one worth dissecting is the account-relationship feature we built to try to grow seats on the customer's account-management team — pulling a second team into the product beyond sales. It largely flopped, for two reasons that are worth separating: the feature was poorly implemented, and I'm not sure the pain point was strong in our customer base to begin with.

That second reason is the one to learn from. The three add-ons I listed earlier — de-duping, enrichment, coaching — all attack pain our customers demonstrably had. The account-relationship feature attacked pain we hoped they had. Expansion products only work when they solve a real adjacent problem for the customer who's already in the store; build for the pain you've seen in the support queue and the QBRs, not the pain that would be convenient for your NRR.