Ash Maurya 7 Sources of Power Moat Framework

Last updated: 10 August 2026

Identify and build one compounding, structural unfair advantage that makes competition irrelevant — rather than chasing features competitors will simply copy.

// TL;DR

The Ash Maurya 7 Sources of Power Moat Framework is a competitive strategy tool for identifying and building one compounding, structural unfair advantage — a moat — instead of chasing features competitors will copy. It filters false advantages (first-mover, great team, better UX, superior tech), maps your business model to one of seven power types (Scale Economies, Network Effects, Counterpositioning, Switching Costs, Branding, Cornered Resource, Process Power), and designs a moat mechanic that compounds as a side effect of core product usage. Use it when defining competitive strategy, responding to an incumbent entering your market, or writing the competitive-advantage section of a pitch deck.

Framework

// When should you use the 7 Sources of Power moat framework?

Use this skill when a founder or product team is defining competitive strategy, responding to an incumbent entering their market, or preparing a pitch deck section on competitive advantages. Also apply it when a 'better features' strategy is stalling or when a well-funded competitor has appeared.

// What do you need before applying the moat framework?

Business model descriptionrequired
How the product is built, sold, and delivered — including who the customer is and how value is exchanged
Product stagerequired
Where the product currently sits: idea, early traction, growth, or scale
Unique Value Proposition (UVP)required
The one thing the product does distinctively well that customers value most — the 'delighter feature' or killer use case
Competitive landscape
Who the incumbents are, what resources they have, and what business model they depend on
Current claimed advantages
What the team currently lists as their competitive advantages (used to stress-test and discard false advantages)

// What are the core principles behind building an unfair advantage?

Unfair Advantages vs. Competitive Advantages

Real unfair advantages are structural positions that are ideally uneconomical for competitors to replicate. Being first, having a great team, superior technology, or better UX are NOT unfair advantages — they are temporary states that get copied, commoditised, or hired away.

Moat Building as a Side Effect

The best moat-building strategy is one that is already a natural side effect of building your core product. When mode building couples with your unique value proposition, it compounds automatically over time like a flywheel rather than requiring a separate parallel effort.

Pick One, Go All-In

You cannot build all seven sources of power simultaneously. You must pick exactly one that matches your current product stage and business model, then go all-in on it. Spreading effort across multiple moats means building none.

Counterpositioning as Shelter

The ideal starting moat for a startup facing an incumbent is something the incumbent would never want to copy because doing so would erode their own business model. This buys time and space to build the moat before the incumbent is motivated to respond.

Lean Into Simplicity, Not Features

When incumbents enter your space, the instinct to build more powerful features is a trap. Instead, lean further into your unique value proposition — often this means embracing more simplicity and speed in the specific use case that creates the strongest emotional response for customers.

// How do you apply the 7 Sources of Power framework step by step?

1
Stress-test the current claimed advantages list
Take every item the team calls a 'competitive advantage' and apply this filter: Can a well-funded competitor replicate this within 18–24 months? If yes, it is not an unfair advantage. Discard first-mover advantage, team quality, technology superiority, and better UX — these are not unfair advantages. Only proceed with items that survive the filter.
2
Map the business model to its natural power type
Conduct a Business Model Assessment. Certain business models are structurally inclined toward specific powers: products where sharing is a natural side effect → Network Effects; products that undercut an incumbent's revenue model → Counterpositioning; products requiring deep customer configuration → Switching Costs; high-volume distribution plays → Scale Economies; unique access to content, data, or talent → Cornered Resource; deeply embedded operational culture → Process Power; emotionally resonant consumer products → Branding. Identify which one or two powers fit naturally given the business model.
3
Apply the Product Stage filter
Conduct a Product Stage Assessment. Some powers require significant time and capital (Branding, Scale Economies, Process Power) and are inaccessible to early-stage startups competing against incumbents. Early-stage products should prioritise Counterpositioning or Network Effects, which can be built with limited resources and provide shelter from incumbents. Later-stage products with traction can layer in harder-to-build powers.
4
Identify the one or two 'delighter features' that reinforce the UVP and that incumbents would not want to copy
The delighter feature must: (a) create a strong emotional or transformative moment for the customer, (b) directly reinforce the unique value proposition, and (c) represent something incumbents would avoid copying because it conflicts with their existing business model or revenue structure. Strip away all features that incumbents could match with budget. Focus on the specific use case where your product creates the most outsized customer response.
5
Select one power and design the moat-building mechanic
Pick exactly one source of power. Then design the specific mechanic that builds it as a side effect of normal product use. Example structure: 'Every time a user does [core action], it contributes to [moat-building asset] that makes the product more valuable for all users.' The mechanic should compound — each unit of usage makes the moat harder to attack. Do not design the moat as a separate workstream.
6
Stress-test with the Defensibility Question
Ask: 'If a well-capitalised incumbent copied this exact feature set today, would our chosen power still protect us?' If the answer is no, return to Step 4. If yes, validate that the moat mechanic is already embedded in the product roadmap and is not dependent on future resources or permissions you do not currently have.
7
Go all-in — align roadmap, messaging, and resource allocation around the single chosen power
Mode building takes time, patience, and discipline. Every roadmap decision, every marketing message, and every resource allocation should now be evaluated against whether it reinforces the chosen power. Features that do not contribute to the moat should be deprioritised even if they seem impressive. The goal is to make the moat compound like a flywheel, not to build the most feature-rich product.

// What does the moat framework look like in real startup scenarios?

A vertical SaaS founder has built a niche project management tool for a specific professional services industry. A large horizontal competitor has just announced they are entering the same niche with a dedicated module.

Step 1: Discard 'better UX' and 'domain expertise of founding team' — these are not unfair advantages. Step 2: Business model assessment reveals that professionals in this field routinely share templates, workflows, and deliverables — pointing toward Network Effects. Step 3: Early-stage, so Branding and Scale Economies are out. Step 4: The delighter feature is a shared, community-contributed template library specific to this profession — something the horizontal competitor would not build because it requires deep domain curation they have no incentive to invest in. Step 5: Moat mechanic — every time a user completes a project deliverable, they are prompted to contribute it to a shared library. The library becomes more valuable with every user. Steps 6–7: All roadmap effort is redirected to growing the library and its quality, not to adding features that match the incumbent.

A consumer app founder is competing against a well-funded incumbent whose business model depends on subscription revenue. The founder's product offers a free, ad-supported alternative.

Step 1: 'Free pricing' is not an unfair advantage on its own — it is easily matched. Step 2: The free model directly erodes the incumbent's subscription revenue if they try to copy it — pointing to Counterpositioning as the natural power. Step 3: Early-stage, counterpositioning is accessible. Step 4: The delighter feature must be something that only makes sense in a free, ad-supported model — e.g., viral sharing mechanics or public profiles that drive distribution. The incumbent cannot adopt this without cannibalising their subscription base. Steps 5–7: The moat is built by making the free, social-sharing behaviour a core product loop, not an add-on. Roadmap is locked to deepening that loop.

// What mistakes should you avoid when building a moat?

Listing first-mover advantage, great team, superior technology, or better UX as unfair advantages — none of these are structural; all can be eroded by a well-funded competitor.
Trying to build all seven sources of power simultaneously — this guarantees you build none of them deeply enough to matter.
Responding to incumbent entry by building more and more powerful features — this plays into the incumbent's strength (budget and engineering scale) rather than your structural difference.
Choosing a power that does not match your business model — for example, pursuing Branding as an early-stage startup against an established incumbent with massive marketing spend.
Designing the moat as a separate strategic initiative rather than embedding it as a natural side effect of core product usage.
Selecting a delighter feature that the incumbent would actually want to copy — the ideal feature is one incumbents are structurally or economically motivated to avoid.
Confusing switching costs created by contractual lock-in with genuine switching costs — real switching costs come from customers investing time, integrations, and effort into making your solution work, not from licence terms they can break.

// What are the key terms in the 7 Sources of Power framework?

Unfair Advantage: A structural market position that is ideally uneconomical for competitors to replicate or buy — not merely a temporary state like being first or having a better team. Real unfair advantages compound over time and create increasing barriers to entry.
Seven Sources of Power: The seven structural categories from which real unfair advantages can be built: Scale Economies, Network Effects, Counterpositioning, Switching Costs, Branding, Cornered Resource, and Process Power.
Scale Economies: The power derived from lowering unit costs as the business grows larger, making it structurally cheaper to serve customers than any smaller competitor can match.
Network Effects: The power derived from a product becoming more valuable as more people use it — each new user increases the value for all existing users.
Counterpositioning: The power derived from introducing a business model that incumbents cannot adopt without eroding their own existing revenue streams or business model.
Switching Costs: The power derived from customers having invested so much time, money, integrations, and effort into your solution that switching to a competitor carries a cost far exceeding the price of the product itself.
Branding: The power derived from an emotional connection with customers that reduces price sensitivity and increases loyalty — distinct from marketing spend or product quality alone.
Cornered Resource: The power derived from exclusive access to a critical resource — such as proprietary data, exclusive content, key talent, or trade secrets — that competitors cannot easily access or replicate.
Process Power: The power derived from embedded organisational capabilities and culture that are so unique they are difficult to copy even when competitors observe and attempt to replicate them.
Moat: The durable competitive barrier created by successfully building one of the seven sources of power — used interchangeably with 'unfair advantage' in the context of long-term defensibility.
Delighter Feature: A specific product capability that creates a strong emotional or transformative moment for the customer, directly reinforces the unique value proposition, and is ideally something incumbents would not want to copy.
Business Model Assessment: Step one of the three-step unfair advantage identification process — mapping the business model to the source of power it is naturally inclined toward.
Product Stage Assessment: Step two of the three-step process — filtering available power types based on the resources and time required to build them relative to the product's current stage.
Go All-In: Step three of the three-step process — committing roadmap, messaging, and resources entirely to building the single chosen power, accepting that moat building requires time, patience, and discipline.
Flywheel: The compounding dynamic achieved when moat building is a natural side effect of core product usage — each unit of usage strengthens the moat, which attracts more usage, which strengthens the moat further.

// FREQUENTLY ASKED QUESTIONS

What is the 7 Sources of Power moat framework?

It's a competitive strategy framework that helps founders identify and build one structural unfair advantage — a moat — from seven power types: Scale Economies, Network Effects, Counterpositioning, Switching Costs, Branding, Cornered Resource, and Process Power. Instead of chasing features rivals will copy, you pick the single power that matches your business model and product stage, then design a mechanic that compounds automatically as customers use your product.

What is the difference between an unfair advantage and a competitive advantage?

An unfair advantage is a structural market position that's ideally uneconomical for competitors to replicate or buy, and it compounds over time. A competitive advantage — like being first, having a great team, superior technology, or better UX — is a temporary state that gets copied, commoditised, or hired away. If a well-funded competitor can replicate it within 18–24 months, it's not an unfair advantage.

How do I build a moat for my startup?

Start by discarding false advantages (first-mover, team, tech, UX), then map your business model to its natural power type and filter by product stage. Identify a delighter feature that reinforces your UVP and that incumbents wouldn't want to copy, pick exactly one source of power, and design a mechanic where every core action strengthens the moat. Then align your entire roadmap around that single power.

How do I respond when a well-funded competitor enters my market?

Don't build more powerful features — that plays to the incumbent's budget and engineering strength. Instead lean further into your unique value proposition, often embracing more simplicity and speed in the use case that creates the strongest emotional response. Use counterpositioning: build something the incumbent would never copy because doing so would erode their own business model, buying you time to compound your moat.

How does this framework compare to just building better features?

Better features are commodities — any well-funded competitor can match them with budget and engineering scale, so a features race plays to the incumbent's strengths. This framework focuses on structural defensibility: one compounding power that becomes harder to attack the more your product is used. Moat building is a side effect of core usage, not a separate feature workstream, so it protects you long after individual features are copied.

When should I use the 7 Sources of Power framework?

Use it when defining competitive strategy, when an incumbent announces entry into your niche, or when preparing the competitive-advantage section of a pitch deck. It's especially valuable when a 'better features' strategy is stalling or a well-funded competitor has appeared. It works at any product stage, but early-stage startups should prioritise Counterpositioning or Network Effects since they require limited resources.

Why can't I build all seven sources of power at once?

Because spreading effort across multiple moats means building none of them deeply enough to matter. Each power requires focused roadmap, messaging, and resource commitment to compound into a real barrier. You must pick exactly one power that matches your current business model and product stage, then go all-in. Later-stage products with traction can layer in additional powers, but only after the first one is established.

What is counterpositioning and why is it best for early-stage startups?

Counterpositioning is the power derived from introducing a business model that incumbents cannot adopt without eroding their own existing revenue streams. It's ideal for early-stage startups because it's accessible with limited resources and provides shelter — the incumbent stays passive since copying you would cannibalise their business. That buys you time and space to build the moat before the incumbent is motivated to respond.

What results can I expect from applying this framework?

You'll end with one clearly chosen source of power, a moat mechanic embedded in your core product loop, and a roadmap where every decision reinforces that power. Expect competition to become less relevant over time as your moat compounds like a flywheel — each unit of usage makes it harder to attack. You'll also stop wasting effort on impressive-but-copyable features that don't strengthen your defensibility.

What are the seven sources of power?

The seven structural sources of power are: Scale Economies (lower unit costs at size), Network Effects (more valuable as more people use it), Counterpositioning (a model incumbents can't copy without harming themselves), Switching Costs (customers invested too much to leave), Branding (emotional connection reducing price sensitivity), Cornered Resource (exclusive access to data, content, or talent), and Process Power (embedded organisational capabilities that are hard to copy).

How do I know if my claimed advantage is actually a moat?

Apply the Defensibility Question: 'If a well-capitalised incumbent copied this exact feature set today, would our chosen power still protect us?' If yes, and the moat mechanic is already embedded in your product roadmap without needing future resources you don't have, it's a real moat. If no, your advantage is copyable and you need to return to identifying a genuine delighter feature.

// GET THIS SKILL — FREE