OptimoRoute · Signal-Triggered Outbound

01

What we actually do.

Three lines, no jargon.

Who

We build the list before writing a word.

Fleets first, then the people inside them who sign. You see the list before anything sends.

When

We write when something has happened.

A depot opens, two fleets merge, a vendor gets bought. It lands while the decision is open.

Hand over

You get replies. Your team runs the deal.

We are the front end for people who already know how to close a fleet.

02

Who we would be writing to.

All nine segments, US only, and the seats that sign off.

Segment	The seats we write to
Food, beverage and produce distributors 25 to 250 vehicles	VP Operations, Director of Distribution, Transportation Manager
Multi-brand home and commercial services groups 50 to 500 technicians	COO, VP Field Operations, Director of Dispatch
Regional 3PL, courier and parcel networks 30 to 400 vehicles	Managing Director, Head of Last Mile, Operations Director
Retail distribution and big-ticket home delivery 25 to 300 vehicles	VP Supply Chain, Head of Home Delivery, Transportation Manager
Pharmacy, medical supply and healthcare at home 20 to 200 vehicles	Director of Logistics, VP Pharmacy Operations, Head of Home Health
Waste, laundry and route-based commercial services 20 to 200 vehicles	Operations Director, Route Manager, General Manager
Inspection, insurance survey and utility field services 40 to 400 field staff	Head of Field Operations, VP Claims Operations, Regional Operations Manager
Ecommerce, meal kit and grocery brands running their own vans 15 to 150 vehicles	Head of Fulfilment, Director of Last Mile, COO
Larger twins of the customers already on your case-study pages Look-alikes	The same seats as the segment each one sits in

Named fleets inside each segment stay off the page. They are yours on the call.

03

When we would write.

Each one is a real event, at a real fleet, on a real date.

All fourteen. What is not here is where we find them, or which fleets are showing one right now.

01

Their routing vendor got acquired

The software they plan on now belongs to somebody else.

Why it is strong

New owner, new roadmap, new price list. Three of these closed in the last eight months.

02

Their routing app changed its name

Same product, different name on the invoice.

Why it is strong

A rebrand is the cheapest moment anyone ever re-opens the question.

03

The tool they run changed, or went away

What they were planning with is not what they are planning with now.

Why it is strong

Either they just bought something and it is not sticking, or they have nothing again. Both are worth an email.

04

One fleet bought another

Two dispatch boards, two sets of habits, one operation.

Why it is strong

Somebody has to pick which way of planning wins, and they have weeks to do it.

05

A multi-site group took over a new territory

New ground, no route history, and a promise already made to customers.

Why it is strong

The first plan for that territory gets built from nothing.

06

A new depot or distribution centre opened

Every route out of that building is planned from zero.

Why it is strong

For the first three months it is planned by hand. That is the window.

07

They promised same-day or next-day

A delivery promise is a routing constraint with a press release attached.

Why it is strong

They have committed publicly to something the old plan cannot hold.

08

The fleet went electric

Charge, chargers and depot power are route constraints now.

Why it is strong

This is the month a plan that worked for years stops working.

09

They announced more vehicles

The fleet grew faster than whoever plans it.

Why it is strong

The pain is proportional to vehicle count, and it just went up.

10

A new operations leader took the seat

Somebody new owns the dispatch board.

Why it is strong

New leaders buy a fast, visible win. Route cost is the most measurable one they have.

11

A dispatch or planning role went live

They are hiring the person who does this by hand.

Why it is strong

They wrote the problem down themselves, and dated it. Driver adverts are noise. This one is not.

12

Someone from a target fleet reads your pages

An operations lead is on your pricing page this week, not next year.

Why it is strong

They came to you. It is the warmest thing that happens all month and today it goes unanswered.

13

A trial or demo arrives from a large fleet

The signup is small. The company behind it is not.

Why it is strong

It gets spotted, enriched and routed to a person the same hour, instead of self-serving into the wrong plan.

14

A fleet already on your books outgrew its plan

The order ceiling they signed up under stopped fitting.

Why it is strong

The cheapest pipeline in the building, and nobody has to be convinced you exist.

04

What lands on your desk.

Results, not machinery. How it is built is the call.

The person who owns the dispatch board.

Not a form fill and not a trial signup. The operator who signs, written to as themselves.

Deals the trial was never going to produce.

Fleets whose volume rules the small plans out before the first call is over.

Your own traffic, turned into named accounts.

The fleets already reading your pages get identified and worked, instead of leaving without a trace.

One thread, one owner, nothing dropped.

Every reply arrives in one place with a name attached, logged against the account rather than remembered.

Under the hood: thirty agents in six departments, one core. Each agent is single-purpose, so new ones slot in without rebuilding anything. Reactivating closed-lost deals, enriching inbound, feeding ABM. What starts as one channel becomes the operating system.

05

Generic outreach, and ours.

You have probably been sold the left-hand column before.

What most agencies do	What we would do
One list, one message, sent to everyone on it.	A field service COO and a produce distributor’s transport manager do not buy for the same reason. Each is written separately.
Send on a schedule, and hope the timing works out.	Send when something has happened at that fleet, while the decision is still open.
Chase net-new only, and leave the inbound alone.	Work the fleets already on your site and already on your books first. They are the cheapest pipeline you own.
A dashboard, and a report at the end of the month.	Replies with a name on them, in a thread your team already watches.

06

Commercial terms.

Two packages. Month-to-month, no long lock-in.

Recommended

Package 1

Signals + Outbound

Full engine. We build the signals, we write the copy, we send, we route replies to your team.

$8,000 / month

Month-to-month. Invoiced on the 1st, net 15.

Signal engine on all 14 triggers (see section 03)
9-segment US fleet enrichment (see section 02)
Multichannel outbound: email + LinkedIn
Copy written per segment, per trigger tier
Human review before every send
Sending infrastructure procured and warmed
Reply management, routed to your team with signal context
Weekly reporting: signals surfaced, contacts touched, replies, meetings

Package 2

Signals only

The list and the live signal feed. You keep the outreach in-house or feed it to your existing team.

$4,000 / month

Month-to-month. Invoiced on the 1st, net 15.

Signal engine on all 14 triggers (see section 03)
9-segment US fleet enrichment (see section 02)
Weekly signal feed with enriched contacts
Delivered as CSV + optional CRM sync
Signal severity scored, briefed per event
Monthly working session to tune filters
Sending infrastructure — your team keeps outreach in-house
Copy authoring — your team writes it
Reply management — your team handles

Add-on · optional

Event support

Per-event outreach: attendee sourcing, pre-event sequences, on-site LinkedIn touches, post-event follow-up. Runs on top of either package, turned on for one event at a time.

$2,000/ event

Taxes added where required. Setup included in either package. Upgrade from Package 2 to Package 1 anytime, credited for what you paid.

07

The 90-day plan.

Kickoff within 5 business days of signature.

WEEKS 1–2

Kickoff & build

ICP codified. Signal sources wired across all 14 triggers. Sending domains procured, mailboxes provisioned, warmup started (Pkg 1). CRM audit and integration.

WEEKS 3–4

First signal feed

All 14 triggers producing live events across the 9 segments. First contacts enriched with buyer seats. Copy authored per segment and signal tier (Pkg 1).

WEEKS 5–6

First sends & replies

First sequences launch on Tier 1 signals (acquisition, merger, new depot). Reply management live (Pkg 1). First qualified replies routed to your team with signal context.

WEEKS 7–12

Full run & iterate

Full send volume. All 14 triggers running continuously. Copy iterated on reply data. Weekly reporting. Monthly working session to tune filters and add new segments if needed.