Real Example
What this looks like in practice.
A fleet safety technology company needed to reach safety leaders at carriers facing FMCSA investigation triggers. Here's what I built using nothing but public data.
Trucking — FMCSA
Without the data, you're stuck writing this.
I wanted to reach out because we help carriers improve their safety scores and stay ahead of DOT compliance issues. A lot of fleet operators are dealing with audits and CSA scoring pressure right now.
We've worked with similar carriers to identify exposure and build out corrective plans. I'd love to show your team how we could help.
Do you have 15 minutes this week?
With the data, your rep sends this.
Your Unsafe Driving BASIC hit the 78th percentile this month. That puts your fleet above the 65% threshold that lands you on FMCSA's prioritization list for compliance review — it's also the same number your insurance carrier pulls when they price your next renewal.
I built a safety scorecard from your publicly available FMCSA data — your trend over the last 12 months, how you compare to carriers your size, and the violation categories driving the score.
Want me to send it?
Sourced from FMCSA Safety Measurement System (ai.fmcsa.dot.gov/SMS) — public DOT data, refreshed monthly. Every claim verifiable in 5 minutes.
What Reps Say When They See It
"I would absolutely send that to a customer."
Enterprise Rep // Samsara
"All of that is insanely actionable. Can you run it for another company?"
Enterprise Rep // Trane
"Damn dude this is amazing. We need this a lot in my industry."
Enterprise Rep // Truckstop
How It Works
01_
I build the system.
Public data triggers (FMCSA, OSHA, EPA, LL97) → enriched list → custom messages. The intelligence layer the AI-SDR stack can't replicate.
// Weeks 1–3
02_
I run it.
Sends, replies, meeting-booking, cold calls — all me. I sit the seat while the playbook proves itself in production.
// Weeks 4–7
03_
I hand it off.
Instrumented dashboard, permanent runbook, full transition with your team. You inherit a working production line, not a deck.
// Weeks 8–12
Ways To Start
Three shapes of engagement.
Pick how much I carry.
Every engagement starts with the same proof: a hand-built playbook for your company. From there you decide how deep I go.
Start Here
GTM Alpha Playbook
Free sample, hand-built per company
See the power of public-data signals on your exact vertical. No commitment, no call required.
- →Pain Signal Map for your buyers
- →Public databases mapped to your buyer's pain (FMCSA, OSHA, EPA, FDA, ENERGY STAR, LL97, etc., depending on your market)
- →Buyer Channel Map — which titles read email, which take phone calls, which live on LinkedIn
- →3 written PVPs matched to each buyer's actual channel
- →5 named, hyper-targeted prospects bleeding from those triggers right now
- →Delivered as a 5-min Loom walkthrough + written brief
// Hand-built per company
Claim a PlaybookOngoing
Signal Intelligence Retainer
For teams with execution headcount
Ongoing intelligence work for sales orgs that already have an SDR seat — I keep the lists fresh and the messaging sharp, your team runs the sends.
- →I refresh your target list daily / weekly with verified public-data signals
- →I maintain the data pipes and signal sources
- →I iterate the messaging based on what's working
- →I deliver scored leads to your team weekly
// I don't run sends or replies on this tier
Apply for RetainerFull Build // Focal
90-Day Build
I build it, run it, hand it off
I build the system AND run it. For 4 weeks I'm an extension of your sales team — sends, replies, meetings, calls, all me.
Kickoff
Setup
I Carry
Handoff
- →48-hour kickoff: expanded Signal Map + Buyer Channel Map + 20 hyper-targeted prospects delivered the moment we sign
- →Weeks 1–3: I set up infrastructure, warm inboxes, finalize messaging, lock the playbook with your team
- →Weeks 4–7: I carry the bag — sends, replies, meeting-booking, cold calls, all me
- →Weeks 8–12: Transition + full handoff with permanent runbook
Who It's For
Built for these companies.
- Vertical SaaS, fintech, healthcare, or industrial tech selling into regulated, licensed, or inspected industries where US public data tracks the buyer's problems
- Seed to Series B ($1M–$25M ARR), small sales team (1–5 reps), founder-led or with a VP Sales who recently walked into no playbook and no outbound infrastructure
- Outbound exists but is mediocre — generic ZoomInfo + Apollo sequences, or burned by an AI SDR / agency that went pure spray-and-pray
Who It's Not For
Not the right fit for these.
- Horizontal SaaS selling to other tech companies — buyers are data-literate and public compliance data isn't a moat
- Pre-product or pre-revenue — the signal-based list is useless without a product behind it
- "Let's test some AI outbound" budgets — if the problem isn't obvious and the data doesn't exist, this dies in month 1
Who Built This
Lucas Linares — ex-Clay GTM Engineer. 4 years carrying quota (SDR → Founding AE) at Tonic.ai, Rutter, and Clay before building Thresh. LinkedIn →
Claim the playbook.
Hand-built for your company.
Drop your details below and I'll build the playbook for your company. Here's what's in it:
- →Pain Signal Map for your buyers
- →Public databases mapped to your buyer's pain
- →Buyer Channel Map — which titles read email, which take phone calls, which live on LinkedIn
- →3 written PVPs matched to each buyer's actual channel
- →5 named, hyper-targeted prospects bleeding from those triggers right now
- →Delivered as a 5-min Loom walkthrough + written brief
// No commitment, no call required
Or skip ahead
Book a 30-minute call →