Tech stack

The tools I run, and what I actually do in each one

A logo list proves nothing. This page says what I configure, what I report out of, and where each tool is the right or wrong choice for your campaign.

3 CRMs 3 dialers / VOIP Python automation FMCSA data tooling
Production stack

Twelve tools, in the order I'd set them up

If you're starting from nothing, the sequence is: CRM first, then VOIP, then list sourcing, then dialer, then automation. Setting up a dialer before a CRM is the most common expensive mistake.

HubSpot CRM

CRM · Free tier onwards

My default recommendation for teams under about ten users. I configure deal stages with real exit criteria, custom properties for the qualification data that actually matters in your niche, call dispositions, and sequences for the 10–14 day follow-up. The Friday report comes out of a dashboard, not a spreadsheet.

What I do with it
  • Pipeline and stage architecture
  • Custom qualification properties
  • Sequences and task queues
  • Dashboards for weekly reporting

Salesforce

CRM · Enterprise

Where you already have it, or where reporting complexity genuinely requires it. I work inside Sales Cloud on lead and opportunity objects, log activity properly, and keep the data clean enough that your ops team doesn't have to fix it later.

What I do with it
  • Lead and opportunity management
  • Activity logging discipline
  • Report and list-view setup
  • Data hygiene and dedupe

Go High Level

CRM + automation · Agency favourite

Strong fit for MCA and local-services campaigns because pipelines, SMS, email and calendars live in one place. I build the opportunity pipeline, the SMS follow-up cadence and the calendar booking flow, then wire them together so a booked appointment triggers its own confirmation sequence.

What I do with it
  • Opportunity pipelines
  • SMS + email workflows
  • Calendar and booking automation
  • Snapshot setup

LinkedIn Sales Navigator

Prospecting · Sourcing

Primary sourcing tool for B2B lists where the buyer has a LinkedIn presence. Saved searches by headcount, geography, seniority and function; exported, enriched and verified before anything reaches the dialer.

What I do with it
  • ICP-based saved searches
  • Decision-maker title verification
  • Account mapping
  • Export and enrichment

FMCSA portal & Clearinghouse

Compliance data · Trucking

For motor carrier work: carrier census lookups, operating status and authority checks, safety data review, and Drug & Alcohol Clearinghouse registration and query tracking. This is where trucking list-building beats anything you can buy — the data is public, current and segmentable by fleet size and registration date.

What I do with it
  • Carrier census pulls and segmentation
  • Operating authority verification
  • Clearinghouse query tracking
  • MCS-150 due-date calculation

Mojo Dialer

Dialer · High volume

Multi-line power dialling when the campaign is volume-led and the list is large. Set up with disposition mapping back to the CRM so nothing gets logged twice or lost.

What I do with it
  • Multi-line dialling
  • Disposition mapping
  • Callback scheduling
  • List import and management

RingCentral

VOIP · Business lines

Where clients want a proper business line, call recording and voicemail drop. Reliable US numbers with local area codes, which measurably lifts answer rates over unfamiliar toll-free prefixes.

What I do with it
  • Local-presence numbers
  • Call recording
  • Voicemail drop
  • Call logs and analytics

Dialpad

VOIP + AI · Coaching

Useful when a client wants transcripts and call analytics. The transcription is good enough to review objection patterns across a week's calls and adjust the opener based on evidence rather than memory.

What I do with it
  • Transcription and search
  • Call analytics
  • Objection pattern review
  • Coaching notes

Python (pandas, NumPy)

Data · Automation

The unglamorous edge. Scraping, enrichment, phone normalisation, deduplication across sources, DNC screening, and building the weekly metrics file. It's why a list I build has under 10% dead numbers instead of the 20–40% typical of a purchased list.

What I do with it
  • Scraping and enrichment
  • Phone normalisation and dedupe
  • DNC screening
  • Automated metrics reporting

Excel & Google Sheets

Reporting · Universal

Every client wants the numbers in a sheet eventually. Clean weekly trackers, cohort views of follow-up performance, and pivot summaries that let you see whether week three of a sequence is actually producing.

What I do with it
  • Weekly KPI trackers
  • Follow-up cohort analysis
  • Pivot reporting
  • Client-ready summaries

Google Workspace

Comms · Daily

Gmail for follow-up sequences, Calendar for appointment handoff, Drive for shared document collection — which matters enormously in DOT work where you're chasing eight documents per driver.

What I do with it
  • Follow-up email sequences
  • Calendar handoff
  • Shared document collection
  • Client reporting folders

Calendly / HubSpot Meetings

Scheduling · Booking

Booking links wired into the call flow so the appointment is set while the prospect is still on the phone, then confirmed at 24 hours and one hour. Booking on the call rather than after it is worth 15–20 points of show rate.

What I do with it
  • On-call booking
  • Confirmation sequences
  • Reschedule handling
  • No-show recovery
Stack questions

What clients ask about tooling

Short answers first. Tap any question to expand.

Which CRM should a small B2B team use for outbound?
Under ten users with no existing system: free HubSpot CRM. It configures fastest, the sequences are good enough for 10–14 day follow-up, and the reporting is usable without a consultant. Choose Go High Level instead if SMS is central to your follow-up or you're in local services or MCA. Choose Salesforce if you already own it or your reporting needs are genuinely complex.
Do I need to buy a dialer?
Not immediately. For under about 100 dials a day a good VOIP line like RingCentral is enough. Above that, a power dialer such as Mojo pays for itself in recovered talk time. Buy the dialer when dial volume is the constraint, not before.
Can you work in the tools we already use?
Yes. I'd rather adapt to your stack than move you onto mine — migrations lose data and momentum. If your CRM is a mess I'll clean it up, but I'll clean up the one you have.
Why does a cold caller need Python?
Because list quality sets the ceiling on the campaign. Scraping, enrichment, phone normalisation, deduplication and DNC screening are tedious by hand and instant in code. On trucking campaigns it also lets me pull and segment FMCSA carrier census data by fleet size, operating status and registration date, which is not something you can buy off the shelf in usable form.
Do you record calls?
Where the dialer supports it and the law allows. Several US states require all-party consent, so the answer varies by where you're calling. I'll flag which states apply to your list before we start, and I'll always tell you what I can and can't share.

Already have a stack? I'll work inside it.

Send me your CRM and dialer and I'll tell you what's configured wrong before you hire me. That review is free and it usually finds something.