I’m going to tell you something that might sound crazy. Hiring more salespeople can actually kill your revenue. I learned this the hard way. It cost me dearly, but it also led to a breakthrough that completely changed how I build companies.
Most founders, especially first-timers, are obsessed with a single, fatally flawed equation: more reps = more revenue. It seems logical, right? You want to grow, so you hire more people to sell. I get it. I was that founder. At my first company, MovieLaLa, and then again at RemoteTeam, I fell into the same trap. We’d raise a round of funding, and the first thing I’d do is greenlight a bunch of new sales hires. And for a while, it felt like progress. The team was growing, the office was buzzing, and our burn rate was… well, let’s just say it was also growing. Fast.
But the revenue? It sputtered. It wasn’t scaling at the same pace as our team. We were running faster and faster just to stay in the same place. It was a nightmare, and it was all my fault.
The Scaling Fallacy: My Big, Expensive Mistake
At RemoteTeam, we had a great product that was solving a real problem for a new generation of remote companies. We had happy customers and a ton of inbound interest. The pressure to scale was immense, both from our investors and from my own ambition. So, I did what I thought you were supposed to do: I hired a bigger sales team.
We went from two reps to ten in about six months. On paper, it looked like we were crushing it. We had a proper sales floor, a fancy CRM, and all the tools that a “real” company is supposed to have. But our pipeline was a mess. The reps were stepping on each other’s toes, chasing the same low-quality leads, and spending most of their time on demos that went nowhere. Morale was plummeting, and our customer acquisition cost was through the roof.
I remember one particularly brutal board meeting. We had missed our quarterly target by a mile. I tried to explain it away, talking about ramp-up time for the new reps and a competitive market. But I knew those were just excuses. The truth was, I had built a sales engine that was all gas and no steering. We were generating a ton of activity, but it was unfocused and inefficient. We were burning cash and churning through leads, and I had no idea how to fix it.
That night, I went home feeling completely defeated. I had raised millions of dollars from investors who trusted me, and I was letting them down. I had a team of talented people who were looking to me for leadership, and I was failing them. I seriously considered firing the entire sales team and starting over. It was one of the lowest points in my career.
The Epiphany in the Data
I couldn’t sleep that night. I just kept replaying that board meeting in my head. Around 3 AM, I gave up on sleep and opened my laptop. I started digging into our CRM data, looking for some kind of answer. I wasn’t even sure what I was looking for, but I had to do something.
I spent hours exporting data, building pivot tables, and staring at spreadsheets until my eyes blurred. And then, slowly, a pattern started to emerge. A tiny fraction of our leads were converting at a much higher rate than the rest. These weren’t necessarily the biggest companies or the ones with the most impressive names. They were the ones that were taking specific actions on our website, engaging with our content in a certain way, and asking particular questions during the demo.
It was like a lightbulb went off in my head. The problem wasn’t our reps. The problem was our process. We were treating every lead as equal, when in reality, they were anything but. We were wasting our best salespeople on tire-kickers and letting our hottest prospects go cold.
That’s when I discovered the concept of deal scoring. It wasn’t a new idea, but the way most companies were doing it seemed overly complicated and academic. They were using dozens of data points and complex algorithms that no one on the sales team actually understood. I wanted something simpler, something that was based on real buying signals and that my team could actually use.
So, I decided to build my own deal scoring framework from scratch. It was a counterintuitive approach, but it was based on the actual data from our most successful customers. And it changed everything.
The 3x Pipeline Framework: My Counterintuitive Deal Scoring System
Our framework was built on a simple but powerful idea: a lead’s behavior is a much better predictor of their intent to buy than their demographics. We stopped obsessing over company size, industry, and job titles, and started focusing on what our prospects were actually doing.
Here’s how it worked. We assigned points to every lead based on a handful of key actions. It was a simple system, but it was incredibly effective. Here are the core components:
High-Intent Website Actions (25 points): We identified a few key pages on our website that were strong indicators of buying intent. For us, it was the pricing page, the case studies page, and the integration page. If a lead visited one of these pages, they got 25 points. Simple.
Content Engagement (15 points): We had a few key pieces of content—a webinar on remote team management, a whitepaper on payroll automation—that were highly correlated with closed deals. If a lead downloaded one of these, they got 15 points.
Demo Request Source (10 points): We found that leads who requested a demo through our organic search traffic were much more likely to close than leads who came from paid ads. So, we gave them an extra 10 points.
Product-Specific Questions (20 points): During the demo, we trained our reps to listen for specific questions about our product. Questions about our API, our security protocols, or our onboarding process were all strong buying signals. If a prospect asked one of these questions, the rep would manually add 20 points to their score.
That was it. No complex algorithms, no machine learning, just a simple, points-based system that was easy for everyone to understand. The beauty of this system was its simplicity. Our reps could see at a glance which leads were hot and which were not. They stopped wasting time on low-scoring leads and started focusing their energy on the prospects who were most likely to buy.
The Results Don’t Lie
The impact was immediate and dramatic. Within the first quarter of implementing our new deal scoring system, our pipeline tripled. Let me say that again: we 3x-ed our qualified pipeline without hiring a single new salesperson.
But it wasn’t just the size of the pipeline that changed. The quality of our deals went through the roof. Our sales cycle shortened by 30%, and our average deal size increased by 50%. Our reps were happier and more motivated because they were finally spending their time on deals that they could actually win.
I remember one deal in particular. It was a mid-sized tech company that had been in our system for months. They had a low score, so our reps had been ignoring them. But then, one day, their score suddenly jumped. They had visited our pricing page, downloaded our security whitepaper, and then requested a demo. Our top rep got an alert, jumped on the phone with them, and closed the deal in less than a week. That one deal paid for the entire cost of our CRM for the year.
That’s when I knew we had cracked the code. We had built a system that was not only scalable but also incredibly efficient. We were no longer just throwing bodies at the problem. We were using data to work smarter, not just harder.
How to Avoid My Mistake: Your Action Plan
You don’t have to make the same mistakes I did. You can build a scalable, efficient sales engine from day one. Here’s how:
Resist the Urge to Hire: The next time you feel the pressure to scale your sales team, take a deep breath and look at your data first. Are you really getting the most out of your existing team? Or are you just masking a process problem with more headcount?
Identify Your Buying Signals: Dig into your CRM and find out what your best customers have in common. What actions did they take before they bought from you? What pages did they visit? What content did they download? These are your buying signals.
Build a Simple Scoring System: Don’t overcomplicate it. Start with a handful of key buying signals and assign points to each one. The goal is to create a system that is easy for your team to understand and use.
Automate and Iterate: Use your CRM to automate the scoring process as much as possible. Set up alerts so that your reps know immediately when a lead’s score changes. And don’t be afraid to iterate. Your buying signals will change over time, so you need to constantly review and update your scoring system.
Stop Selling, Start Guiding
The biggest lesson I learned from this whole experience is that the role of sales has changed. It’s no longer about convincing people to buy your product. It’s about guiding them through the buying process. Your job is to identify the prospects who are already on the path to purchase and help them get to the finish line.
Deal scoring is the compass that shows you the way. It helps you separate the signal from the noise and focus your energy on the deals that matter. It’s the difference between running in circles and running a race that you can actually win.
So, before you go out and hire a bunch of new salespeople, take a hard look at your process. Are you setting them up for success? Or are you just setting them up to fail? The answer to that question could be the difference between building a company that sputters and one that scales to the moon.
Frequently Asked Questions
Do all experts agree with this view?
No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.
How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.