Jett McCandless: project44, LSP44 and Supply Chain Data

At a glance

Most useful for explaining how timely logistics data and AI agents can support operational action.

Best for

Supply chain software campaigns about real-time visibility, lead-time analytics, and carrier connectivity.

Not for

Marketplaces that aim to cut out logistics service providers or brokers.

Key takeaways

Los Angeles-area lane booking-to-pickup shifted from four or five days to nine or ten.
People cannot monitor every shipment deviation at scale; AI flags patterns and agents contact carriers.
LSP44 is meant to back logistics service providers rather than replace them.

Check first: Confirm availability, terms, disclosure, and audience composition before contacting them.

Main ideas: Visibility was the last decade's edge; acting on the signal is this one's · Connectivity quality is the one metric that predicts logistics maturity · Lead times move constantly, but planning systems do not
Read first: Connectivity quality as the one metric that predicts logistics maturity

Sources for this section

What they are known for

Jett McCandless is a supply-chain technology founder known for building project44 and LSP44 around a practical challenge: logistics data is only useful when it is complete and timely enough to support action.

In his posts, he traces the shift from basic shipment visibility to connecting carriers, interpreting changing conditions, and automating routine responses.
He also argues that logistics service providers should be supported, not displaced.
Follow his work for concrete explanations of how data gaps affect planning and operations, and how people, software, and AI agents might divide the work.

McCandless makes broad technology claims tangible with operational examples.

He describes a Los Angeles-area freight lane where booking-to-pickup time shifted from four or five days to nine or ten, while a planning system still used the old figure; the mismatch can affect safety stock, delivery promises, and replenishment.
Elsewhere, he argues that people cannot monitor every shipment deviation at scale, and offers a specific division of labor: AI flags patterns, agents contact carriers, and people make consequential decisions.
Across the posts, the through-line is that better connectivity and current data should enable action—not just another dashboard.
His posts also include exceptions to a simple automation narrative: he says LSP44 is meant to back logistics service providers rather than replace them, and that different automakers can require nearly bespoke supply-chain use cases.
The reviewed material supports this account of his recent public work; it does not establish whether a signature book, show, or earlier work is also central to name searches.

Sources for this section

Ideas and priorities

Jett McCandless is a supply chain technology founder whose public writing argues about how logistics data becomes useful.

The recurring positions across these posts are: seeing a shipment is no longer the advantage, because the advantage has moved to finding the signal and letting automation act on it; connectivity quality is the single best measure of a company's logistics maturity; lead time is treated as fixed when it actually moves constantly; human oversight means deciding the few things worth deciding rather than reviewing everything; logistics providers should be backed rather than disintermediated; and one platform still has to serve operating models that barely resemble each other.

Visibility was the last decade's edge; acting on the signal is this one's

McCandless argues that being able to see your product at all used to be the advantage, and that seeing the problem is now table stakes.

The teams pulling ahead, in this argument, are the ones that can find the signal in the noise, understand what it means, and trust automation to act on it before a person is in the room.

He applies the same logic to data generally: knowing where things are and when they will actually arrive lowers the inventory a company has to carry, keeps customers from finding out late, and lets a business plan instead of react.
He points to Amazon, Walmart, and NVIDIA as companies whose unglamorous operating work eventually became the reason they won, and says his version of that work is location-and-arrival data.

His flagship event was renamed from decision44 to signal44 to mark the shift. In the same post he states that the company's agents are on pace for more than two million autonomous interactions with supply chain partners that year, all running in customer operations.

The rename is itself the marker of a change in his own framing: from helping companies decide, to acting on machine-detected signal.

Read original · Original 2

Connectivity quality is the one metric that predicts logistics maturity

Asked what single metric he would use to judge a company's logistics maturity, McCandless says connectivity quality, because it lets a company reach nearly every other supply chain goal while weak connectivity puts most of them out of reach.

His reasoning is historical: he started project44 in 2014 because he believed APIs were the best way to move information between the people who ship goods and the people who carry them, after finance, payments, and travel had already adopted them.

The limit was the carrier on the other end, because an API can only move as fast as the carrier's own innovation cycle, and a slice of carriers could not send complete, timely data.
Agents, in his account, fill those gaps and reach carriers directly where no API exists, which is the idea behind both project44 and LSP44.

He says he made this case to Joe Lynch on The Logistics of Logistics podcast, and traces the argument back to the 2014 decision to build on APIs rather than dashboards.

The argument moves from APIs alone as the mechanism to APIs plus agents, described as closing a gap that strained the original thesis.

Read original

Lead times move constantly, but planning systems do not

McCandless argues that most companies set lead time once and never change it, while actual lead time shifts constantly, so every safety stock target, promise date, and replenishment order tied to an outdated assumption is wrong.

His prescription is live data rather than a periodic review: better plans start with current lane-level information.

One over-the-road lane he monitors, Jurupa Valley to Los Angeles, took four or five days from booking to pickup in early 2025 and nine or ten days by that summer.

A planning system set up the previous year still says four, leaving plans off by nearly a week.
The 98 percent figure he cites comes from research by Lora Cecere at Supply Chain Insights, which he credits; Cecere's fix is set out in three chapters, the first live and ungated.

Read original

Human-in-the-loop means deciding the few things worth deciding

McCandless starts from volume: some customers move a thousand truckloads a day, and a single trailer can carry tens of millions of dollars of product.

Asking a team of people to watch every route, dwell, hot zone, and deviation cannot be done, he writes, not with more headcount and not with a better dashboard.

So the division of labour has to be honest about that: AI watches patterns and flags what moved because that is a volume problem, agents handle outreach and carrier contact, and a person makes the call when the call actually matters.
He defines human-in-the-loop as somebody deciding the things worth deciding, and calls reviewing everything theatre.

The thousand-truckloads-a-day customer and the tens-of-millions-per-trailer figure are the scale he uses to show why monitoring cannot stay manual.

Read original

LSP44 backs logistics providers instead of replacing them

Answering a recurring question about what LSP44 is, McCandless says he never wanted to build a marketplace or become the Uber Freight of logistics, and that cutting logistics service providers out was never on the table.

His reasoning is partly personal and partly market-based: LSPs are some of his closest friends and the people who helped him build the company, and he does not believe disintermediation is necessary or possible, because LSPs sit at the front of the innovation curve with the expertise and relationships to move. The post also describes project44 and LSP44 as two focused businesses rather than one.

He says the anti-disintermediation stance was the hardest part of early fundraising, because the venture pitch decks he saw argued that removing LSPs would make the market explode.

This is a position stated against the investor consensus he describes from his own early fundraising, not a change he reports in his own view.

Read original · Original 2

One platform still has to serve operating models that barely resemble each other

McCandless draws a lesson from an unfamiliar corner of logistics.

Auto supply chain conversations start at the production line, engineered to the minute, but the other half of the business serves every generation of every model going back decades, most of which stopped being built long ago: millions of SKUs against a simple constraint, that inventory costs capital while the person whose car broke this morning expects it fixed this week.

He adds a second surprise from the sector: put an American, a Japanese, and a German automaker on the same platform and they run their supply chains in ways that barely resemble each other, enough that use cases come out almost bespoke.
The tension sits against the idea of a single standard product.

His opening observation is the car people drove in high school; one of those still needs a part this week, and nobody has forecasted their way out of that problem.

Read original

Sources for this section

Start with their work

Connectivity quality as the one metric that predicts logistics maturity

If you only read one piece, read this.

It is the clearest statement of what McCandless has been arguing for a decade and what any partnership with him would actually be about.

McCandless picks connectivity quality as the single metric he uses to judge a company's logistics maturity, and says he told Joe Lynch exactly that on The Logistics of Logistics podcast.

He explains the origin of the idea: he started project44 in 2014 because he believed APIs were the best way to move information between the people who ship goods and the people who carry them, following finance, payments, and travel.
The limit, in his telling, was the carrier on the other end, because an API moves only as fast as the carrier's own innovation cycle, and a slice of carriers could not send complete, timely data.
Agents close that gap, handling the direct system-to-system connection where an API exists and reaching the carrier directly where one does not, which is the idea behind both project44 and LSP44.

For brands planning a campaign

A thought-leadership partnership framed around this thesis would be about data quality and coverage of the long tail of carriers, not another visibility dashboard. The natural editorial angle is 'what actually makes logistics data usable,' with McCandless as the person who named the metric.

Lead times move constantly, but planning systems do not

This is the most concrete, checkable piece of the set, and it answers the question of how McCandless turns a data claim into a specific example a buyer can evaluate.

McCandless argues that most companies set lead time once and never change it, citing industry research from Lora Cecere at Supply Chain Insights that this is true in 98% of organizations.

He then gives a named lane: Jurupa Valley to Los Angeles.
In early 2025, booking to pickup took four or five days; by that summer it took nine or ten.
A planning system configured the previous year still says four days, so every safety stock target, promise date, and replenishment order tied to that lane is off by nearly a week.
He points to Cecere's three-chapter fix, with chapter one live and ungated.

For brands planning a campaign

Directly usable for a brief about real-time visibility and lead-time data. A co-produced piece could pair his lane-level example with a sponsor's data or product, and the ungated-chapter structure is a model for a lead magnet that does not sit behind a form.

Renaming an event around signal instead of decision

It shows how McCandless frames the shift from seeing a problem to acting on it, which is the argument behind the two companies he runs.

McCandless writes that visibility was the edge in supply chain for a decade, and that seeing the problem is now table stakes.

The teams pulling ahead, he says, are the ones who can find the signal in the noise, understand what it means, and trust automation to act before a person is in the room.
That framing is why the flagship event was renamed from decision44 to signal44.
He states that the company's agents are on pace for more than two million autonomous interactions with supply chain partners that year, running in customer operations, and describes the event as bringing together customers running real orchestration, the project44 team shipping new AI, and operators facing the same disruption and cost pressure.
Registration covered Chicago and Amsterdam.

For brands planning a campaign

Shows the vocabulary a partner should adopt: signal over visibility, orchestration over dashboards. Useful if the campaign needs an event or launch moment, since McCandless already treats his own event as a platform for showing new AI work.

LSP44 is not a marketplace, and the reason is personal

Anyone considering a partnership needs to know where this person draws the line in the market, and this post states it plainly and explains the motive.

Answering a recurring question about what LSP44 is, McCandless says he never wanted to build a marketplace or become the Uber Freight of logistics.

He describes that as the hardest part of early fundraising, because every pitch deck pushed the idea of disintermediating logistics service providers.
His counter is that LSPs are some of his closest friends and the people who helped him build the company, that cutting them out was never on the table, and that he does not believe it is necessary or possible, since LSPs sit at the front of the innovation curve with the expertise and relationships to move.
LSP44 exists to back that rather than replace it.

For brands planning a campaign

This is the clearest statement of the company's positioning toward intermediaries. A partner whose model depends on displacing brokers or forwarders would be swimming against the stated thesis; one that sells into or alongside LSPs fits it.

What human-in-the-loop actually means at volume

It answers the practical question of who does what once automation arrives, using volumes big enough to make the argument obvious.

McCandless starts with scale: some customers move a thousand truckloads a day, and one trailer can carry tens of millions of dollars of product.

Asking people to watch every route, dwell, hot zone, and deviation cannot work, he writes, not with more headcount and not with a better dashboard.
So the division of labour has to be honest: AI watches patterns and flags what moved because that is a volume problem, agents handle outreach and carrier contact, and a person makes the call when the call matters.
He defines human-in-the-loop as somebody deciding the things worth deciding, not somebody reviewing everything, which he calls theatre.

For brands planning a campaign

A strong hook for a partnership aimed at operations leaders. It gives a sponsor a defensible way to talk about automation without promising headcount removal, and the 'theatre' line is quotable in campaign copy.

The half of the auto supply chain nobody plans for

It shows McCandless drawing a lesson from an unfamiliar corner of logistics, which is the kind of specific observation that separates this profile from generic supply chain commentary.

Opening with the car people drove in high school, McCandless points out that a vehicle long gone from any production line still needs parts this week.

Auto supply chain conversations start at the line, engineered to the minute, but the other half of the business serves every generation of every model going back decades, most no longer built: millions of SKUs against a simple constraint that inventory costs capital while the person whose car broke this morning expects it fixed this week.
He adds a second surprise from working in the sector: put an American, a Japanese, and a German automaker on the same platform and they run their supply chains in ways that barely resemble each other, enough that use cases come out almost bespoke.

For brands planning a campaign

Useful if a partner sells into aftermarket, parts, or multi-OEM manufacturing. It gives a campaign a concrete, non-obvious example and supports a message about configuration over one-size-fits-all platforms.

A decade of connecting carriers, shippers, and ports, in his own framing

It is the closest thing in this set to a summary of the career story and the company's claim on being first, written at a moment of public recognition.

Accepting FreightWaves' inaugural Vanguard Award, McCandless reads the word as going first so others can follow, and says that has been the story since 2014: over a decade connecting carriers, shippers, and ports until every truck, train, plane, and vessel was synchronized into one platform, with AI now being built on that base rather than on hype.

He ties the work to the 2am call about a shipment gone sideways, when nobody knows what is on it, who is waiting on it, or where to start looking, and says project44 and LSP44 were built so that call could eventually stop happening.
He credits carriers, customers, and the team, and thanks Craig Fuller and FreightWaves.

For brands planning a campaign

Best used as the credibility anchor in a pitch or intro. The 'going first' framing is ready-made for a partner that wants to position alongside a category-defining claim rather than a product feature.

Sources for this section

Topics and approach

Posts cited for each topic

From shipment visibility to actionable data3

McCandless says LSP44 is intended to support logistics service providers rather than replace them.

He also describes project44 and LSP44 as two focused businesses and presents their work as building on relationships with carriers, customers, and logistics partners.

For brands planning a campaign

For a campaign involving logistics providers or ecosystem partners, his posts offer a partnership-first perspective. Clarify the intended role of each business and partner in any proposed message; the posts do not establish a third-party partnership offer or sponsorship format.

Examples: Source 1 · Source 2 · Source 3

Sources for this section

Brands and businesses

Jett McCandless's posts document two owned businesses—project44, which they say they started in 2014, and LSP44, which they describe building alongside it.

The posts also mention industry relationships: FreightWaves recognized project44 with its Vanguard Award and hosted McCandless at F3; they spoke at the Armstrong & Associates 3PL Summit and shared a stage with AVRL and Mastery Logistics Systems; and they appeared on The Logistics of Logistics podcast. The retained posts do not document sponsorship, affiliate, client, or investment relationships.

project44

Owned business

Jett McCandless says they started project44 in 2014 and describes it as a company they built and lead.

Posts describe project44's carrier connectivity, AI agents, and signal44 event. The posts present project44 as their company, not a client or sponsor.

Original disclosure

I started project44 in 2014 because I believed APIs were the best way to move information between the people who ship goods and the people who carry them.

View example

LSP44

Owned business

McCandless describes LSP44 as a business they built alongside project44.

Jett McCandless writes about supply chain technology from the founder's side: how logistics data gets collected, cleaned, and acted on.

A good way into the posts is his argument that shipment visibility has stopped being the advantage and the edge now sits in finding the signal and letting automation act before a person is in the room.

From there, follow his lead-time post, which uses one over-the-road lane whose booking-to-pickup time stretched from four or five days to nine or ten to show why plans built on fixed assumptions drift.
His posts on monitoring volume with AI and agents, on what human-in-the-loop should actually mean, and on backing logistics providers instead of replacing them explain how he divides work between software and people.
Readers who want the mechanism should start with connectivity and APIs; readers who want industry context can begin with his Amazon, Walmart, NVIDIA, and auto-aftermarket examples.

Hugh Williams

Both write about end-to-end supply chain thinking for a professional audience and treat how people frame a problem as the first obstacle.

Williams argues that process and technology changes stall without breaking silo thinking, which is close in spirit to McCandless's point that seeing a problem is not the same as acting on it.

Williams works on organizational mindset, regulation, and complexity in life-sciences and cross-border supply chains; he does not describe the data or platform mechanics McCandless spends his posts on. His retained posts are also much older, from 2014 and 2016.

Read original · Original 2

Indira Uppuluri

Both write about using technology and automation to read demand and place inventory across a large supply chain network, and both reach for seasonal examples to make the point concrete.

Uppuluri writes from inside a retailer's supply chain operation, describing peak-season execution, shifting order patterns, and the associates who keep it running. McCandless writes as a technology founder about the data layer and how decisions should be split between software and people.

Read original · Original 2

Sidney Severson

Severson works on the same location layer McCandless builds his arguments on: geofencing libraries, a large database of supply chain locations, and getting accurate data to customers quickly.

Severson's posts are short product and scale updates, such as standing up 15,000 locations in days, plus conference recaps aimed at customers. They do not develop a position on how monitoring, automation, and human judgement should be divided.

Read original · Original 2

Sources for this section

Audience

Jett McCandless’s posts give a clear content-fit signal for a supply chain software campaign: they discuss real-time logistics data, carrier connectivity, and how changing lead times affect planning.

They do not establish who makes up the audience. Before committing, ask for recent LinkedIn audience insights and, if the brief requires reaching supply chain decision-makers by role or seniority, documented audience survey results or another source that measures those attributes.

Sources for this section

Partnership options

Nothing in the reviewed material shows a published partnership programme.

Jett McCandless does not post sponsorship packages, rates, media-kit terms, or a booking route, and no linked sponsor policy or rate card appears in the evidence reviewed.

What the posts do show is a founder who speaks at industry events and promotes events his own companies run, which is the practical shape a partnership would take here.
For a brand building a thought-leadership partnership around real-time logistics visibility and lead-time data, the realistic approach is to reach Jett McCandless as an executive commentator through the venues already visible in the material: signal44, project44's flagship conference (registration open for Chicago and Amsterdam), F3: Future of Freight Festival, where Jett McCandless held a fireside chat with Craig Fuller, and the Armstrong & Associates 3PL Summit, where Jett McCandless joined a panel on the brokerage tech stack.
Podcast appearances cut the same way; Jett McCandless discussed connectivity quality on The Logistics of Logistics with Joe Lynch.
None of this is evidence of a paid sponsorship format, and payment should not be assumed from any event or company named.
Because formats are stated only as an empty list, a buyer should treat any sponsorship arrangement as an open commercial conversation rather than a purchasable package, and should confirm availability, terms, and disclosure directly.

Sources for this section

Campaign fit

A campaign to shortlist

Fit, with two conditions to settle before committing: there is no published partnership programme, and no evidence about who his audience actually is.

Brief

A supply chain software company building a real-time visibility and lead-time analytics product wants a thought-leadership partnership with Jett McCandless: co-produced commentary, a joint session or resource on why visibility alone no longer helps, and use of his name and material in campaign promotion.

Conditions

Nothing in the reviewed material shows sponsorship packages, rates, media-kit terms, or a booking route. Treat any arrangement as an open commercial conversation and confirm availability, terms, and disclosure directly rather than assuming a purchasable package (see the accepted partnership section).
Audience composition is unmeasured. The posts show subject-matter fit, not that the audience contains supply chain decision-makers by role or seniority. If the brief requires that, ask for recent audience insights or a documented survey before committing.
His voice is executive commentary and company advocacy. A sponsor's product claims have to survive his own framing of signal, automation, and coverage gaps; a message that reads as a feature pitch will not travel in his register.

Why

McCandless already argues the sponsor's core thesis in public and with specifics. He names connectivity quality as the single metric he uses to judge logistics maturity, and traces it to the gap that APIs alone cannot close when a carrier cannot send complete, timely data. A partner that sells coverage of the long tail of carriers is arguing alongside him rather than inserting a message into his content.

The lead-time theme is documented with a checkable example rather than a claim. In one post he contrasts a Jurupa Valley to Los Angeles lane, where booking to pickup moved from four or five days in early 2025 to nine or ten by that summer, against planning systems still configured at four days, and lists the consequences: safety stock targets, promise dates, and replenishment orders tied to that lane off by nearly a week. That is exactly the material a lead-time data campaign wants.

The vocabulary is settled and quotable. McCandless says visibility was the edge for a decade and is now table stakes, and that the teams pulling ahead find the signal in the noise, understand it, and trust automation to act before a person is in the room, which is why the flagship event moved from decision44 to signal44. A partner can adopt signal over dashboard without re-educating the audience.

There is an operating-model argument, not just a technology claim. McCandless describes a division of labour at volume: AI watches patterns, agents handle carrier outreach, and a person decides the moments that matter, calling full human review of everything theatre. That gives a campaign a defensible way to talk about automation without promising headcount removal.

He has an existing event and industry platform to hang a launch on, and posts about appearing at F3: Future of Freight Festival, the Armstrong & Associates 3PL Summit, and The Logistics of Logistics podcast. A partnership can travel through those venues rather than requiring a new format.

He states a partnership-first market position: LSP44 is meant to support logistics service providers, not replace them, and he says he never wanted to build a marketplace or become the Uber Freight of logistics. Partners that sell into or alongside service providers are aligned with that stance.

When to choose a specialist

Poor fit, for a reason that is documented rather than a matter of tone.

Brief

A digital freight marketplace whose positioning is that shippers should cut out brokers and third-party logistics providers wants a paid short-form video push with Jett McCandless as the face of an aggressive disintermediation message, aimed at small carriers and owner-operators.

What would change this

A material change in the published position on intermediaries, or a campaign reframed as supporting service providers rather than removing them, would change the answer. A published sponsorship or booking policy would also change what can be bought, though not the message conflict.

Why

The brief's central claim contradicts what McCandless has already said in public. He writes that he never wanted to build a marketplace or become the Uber Freight of logistics, that disintermediating logistics service providers was pushed at him during fundraising and he refused it, that LSPs are some of his closest friends and the people who helped him build the company, and that he does not believe cutting them out is necessary or possible. A campaign built on removing intermediaries would have him arguing against his own stated position, and readers who have seen that post would notice.

There is no documented paid format to buy. The reviewed material contains no sponsorship packages, rates, or booking route, so the brief assumes a commercial product that the evidence does not show exists.

The content shape does not match the request. The material is long-form written argument aimed at people who run supply chains, built around operational reasoning and named examples rather than short consumer-style video. Nothing reviewed shows McCandless producing that format.

Audience evidence points away from the brief's target. The posts are written for operators, logistics technology buyers, and industry peers; nothing reviewed establishes reach among small carriers or owner-operators, and no audience composition data was available at all.

One post explicitly credits carriers, customers, and team rather than any intermediary-free model, and another frames the work as backing service providers rather than replacing them. The brief would require McCandless to adopt a message his own recent writing rejects.

A worked campaign example

Angle

Own the lead-time assumption, not the dashboard. Frame the campaign around the fact that plan settings age while the network moves, and use McCandless's own lane example as the spine. Most planning systems were configured once and still say what a lane used to take; the campaign shows what that costs and what live data does about it.

Brief

The supply chain software brief: a thought-leadership partnership on real-time logistics visibility and lead-time data, delivered as a co-produced piece plus one live session.

Deliverables

One long-form co-produced piece or interview running the four steps above, with the lane example shown in full so a reader can map it onto a lane of their own.

One live session at signal44 in Chicago and Amsterdam, where McCandless already describes customers running real orchestration, the project44 team shipping new AI, and operators facing the same cost pressure.

One ungated short resource in the style he already endorses: in the lead-time post he points to a three-chapter fix with the first chapter live and ungated. Keeping the first piece ungated matches his stated preference and fits a thought-leadership rather than lead-capture goal.

Risks and open items

Confirm commercial terms, disclosure, and availability directly. No sponsorship package, rate card, or booking route appears in the reviewed material.

Confirm audience fit against the sponsor's target roles; no audience composition evidence was available.

Two posts describe appearances on The Logistics of Logistics and a fireside chat with Craig Fuller at F3, but no transcripts or recordings were reviewed, so treat those as reported appearances rather than verified content.

No transcripts of signal44 sessions were reviewed either; the event is described from McCandless's own post, including the claim of more than two million autonomous interactions planned with supply chain partners for the year. That figure is his statement and should be labelled as such.

If the campaign needs the aftermarket or multi-OEM angle, the automotive post offers a concrete example of parts demand for models long out of production and of American, Japanese, and German automakers running their supply chains differently enough that use cases come out almost bespoke. It is a supporting example, not a quantified result.

Why it works

The sponsor's subject matter is already McCandless's argument, so the partnership adds distribution and credibility rather than asking him to change position.

The lane example converts an abstract data claim into something a buyer can evaluate this week, which is the standard the profile's work section holds up.

It uses vocabulary he has already established, signal over visibility and orchestration over dashboards, so the campaign does not have to teach a new frame.

It stays inside his stated market stance toward service providers, avoiding a message conflict that would surface in comments.

Worked sequence

Detail: Lead with McCandless's statement that most companies set lead time once and never change it, cited to Lora Cecere at Supply Chain Insights, who puts it at 98% of organizations. Attribution stays with the source named in the post.
Step: Opening claim

Detail: Use the Jurupa Valley to Los Angeles lane: booking to pickup at four or five days in early 2025, nine or ten by the summer, against a system still saying four, so safety stock targets, promise dates, and replenishment orders on that lane are off by nearly a week. This is the part a reader can check and take into their own planning review.
Step: The concrete example

Detail: Bring in the connectivity argument: APIs move only as fast as the carrier's own innovation cycle, a slice of carriers cannot send complete, timely data, and agents close that gap where no API exists. This is where the sponsor's product enters as coverage, not as another visibility layer.
Step: Why it happens

Detail: Close on the operating model: AI watches patterns and flags changes, agents handle carrier contact, a person decides the moments that matter. The reader leaves with a division of labour, not a dashboard tour.
Step: What to do with the signal

Sources for this section

Who else to consider

Sidney Severson

Choose Sidney Severson over Jett McCandless when the campaign's audience is the data and operations people who build a visibility stack rather than the executives who buy one.

The reviewed posts work at the level of the data itself: polygon accuracy in a geofencing library, standing up 15,000 monitored locations in days rather than months, and the argument that this comes from repeatable processes and a database of millions of supply chain locations, not shortcuts. The line that accuracy gets you trust while scalability lets you earn it at scale is a specific technical claim a location-data vendor can build a piece around, and it sits closer to the product than McCandless's executive argument about why visibility stopped being the edge.

The tradeoff is reach and depth.

The two reviewed posts are short and promotional: one is a conference recap from Samsara Beyond and the other is a bulleted capability post.
Nothing reviewed shows an event platform, an award, a co-authored book, or the sustained long-form argument McCandless produces, and no audience information was reviewed for either creator.
A sponsor that needs a well-known name and ready-made distribution gets less here than from McCandless, even though the subject match is tighter.

Examples: Source 1 · Source 2

Indira Uppuluri

Choose Indira Uppuluri when the brief targets retail or consumer-goods demand planning at enterprise scale rather than carrier connectivity.

The reviewed Walmart posts describe preparing a national supply chain for seasonal demand months in advance, using technology and automation to understand demand and place inventory, and leaning on associates plus technology to hold service through the holiday peak.

That is a first-person view from inside one of the largest networks in the world, and it speaks directly to forecast-driven planning, which is the buyer problem behind lead-time data.
For a brief that needs a retail-scale operator voice, this is a better match than a logistics-technology founder.

The tradeoff is independence and range.

The posts read as employer advocacy: they promote Walmart's supply chain organisation and link to Walmart material, so the voice is a company position as much as a personal one, and the topics stay inside retail seasonal execution.
There is no visibility-data or connectivity thesis to adopt, no reviewed evidence of an independent media platform or event, and no audience or commercial-availability information.
A co-produced thought-leadership piece that needs an independent, quotable point of view is a narrower fit here than the subject proximity suggests.

Examples: Source 1 · Source 2

Hugh Williams

Choose Hugh Williams when the campaign's angle is organisational change and supply chain thinking rather than logistics data.

The reviewed posts argue that the real barrier to end-to-end supply chain work is traditional siloed thinking, that supply chain thinking means breaking the mould rather than learning new processes or technologies, and that rising complexity brings more regulation across cool chain, emerging markets, cross-border trade, and M&A. A sponsor framing a partnership as a transformation or change-management conversation, not a product conversation, gets more from that framing than from a data-platform pitch.

The tradeoff is recency and specificity.

The two reviewed posts are dated 2014 and 2016, around a decade before the other material on this page, so nothing reviewed shows current activity, current themes, or the state of this work now.
The posts are short reactions and conference notes rather than sustained analysis, and they address mindset and regulation rather than real-time visibility or lead-time measurement.
A visibility-data campaign would have to translate the argument before it fit, and the small, dated sample means the comparison rests on thin evidence.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief: Jett McCandless

Download

Worked example: real-time visibility and lead-time data

Download

Sources for this section

Research methodology

This profile is built from ten posts published on Jett McCandless's own LinkedIn account, each read in full.
The posts are first-person commentary on supply chain data: connectivity quality and APIs, a named freight lane whose lead time changed while the planning system did not, a proposed division of labour between AI, agents and people, the company's stated position on logistics service providers, an automotive aftermarket example, and recaps of an award, two conferences and a podcast appearance.

Publication dates were supplied for only a small part of the set, so the material is organised by theme rather than as a timeline, and it is a sample of recent activity rather than a complete career record.
The available evidence does not identify a signature book, show, or earlier career work beyond project44 and LSP44; that gap is stated in the profile rather than filled.
No transcripts or recordings of the podcast and conference appearances described in the posts were available, so those are reported as the posts describe them, and figures such as the company's stated pace of autonomous interactions come from McCandless's own posts.
No audience composition data, sponsorship terms or booking route appeared in the reviewed material.

Recent engagement

Across their last 7 LinkedIn posts, the median post got 68 reactions and 4 comments. Checked 2026-11-02.

Brands they talk about

Amazon Walmart Uber FreightWaves