Frequently Asked Questions About Ash Maurya 7 Sources of Power Moat Framework
21 answers covering everything from basics to advanced usage.
// Basics
What does 'moat building as a side effect' actually mean?
It means the best moat is one that gets built automatically as customers use your core product, rather than as a separate strategic initiative. When moat building couples with your unique value proposition, it compounds like a flywheel — every core action contributes to a moat-building asset that makes the product more valuable for everyone. If you have to run a parallel workstream to build your moat, you've likely chosen the wrong one.
What is a delighter feature and how is it different from a normal feature?
A delighter feature creates a strong emotional or transformative moment, directly reinforces your unique value proposition, and — critically — is something incumbents would avoid copying because it conflicts with their business model. A normal feature can be matched with budget. The delighter is defined by what the incumbent won't touch, not by how impressive it is.
What is a flywheel in the context of this framework?
A flywheel is the compounding dynamic where 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. The classic mechanic structure is 'Every time a user does [core action], it contributes to [moat-building asset] that makes the product more valuable for all users.'
Why isn't first-mover advantage a real moat?
Because being first is a temporary state, not a structural position — a well-funded competitor can enter later and out-execute you. First-mover advantage only matters if you use the head start to build one of the seven durable powers before rivals catch up. On its own it fails the filter: it can be eroded within 18–24 months, so discard it in Step 1.
// How To
How do I map my business model to the right source of power?
Match structural traits to powers: products where sharing is natural point to Network Effects; products that undercut an incumbent's revenue model point to Counterpositioning; products requiring deep configuration point to Switching Costs; high-volume distribution points to Scale Economies; unique access to content, data, or talent points to Cornered Resource; embedded operational culture points to Process Power; emotionally resonant consumer products point to Branding.
How do I stress-test my current list of competitive advantages?
Take every item your team calls an advantage and ask: can a well-funded competitor replicate this within 18–24 months? If yes, discard it — this eliminates first-mover advantage, team quality, superior technology, and better UX. Only items that survive this filter are candidate unfair advantages worth pursuing. Do this before any other step so you're not building strategy on false foundations.
How do I design a moat mechanic that compounds automatically?
Pick one power, then write the mechanic as: 'Every time a user does [core action], it contributes to [moat-building asset] that makes the product more valuable for all users.' The mechanic must compound — each unit of usage makes the moat harder to attack — and it must be part of normal product use, not a bolt-on. If it requires users to do extra work, it won't compound.
How do I choose between two powers that both fit my business model?
Apply the Product Stage filter. Some powers (Branding, Scale Economies, Process Power) require significant time and capital and are inaccessible to early-stage startups against incumbents. If you're early-stage and torn, favour the power that can be built with limited resources and provides shelter — usually Counterpositioning or Network Effects. Later-stage products with traction can pursue the harder, capital-intensive powers.
// Troubleshooting
My delighter feature keeps getting copied by competitors. What went wrong?
You chose a feature the incumbent was actually willing to copy. The ideal delighter is one incumbents are structurally or economically motivated to avoid — because copying it would erode their revenue model or existing business. Return to Step 4, strip away anything matchable with budget, and find the use case where copying you would hurt the incumbent's own economics.
I'm building features to match the incumbent but losing ground. What should I do?
Stop the features race — it plays to the incumbent's strength in budget and engineering scale. Lean into your unique value proposition instead, often by embracing more simplicity and speed in the single use case that creates the strongest emotional customer response. Then pick a power (usually Counterpositioning at your stage) and redirect all roadmap effort to building that moat, not matching their feature set.
My moat mechanic depends on future resources I don't have yet. Is that a problem?
Yes — that fails the Step 6 validation. A viable moat mechanic must already be embedded in your current product roadmap and not depend on resources, funding, or permissions you don't currently possess. If it does, you've chosen a power beyond your stage. Re-run the Product Stage Assessment and pick a power you can start compounding today.
I have contractual lock-in — isn't that a switching cost moat?
No. Contractual lock-in is a licence term customers can break, and it breeds resentment. Genuine switching costs come from customers investing time, integrations, data, and effort into making your solution work — so switching carries a cost far exceeding the price of the product itself. Real switching costs are earned through embedded value, not enforced through contracts.
// Comparisons
How does this framework compare to a generic SWOT analysis?
SWOT catalogues strengths and weaknesses broadly and often lists copyable traits as 'strengths.' This framework is sharper: it applies a hard filter that discards temporary states, forces you to pick exactly one structural power, and requires the moat to be embedded in core usage. SWOT describes; the 7 Sources of Power prescribes a single compounding action and stress-tests it with the Defensibility Question.
How does this compare to Hamilton Helmer's original 7 Powers?
This framework uses Helmer's seven power categories but adapts them for founders through Ash Maurya's lens: it adds a practical three-step identification process (Business Model Assessment, Product Stage Assessment, Go All-In), emphasises building the moat as a side effect of core usage, and foregrounds Counterpositioning as the ideal starting moat for early-stage startups facing incumbents. It's Helmer's theory turned into a founder workflow.
How is counterpositioning different from just being cheaper?
Being cheaper is easily matched — the incumbent can drop prices. Counterpositioning works because the incumbent won't copy your model even though they could, since doing so would erode their own existing revenue streams. Cheap pricing is a competitive advantage; a business model the incumbent is economically forbidden from adopting is a structural unfair advantage.
How does building a moat compare to focusing purely on product-market fit?
Product-market fit gets you traction; a moat keeps it. PMF answers 'do people want this?' while the moat framework answers 'why can't a well-funded competitor take it from you?' The two work together — your delighter feature should reinforce both your UVP (fit) and your chosen power (defensibility). Achieving fit without a moat invites a fast-follower to capture your market.
// Advanced
Can a startup build multiple moats over time?
Yes, but sequentially, not simultaneously. Pick one power that matches your current stage and go all-in until it compounds into a real barrier. Later-stage products with traction can then layer in harder-to-build powers like Branding, Scale Economies, or Process Power. The rule is to never split early effort — spreading across multiple moats early guarantees you build none deeply enough to matter.
How do I use this framework in a pitch deck's competitive advantage slide?
Lead with your one chosen source of power, not a list. State the delighter feature, then articulate the moat mechanic — 'every time a user does X, it strengthens Y for all users.' Explain why incumbents won't copy it (ideally counterpositioning). Investors want a compounding, structural reason competition becomes irrelevant, not a bullet list of features that read as temporary states.
What if my business model doesn't cleanly map to any single power?
Look harder at your core product loop — most models have a latent power in how value is created or shared. If sharing happens naturally, that's Network Effects even if subtle. If your model undercuts how incumbents make money, that's Counterpositioning. If none fits, your unique value proposition may be too weak or copyable; sharpen the delighter feature first, then re-run the Business Model Assessment.
How do I keep my roadmap aligned to one power without ignoring customer requests?
Evaluate every roadmap decision, marketing message, and resource allocation against one question: does it reinforce the chosen power? Features that don't contribute to the moat should be deprioritised even when impressive or requested. This is the Go All-In discipline. You can still address critical customer needs, but the default bias is toward the flywheel — the goal is a compounding moat, not the most feature-rich product.
Does the Defensibility Question apply to every power equally?
Yes — the question 'if a well-capitalised incumbent copied this exact feature set today, would our chosen power still protect us?' is universal. It tests whether your protection is structural rather than feature-based. Network Effects and Switching Costs survive feature copying because value lives in users and embedded investment; a moat that collapses when features are matched was never a moat, regardless of which power you claimed.