For Jay Lohman and PJ Krstic, VSL Global

The outbound engine
for VSL Global

The scope and the expected output, as promised on the September 10 call. The numbers come on the next one.
Design. Build. Run. Hand over.
BUILD RUN OWN
Prepared for VSL Global by Enquirer Consulting Group, September 2026. Your contact: Paul Smaldone.
Enquirer AI is the outbound engine of Enquirer Consulting Group.
What we heard on the call

Everything else is in a good place. The pipeline is the job.

"Right now our focus is the lead gen... We just need to really set that pipeline alight and turn it on."Jay
"Something that does the heavy lifting, starts setting appointments, and puts me in a position where I can speak to five to ten people a week."Jay
"The KPI needs to be the amount of scheduled warm calls with people that are interested."PJ
"I don't like revolving doors... What we're looking for is to find consistency, to find partners that we can work with, we can build with."Jay
2
Where you are today

The pipeline runs on the advisory board and on Jay's own hours.

What you told us

  • New conversations come from warm introductions through a five or six person advisory board. Nothing is converting from cold outreach, Sales Navigator or email right now.
  • Ten to fifteen active enterprise conversations a month, carried by Jay personally.
  • Tools tried earlier this year. One started well, went fully automated, and fell over.
  • Two clear buyer profiles, a soft launch behind you, a CRO coming in, and a raise in progress.

What that means for the build

  • The ceiling on volume is Jay's calendar and his network, not the market.
  • Every new conversation depends on an introduction. Nothing runs when Jay is not in the room.
  • The next stage needs a channel that works every week, with a person on the replies who is not the founder.
  • You already know who buys. Our job is to reach them at volume, in your voice, without another tool to babysit.
3
The market, as you defined it

Two lanes. One buyer profile in each.

LANE 1

Production houses

Post-production and content production companies with more than a million a year in revenue. North America and Europe first.

Who we reach: heads of post-production, heads of production, operations directors, and whoever owns the localization step and its budget.

LANE 2

Media agencies

Agencies and distribution businesses producing multilingual video for brands, a million a year and up. North America and Europe first.

Who we reach: managing directors, heads of production, heads of content operations, and the person who signs off studio spend.

SEQUENCED

Asia, when you say

The two or three countries you name, added as their own lane once the first two are running. Sequenced, not dropped: one account working one time zone cleanly before it works three.

If you want Singapore in the first month, say so and we size for it.

The lanes and the roles above are our first cut. You know these buyers better than we do. You correct and cross out, and nothing moves until you have.
4
What we build for VSL

One outbound unit, scoped to the pipeline and nothing else.

The LinkedIn engine

Personalized outreach from real accounts, inside LinkedIn's limits, working both lanes every week.

The target lists

Named companies and named people in each lane, verified before anything sends, and reviewed by you first.

The messaging

Written for the person it goes to, in VSL's voice, from a framing you sign off. No templates, no blast.

The human layer

A reply stops the automation. A person reads it, answers it, and hands it to you with the whole thread.

Reporting

A live view of every account and every conversation, and a plain weekly summary per lane, measured on scheduled calls.

The operator and the handover

Your person, trained during the run, who keeps the playbook, the lists, the dashboards and the accounts at the end.

Left out on purpose: your website, your brand and your product story. You told us everything outside the pipeline is in a good place, so they are not in this plan. They are disciplines we run, and if that changes we will say so.
5
How a week runs

The engine, week by week, pointed at your two lanes.

01

Find

Named companies in both lanes and the right person inside each, verified. The list goes to you for cross-outs before anything sends.

02

Open

A short, specific connection note from a real account, then follow-ups written for that person. Inside LinkedIn's limits, every week.

03

Reply

The moment someone engages, the automation stops. A person reads it and answers, or hands it straight to you with the context.

04

Book

A scheduled warm call lands on your calendar with the thread and a short brief on who they are. That number is the one we count.

05

Rotate

Connected but quiet gets a later touch from the same account. Never connected gets a different one. That is the part that does not survive being done by hand.

Two things stay constant. Nothing goes out that you have not signed off, and every conversation that gets a human reply gets a human on our side.
6
The starting shape

Three accounts, two lanes, and scale once the numbers hold.

Jay's own account

Takes the named enterprise conversations, so anything that matters opens in your voice.

Used only with your authorization and only with wording you have signed off. You keep the profile, the posting and the strategy. We take the daily outbound grind off it.

Two accounts we provide and run

Real people we know, branded to VSL, working under your name.

They do the finding and the opening across both lanes, so your account is not the one carrying the volume. If one of them is ever restricted, we replace it, not you.

Scaling

Each account works inside LinkedIn's weekly connection limit, ramped up over the first weeks rather than hit on day one.

When a lane converts, we add accounts to it. The count is sized on the call, against the volume you named and the pace you want to reach it at.

Email stays in reserve. LinkedIn is where a specific, human approach to these buyers gets answered, so it is where we start. If a lane later needs email as well, that is a separate build with its own sending domains, never your own.
7
How it starts

Prove the channel first. Then build the unit. Then it is yours.

Month one

The pilot

LinkedIn only. Three accounts, two lanes.

Week one: lists and messaging with you for sign-off. Live once approved. A weekly summary from the first week.

At the end of the month we take stock together: continue, stop, or scale what worked.

The four months after the pilot

Build and Run

More accounts on the lanes that convert, and the third lane when you name it.

Replies wired into whatever you track deals in, so nothing sits in a shared inbox waiting for Jay.

Your operator trained inside the run, not handed a manual at the end.

Then

Own

Your team runs it: the playbook, the lists, the messaging, the dashboards and the accounts we branded for you.

If you would rather we keep running it, that is a managed service you choose, month by month. It is not a lock-in.

Nothing goes live until you have approved the lists and the wording. The pilot is there so you see the engine work on your lanes before you commit to the build.
8
Two questions from the call

The operator, and the KPI.

Who is the operator, and whose side are they on?
PJ asked

Yours. Someone on PJ's team, or a hire we help you find and vet. PJ owns the number; the operator runs the machine. They sit inside the run from the start of the build, learn the lists, the messaging and the rotation rules by doing them alongside us, and take the keys at handover.

You own it, so you are never dependent on us. If you want us running it in year two and year three, we stay, on your terms, and that is your choice rather than a lock-in.

What is the KPI, and who sets it?
PJ asked

Scheduled warm calls with people who want the conversation. A reply is not a result, and neither is a thumbs up. We agree the definition and the number together before anything sends, and the weekly summary reports against it.

The target we build to is the one Jay named: five to ten conversations a week, reached on the ramp Jay described himself. Nothing switches on overnight, and the first weeks are the lists, the wording and the first connections. The number we put in writing is the one we agree together before anything sends.

9
For the comparison you will run

The AI reads and drafts. A person owns every conversation.

A tool gives you software.

You run it, you write it, you chase it, and you own the result when it stalls. We run the whole unit: the lists, the words, the accounts, the replies and the reporting.

Fully automated fell over on you once already.

Here the automation stops the moment a human replies. Every live conversation has a person on it, and you see all of it.

The accounts are real people we know.

Branded to VSL, run by us, replaced by us if anything breaks. Nothing about them reads as a bot, because they are not one.

At the end, you own it.

A subscription ends when you stop paying. This ends with your team running the machine and the playbook in your hands.

What we do not do: long lock-ins, or a meetings-per-week promise in writing. The number we agree together is the number we report against, every week.
10
Proof

Clients in their own words, and numbers from live work.

"
Enquirer AI helps us identify the right people and start the conversation in a much smarter way.
Tim RathChief Operating Officer, Innovative RadiologyTwo minutes with Tim, on video
"
Tools like Enquirer AI allow us to personalize outreach at scale in a way that simply was not possible before.
Sales DirectorInnovative Medical
$10M+
New business sold for clients
3,500+
Qualified conversations generated
100,000+
Decision makers reached for clients
Cumulative figures from live client work. New business is client-reported. None of it is a promise of VSL's result. The KPI for your build is set with you.
11
Next step

The numbers, on the call, sized to the shape we settle.

What we cover on the next call

  • The roles inside each lane. You correct our first cut, and that becomes the list.
  • The account count against the volume you want and the pace you want it at.
  • The KPI definition and the number, agreed before anything sends.
  • The cost of the pilot month and of the full build, in one number each, so you have a straight comparison to put beside anything else you are looking at.

Before then

  • Take the three to five days you asked for. Share this with the advisory board.
  • Send their questions ahead if it helps, or bring them, however detailed.
Paul Smaldone
Enquirer Consulting Group
paul@enquirerconsulting.com
12

We build it, run it until it works, then hand you the keys.

Arrow keys or click to move through the pages