← enzosoler.com

The Outbound System That Helped Double Revenue

Targeting, process repair, CRM workflows, conversion lifts, and the operating cadence behind repeatable B2B SaaS pipeline.

Between FullStack Labs and Bluelight Consulting, I spent four years building and fixing outbound revenue systems. At FullStack, I built outbound from zero — no process, no playbook, no pipeline. At Bluelight, I inherited a broken system and rebuilt it until it tripled conversion and doubled annual revenue.

This isn't a growth hack article. This is what I actually did, how it worked, and what I learned about the mechanics of repeatable pipeline in B2B SaaS.

The State of Things When I Arrived

FullStack Labs (2021)

When I joined FullStack Labs as an Account Executive, there was no structured outbound function. Leads came in through the website and referrals. There was no ICP definition, no sequencing tool, no SDR team, no pipeline reporting beyond a spreadsheet.

I was hired to sell. I realized the first job was to build the system that would make selling possible at scale.

Bluelight Consulting (2023)

Two years later, I joined Bluelight as Head of Sales. The situation was different but the problem was similar: the outbound motion existed, but it leaked. Leads entered the funnel and disappeared. Conversion rates were low. The CRM was a graveyard of unworked opportunities. No one trusted the pipeline numbers because the data was inconsistent.

Step 1: Define Who You're Actually Selling To

Most outbound problems start with targeting. You can have perfect messaging, perfect cadence, perfect tooling — but if you're reaching the wrong people, none of it matters.

At both companies, I started with the same exercise: analyze every closed deal from the past 18 months. Not the pipeline. The closes. I looked at:

• Company size — revenue range, employee count, funding stage
• Industry vertical — which industries closed fastest and expanded most
• Buyer persona — who actually signed? CTO? VP Eng? CEO? Product lead?
• Deal trigger — what was the event that made them buy now? (new funding, team scaling, migration, compliance deadline)
• Deal velocity — how long from first touch to close? Which segments moved fastest?

At Bluelight, this analysis revealed that 70% of revenue came from Series A-C startups with 50-200 employees who needed to scale engineering capacity fast — usually after a funding round. The ICP wasn't "any tech company." It was a specific company at a specific moment.

The ICP is not a persona slide. It's a targeting filter. If your SDR can't use it to build a list in Apollo in under 5 minutes, it's not specific enough.

Step 2: Fix the CRM Before You Fix the Outreach

The most underrated step in outbound repair is CRM hygiene. At Bluelight, I spent the first three weeks doing nothing but cleaning HubSpot.

• Removed 4,000+ duplicate contacts
• Standardized lifecycle stages (Lead → MQL → SQL → Opportunity → Customer)
• Built required fields on deal creation: source, ICP match score, expected close date, decision-maker confirmed
• Created pipeline stages with clear exit criteria — no deal moves forward without a next step scheduled
• Set up automated alerts: stale deals (no activity in 7 days), missing next steps, overdue tasks

This wasn't glamorous work. But it meant that when I later looked at pipeline reports, the numbers meant something. You can't optimize what you can't measure, and you can't measure what's dirty.

Step 3: Build the Sequencing Engine

At FullStack, I built the outbound stack from scratch:

• Apollo — prospecting and enrichment. ICP filters directly from the analysis above
• Instantly — email warm-up and sending infrastructure. Multiple domains, rotation, deliverability monitoring
• LinkedIn Sales Navigator — manual high-value outreach for strategic accounts. Not automated — personal, researched, specific
• HubSpot — CRM, deal tracking, reporting, task automation

The sequence structure that worked consistently across both companies:

1. Day 1 — personalized email. Reference a specific trigger (funding round, job posting, tech stack signal). One ask: 15-minute call
2. Day 3 — LinkedIn connection request with a short note (not a pitch)
3. Day 5 — second email. Different angle — share a relevant case study or insight, not a follow-up to the first email
4. Day 8 — LinkedIn message (only if connected). Brief, direct
5. Day 12 — breakup email. "Seems like timing isn't right. No hard feelings. Here's my calendar if that changes."

The breakup email consistently had the highest reply rate. People respond to the removal of pressure.

Step 4: Build the Team

At FullStack, I went from solo AE to leading a team of SDRs. The hiring criteria that mattered:

• Coachability over experience. An SDR who listens, adjusts, and iterates will outperform a "veteran" who runs the same playbook everywhere
• Writing quality. Outbound is a writing job. If the candidate can't write a clear, concise cold email in the interview, they won't write one on the job
• Research instinct. The best SDRs spend 5 minutes researching before writing. The worst send the same template to everyone

I ran weekly pipeline reviews, call listening sessions, and A/B test readouts. Every SDR knew their numbers: emails sent, reply rate, positive reply rate, meetings booked, show rate, conversion to opportunity.

The result at FullStack: hundreds of qualified meetings in under a year, dozens of net-new enterprise clients signed.

Step 5: The Conversion Fix at Bluelight

At Bluelight, the outbound system generated leads. The problem was downstream — leads weren't converting to revenue. The diagnosis:

• No discovery framework. Sales calls were product demos, not needs assessments. We were showing features to people who hadn't articulated their problem
• Proposal delays. Proposals took 5-7 days to deliver after a call. By then, momentum was dead
• No objection handling playbook. Each rep handled objections differently. Pricing pushback, timeline concerns, internal stakeholder blockers — all improvised
• No win/loss analysis. Deals closed or died and nobody asked why

The fixes:

• Built a structured discovery call framework: situation, pain, impact, timeline, decision process. No demo until pain is confirmed
• Created proposal templates that could be customized and sent within 24 hours of a discovery call
• Documented the top 15 objections and tested response frameworks. Shared the best performers across the team
• Instituted monthly win/loss reviews — recorded calls, analyzed patterns, fed insights back into messaging and targeting

The result: 3x conversion lift from lead to close. Doubled annual revenue. Doubled the client base.

The Operating Cadence

The system isn't any single tool or technique. It's the cadence — the rhythm of activities that keeps the pipeline healthy:

• Daily: SDR activity metrics review, reply triage, pipeline movement
• Weekly: Team pipeline review, call listening, sequence performance, A/B results
• Monthly: Win/loss analysis, ICP refinement, messaging refresh, territory rebalancing
• Quarterly: Full funnel audit, conversion rate analysis, comp/incentive review

The companies that grow consistently aren't doing something magical. They're doing the basics on a rhythm and measuring everything.

What I Took Away

Outbound revenue isn't about tricks. It's about process, targeting, measurement, and iteration. The companies that fail at outbound usually fail at one of those four things — often targeting or measurement.

The meta-lesson: building revenue systems is not that different from building software systems. You define requirements (ICP), build the architecture (CRM + tools), write the logic (sequences + messaging), test it (A/B + metrics), deploy it (SDR team), and iterate based on production data (win/loss analysis).

That's probably why doing both — selling and building — feels like the same job to me.