Performance Fasteners · Automotive Aftermarket
May 2026 Monthly Report
6 Reps Active
Executive Summary
What Beacon Ridge heard about Merrick in the field this month, drawn from 34 notes across 14 accounts. The clearest signal is a possible finish problem on the Pro Series MPS-2043 head stud kit — the black-oxide came in “hazy and rough” at Lakeshore, and “two came back rusty out of the box” at the same shop; a kit at Ironwood “looked used.” Reorders on LS kits and main studs stayed steady across the territory. On the FoundryLine side, Halstead is asking about a dropship program so they don't have to stock the hardware — a real opening worth pricing. A handful of fainter signals came in but didn't resolve: a Louisville shop asking about “Duncan,” some counter confusion about the Spring Torque-Up rebate, a possible second sighting of the 2043 finish issue further out.
Treat these as leads, not conclusions. At this month's level of note detail we can flag what came up but can't yet size it, date it, or confirm how far it spreads — which is why we can't hand Merrick the target list or the goal-progress readout they asked for off this data alone. The section below on capture is the reason, and the fix.
Month at a Glance
Note length ranged 3–21 words this month. Dana Whitfield's 7 notes averaged ~18 words and read like real accounts of a visit or call; the other five reps' 27 notes averaged ~5 words — all 27 of them under 9 words apiece. 1 of 6 reps is writing notes this report can actually use.
Capture Quality
One Rep's Notes Are Carrying This Report
Dana Whitfield's seven notes this month average about 18 words and read like real accounts of a visit or call — who, what, what's next. The other five reps' 27 notes average about 5 words apiece: “Stan pricing sent”, “pricing sent ok”, “quote sent no reply”. This isn't a knock on Tom, Marcus, Priya, Curt, or Reggie's fieldwork — they were in these accounts, same as Dana, the same month. It's a capture problem: whatever got said at the counter mostly didn't make it into the note. The practical effect is that this report can really only see Dana's Michigan territory. The other five reps' accounts may hold just as much — there's no way to know from what's written down.
Lakeshore Speed & Machine · Ironwood Engine Works · Kettle Moraine Machine
MPS-2043 Finish Issue — Legible In Michigan, Fog Everywhere Else
Four notes touch the Pro Series MPS-2043 head stud kit this month, across three accounts — and the same issue reads two completely different ways depending on who wrote it down. At Lakeshore, Dana logged: “Stopped by Lakeshore, saw Gary. Showed me a 2043 SBF kit, the finish looked hazy and rough. Left catalogs.” (May 4), then eight days later: “Called Gary on those 2043 stud kits — two came back rusty out of the box. Flagging it, will follow up.” (May 13). At Ironwood, also Dana: “Ironwood, Sal slammed. Mentioned a head stud kit that ‘looked used.’ Didn't get details. Left samples.” (May 5). Three notes, three legible descriptions, one rep. Then Kettle Moraine, in Curt Ellison's territory, where the exact same SKU shows up as: “KMM Stan, some 2043 issue? didn't say what” (May 5). If all six reps captured like Dana, this would already be a confirmed, quantified finish-defect finding across three accounts. Instead it's two-thirds visible — readable the moment it's in Dana's territory, opaque the moment it crosses into anyone else's.
Beacon Ridge ActionHave Dana keep pressing Gary and Sal for kit counts, purchase dates, and lot numbers — that's the part of this signal we can actually act on. Separately, get Curt back to Stan at Kettle Moraine with specific questions: what exactly he meant by “some 2043 issue”, and how many kits were affected.
Derby City Machine · Louisville, KY
A Signal Nobody Can Read
Reggie's entire note from Derby City reads, in full: “Derby — duncan?? idk what he meant. reorder” That's the whole record — no name for who asked, no context on what the customer wanted, no note on whether Marla knew what “Duncan” meant or whether the customer bought elsewhere instead. It could be nothing. It could be the same legacy-brand confusion that costs FoundryLine sales at other counters. From eight words, there's no way to tell.
Halstead Auto Warehouse · Livonia, MI
WD Asking About FoundryLine Dropship, Again
Dana's email note: “Halstead, Janet asking again about dropship on the FoundryLine hardware. Told her I'd take it to Merrick.” A follow-up call two weeks later just confirms “Fill rates fine, no complaints. June restock order coming” — nothing further on the dropship question itself. A warehouse-distributor contact raising this twice, in one of the only accounts with notes solid enough to trust, is a real opening — but there's no SKU list, no volume, no timeline. It's also worth naming: this is the one opportunity this month Dana's notes made visible at all. The same kind of ask could be sitting unread in any of the other five reps' accounts.
Beacon Ridge ActionHave Dana call Janet directly to scope the ask: which FoundryLine SKUs, expected volume, and whether Halstead wants a formal dropship proposal.
Rockford Racing Engines · Rockford, IL
Maybe A New Dyno Cell — Can't Confirm
Priya's entire note: “Rockford slammed, new dyno going in??” — the double question marks are hers. Her two follow-ups that month, “reorder studs, real busy there” and “pricing sent ok”, don't confirm or deny it. A shop investing in a new dyno cell would be a real expansion signal worth staffing for. At six words, even Priya doesn't sound sure what she saw.
Crossroads Cylinder · Kokomo, IN
Rebate Confusion, Unresolved
Marcus's entire note: “Crossroads — promo?? rebate thing, cust confused”. Something about the Spring Torque-Up rebate confused the contact at Crossroads — that's the whole record. Two later notes from the same account, “quote sent no reply” and “FL fill rate q, TBD”, never circle back to it. Whether this is a one-off or the same confusion is showing up at other accounts running the campaign, we can't say.
Bishop Brothers Racing · Findlay, OH
Returns Friction, Again
Tom's note: “Bishop, Terry — returns pita again. left cats”. “Again” implies this has come up before, but nothing here says what the actual returns issue is, how often it recurs, or whether it connects to the MPS-2043 finish problem turning up elsewhere. Terry still reordered three LS kits eleven days later, so it isn't costing the account — yet.
1
Only one note this month even claims a display placement — Tom's, in full: “TB Rick ok, put disp up”. The other two campaign-tagged notes, Marcus's “Crossroads — promo?? rebate thing, cust confused” and Reggie's “Bluegrass promo. kinebolt guy in again?”, are rebate and promo confusion, not display confirmations. Across 14 accounts touched, that's one placement on record, in a six-word note, with no photo or count. We can't tell whether Spring Torque-Up actually reached the rest of the territory.
2
Dana's three notes at Lakeshore and Ironwood are legible: hazy/rough finish, kits coming back rusty, a kit that “looked used.” Curt's note on the identical SKU at Kettle Moraine — “KMM Stan, some 2043 issue? didn't say what” — answers none of the same questions: no count, no date, no description. If this defect is spreading past Dana's territory, these notes won't show it.
3
Reggie's full note from Derby City: “Derby — duncan?? idk what he meant. reorder”. Nobody wrote down who asked, what they were told, or whether the customer bought a competitor's part instead. It's either nothing, or it's the same legacy-brand confusion FoundryLine has elsewhere — unresolvable from this note.
4
Several notes across five reps use some form of “reorder” with no SKU, quantity, or dollar figure attached — “small reorder ok”, “reorder, gd mo he says”, “Stan reorder, said he handled it”. Only Tom's “Terry reorder LS x3” names a product and count. We can't total May's reorder volume, or tell which of these already happened versus which are still, as Priya put it, “maybe next mo”.
5
Merrick asked for a target list and a goal-progress readout for the Torque-Up push. We don't have the signal depth to build either one from 34 notes — 27 of them three to eight words — there isn't enough detail per account to rank demand or confirm results.
6
TorqMax doesn't appear anywhere in the 34 notes this month. That's not evidence they're quiet — it just means nobody wrote it down. We have no read on their pricing, rebates, or counter-day activity anywhere in the territory.
| Q2 Goal | Target | Progress (as of May 31) |
|---|
| Merrick-tagged field touches |
240 |
not reliably measurable — count is soft |
| Torque-Up displays placed |
20 |
not measurable from current inputs |
| New-line adds (FoundryLine / Pro Series) |
8 |
not measurable from current inputs |
These are the three goals Beacon Ridge and Merrick agreed to for Q2. Even the touch count, which looked pullable from tagged contacts, isn't reliable this month: 27 of the 34 tagged notes are three-to-eight-word fragments that don't clearly say what kind of touch happened, with whom, or what came of it — so the raw count of 240-tagged activity is soft, not a confirmed number. Whether displays actually went up or new lines actually got added can't be reconstructed from notes this thin. This is a stub, not a scorecard.
1
Call Gary to confirm the 2043 finish complaints — how many kits, when they were bought, and lot numbers if he still has them. This is the anchor account for whether the 2043 signal is real, because Dana's notes are the only ones detailed enough to build a case from.
2
Get Curt back to Stan with real questions about the 2043 issue. Right now the entire record is eight words — “KMM Stan, some 2043 issue? didn't say what” — and explains nothing. This is the same finding as Lakeshore and Ironwood; it just hasn't been captured.
3
Ask Marla who the “duncan”-asking customer was and what happened next. Right now the whole note is eight words — worth a direct question before it's forgotten.
4
Scope Janet's FoundryLine dropship ask before it stalls a third time — which SKUs, what volume, and whether Merrick wants to build a formal program around it.
Field Coverage
6 reps
7 in-person visits evidenced
14 of 22 accounts appear in notes
1 of 6 reps writing notes this report can use
From Your Beacon Ridge Team
This month's report is built from 34 field notes — but really, it runs on seven of them. Dana Whitfield's notes on her Michigan accounts are the only ones solid enough to act on: a real 2043 finish problem at two accounts, a live FoundryLine opportunity at a third. Same six reps, same accounts, same May — but Tom, Marcus, Priya, Curt, and Reggie's 27 notes didn't capture enough to say what they saw. That's not a fieldwork gap; it's a capture gap, and Dana's own notes prove it's fixable — the conversations were there to write down, in her territory just like everyone else's. Flip to the Minecart version of this report to see what May looks like when all six reps capture at Dana's level, and past it.