Between FullStack Labs and Bluelight Consulting I spent four years building and fixing outbound revenue systems. At FullStack I started from nothing: no process, no playbook, no pipeline. At Bluelight I inherited a system that leaked and rebuilt it until conversion tripled and annual revenue doubled.
This is what I did at each company, in the order I did it, and what I learned about repeatable pipeline in B2B SaaS.
What I walked into
FullStack Labs, 2021
When I joined FullStack Labs as an account executive there was no outbound function. Leads came from the website and referrals. There was no ICP definition, no sequencing tool and no SDR team, and pipeline reporting was a spreadsheet. I was hired to sell, and the first job turned out to be building the system that would make selling possible at any scale.
Bluelight Consulting, 2023
Two years later I joined Bluelight as head of sales. The outbound motion existed, but it leaked. Leads entered the funnel and disappeared, conversion was low, and the CRM was full of opportunities nobody had worked. No one trusted the pipeline numbers because the data behind them was inconsistent.
Step 1: work out who actually buys
Most outbound problems start with targeting. You can have good messaging, good cadence and good tooling, and if you’re reaching the wrong people none of it matters.
At both companies I started the same way: I went through every closed deal from the previous 18 months. Closed deals only, never pipeline. For each one I looked at company size (revenue, headcount, funding stage), industry, who signed (CTO, VP of engineering, CEO, product lead), what event made them buy right then (new funding, team growth, a migration, a compliance deadline), and how long it took from first touch to close.
At Bluelight that analysis showed 70% of revenue came from Series A to C startups with 50 to 200 employees that needed to add engineering capacity fast, usually right after a funding round. The ICP wasn’t “any tech company.” It was a specific kind of company at a specific moment.
An ICP is only useful as a filter. If your SDR can’t use it to build a list in Apollo in under five minutes, it isn’t specific enough.
Step 2: clean the CRM before touching the outreach
The most underrated step in fixing outbound is CRM hygiene. At Bluelight I spent my first three weeks doing nothing but cleaning HubSpot.
- I removed more than 4,000 duplicate contacts.
- I standardized the lifecycle stages: lead, MQL, SQL, opportunity, customer.
- I made four fields required when a deal is created: source, ICP match score, expected close date, and whether the decision maker was confirmed.
- I gave every pipeline stage an exit criterion. A deal couldn’t move forward without a next step on the calendar.
- I set up alerts for deals with no activity in seven days, deals with no next step, and overdue tasks.
None of it was glamorous. It meant that when I later read a pipeline report, the numbers meant something, which hadn’t been true of any report at Bluelight before that.
Step 3: build the sequencing stack
At FullStack I built the outbound stack from scratch. Apollo handled prospecting and enrichment, with ICP filters taken straight from the deal analysis. Instantly handled email warm-up and sending, across several domains with rotation and deliverability monitoring. LinkedIn Sales Navigator was for manual, researched outreach to strategic accounts, never automated. HubSpot held the CRM, deal tracking, reporting and task automation.
The sequence that worked at both companies ran twelve days.
- Day 1: a personalized email that references a specific trigger, such as a funding round, a job posting or a tech stack signal, with one ask, a 15-minute call.
- Day 3: a LinkedIn connection request with a short note and no pitch.
- Day 5: a second email from a different angle, sharing a relevant case study or insight. Never a “just following up.”
- Day 8: a LinkedIn message, only if they connected. Brief and direct.
- Day 12: the breakup email. “Seems like the timing isn’t right. No hard feelings. Here’s my calendar if that changes.”
The breakup email had the highest reply rate every time. People respond when the pressure comes off.
Step 4: hire the team
At FullStack I went from the only AE to leading a team of SDRs. When I hired, I weighted coachability over experience: an SDR who listens, adjusts and tries again beats a veteran who runs the same playbook everywhere. I also made every candidate write a cold email in the interview, because outbound is a writing job, and someone who can’t write a clear, short one under a bit of pressure won’t write one on a Tuesday afternoon either. The last filter was research habit. The best SDRs I worked with spent five minutes reading about a prospect before writing. The worst sent the same template to everyone.
I ran weekly pipeline reviews, call listening sessions and A/B test readouts. Every SDR knew their own numbers: emails sent, reply rate, positive reply rate, meetings booked, show rate and conversion to opportunity.
In under a year at FullStack that produced hundreds of qualified meetings and dozens of new enterprise clients.
Step 5: fix conversion at Bluelight
At Bluelight the outbound system produced leads. The problem was downstream, where leads failed to turn into revenue, and when I listened to the recorded calls the reasons were plain.
Sales calls were product demos. We showed features to people who hadn’t yet said what their problem was. Proposals took five to seven days to arrive after a call, and by then the momentum was gone. Every rep handled objections differently, so pricing pushback, timeline worries and internal blockers were all improvised. And nobody asked why deals closed or died.
So I built a discovery call structure covering situation, pain, impact, timeline and decision process, with no demo until the pain was confirmed. I wrote proposal templates that could be customized and sent within 24 hours of a discovery call. I documented the fifteen most common objections, tested responses and shared the ones that worked across the team. And I started monthly win/loss reviews, with recorded calls, that fed back into messaging and targeting.
Lead-to-close conversion tripled. Annual revenue doubled, and so did the client base.
The cadence
The system was never one tool or technique. It was the rhythm of activities that kept the pipeline healthy.
- Daily: SDR activity metrics, 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 and incentive review.
Companies that grow steadily do the basics on a schedule and measure everything. There’s no trick in it.
What I took from it
Outbound comes down to process, targeting, measurement and iteration, and the companies that fail at it usually fail at targeting or measurement.
Building a revenue system turned out to be a lot like building software. You define requirements (the ICP), build the architecture (CRM and tools), write the logic (sequences and messaging), test it (A/B tests and metrics), deploy it (the SDR team) and iterate on production data (win/loss reviews). That’s probably why selling and building feel like the same job to me.