Own the Front Door
Control customer access to protect distribution, margins, and strategic freedom
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 96%
Own the Front Door treats direct customer access as a strategic asset rather than merely a marketing channel. Start by mapping the platforms, stores, browsers, carriers, or distributors standing between the company and its users. Measure both the visible tax, such as a revenue share, and the strategic risk that an intermediary could change defaults, privilege a rival, or block access. The company then decides whether to own, build, acquire, or influence the narrowest gateway necessary to neutralize that dependency. The gateway does not need to earn standalone profits: it can create value by preserving demand, avoiding fees, supplying data, and protecting freedom of action. Android illustrates the mechanism because broad free distribution helped Google retain direct access to mobile search users while limiting dependence on Apple's platform.
Origin
The hosts derive this model from Ben Thompson's aggregation analysis and Google's use of Android to protect access to mobile search customers.
Core principles
- 01Direct customer access creates strategic leverage
- 02Free digital distribution shifts power toward customer ownership
- 03An intermediary can tax access to customers you already serve
- 04A free complement can defend a highly profitable core business
- 05Platform control can be valuable without standalone profit
How to run it
- 1
Map the Access Chain
List every technical and commercial layer a customer crosses before reaching the core service. Include devices, operating systems, app stores, browsers, distributors, and default settings.
Pro tip Map the chain separately for each major customer segment or geography.
Watch out A layer that looks neutral today may become a competitor after the market shifts.
- 2
Measure the Dependency Tax
Calculate direct fees, revenue shares, acquisition costs, data loss, and restrictions created by each intermediary. Estimate how those costs change as usage grows.
Pro tip Include avoided future costs, not just current invoices.
Watch out Do not present avoided fees as booked revenue.
- 3
Identify the Strategic Chokepoint
Find the layer capable of changing defaults, steering users elsewhere, or withholding essential capabilities. Prioritize control of that chokepoint rather than indiscriminately owning the whole stack.
Pro tip Ask which single policy change by another company would damage the core business most.
Watch out Vertical integration beyond the chokepoint can add complexity without adding protection.
- 4
Choose a Control Strategy
Decide whether to acquire, build, partner, standardize, or open-source a defensive layer. Match the approach to the speed of the market transition and the company's capabilities.
Pro tip A free or open complement can achieve wider distribution than a directly monetized product.
Watch out An open strategy may enable forks that remove your services entirely.
- 5
Win Ecosystem Adoption
Recruit the manufacturers, carriers, developers, or other partners required to make the gateway credible. Reduce their dependence on the dominant incumbent while preserving incentives to participate.
Pro tip Coordinate multiple threatened parties around a shared alternative.
Watch out A platform without applications, partners, or distribution still faces a cold-start problem.
- 6
Track Defensive Returns
Measure retained users, reduced revenue shares, protected defaults, ecosystem reach, and strategic options alongside direct profit. Reassess whether the controlled layer remains the relevant gateway as competition moves up the stack.
Pro tip Create a separate avoided-cost line in strategic reporting.
Watch out The front door can migrate from hardware to operating systems, applications, assistants, or other interfaces.
In the wild
As computing shifted from desktop browsers to smartphones, Google risked placing Apple between its search service and users. By distributing Android broadly through an open hardware ecosystem, Google gained direct access to a large share of mobile users, reduced the revenue share it otherwise might pay platform owners, and preserved search as the default route into its advertising business.
→ Android became a defensive platform asset that protected Google's core search margins and customer relationship.
A specialist retailer depends on a marketplace that controls ranking and charges rising commissions. The retailer keeps the marketplace for discovery but develops a direct membership channel with exclusive support, educational content, and replenishment reminders rather than recreating the entire marketplace.
→ The retailer reduces dependency while retaining the intermediary's useful reach.
Common mistakes
Owning the entire stack
Control should target the decisive gateway; unnecessary vertical integration can consume capital and antagonize partners.
Demanding direct profit
A defensive platform may justify itself through avoided taxes, retained users, and strategic freedom rather than standalone earnings.
Ignoring ecosystem incentives
Owning technology is insufficient when manufacturers, developers, distributors, or customers have no reason to adopt it.
Is it for you?
Best for
It is best for digital businesses whose demand, margins, or default status depends on operating systems, marketplaces, browsers, or other gateways.
Not ideal for
It is not ideal for businesses where direct ownership adds heavy fixed costs without reducing meaningful dependency or improving the customer experience.
From the transcript
“you have to own the front door to the customer in this day and age.”
“what the internet has done is it has made distribution free.”
“Google basically is is uh the entire reason that Android exists is so that Google doesn't need to pay for access to their own existing…”
From the episode
Android