Shipping data is already there; merchants lack interpretation, not more data.
AI agents should let people ask for shipping outcomes instead of clicking through software.
MCP examples include comparing rates, creating labels, handling returns, and generating shipping-cost summaries.
Check first: Confirm whether they accept sponsored work and can share recent audience data.
Main ideas
Shipping data is already there; what merchants lack is interpretation · AI agents should let people ask for shipping outcomes instead of clicking through software · New value should not require setup work
Gabe Martini explains Shippo products for e-commerce shipping.
Their posts cover Shippo Intelligence, which presents shipping data through dashboards and AI-powered recommendations, and Shippo’s MCP workflows, which let users request actions such as comparing rates, creating labels, or handling returns.
The examples make the posts useful to follow if you want to see how shipping tools are presented as practical ways to understand costs, delivery, and operations.
The posts connect product features to decisions a merchant or builder can recognize.
For Shippo Intelligence, Gabe moves from dashboards for spend, labels, and shipments to outcomes such as finding hidden costs or spotting delivery problems.
For MCP, Gabe makes the AI proposition concrete with sample requests, including finding the fastest and cheapest shipping option and generating a shipping-cost summary.
That range—from buyer-facing benefits to usable workflow examples—is the clearest distinctive contribution in this small sample.
The posts also show product-launch and update messaging.
Across Gabe Martini's posts, Gabe Martini argues that shipping data is already available to most e-commerce merchants and that the real problem is knowing what it means and what to do next.
Read more
Shippo's products are presented as the interpretation layer: dashboards that explain costs and trends, an AI digest that recommends next steps, and agent workflows that let someone ask for a shipping outcome instead of operating a tool. A second recurring priority is removing effort — again and again the posts promise no integrations, no setup, and answers in seconds, aimed at API customers, platform builders, and internal operations teams.
Shipping data is already there; what merchants lack is interpretation
Gabe Martini repeatedly frames shipping data as an underused asset and locates the difficulty not in collecting it but in understanding it.
Read more
Many merchants can see their shipping numbers but cannot tell what changed, why, or what to do about it, so software should close that gap rather than add another data source. The posts support this argument with specific dashboards and the decisions they enable, presenting the product as clarity, control, and confidence rather than raw reporting.
The Shippo Intelligence launch post describes three dashboards—Spend, Labels, and Shipments—built to uncover hidden costs, catch volume trends early, and monitor delivery performance in real time, with peak season named as the moment this matters most. A landing-page post for the same product sharpens the claim to "not just into what is happening in shipping, but why," listing actions such as acting on delivery issues before customers notice.
The later Intelligence upgrade adds a weekly AI-powered digest that reports what changed and recommends next steps, plus interactive maps and surcharge and adjustment dashboards. The stated goal shifts from showing merchants what happened to telling them what to do next.
AI agents should let people ask for shipping outcomes instead of clicking through software
The MCP post argues that agentic e-commerce moves shipping from clicking and searching to asking and doing.
Read more
Rather than walking through a portal to compare rates or create a label, a person or agent states the outcome they want and gets a finished action or answer back. Gabe Martini positions this as built on Shippo's multi-carrier API and aimed at three audiences: merchants, platforms, and internal operations teams—in other words, people building workflows on shipping infrastructure as well as people shipping orders.
The post gives concrete commands rather than abstractions: "create a return for this order," "give me the fastest and cheapest shipping option," and "generate a P&L summary of my shipping costs," with the claim that production-ready actions and insights come back in seconds without complex integrations or deep logistics expertise.
The product posts promise that the tools work immediately: no integrations, no setup, everything inside the Shippo API portal.
Read more
This is an argument about adoption as much as features—the value of shipping analytics depends on merchants turning it on during a busy period, so the posts cast friction as the obstacle to remove. The MCP post similarly emphasizes avoiding complex integrations.
The launch and landing-page posts both say insights appear with no integrations and no setup, and that access is through the portal API customers already use. The MCP post makes a similar claim for agent workflows, saying agents can handle rate shopping, label creation, tracking, returns, and analytics without deep logistics expertise.
Shipping is complex enough that each release has to be taught, not just announced
The posts consistently pair an announcement with a route to more detail—a press release, landing page, or documentation—and follow a launch with a second post that repeats the message and points to outside coverage.
Read more
The posts say directly that shipping is one of the most complex parts of running an e-commerce business, so each new capability needs explanation before it can be adopted. The tone stays team-oriented, crediting the people who built the release and signalling more to come.
The Shippo Intelligence launch post thanks the team and links a press release; the landing-page post points readers to a new page showing the product in action; the upgrade post directs API customers to the portal with press-release and learn-more links. A companion post points to industry coverage of the same upgrade, repeats the three new capabilities, and closes with "More to come."
Start here to see the product most associated with Gabe M. in the posts here, and the problem it is meant to solve.
Read more
The post states plainly what shipping data is worth and what the tooling does with it, which answers the newcomer question "what does this person actually work on?"
The post announces that Shippo Intelligence is live.
It argues that shipping data is one of the most underused assets in e-commerce, then describes three purpose-built dashboards — Spend, Labels and Shipments — that surface hidden costs, catch volume trends early and monitor delivery performance in real time.
The pitch leans on ease: no integrations, no setup, insights delivered inside the Shippo API portal.
Peak season is named as the moment the tooling matters most, and the post closes with credit to the team.
For brands planning a campaign
This gives a partner a ready-made frame for a shipping-analytics campaign: three dashboards as the concrete product hook, peak-season timing as the urgency and “no integrations, no setup” as the objection to answer in copy. It also shows the creator is comfortable writing a full launch announcement, not just short reactions.
Read this one to see how the same product is translated into buyer-facing language.
Read more
It shows how they talk to fast-growing brands rather than developers or existing customers.
This landing-page post targets fast-growing e-commerce brands.
The claim is a specific kind of visibility: not just what is happening in shipping, but why.
The benefits are listed as actions: uncover hidden costs, spot demand trends early and act on delivery issues before customers notice.
The no-setup, no-integration promise repeats, and the post points readers to a new landing page rather than documentation.
For brands planning a campaign
Useful as a copy reference.
A partnership could reuse or test this benefit-first structure.
It shows the creator will write conversion-oriented marketing text, not just product announcements — relevant if a campaign needs landing pages, ad copy or email.
This is the clearest statement about AI agents in shipping, with worked commands rather than abstractions.
Read more
It shows what they say about AI workflows and who those workflows are for.
The post frames agentic e-commerce as shipping moving from clicking and searching to asking and doing.
Built on Shippo's multi-carrier API, MCP is described as letting AI agents handle rate shopping, label creation, tracking, returns and shipping analytics without complex integrations or deep logistics expertise.
The examples are concrete spoken commands: “create a return for this order,” “give me the fastest and cheapest shipping option,” and “generate a P&L summary of my shipping costs.”
It closes by inviting people building AI workflows for merchants, platforms or internal operations teams.
For brands planning a campaign
This is one of the few posts that names a builder audience directly.
A campaign around AI agent workflows could use the example commands as demo scripts or as the spine of a technical partnership.
The merchant-versus-platform-versus-ops split suggests three distinct audience angles to test.
Read this to see how the product narrative advances after launch.
Read more
It shows what changed for merchants and the kind of follow-up announcement they write.
The post announces an update to Shippo Intelligence with three new capabilities: a weekly AI-powered insights digest that reports what changed and recommends next steps, interactive maps for spotting patterns, and new surcharge and adjustment dashboards that break down what is driving cost changes.
API customers are told they can explore it in the API portal, with links to a press release and a learn-more page.
A companion post points to outside coverage of the same upgrade, repeats the three capabilities and frames shipping as one of the most complex parts of running an e-commerce business.
It closes with “More to come.”
The two posts overlap closely and are treated here as one body of work.
For brands planning a campaign
This shows a release-cycle habit: launch, then a follow-up amplifying the update.
A partnership could be timed to a release rather than a standalone campaign.
The surcharge and adjustment dashboard is the sharpest cost hook for merchants, while the weekly AI digest offers the strongest recurring-engagement angle.
Gabe Martini presents Shippo Intelligence as a way for merchants to see not just what is happening in shipping, but why.
Read more
The posts name the Spend, Labels, and Shipments dashboards and describe uses such as uncovering hidden costs, spotting volume trends, and monitoring delivery performance. Shippo Intelligence is presented as working inside the Shippo API Portal, with no integrations or setup.
Plain-language problem framing, followed by a short list of dashboards and merchant outcomes.
For brands planning a campaign
A shipping platform could partner with Gabe Martini on merchant-facing content that translates analytics into operational decisions: which shipping costs changed, which trends matter, and what to do next. The strongest angle is practical diagnosis, not generic product awareness.
Gabe Martini describes later Shippo Intelligence capabilities as helping merchants move from data to action.
Read more
The posts name a weekly AI-powered insights digest, interactive maps for spotting patterns and operational risk, and surcharge and adjustment dashboards that break down what is driving cost changes. These features address the challenge of interpreting shipping data and deciding what to do next.
Capability announcements organized around a merchant pain point, with each feature tied to a decision or cost outcome.
For brands planning a campaign
A product marketing partnership could show how to turn shipping data into routine decisions: weekly reviews, risk mapping, and explanations of cost changes. The content would suit an audience that already has shipping data but needs a clear way to interpret it.
Gabe Martini covers Shippo MCP as a way for AI agents to handle rate shopping, label creation, tracking, returns, and shipping analytics.
Read more
The post gives example prompts, such as creating a return, asking for the fastest and cheapest shipping option, or generating a profit-and-loss summary of shipping costs. It says these actions and insights come back in seconds and are built on Shippo's multi-carrier API for merchants, platforms, and internal ops teams.
Use-case examples and quoted prompts that help readers picture the workflow before they get into product details.
For brands planning a campaign
A platform could partner on developer or operator education that demonstrates concrete agent workflows rather than making abstract AI claims. Useful campaign assets could include prompt libraries, workflow walkthroughs, and a clear account of what requires integration work.
Gabe Martini's posts announce launches, updates, and upgrades: Shippo Intelligence is live, receives important updates, and recently got a major upgrade.
Read more
The language is celebratory and team-oriented, and each post points readers to a press release, landing page, or documentation.
For brands planning a campaign
A brand could use this pattern for launch windows and feature adoption campaigns, especially when a shipping product needs a clear merchant-facing explanation alongside a press release. The partnership would work best when there is a specific new capability to demonstrate.
Across the posts, shipping data is underused, and interpretation is the hard part.
Read more
Shippo Intelligence is positioned as a way to give merchants clarity, control, and confidence, particularly during peak season; MCP is positioned as moving shipping from clicking and searching to asking and doing.
For brands planning a campaign
A campaign could focus on the gap between data access and operational action. This suits educational content for e-commerce operators who need to justify shipping technology investments with concrete cost and service outcomes.
The posts address Shippo API customers and people building AI-powered workflows for merchants, platforms, or internal ops teams.
Read more
Product access is described through the API portal, while MCP is described as available to those building on Shippo's multi-carrier API. The material assumes readers understand shipping operations or platform development.
For brands planning a campaign
A partnership would suit a technical or operator audience, not general consumers.
Campaign content should account for readers who may be API customers, platform builders, or internal logistics teams.
Ask which commercial controls are available before presenting them as ready to use.
Gabe Martini's LinkedIn posts all center on Shippo.
Read more
Across five posts, they announce and explain Shippo's shipping products—Shippo Intelligence, Shippo MCP, and API updates—in the company voice, using "we" and "our merchants" and crediting the team behind the work. The posts mention no other brand or business.
Shippo
Disclosed partnership
Gabe Martini's posts introduce, launch, and update Shippo shipping products, including Shippo Intelligence analytics dashboards, the Shippo MCP workflow for AI agents, and API-portal features such as weekly AI insight digests, interactive maps, and surcharge and adjustment dashboards.
Read more
Written from inside the company ("we launched," "our merchants," "the team that helped me bring this to life"), they show a working association with Shippo. The posts state no employment title, ownership, or commercial terms; ask whether the relationship is employment, sponsorship, or another commercial arrangement.
Follow Gabe Martini for a working view of how e-commerce shipping is becoming a data and agent problem.
Read more
Start with the Shippo Intelligence launch and later upgrade posts to see the recurring argument: merchants already have shipping data but need help understanding cost changes, spotting demand shifts, and acting before customers notice.
Then read the Shippo MCP post for the technical thread, where rate shopping, labels, tracking, returns, and cost summaries move from portal work to plain-language agent commands.
The practical through-line is adoption with little setup: dashboards, weekly AI digests, and examples such as 'create a return for this order.' The adjacent creators below cover fulfillment operations, supply-chain cost changes, and agentic commerce infrastructure rather than shipping analytics itself.
Tony Runyan writes from inside fulfillment operations about how 3PL and warehouse choices affect e-commerce brands, using practical examples.
Read more
That aligns with Gabe Martini's focus on the shipping and fulfillment decisions behind e-commerce operations.
Tony Runyan's examples center on warehousing, big-and-heavy inventory, and 3PL support quality, while Gabe Martini's posts focus on shipping analytics software and AI agent workflows.
Divey Gulati covers e-commerce fulfillment technology and operating costs, including fuel surcharges and AI in the supply chain.
Read more
Those subjects overlap with Gabe Martini's focus on shipping costs and technology.
Divey Gulati largely explains provider capabilities and macro cost changes, while Gabe Martini covers software features, dashboards, and agent commands for merchants and platform teams.
Amelia Van Camp discusses agentic commerce and how AI agents change product discovery, recommendations, and purchasing.
Read more
That connects with Gabe Martini's post on AI agents handling shipping actions through MCP.
Amelia Van Camp focuses on marketplace infrastructure and product-data readiness for AI platforms, while Gabe Martini covers shipping execution, including rate shopping, labels, tracking, and returns.
Gabe Martini’s posts address e-commerce merchants and describe dashboards, cost insights, and agent-enabled shipping tasks, making them relevant to a campaign about shipping analytics and AI processes.
Read more
The posts do not report audience demographics or professional roles. Before deciding on reach, ask for recent audience data relevant to the campaign; for employer, occupation, or seniority, request survey results or another documented source.
Gabe Martini's five available LinkedIn posts are first-party product announcements promoting Shippo's shipping analytics tools to e-commerce merchants: Shippo Intelligence dashboards and the Shippo MCP integration for AI agent workflows.
Read more
None describes a sponsored placement, paid brand collaboration, rate card, audience-deliverable package, or way for an outside brand to commission work. The posts provide no official sponsor policy, format specification, disclosed partnership example, or inquiry route; ask the creator for these details before planning a campaign.
A shipping platform that sells analytics or AI agent tooling to e-commerce operators is the closest match in Gabe Martini's posts.
Read more
Across five posts, they consistently translate technical shipping capabilities into merchant decisions.
The Shippo Intelligence posts don't describe the product in feature terms alone; they name the buyer's problem first (shipping data is underused; merchants have data but not the meaning) and tie each capability to an outcome a merchant already cares about, such as uncovering hidden costs, spotting volume trends early, or acting on delivery problems before customers notice.
The MCP post goes further and shows the workflow instead of asserting it, with spoken commands like "create a return for this order," "give me the fastest and cheapest shipping option," and "generate a P&L summary of my shipping costs."
That is unusually concrete for social copy and exactly the raw material a product marketing partnership needs.
The fit is strongest when a campaign is tied to a release.
Their posts follow a repeatable rhythm: a launch announcement, a landing-page post that restates the same benefit in buyer-facing language, then a follow-up post when the product gets an upgrade.
Each one points to a press release, a landing page, or documentation.
A partner gets a writer comfortable producing the full announcement, not just a short reaction, and carrying a product narrative across several posts rather than dropping it after launch.
The audience orientation also matches.
The posts address Shippo API customers, merchants, and people building workflows for platforms or internal operations teams.
A campaign aimed at that reader, rather than a general business audience, won't have to be translated downward.
Two points belong in the fit decision.
Their posts don't mention a sponsorship format, rate card, or inquiry route, so ask them to define partnership terms.
The posts also don't publish audience composition or engagement data, so ask for those figures before relying on a reach claim.
When to choose a specialist
Three types of campaign are a poor match.
Read more
A campaign that needs independent, third-party evaluation of shipping vendors.
Their posts promote Shippo's own products.
They celebrate launches, credit the team, and never compare against competitors, weigh tradeoffs, or test a claim critically.
A campaign built on vendor comparison, buyer's-guide scoring, or an honest teardown of shipping APIs would ask them to write against the grain of the posts.
A consumer or non-shipping campaign.
The subject matter is shipping operations and the developer-facing plumbing behind them.
The posts assume a reader who already understands carrier rates, labels, returns, surcharges, and API access.
They don't discuss consumer products, lifestyle content, retail audiences, or general B2B topics outside logistics, so a campaign outside shipping has no support in the posts.
A campaign whose success depends on measured reach or a disclosed sponsored-placement format.
The posts don't publish audience demographics, follower composition, or engagement data, or mention a sponsor policy, media kit, rate card, or audience-deliverable package.
Ask for those details before planning a packaged placement with guaranteed impressions.
A fourth, softer mismatch: a campaign requiring long-form technical depth.
Everything in the posts is short social copy; they include no transcript, talk, article, code, or technical documentation.
Ask for a sample before commissioning a deep implementation walkthrough or long-form engineering post.
A worked campaign example
Campaign tested: a shipping-analytics platform wants a campaign around cost visibility for e-commerce operators heading into peak season, using both its dashboards and its AI agent workflow.
Angle: surcharge creep.
Most merchants can see their shipping spend go up; the harder question is which line moved and why.
That's the same gap their posts keep returning to, and it gives the campaign a diagnosis frame rather than a generic awareness frame.
Worked sequence.
First, a launch post written benefit-first, following the structure they already use: state the problem in one line (shipping data is underused because interpretation is the hard part), name the tools that close the gap, and promise no integrations or setup if that's true of the product.
Second, a landing-page post aimed at fast-growing brands that makes the same claim in buyer language: not just what is happening in shipping, but why.
Third, a prompt library for the agent workflow, drawn from the same worked-command format as the MCP post, for example "create a return for this order," "give me the fastest and cheapest shipping option," and "generate a P&L summary of my shipping costs," each paired with the operational question it answers.
Fourth, a follow-up post tied to the next product release or upgrade, repeating the capability set and adding the merchant consequence, the pattern their posts show after a launch.
Supporting asset that carries across the campaign: a weekly review checklist built from the same three questions the posts imply: what changed in spend, which lanes or surcharges moved, and what the operator should do next. This gives the campaign something to sustain after the launch posts have run.
Success looks like operators completing a first cost review using the prompts and the checklist, not impressions.
Verify that the dashboards and agent actions exist before writing copy, so the campaign's product claims match what the shipping analytics can do at launch.
A short paid test is also warranted before committing the full budget, since their posts don't establish engagement or audience composition.
Choose Tony Runyan when the campaign's deciding question is fulfillment operations rather than a shipping-software launch.
Read more
The two posts argue about physical network choices: whether a warehouse is genuinely in the right place for a brand's inventory, and how a buyer should judge a 3PL's support before signing.
The warehouse post uses a finding from the State of Big, Heavy & Bulky Fulfillment report — about one in eight big-and-heavy brands named warehouse location as their biggest fulfillment challenge, more than twice the rate for lighter products — then explains why saving money on inbound freight can add costs to every outgoing order.
The support post gives buyers a concrete test: ask to talk to a couple of current clients, and ask how long the client success team has been employed and where it sits relative to a warehouse.
That is the same practical, decision-shaped writing a shipping platform wants, aimed at the fulfillment center instead of the analytics dashboard.
A campaign on 3PL selection, warehouse siting, or service-level expectations fits these posts more naturally than Gabe Martini's.
The posts move the buyer decision upstream, away from the analytics and agent workflow a campaign aimed at that need would be built around.
Neither discusses shipping data, API tooling, or AI agents, so a partner would be writing outside the topics covered and outside their own expertise.
The voice is also the operator speaking for its own service: in-house, U.S.-based support is the answer being sold.
That makes this first-party promotion, like Gabe Martini's posts, not independent comparison.
Two posts are a thin sample for a sustained campaign.
Choose Divey Gulati when the campaign needs cost math at the invoice line or an AI launch told at fulfillment scale.
Read more
The fuel-surcharge post tracks diesel rising from roughly $3.71 to $4.86 a gallon and turns that into concrete numbers: FedEx Ground fuel surcharge moving from about 21.75% to 25%, and freight fuel surcharge from about $0.51 to $0.74 per mile, or roughly $230 more on a thousand-mile load.
It explains why that matters — surcharges can move faster than base rates, parcel impact shows up as a percentage and freight as dollars per mile — then closes with what the operator does about it.
The ShipBob AI post covers the same agentic territory as Gabe Martini's MCP post, but from the warehouse side: a connector with read and write access that is verified in Claude, an in-dashboard agent in beta that answers plain-language questions and then acts, and the framing that a storefront can become AI-ready in a weekend while a supply chain cannot.
A brief about total landed cost, surcharge exposure, or AI running through fulfillment operations suits this material.
The subject is an operator's own network and pricing position, not an API a merchant integrates.
The surcharge post ends by selling the company's ability to absorb fuel costs through carrier relationships, total customer volume, and its own logistics arm — a claim a different platform cannot simply reuse and would have to answer rather than echo.
The AI post is a launch-day vision statement: it names capabilities but offers no worked commands or merchant-facing prompts to build an agent campaign around.
Both posts are first-party promotion, as are Gabe Martini's.
Choose Amelia Van Camp when the campaign is about being found by AI agents rather than running shipping.
Read more
The two posts reviewed make agentic-commerce readiness arguments for enterprise retail: a scan of hundreds of product pages where under 1% scored above the threshold at which AI agents reliably surface and recommend products; a figure of $67 billion in Cyber Week 2025 sales already influenced by AI agents; and a joint research playbook citing 393% year-over-year growth in AI-sourced traffic to U.S. retail sites and 55% of U.S. e-commerce spending becoming agent-assisted.
One post describes product enrichment and direct connections to LLM platforms; the other frames marketplace platforms growing at 31% GMV year over year against 6.9% for traditional e-commerce, and ties the argument to a conversation with a named practitioner.
A brief about catalog and discovery readiness, marketplace strategy, or how enterprises should prepare for agent-driven buying fits here.
The posts support a different decision.
Neither concerns shipping rates, labels, returns, or carrier analytics, so a shipping platform would be buying an adjacent argument and would have to build the bridge from discovery to fulfillment itself.
The audience is enterprise retail and marketplace leadership, not the developer and operations readers the shipping posts address.
The claims rely heavily on market data attributed to the company's own research and to third parties; a partner would need to source and date those figures independently before reuse.
Two posts per person are a limited sample.
Ask for audience, engagement, and commercial-availability information.
Gabe M.'s five LinkedIn posts here are all about Shippo products: the Shippo Intelligence launch, a landing-page post for the same product, a post on Shippo MCP and AI agent workflows, and two closely overlapping posts about a later Intelligence upgrade adding AI insight digests, interactive maps, and surcharge and adjustment dashboards.
All five posts are short social copy — there are no transcripts, long-form articles, code, or third-party coverage here.
The posts have no publication dates, so no chronology or currency is claimed.
The similar-creator shortlist elsewhere on the page draws on two posts each from Tony Runyan, Divey Gulati, and Amelia Van Camp.
Audience size, engagement, sponsorship formats, rates, and an inquiry route are not established in Gabe M.'s posts, and signature books, shows, businesses, and earlier career history remain open gaps.