Programs in Practice

How a program is built, sector by sector.

Six illustrative scenarios, one per sector we work in. Each describes the mechanics of a market access program: how the audience was defined, how the message was structured, how distribution was sequenced and how responses were handled. The figures given describe program inputs such as universe size, waves and territories. They are not client results.

Status

Illustrative scenarios, composite patterns

01Origination
1,400 ownersM&A & Private Markets
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

A universe of 1,400 owners, reached without a broker in the room.

  • Audience definition: specialty manufacturing businesses inside a defined revenue band and geography, resolved to the named owner rather than a generic company address.
  • Message architecture: a principal to principal letter written in the acquirer's own voice, stating the thesis, the intent to hold rather than flip, and a single specific reason for writing to that business.
  • Distribution cadence: quarterly waves across the full universe, each wave carrying new content rather than a repeat of the previous letter.
  • Response routing: replies land with a named partner, not a shared inbox, and every response is recorded against the audience file so the following wave can be adjusted.
What determined the outcome

What determined the outcome was patience in the audience definition. The first draft of the universe was almost three times larger and included businesses the acquirer could not credibly buy. Cutting it back made the letter specific, and specificity is what earns a reply from an owner who receives approach calls every month. The program was built to change where the first conversation happens: before a process exists, rather than inside one where price has already been set against the buyer.

Illustrative economics: at this deal size a single completed acquisition carries value measured in years of program cost, so the program is judged on the quality of conversations opened, not on volume.

02Acquisition
6,000 businessesInsurance
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

6,000 mapped businesses, contacted before renewal season opened.

  • Audience definition: three trades where the brokerage had genuine underwriting relationships, mapped at business level across a defined region and filtered by size and risk profile.
  • Message architecture: one letter per trade, written around the specific coverage gaps that trade tends to carry, addressed to the owner or the person who signs the policy.
  • Distribution cadence: waves timed to land ahead of the trade's common renewal months rather than spread evenly through the year.
  • Response routing: each wave released in territories matched to a named producer, so a reply reaches someone who can talk about that trade the same day.
What determined the outcome

The judgment call was sequencing. Sending the whole file at once would have produced more replies than the producer team could handle well, and a slow callback wastes the letter. Splitting the file by territory and renewal month kept the follow-up credible. The program was built to change the timing of the first conversation, moving it upstream of the incumbent broker's renewal paperwork.

Illustrative economics: commercial accounts renew annually, so the relevant figure is the multi-year value of a retained account rather than the cost of a single wave.

03Territory
18 postcodesHome Services
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

18 postcodes covered repeatedly, until the name was already familiar.

  • Audience definition: households inside 18 postcodes selected for roof age, property type and drive time from the depot, rather than a wide radius around the city.
  • Message architecture: a plain, specific letter naming the streets the crews were working on that month, with a short note on what storm damage actually looks like from the ground.
  • Distribution cadence: a base wave before storm season, then reactive waves into affected postcodes within days of a significant weather event.
  • Response routing: calls tracked by postcode so the operator could see which territories were carrying the work and which needed a further wave.
What determined the outcome

Concentration decided this one. The operator's instinct was to cover the whole metro area once. Covering a smaller footprint several times builds the recognition that makes a homeowner call the name they have seen rather than search from scratch. Route density also made the crews cheaper to run. The program was built to change how the territory thinks about the business over a full year, not to win a single week of jobs.

Illustrative economics: a full roof replacement carries a value high enough that the arithmetic turns on required response rate, which is why territory concentration matters more than reach.

04Origination
3 wavesProperty
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

Three sequenced waves to owners of stock that was never listed.

  • Audience definition: registered owners of older multifamily buildings inside target submarkets, identified at address level and matched to the individual or entity on title.
  • Message architecture: a letter that named the building, acknowledged the work it needed, and made a direct statement about the investor's intent and ability to close.
  • Distribution cadence: three waves over roughly nine months, each one shorter and more specific than the last as the file was refined.
  • Response routing: replies handled directly by the principal, with a documented note against every owner contacted so the file stayed useful for years.
What determined the outcome

The decision that mattered was accepting a long clock. Owners of tired stock sell when something in their own circumstances changes, and no letter creates that moment. The program's job was to be the name on file when it arrives. Anything written to force a decision in one wave would have burned the relationship. The program was built to change who the owner calls first.

Illustrative economics: one acquired building can carry several years of program cost, so the program is measured by conversations sourced off-market rather than reply volume.

05Reactivation
Dormant bookFinancial Services
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

A dormant SME book re-opened through a channel no filter blocks.

  • Audience definition: former borrowers with no activity for a defined period, segmented by why the relationship went quiet and whether the business still trades.
  • Message architecture: a letter that referenced the prior relationship plainly, without pretending it had continued, and stated what had changed on the lender's side.
  • Distribution cadence: a first wave to the strongest segment, then a wider release once the message had been read against real replies.
  • Response routing: a named relationship manager per segment, with a direct line rather than a general enquiries number.
What determined the outcome

The useful judgment here was about honesty of tone. Reactivation copy usually reads as if nothing happened, and business owners notice. Naming the gap made the letter credible. Segmenting by cause of dormancy also stopped the lender writing the same thing to a business that had been declined and one that had simply repaid and moved on. The program was built to change reachability: these contacts were already unreachable by email long before the campaign started.

Illustrative economics: a re-opened lending relationship generates income over multiple facilities, so the comparison is against the cost of acquiring an equivalent new borrower.

06Acquisition
Full catchmentHealthcare
Illustrative scenario

Composite of program patterns. Not a named client engagement and not a promise of results.

Full catchment coverage inside a realistic travel radius.

  • Audience definition: households within an honest drive time of each clinic, filtered by property profile and age band rather than by postcode boundaries.
  • Message architecture: correspondence written for a reader making a considered clinical decision, explaining what implant treatment involves and what it does not, with no urgency devices.
  • Distribution cadence: rolling coverage of the catchment so that each household sees the practice more than once across a year, with volume set by consultation capacity.
  • Response routing: enquiries booked into a consultation diary that the practice could actually staff, with source captured at booking.
What determined the outcome

Capacity set the shape of this program. A larger release would have generated enquiries the clinics could not see quickly, and in considered treatment a delayed consultation is usually a lost one. Matching wave size to diary capacity was the constraint we designed around. The program was built to change how many qualified households in the catchment know the practice exists at all.

Illustrative economics: full arch and multi-implant treatment carries a high single case value, which is what makes household level coverage of a defined catchment defensible.

Market Review

There are people your business should know.

If there is a market you are not currently reaching, a market review is the place to begin. We will look at the audience, the objective and whether a structured program is warranted.