← Back to list
Colossus (Invest Like the Best / Business Breakdowns)Podcast29 Oct 2020Source: traffic.libsyn.comHost: Patrick O'Shaughnessy

Laura Behrens Wu - When Digital and Physical Worlds Converge - [Founder’s Field Guide, EP.5]

In plain words

This episode covers how Shippo simplifies shipping for e-commerce sellers. Founder Laura believes shipping's complexity—mixing digital orders with real-world hiccups like a driver hitting a deer—is its moat. She's bullish on Shippo's model: aggregating small businesses' volume to negotiate better rates with carriers (UPS, FedEx) and using data to recommend the cheapest option. Key mentions: Amazon as a potential risk but with a different model; Shopify as a key partner for customer acquisition; Stripe as a comparison, though Shippo serves a broader audience.

AI SummaryAI-generated · may contain errors · verify against the original

At a Glance

Laura Behrens Wu is the co-founder and CEO of Shippo, a company that simplifies e-commerce shipping through an API and dashboard. The main thread of this episode is how Shippo began by solving its founders' own pain points, built a platform within the ancient logistics industry, and navigates the unique challenges of merging the physical and digital worlds. Laura Behrens Wu believes that the inherent complexity of the shipping industry is its deepest moat, but she warns of the risk of imitation by giants like Amazon. Shippo's core competitive advantage lies in continuously amplifying its scale advantage through an "aggregation model" and a "data flywheel."

Shipping Complexity Is a Moat, but Also a Perpetual Pain Point

Laura Behrens Wu argues that the complexity of the shipping industry stems from the "fusion of the physical and digital worlds," which forms Shippo's innate moat but also imposes a persistent engineering burden. She notes that every e-commerce process is purely digital until the moment an item needs to be shipped, and that "shipping is the intersection of the digital world and the physical world," requiring the translation of "what happens in the real world" back to the internet. This complexity leads to "very strange error messages," such as real-world events like "a driver hit a deer." Software must handle this unpredictability.

  • Evidence: Shippo is built on top of the APIs of multiple carriers (UPS, FedEx, USPS, etc.), but these carriers are "non-tech companies" whose API documentation is "unfriendly" and who "will change API endpoints without notifying" Shippo. This forces Shippo to invest significant engineering resources in "critical infrastructure work" because "customers expect it to work, and it doesn't earn you points when it works, but they get very angry when it doesn't."
  • Implication: Laura believes that this "expensive, sometimes tedious work" is "something you can never get rid of," but it is precisely Shippo's value proposition—letting customers "not have to figure out UPS endpoint changes one by one." She positions Shippo as a "buffer," which is itself a competitive barrier. Falsification signal: If a major carrier significantly opens up and standardizes its API, or if a general middleware emerges that manages all carrier APIs, Shippo's layer of value would be eroded.

Aggregation Model and Data Flywheel

Laura Behrens Wu points out that Shippo's core business model is "aggregating and reselling discounted shipping rates," and that data is the second flywheel driving growth. She summarizes Shippo's business logic into two mutually reinforcing flywheels.

  • Flywheel One: Volume-Driven. By aggregating the parcel volumes of many SMBs (small and medium businesses), Shippo gains leverage to negotiate better discounts with carriers. Better discounts, in turn, attract more customers and generate more volume. She emphasizes, "We have five years of data proving this is a working flywheel."
  • Flywheel Two: Data-Driven. As the platform accumulates a large amount of shipping data, Shippo can "recommend which carrier to use," "share industry benchmarks," and "inform about delays on specific routes with specific service levels." She likens this to "providing Amazon-level shipping best practices for the masses," with the goal of making customers "not have to think"—letting Shippo make the "most economical and fastest shipping decisions" for them.
  • Implication: Laura believes that part of Amazon's shipping advantage stems from its "massive shipping data," while SMBs have limited data. By aggregating data, Shippo enables SMBs to access such optimization. Falsification signal: If carriers start offering dynamic pricing (similar to the airline industry), or if SMB shipping patterns become extremely standardized, the room for data-driven optimization could shrink.

The Challenge of Transitioning from "Aggregator" to "Platform"

Laura Behrens Wu acknowledges that Shippo is facing a critical challenge in transitioning from an "aggregator" to a "platform," a transition that has no successful precedent in this space. She notes that most of Shippo's current competitors "mainly make money through the arbitrage of shipping rate discounts," but Shippo wants to "create more high-margin software products."

  • Data and Dilemma: Shippo's customer base follows an "80/20 rule"—80% of customers (SMBs using the dashboard) contribute only 20% of parcel volume, while 20% of customers (tech companies using the API) contribute 80% of parcel volume. This creates significant internal conflict over product priorities: how to serve these two very different customer types simultaneously.
  • Mechanism: Laura compares Shippo's evolution to the path of Stripe and Twilio, which expanded from a single API to multiple product lines. However, she also admits, "No other shipping software company has successfully taken this step," implying that there may be unknown obstacles.
  • Implication: Laura plans to "balance engineering resources" to maintain infrastructure while developing new features. She believes that Shippo's "shipping rate discount arbitrage" is "a good foundation," but the future requires "creating almost independent products." Falsification signal: If Shippo's core infrastructure (e.g., carrier API compatibility) begins to break down while expanding product lines, or if newly launched software products fail to achieve the same user stickiness as the core product, the transition may fail.

Companies Mentioned

Company Guest Attitude Key Data
Amazon Risk Warning Laura believes Amazon's logistics advantage stems from its "predictable pickup locations." Unlike Shippo's model of "50,000 dispersed SMBs," Amazon's imitation is the "worst question" (because it can be asked of any company) but is not a core threat.
Shopify Partner Shopify was Shippo's most important customer acquisition channel in the early days. Through Shopify's App Store ecosystem, Shippo acquired a large number of SMB customers. Laura praises Shopify's ecosystem as "the most vibrant among all shopping cart builders."
Walmart Neutral/Comparison Laura lists Walmart alongside Amazon as a giant with "its own shipping infrastructure," but notes that its model does not apply to the highly fragmented SMB market, which differs from Shippo's customer base.
Stripe Analogy As an analogy for Shippo's business model, Laura points out that Stripe only sells to "people who know what an API is," while Shippo serves both API users and dashboard users.
Twilio Analogy Used as a reference for Shippo's expansion from a single API to multiple product lines.

Judgments Worth Remembering

1. "Shipping is the intersection of the digital world and the physical world" — Laura Behrens Wu believes this is the root of the unique complexity of the shipping industry and the source of Shippo's value: translating the unpredictability of the real world (e.g., a driver hitting a deer) into error messages that the internet can understand. Support: This judgment explains why Shippo's moat comes from the friction of the "physical world," not purely from software technology advantages.

2. "The worst question is always, 'What if Amazon does this?'" — Laura Behrens Wu notes that this question "can be asked of any company" and is completely undifferentiated. Support: She argues that Amazon's model (predictable pickup points) is fundamentally different from Shippo's customer model (50,000 dispersed locations), and therefore is not a core threat.

3. "Pricing power is not in software, but in the arbitrage of shipping rate discounts" — Laura Behrens Wu describes Shippo's pricing model: software fees are only part of the revenue; the core is "reselling discounted shipping rates." Support: She points out that almost all competitors rely on the "shipping rate discount arbitrage model," which provides Shippo with a stable foundation but also means its profits are highly dependent on bargaining power with carriers.

4. "No shipping software company has successfully transitioned from an aggregator to a platform" — Laura Behrens Wu admits this is the biggest unknown challenge facing Shippo. Support: She compares the goal to the expansion paths of Stripe and Twilio, but acknowledges, "There might be something I don't know that makes this step particularly difficult."

5. "The data flywheel can give SMBs Amazon-level shipping optimization" — Laura Behrens Wu believes that by aggregating data, Shippo can provide "data-driven optimization," freeing SMBs from the "limitations of a small data set." Support: She cites examples like "recommending carriers" and "sharing industry benchmarks" to illustrate how data translates into concrete decision support.

6. "The fusion of the physical world and the digital world is a future trend" — Laura Behrens Wu uses the example of "farmers selling directly to consumers," noting that bypassing intermediaries and delivering physical products (e.g., Hawaiian purple sweet potatoes) directly to consumers is a trend worth watching. Support: She believes this "shortening of the supply chain" model is highly aligned with Shippo's mission (making shipping as easy as building a website).

~9 min full read
Deep Analysis