Lead Finder

We are a software development company, we have many excellent cusotmer case studies, we provide our services via channel partenrs, we want to develop leads to pass to these partners as a value add of our services. Vertical: Field-service / frontline-operations businesses, facilities management, building services, fleet/automotive, catering & contract services, logistics.

a. find the data
b. do the reach out
c. provide report
d. give us the number of expected calls for the fixed contract price,
e. if youhave an alternative approach, then we are open to discuss what's worked for you in the past.

NOTE: this is a pilot, if this provides good output we will look repeat.

Outbound Call Script & Qualification Checklist Field-Service / Frontline Operations, Software Development Outreach

Target Filter (for list-building)
Industry: Facilities management, building services/BMS, contract catering, field service/maintenance
Size: 20–200 field/frontline staff
Signals: Job postings for "operations manager," mentions of "digital transformation," careers page describing manual/paper-based processes
Title to reach: Operations Director, Head of Digital/IT

The Opener
(use your natural style, don't read it word-for-word if it sounds stiff on you) The core find is companeis using paperbased processes that we can autmate with software, either building inot their exsiting soluiton or building a new application.

"Hi [Name], I know this is out of the blue quick one. We just helped a building services company get their engineer job-scheduling and reporting off spreadsheets and into one system, live in weeks. I'm calling round a few similar-sized ops teams to see if that's a live problem for you too, or if I've got the wrong door."

Goal: give them an easy way to engage, not an easy way to hang up.

Qualifying Questions

(Only ask if they engage past the opener)

"What are you using today for [scheduling/inventory/inspections] is it a proper system, or more spreadsheets and WhatsApp?"
"Has that started causing problems as you've grown, or is it more of a nice-to-have fix?"
"Who'd be the person internally who owns that decision is that you?"

A meeting is worth booking when all three are true:

Manual/legacy process confirmed
Some real pain or cost named (not just "it'd be nice")
Right person on the line (or a warm intro to them)

Don't book a meeting on "sounds interesting" alone.

Objection Handling

"We're not looking right now"

"Totally fair can I ask, is that because it's not painful enough yet, or because you've been burned by a dev project before?"

"Send me something in an email"

"Happy to can I ask what specifically you'd want it to speak to, so I'm not sending generic stuff?"

If They Ask Technical Questions

Don't improvise. Redirect every time:

"Great question that's exactly what [Leon, project lead] can walk you through. When works for a 15-minute call?"

Call Outcomes to Log

For every call, record:

Company + contact name/title
Outcome: Meeting booked / Callback requested / Not interested / No answer
Pain point mentioned (if any, in their own words)
Objection raised (if any)