Your audit team finds money in vendor invoices no one else checked.

Your firm finds money suppliers already collected. Duplicate payments, missed early-pay discounts, statement credits never applied, invoices paid against the wrong PO. The work is granular, technical, and invisible until the check arrives. Your pipeline works the same way: built on introductions from existing CFOs and controllers, warm handoffs from accounting firms, the occasional conference where a controller mentions a $400,000 duplicate they caught too late. That pipeline has a ceiling. The controllers who know you already know you. The ones who do not are paying invoices your firm would have caught.

The Referral Ceiling Is a Revenue Ceiling

A single controller who trusts you might refer one peer a year, maybe two. The referral carries weight because it comes with a story: your firm recovered $1.2 million in duplicate payments from a single ERP migration, or found that a vendor had been double-billing on maintenance contracts for fourteen months. But the controller's network is finite. Their new job changes the account. Their peer group is the same forty people at the same regional CFO roundtables.

Meanwhile, the market of potential buyers is larger and more dispersed than the referral path can reach. Mid-market manufacturers with $50 million to $500 million in revenue often lack a dedicated AP recovery function. Private equity portfolio companies run fast integrations with messy vendor master files. Hospital systems acquired in roll-ups maintain separate AP instances that no one reconciled. These organizations do not appear at the conferences your clients attend. They do not know to ask for what you do.

The referral ceiling is not a marketing problem. It is a coverage problem. Your firm's expertise outruns its visibility.

Who the Correspondence Reaches

ROI Wire builds lists of specific individuals: the CFO at a $200 million industrial distributor, the corporate controller at a regional hospital chain, the VP of finance at a private equity-backed SaaS company with three recent acquisitions. These are not titles scraped from LinkedIn. Each name is verified against current filings, press releases, and corporate registration data. The list is rebuilt before each correspondence cycle.

The buyer profile varies by firm capability. A practice strong in ERP-driven duplicate detection belongs in front of companies that recently migrated to NetSuite or SAP. A firm that specializes in vendor statement audits fits organizations with high transaction volume and decentralized AP operations. A team with construction industry expertise targets general contractors with joint-venture payables and retention-release complexity.

The correspondence names the buyer's situation specifically. A letter to a controller at a roll-up healthcare practice mentions the integration period and the vendor master files that typically do not merge cleanly. An email to a CFO at a distributor references the early-pay discount leakage that accompanies rapid SKU expansion. The buyer recognizes their own operation in the first paragraph.

Email Correspondence: The Technical Opening

Email Correspondence from ROI Wire is a single message to a named individual, written as if from a principal at your firm. It does not attach a brochure. It does not invite the recipient to a webinar. It states a specific observation about their business and offers a single, low-friction next step.

A typical opening for an AP audit firm:

"Your firm recently completed the acquisition of Midwest Packaging. In our work with similar roll-ups, the vendor master file integration typically leaves 3 to 5 percent of annual spend exposed to duplicate payment and statement credit leakage for the first eighteen months. We recovered $890,000 in such leakage for a regional food distributor in a comparable integration. A brief review of your vendor statements against payment history would confirm whether the same pattern holds. I can arrange that directly, without involvement from your AP staff beyond file access."

The email is three paragraphs. The first names the situation. The second cites an anonymized comparable engagement. The third proposes a concrete, bounded next step. The signature is a principal at your firm, with a direct phone line.

The follow-up email, sent ten days later, references the first by date and adds specificity:

"I wrote on March 3 regarding vendor master file exposure from the Midwest Packaging integration. I noted the typical 3 to 5 percent leakage window. For a firm with your transaction volume, that exposure window likely represents $200,000 to $400,000 in recoverable overpayment. The review requires two hours of your staff's time and can be conducted against historical data without disrupting current operations."

The follow-up does not ask if the recipient received the first email. It assumes they did and advances the argument.

Direct Mail: The Physical Anchor

Direct Mail reaches the same individuals with a letter on your firm's stationery, signed by the same principal who appears in the email sequence. The letter is one page, dense with specifics. It includes a single-page case summary, anonymized and by industry, that walks through the detection method, the recovery amount, and the time required from the client's team.

The physical letter serves a distinct function in this vertical. CFOs and controllers handle sensitive vendor relationships. A vendor statement audit, even when it recovers money, can strain a long-standing supplier relationship if mishandled. The physical letter signals that your firm understands this gravity. It is not a mass communication. It is a considered approach to a specific situation, documented on paper that the recipient can show to a CEO or audit committee.

Direct Mail also reaches the buyer when email does not. Controllers at manufacturing firms often manage vendor communications through shared inboxes with aggressive filtering. The letter arrives at the physical address associated with their corporate registration, typically the headquarters where the CFO's office sits.

The Phone Follows the Letters

The phone call comes after the second email and the mailed letter have both been delivered. The caller, trained on your firm's methodology and recent engagements, references both pieces by date:

"Ms. Chen, this is David Park with Meridian Recovery. I wrote on March 3 and March 13, and sent a letter on March 15, regarding the vendor master file exposure from your Midwest Packaging integration. The review I described, two hours of staff time against historical data, typically identifies recoverable overpayment in the first thirty days. I am calling to see if you have had a chance to consider whether that review fits your current priorities."

The prospect has seen your firm's name three times. They know why you are calling. The conversation moves directly to fit and timing, not to explanation.

What the Engagement Looks Like

ROI Wire structures engagements to match the economics of AP audit work. Some firms prefer a revenue share: the client covers the cost of list building, correspondence production, and delivery infrastructure, and ROI Wire participates in the revenue from engagements that originate through its correspondence. This aligns the work with outcomes and suits firms that are confident in their close rate but cautious about fixed marketing spend.

Other firms run on a retainer basis, particularly those with established sales capacity and a need for predictable pipeline volume. The retainer covers the full correspondence program, list maintenance, and phone follow-up, with no variable component.

There is no single price. The structure depends on your firm's average engagement size, your sales cycle, and whether you are entering a new industry vertical or deepening presence in an existing one. What does not vary is the correspondence: named individuals, specific situations, concrete next steps.

The Work Stays Yours

ROI Wire handles the correspondence only. We do not access your client's AP systems, vendor files, or payment history. We do not review invoices or conduct statement audits. We do not touch financial data. The recovery work, the vendor negotiation, the final report to the audit committee: that remains entirely with your firm.

This separation matters in a field where client trust is built on discretion. A CFO who allows vendor file access is granting visibility into supplier relationships that may span decades. The correspondence that opens that relationship must demonstrate the same discretion that the audit itself will require.

The Buyers Who Respond

The correspondence generates meetings with buyers in specific situations. Recent ERP migrations or system consolidations create master file chaos that your firm can map and clean. Private equity hold periods impose timeline pressure that makes a sixty-day recovery review attractive to a CFO measured on quarterly cash flow. High-growth companies with rapid vendor onboarding often lack the controls that prevent duplicate payment setup.

The buyer who responds is not shopping for an AP audit. They are living with a problem they have not named: the controller who knows something is off in the integration but cannot get resources to investigate it, the CFO who sees early-pay discount rates declining and suspects process failure, the VP of finance at a company that has never conducted a vendor statement review because no one thought to ask.

Your firm's job is to name the problem, quantify the exposure, and offer a bounded entry point. The correspondence does the first two. The phone call does the third.

What This Requires From Your Firm

The program works when your firm can describe its methodology with specificity. Not "we review your AP process" but "we match vendor statements to payment history at the invoice level, then trace unmatched payments against open credits and duplicate vendor setups." Not "we find savings" but "we recover early-pay discounts lost to batch-processing delays, typically 0.4 to 0.7 percent of annual spend for firms with your payment volume."

This specificity is not marketing polish. It is the actual work, stated plainly. The controller who reads it recognizes whether your firm understands their operation or is genericizing from a template.

The program also requires availability for the meetings it generates. A CFO who responds to a March 13 letter expects to speak with the principal named in that letter, or with a senior director who can speak to the specific engagement cited, within days. A two-week delay signals that the firm does not prioritize new relationships. The pipeline fills and empties quickly.

Who This Is Not For

ROI Wire does not work with firms that want to buy a list and "see what happens." The correspondence requires investment in research, writing, and follow-up. It assumes a sustained program, not a single send.

We do not work with firms that cannot articulate their own methodology. If your pitch is indistinguishable from a competitor's, the correspondence will not distinguish it either.

We do not work with firms that dispute their own success rates or hide recoveries from clients. The revenue share model depends on transparent reporting. The retainer model depends on a sales process that converts the meetings we generate.

The Recovery Business and the Pipeline Problem

Accounts payable audit firms live in the gap between what was paid and what should have been paid. That gap is everywhere and invisible. Your best clients did not know it existed until you showed them. Your next best clients do not know you exist because no one has shown them.

The referral pipeline rewards the known. Correspondence reaches the unknown, names their situation, and offers a path to discovery. The work is quiet, specific, and cumulative. A controller who does not respond in March may respond in October, when the ERP migration finally hits the vendor file. The letter from March is still in their file. The email from March 13 is still in their inbox, searchable by your firm's name.

The pipeline you need is not larger than the one you have. It is simply the one you have not met yet.