Charm builds and runs outbound for
+ others
+ others
We find the cases. We build the lists.
We run email and LinkedIn. You file the claims.
Speed to signal. The second a case appears anywhere, the engine is already moving.
+ others
Four steps, in your words from the call. The first three are ours to run. The last one is yours, and everything we do is built to make it easier.
"It's scouring Law360. It's scouring CourtListener. It's scouring PACER. Something gets filed, it knows."
And if we need to work with whatever Danny is building, we can. His flags feed the same pipeline, and we iterate with him as his build grows.
"He'll have full access to our lead database where he can go and run crazy."
Today: the lead platform and List Kit exist, but every case's list is assembled by hand. After: the court-approved class definition, which is a free ICP document, runs as a query against your own platform first. Our stack fills the gaps, then resolves every company to the person with signing authority: CFO, controller, VP finance. Verified, deduped, suppressed across cases so nobody gets four pitches in a week.
"The right hand knows what the left is doing... one mechanism that's got many arms working in tandem."
Today: ListKit fires email and Peter runs LinkedIn at the same 100-to-200k list, and neither system knows what the other did. After: both written channels run off one dataset, sequenced per prospect: the email lands, and 24 hours later the LinkedIn message says "putting a face to the name, I'm the guy that shot you over that email." That one-two is why coordinated outreach reads human and separate blasts read like junk. All of it on a dedicated domain portfolio we manage end to end: registration, warm-up, rotation, deliverability, and replacement when Google or Microsoft change the rules again.
The pixel side is covered too: we de-anonymize the people visiting your site, up to 300 visitors a month included (more available if you want it), and retarget them on LinkedIn. Everything currently spread across ListKit and your LinkedIn setup, under one roof, doing more. And if consolidating it all with us is where the numbers point, we are glad to work that out.
What we deliberately do not touch: texts, voicemail and the phone. Those stay yours on FlexConnect, and they get sharper anyway, because they can run off the same per-case dataset we hand you.
"This is exactly me. Boom. Here's the fill form, fill it out, bang, you're now with Macmoor."
Every sequence asks one question, and the yes routes into your existing intake with the case already tagged, so your team sees qualified, case-tagged conversations instead of cold starts. The fill-form flow you are building slots straight in whenever it ships: our CTA simply points at it. Until then it points at the intake you have.
And we help where helping is reasonable: wiring the CTA into your intake, advising on the fill-form flow as you build it, holding your hand on anything adjacent. The line we draw is on big software builds: per-settlement landing pages, e-sign flows and CRM engineering are their own projects with their own price, not something hiding inside this retainer.
These are the six cases published on macmoor.com/current-cases as of 6 August 2026, re-sorted by the only two columns that matter to outbound: who is eligible, and how long is left. The engine keeps this table current automatically and fires campaigns against it.
We want to be straight with you about the calendar rather than sell you a timeline that does not fit it. Most of this engine already exists inside our stack, so the software moves in week one, but domain warm-up has a physical floor that cannot be rushed without wrecking deliverability, and that is not a corner worth cutting. Kicked off this week, that leaves roughly four weeks of live sending against Toyota before the window shuts on September 22.
That is genuinely enough to prove the motion on a dated, verifiable case, but it does not stretch. Every week of delay removes a week of sending, and unlike every other deadline in a sales proposal, this one is a court order and cannot be moved. If Toyota is not realistic by the time we speak, the generic pharmaceutical fund at 95 days becomes the lead and everything below still holds.
Below is real copy, not placeholder: the engine's first five outputs, ready for your approval. Every campaign is a three-email sequence: E1 fresh, E2 threaded, E3 a fresh third angle. One CTA held consistent across all three, and every reply routes into your existing intake with the case already tagged, never to a calendar link. Values in {{braces}} populate per company from the dataset. Nothing ships until it is QA'd against the compliance position you give us.
The best first campaign you have, for four reasons. The class is physically targetable: companies that run internal-combustion forklift fleets are identifiable by industry code, facility type and equipment signals in a way that "businesses that accepted Visa Debit" is not. The bar date is near and hard, so the motion validates or fails inside eight weeks rather than eight months. The per-unit recovery is public and specific, between $1,000 and $2,500 per eligible forklift, which means a 60-unit distribution centre can be shown a real number in a first email instead of a vague promise. And it is fully verifiable by the recipient on the official settlement site, which is the single fastest way to defeat the scam prior.
The largest fund on your docket at $533M, with a defensible 95-day runway and a buyer who already thinks in claims and reimbursement. Hospital and health-system CFOs are unusually well-conditioned to the idea that money is recoverable from a payer or a manufacturer. The concept needs no explaining, only the specific case does.
Visa Debit and the EMV fraud-liability shift both point at the same buyer: a merchant who has been accepting cards for years and has never once been told that acceptance itself created a claim. The universe is enormous, which is the problem. This play is won with filters, not volume. We would run it against defined revenue and merchant-category bands rather than blasting it, and use it as the second offer to anyone already engaged from another case.
John Deere repair services is at proposed settlement. EMV is awaiting claim notice. In both, the class definition is already public but claims are not yet open, which means the list can be built, the contacts verified and the sequences written now, so the first email lands the week claims open rather than three months into the window. Nobody competes for attention during the pending period, and everybody competes for it after. This is the closest thing to a free position on the board that the model offers, and it is only available to someone with an engine already running.
Claims recovery is routinely referred rather than bought direct, and there is a specific set of professionals who encounter eligible companies constantly: bankruptcy trustees and restructuring advisors, outsourced CFO and controller firms, CPA and audit practices, and AP-recovery consultants. A separate, low-volume sequence to these firms compounds differently from buyer outbound: written as a partnership introduction with credibility and timing, not a pitch, and with no pain-poking. One trustee relationship can feed deals for years, and trustees are the single best channel for the claims purchasing side of the business, since a distressed estate needs cash now and cannot wait years for a distribution. This runs alongside whichever buyer play we lead with, at a fraction of the volume.
One monthly fee, sends and infrastructure included, plus a one-time $1,000 setup. Want more volume than your plan carries? The calculator below prices the extra.
+ $1,000 one-time setup
+ $1,000 one-time setup
Your plan's sends are included, infrastructure and all. Scaling beyond them is $15 per domain plus $10 for its three inboxes, each inbox sending up to 20 a day. Drag to add volume:
They have done right by you, and nothing here requires touching them. Worth knowing: this engine does what they do plus the parts a sending tool cannot, the class-defined lists, the managed deliverability, the LinkedIn coordination. A weekly suppression sync keeps the two programs out of each other's way, and if a point comes where consolidating under one roof makes sense, that is something we would be glad to work out together.
Month 1 is largely infrastructure and warm-up: domains, the class translation and dataset build, compliance review and copy QA. Real sending runs months 2 through 4. If the engine has not generated ROI by the end of month 4, we run month 5 completely free.
Claim your guarantee →Choose the lead case (we recommend Toyota on targetability and clock), lock your compliance position on third-party filing, and give us your contingency rate so the copy can be exact. Everything else is configuration we handle from there.
Domains on order and warming the next business day. The lead case's class definition becomes a dataset of eligible companies resolved to real finance executives, and you review it before anything sends.
Sequences in front of you for one approval, then sending begins on warmed capacity, with LinkedIn following the email motion. Replies arrive in your intake tagged by case. The weekly strategy call starts here and never stops.
Pick a kickoff date. Domains go on order the next business day, the lead case's dataset build starts the same week, and the first settlement campaign is in front of you for approval within five business days, against whichever bar date you tell us is worth the most.
Pick your kickoff date →