# Ryan Kowalski, Operations Manager at Meridian Freight Partners — read of Fleet Growth Signals, June 15 2026

> 8 years in 3PL ops, currently managing carrier relations for a 30-person brokerage in Columbus. Been sketching a "carrier intelligence tool" on paper napkins for 18 months and never built it.

## How I got here

LinkedIn ad hit me on my lunch break. The headline was something like "know when your carriers are expanding before they call someone else." I'm not even sure what the exact copy was -- I just know it was enough to make me stop mid-scroll because I had literally complained about this exact problem to my ops director two weeks ago. I clicked, read the whole page in maybe 4 minutes, and now I'm writing this because I can't figure out if I'm looking at a product I can buy or a business plan someone is selling me for $99.

## What I clicked first

"Know When Your Carriers Are Growing" landed. Clear, specific, I immediately knew what it was promising. The "3-truck expansion threshold within 90 days" line is the first thing that made me think someone in this space actually wrote this copy, because that threshold makes sense as a trigger. Under 3 trucks it's noise. Over 3 trucks in 90 days, someone needs to make a purchasing decision fast.

The "FMCSA databases, state transportation filings, commercial vehicle registrations, and hiring signals daily" line made me stop and think about whether this is actually possible. I know how dirty FMCSA data is. That part I'll come back to.

## Where I paused

The enrichment section: "verified contact information for the carrier's fleet manager, operations director, and procurement lead." I stopped there because I've never seen all three of those at a 6-truck carrier. At that size you're talking to one person who does all three jobs and his name is probably Mike and he answers a flip phone. I don't know if the product assumes larger carriers, but if the growth trigger fires at 3 trucks (so you're watching 5-to-8-truck carriers), the "procurement lead" thing feels like an enterprise feature description dropped into a small-carrier context.

That gap made me wonder how much of this was tested against real carrier data versus assembled from logical-sounding features.

## What I distrusted

The scoring system on the page itself. They give their own idea a "financial upside: 2/10" and project "Year-1 take-home: -$21,200" and "1 in 8 Meaningful-success odds." I actually respect the transparency, but the framing broke my mental model of what I'm buying. Is that MY projected loss if I BUILD this product? Or is that the founder's projection for their own business? And if you already know your idea has a 2/10 financial upside, why are you selling it to me for $99?

Also: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." That line is wild. I read the whole hero section -- "Growth Detection Engine," "Enriched Decision-Maker Intelligence," "Flexible Integration," "Customizable Monitoring Parameters" -- all written as if this is a shipping product. Then I hit that disclosure and realized the hero is describing a product that does not exist. The copywriting is for a product. The pricing is for a business idea. Those are two different things and this page is trying to be both at once.

## What would convince me

One real example with real data. Not "when a carrier crosses the 3-truck threshold you get an alert." I want: "Summit Transport in Memphis went from 7 to 11 trucks in 67 days. Here's the alert that fired. Here's the contact we surfaced. Here's the outreach email it triggered. Here's what happened."

And for the FMCSA piece specifically: FMCSA carrier data has notorious lag. Some state-level updates are weeks old. If you're saying "daily monitoring," I want to know what the actual latency is between a carrier registering a new vehicle and you detecting it. That's not a gotcha question, that's the whole product.

## What I'd ask in an email reply

1. When you say "working code starter" at the $99 tier, what does that mean in practice? Is it a deployed app with a database, or is it a repo I'm expected to stand up myself? And what tech stack?

2. The Fermi estimate says I'll lose $21K in Year 1. Who is the "I" in that sentence? Are you modeling me as the builder selling this as a SaaS, or are you modeling me as the freight broker buying subscriptions?

3. Have you actually pulled FMCSA data and run it against a real carrier list to see how far behind the registrations lag? I'm not trying to be difficult, I'm asking because I almost built this myself and that's where I got stuck.

## Verdict: on-the-fence

The core idea is real and the pain is real and the honesty about the odds is unusual enough that I didn't close the tab. But the page never resolves whether it's selling me a product to use or a business to build, and that confusion is doing real damage. If the $5 dossier opened with a one-paragraph answer to "what exactly are you selling me," I'd buy it in 30 seconds.

---
*Memo by skeptic persona, generated 2026-06-15. Studio breaks own self-grading loop.*