Two years ago, our sales pipeline looked like a business school case study. A handful of enterprise logos at the top, long sales cycles, and the quiet assumption that landing one of those names would change everything.
We were wrong.
The moment that broke the pattern was not a lost deal. It was a quarterly review where we finally looked at the right numbers.
Chasing large accounts felt rational. Bigger contracts, bigger annual commitments, names you could put on a website. Every founder knows the gravitational pull. A recognizable logo on your customer page feels like proof that you belong.
But here is what we weren't measuring: the cost of every dollar those accounts generated.
Our largest prospect at the time wanted custom reporting, a dedicated integration window every sprint, and a security review process that took four months before a single user logged in. We said yes to all of it because the contract number was large enough to justify anything.
Meanwhile, a cohort of smaller accounts — teams of ten to fifty — were signing up, onboarding themselves within days, and quietly adding seats every month.
When we broke revenue down by cost-to-serve, the picture inverted.
Our marquee accounts generated high top-line numbers but consumed disproportionate support hours, required one-off customization, and had expansion rates close to zero. They bought what they needed on day one and never grew.
The smaller accounts behaved differently. They started with a narrow use case, proved value inside one team, and spread. Their expansion rate — net new revenue from existing accounts — was several multiples higher. Support load per dollar was a fraction of what the enterprise accounts required.
One account that started as a five-seat deal was, twelve months later, our third-largest by revenue. No custom work. No dedicated integration sprints. They just kept adding teams.
The hardest part was not the math. It was the decision that followed.
We had a late-stage conversation with a company whose name alone would have opened doors. They wanted changes to our data residency model, a bespoke SLA, and a contractual commitment to a feature roadmap that would have consumed our engineering team for two quarters.
We said no.
It was not comfortable. Our board had questions. Our sales lead had questions. But we had seen the pattern clearly enough to trust it: accounts that require you to reshape your product before they buy will require you to reshape it again after they buy. The cost never ends. It compounds.
After that decision, we changed how we evaluated pipeline. Instead of sorting by contract value, we qualified for fit.
Fit meant: Can this account onboard without custom work? Does their use case align with what the product already does well? Is there evidence of internal expansion potential — multiple teams, multiple geographies, growing headcount?
We stopped asking "How big is this account?" and started asking "How fast could this account grow inside our product without us bending the roadmap?"
The shift was uncomfortable for about one quarter. Pipeline value dropped on paper because we disqualified several large prospects early. But within six months, net revenue retention from the remaining accounts more than offset the gap. We were growing faster with fewer deals, each costing less to support.
Here is what surprised us most: the product got better.
When you build for accounts that fit, you invest engineering time in capabilities that benefit the entire customer base. When you build for a single enterprise buyer, you invest in features that serve one account and create maintenance burden for everyone.
Our roadmap became more coherent. Support volume per account dropped. The team spent less time on bespoke work and more time on problems that mattered broadly.
Saying no to size created room to say yes to speed.
If you are early and chasing large logos to prove legitimacy, we understand the instinct. We had it too.
But track the full cost. Measure expansion rate alongside contract value. Look at how much engineering and support time each account consumes per dollar of revenue. The accounts that grow inside your product without pulling your team sideways are the ones that compound.
Qualifying for fit is slower to show results on a pitch deck. It is faster to show results on a P&L.
The best customers we have today are not the biggest names. They are the ones who started small and never stopped growing.
Be the first to comment.
0 comments
Loading comments...