"I'm thrilled to commend Tom Slocum of SD Lab for his invaluable support in kickstarting our SaaS product sales. Tom's entrepreneurial expertise was pivotal in advising on the ideal tech stack and managing outreach. His contributions greatly enhanced our sales efforts."
Building an outbound engine from scratch
S44 is a lean early-stage automotive SaaS company. There was no outbound function to fix — there was nothing to fix, because there was nothing there yet. The work was to build the first version of an outbound engine and get a small team running it.
27 enterprise meetings
Proof point 01
Client engagement record
$100K+ pipeline
Proof point 02
Client engagement record
First outbound motion built and staffed
Proof point 03
Engagement deliverables
Report thesisWhen a lean early-stage team has no outbound function at all, the constraint is not effort — it is the absence of a defined target, a repeatable message and a calling motion someone actually owns.
- Build From Scratch
- Outbound System
- Pipeline
- Messaging
- Industry
- Automotive SaaS (early stage)
- Engagement
- Outbound engine build from scratch
- Dates
- Engagement dates not published
What was actually happening
S44 was selling into enterprise automotive buyers without a defined outbound function. Early conversations came from network, inbound interest and founder relationships. There was no documented target list, no shared message, no sequence and no owned calling motion — which meant new pipeline could not be created on demand, only waited for.
The published engagement record
Enterprise meetings across six months
Qualified pipeline recorded, not revenue
Build-from-scratch system: target list, messaging, sequence, call motion and weekly operating rhythm. Published outcomes are client-recorded and are not independently audited.
What we found
The gap was structural rather than behavioral. A lean team with limited hours cannot afford broad prospecting, so the first requirement was a narrow, defensible target definition and a message that earned an enterprise conversation. Everything else — sequencing, call structure, follow-up — depended on that foundation being set first.
No documented ICP or account list to work from.
Every outreach decision was made ad hoc, so nothing could be measured or repeated.
Messaging was product-led rather than built around the buyer's operating problem.
Enterprise buyers had no reason to take the meeting, regardless of channel or volume.
No calling motion or owner inside a very small team.
Outbound competed with every other priority and lost by default in any busy week.
What we built
- A narrow enterprise ICP and prioritized target account list
- Positioning and message framing built around the buyer's operating problem
- Outbound sequences across email and phone
- A cold-call structure and objection handling built for enterprise automotive buyers
- A weekly outbound cadence a lean team could actually sustain
- Meeting-setting and follow-up standards so booked conversations were prepared for
How the work ran
Build, run, review. Targeting and messaging were built with the team rather than delivered as a document, then run live against real accounts, then reviewed against what happened on the calls and adjusted the following week.
How the team operates now
S44 moved from having no outbound function to having a defined engine: a target list, a message, a sequence, a call motion and a weekly rhythm run by the team itself. The client engagement record documents 27 enterprise meetings and $100K+ in pipeline generated in connection with the engagement.
What we can verify
- 27 enterprise meetings recorded in the client engagement record
- $100K+ pipeline recorded in the client engagement record
- Enterprise ICP and target account list owned by the team
- Outbound sequences and a repeatable call structure in place
- A weekly outbound cadence a lean team can sustain without outside help
- Outbound became a scheduled operating activity rather than an occasional push
- Conversations were prepared for against a shared standard
The meeting count and pipeline figure come from the client engagement record and are published as documented outcomes, not as independently audited results. No causal claim is made about revenue closed, conversion rate or the durability of these figures beyond the engagement window.
“Tom's flexibility and expertise were game changers for us as an early-stage startup. His ability to adapt to our evolving needs while delivering consistent results made a huge impact. We've built a strong foundation thanks to his guidance.”
What stayed behind
- Enterprise ICP and prioritized account list
- Positioning and message framing
- Email and phone sequences
- Cold-call structure and objection handling guide
- Weekly outbound operating cadence
What remained unproven
Every engagement leaves something unresolved. These are the limits of what this report can claim.
- No audited revenue outcome is available — pipeline value is a recorded figure, not closed business
- Long-run durability of the motion after the engagement was not measured
- Conversion from enterprise meeting to opportunity was not tracked in the published record
Building from scratch is a narrower problem than it looks. Define who you are for, say something a buyer recognizes, and give one person a repeatable motion they own. S44 shows what that looks like inside a team that has no room for outbound guesswork.
The thinking behind this work
- FrameworksYou Don't Have an Activity Problem. You Have an Aim ProblemWhy teams can hit activity KPIs while missing pipeline because targeting and prioritization are wrong.Read
- FrameworksMost Outbound Teams Are Creating Activity Without UrgencyRelevance answers why you. Urgency answers why now. How to investigate legitimate timing in outbound, without manufacturing pressure, scarcity or fake deadlines.Read
- FrameworksReplies Don't Mean PipelineWhy SDR teams are getting more responses but fewer conversations are actually progressing, and what to inspect after reply rate.Read
More in the Resource Library and on Media.
Build Your Outbound Operating System
If you want this kind of operating-partnership work in your own org, see how the Revenue Rebuild works today. Read the evidence first, then we can talk about your system.
Published from the client engagement record. Meeting and pipeline figures are client-recorded and labeled as documented outcomes rather than independently verified metrics. Named client testimonials are published with the clients’ knowledge. No logo or artifact is published for this engagement.