Case Study: Series B Supply Chain SaaS — Vertical Authority for Logistics Buyers in 14 Months

This case study is a composite, anonymized account based on real client engagements. Client identity, exact metrics, and specific dates have been generalized to protect confidentiality while preserving the strategic substance of the work.

The starting position

The client was a Series B supply chain SaaS — a shipment visibility and predictive ETA platform for mid-market shippers — competing against Flexport, Project44, FourKites, E2open, and several specialized regional platforms. ~140 employees, $22M ARR. The product had genuine technical differentiation in carrier integration coverage and real-time ETA accuracy, but their organic visibility lagged far behind their product quality and customer satisfaction.

Baseline: DR48, 720 referring domains, 36 demo requests per month from organic. No top-10 rankings on “shipment visibility platform,” “supply chain visibility,” or “transportation management system” commercial head terms.

The strategic diagnosis

Logistics buyer audience was underserved. Supply chain buyers (VP Supply Chain, Director of Logistics, Chief Supply Chain Officer at 100-2,000 person shippers) read specific logistics publications — Supply Chain Dive, Supply Chain Brain, Logistics Management, JOC, FreightWaves, Logistics Bureau, MH&L. The site had no presence in these publications.

Vertical-within-vertical specialization was open. “Shipment visibility for retail,” “supply chain platform for manufacturing,” “TMS for food and beverage” — vertical sub-segments had thinner competitive coverage than horizontal terms.

Original logistics data was unutilized. The platform processed billions of shipment events but had published no proprietary data — no ETA accuracy benchmarks, no carrier performance comparisons, no industry trend analysis.

The program design

Workstream 1: Logistics publication digital PR. Supply Chain Dive, Supply Chain Brain, Logistics Management, FreightWaves, JOC, MH&L. Sustained presence through guest contributions, expert sourcing, and reactive PR around carrier and shipping news.

Workstream 2: Vertical sub-segment content clusters. Four sub-vertical mini-clusters — retail, manufacturing, food and beverage, automotive. Each cluster of 6-8 pages covered vertical-specific use cases.

Workstream 3: Annual Logistics Performance Index report. Quarterly logistics performance benchmark report based on aggregated platform shipment data — on-time performance by carrier, ETA accuracy benchmarks, transit time trends. Designed for tier-1 logistics publication coverage.

Workstream 4: Comparison cluster. Comparison pages against Project44, FourKites, Shipwell, Convoy (when active), and regional platforms. Substantive technical comparisons including carrier coverage maps and integration patterns.

Workstream 5: Conference and trade show presence. CSCMP Edge, MODEX, NRF (for retail), Manifest, Home Delivery World. Speaking submissions and editorial relationships with conference media.

The execution timeline

Months 0-3: Foundation. Logistics publication relationship building. First Supply Chain Dive expert quotes. Quarterly Logistics Performance Index data infrastructure.

Months 4-6: First sub-vertical cluster (retail) live. First quarterly LPI report launches with Supply Chain Dive and FreightWaves coverage. DR 48 → 54.

Months 7-9: Second sub-vertical cluster (manufacturing) live. Second quarterly LPI report. Conference talk delivered at CSCMP Edge. DR 54 → 60.

Months 10-14: Sub-vertical clusters fully built across four verticals. Quarterly LPI report cadence sustained. “Shipment visibility for retail” rank 3. “TMS for manufacturing” rank 5. AI search citations on supply chain technology queries.

The outcomes

Authority. DR48 → DR64. Referring domains 720 → 1,640. Logistics publication coverage (Supply Chain Dive 7x, Supply Chain Brain 4x, FreightWaves 5x, JOC 2x, MH&L 3x).

Rankings. Top-3 on five vertical-specific commercial terms. Top-10 on “shipment visibility platform” head term. AI search citations on supply chain visibility category queries.

Pipeline. Demo requests 36/month → 168/month (4.7x). Organic-attributed pipeline contribution 8% → 27%. Estimated organic-attributed ARR addition over 14 months: ~$3.4M.

The buyer journey context

The mid-market supply chain buyer is typically a VP Supply Chain or Director of Logistics at a 100-2,000 employee shipper. Buying cycle 12-26 weeks (slower than horizontal SaaS) involving supply chain leadership, IT (for integration), procurement, and sometimes warehouse operations leadership. The buying committee weights peer credibility heavily — references from similar shippers in the same vertical drive decisions.

Publication authority and conference presence build the recognition that produces inbound referrals. Without it, even technically superior platforms lose to established competitors purely on familiarity.

Program cost and team structure

Engagement ran at $28K/month for 14 months. Total program investment: ~$392K. Organic-attributed ARR addition (~$3.4M) represented ~8.7x return. Internal team allocation included a dedicated supply chain industry analyst (former carrier operations leader on the customer success team) and the CEO committing to quarterly LPI report launches.

Specific tactics that mattered

Quarterly data report cadence. Most data reports launch annually. The quarterly cadence created a sustained drumbeat of tier-1 publication coverage and AI search citations. Each report compounded on the prior one’s authority.

Former-operator industry analyst. Internal industry analyst with carrier operations background lent practitioner credibility to content and earned consistent expert-sourcing placements.

Vertical sub-segment specialization. Building separate sub-vertical clusters captured vertical-specific search demand and made the platform discoverable to vertical buyers who searched in vertical-specific vocabulary.

How we measured

Beyond standard metrics: vertical-by-vertical pipeline contribution (identified which sub-vertical clusters drove most pipeline), conference talk influence on subsequent deal flow, and LPI report citation count across logistics publications and AI search systems.

What we’d do differently

Conference presence should have started earlier. CSCMP Edge and MODEX talk recordings compound for 18+ months post-conference. Earlier conference investment would have built the long-tail authority faster. Future engagements front-load conference submissions in month 1, not month 6.

Three lessons that generalize to other operations-tech engagements

Lesson 1: Quarterly data report cadence creates compounding authority that annual reports don’t. Most data reports launch annually. The quarterly cadence created a sustained drumbeat of tier-1 publication coverage that compounded into category authority. The discipline is harder operationally — you need sustained data infrastructure — but the return justifies it for data-rich categories.

Lesson 2: Former-operator subject-matter experts produce content that wins audience trust. A former carrier operations leader writing about carrier performance benchmarks carries authority that a marketing-team writer cannot replicate. The signaling repeats across operations-tech, vertical-specialist SaaS, and any category where practitioners evaluate content by author credibility.

Lesson 3: Vertical sub-segment specialization captures search demand that horizontal positioning misses. “Shipment visibility for retail” and “TMS for manufacturing” captured search intent that “shipment visibility platform” did not. The sub-vertical clusters produced disproportionate pipeline impact relative to their content investment cost.

What changed inside the team

By month 14, the supply chain industry analyst had become a recognized industry voice — quoted regularly in Supply Chain Dive and FreightWaves, invited speaker at multiple logistics conferences, and a frequent guest on supply chain podcasts. The personal brand built the inbound referral flow that paid-channel investment never produced.

What this means for your supply chain program

Supply chain and logistics SaaS rewards publication authority in the specific logistics publication ecosystem, quarterly data report cadence, and vertical sub-segment specialization. The patterns translate to adjacent operations categories — procurement tech, ERP, warehouse management. See the case studies hub for adjacent patterns.

Adjacent operations-tech categories where these patterns translate

Procurement SaaS. Different publication ecosystem (Spend Matters, Procurement Leaders, CIPS), similar buyer dynamics (Chief Procurement Officer, VP Procurement at mid-market and enterprise shippers). The quarterly data report cadence and former-operator authorship patterns translate directly.

ERP and warehouse management. Longer sales cycles, more involved buying committees, but the vertical sub-segment specialization and trade publication authority patterns hold. Conferences shift to Modex, ProMat, and category-specific industry events.

Last-mile and fleet management. The data report cadence works exceptionally well in this category because fleet data is rich and journalists actively want it. Combine with conference presence at Home Delivery World and NPMHU events for compound authority.