Primer - Startup Positioning Narrative Framework For Founders

Startup Positioning Narrative Framework: Claim A Wedge For Founders

Startup Positioning Narrative Framework: Claim A Wedge For Founders

Questions Addressed By This Primer

  • How do you build a startup positioning narrative framework that investors and customers can repeat in one sentence?
  • What are the concrete steps to turn a vague vision into a sharp, testable wedge story that guides product and GTM decisions?
  • How should founders define the “enemy,” the “wedge,” and one flagship proof moment so the story feels credible rather than inflated?
  • What recent shifts in fundraising and AI-heavy markets make wedge-focused positioning more important than generic category claims?
  • What risks come from an over-broad or fundraising-only narrative, and what signals show that the story is starting to drift?

Executive summary / TL;DR

A startup positioning narrative framework turns “what the product does” into a crisp belief about why the market is changing, why the old way is failing, and why the team’s wedge is the fastest path to proof. Done well, it doesn’t inflate the vision. It makes the vision credible by anchoring it to a narrow, winnable first beachhead and a clear tradeoff that competitors won’t take. The practical outcome is sharper investor meetings, faster customer learning, and fewer deck rewrites because the story drives the slides, not the other way around. The playbook below helps founders pick the right enemy, define a wedge that buyers can repeat, and connect early evidence to a long-term arc without overpromising. It’s built to work whether the motion is sales-led, PLG, services-first, or marketplace.

Background and context

Most early-stage companies don’t lose because the product is confusing. They lose because the story is indistinguishable from everyone else’s story, so prospects and investors can’t form a simple mental model of what the company will be “known for” first.

Positioning is the choice of a battleground, not a description of features. Narrative is how that choice becomes memorable and transferable across a deck, a website, outbound messages, demos, and hiring conversations. When narrative and positioning drift apart, the company starts pitching an empire while operating a wedge, and the wedge never compounds into a category.

A strong narrative does two jobs at once. It reduces perceived risk by making the wedge feel inevitable, and it creates urgency by making the status quo feel fragile, expensive, or outdated.

Startup positioning narrative framework essentials

A useful startup positioning narrative framework can be judged by three tests. It should be repeatable by someone else, defensible in a competitive conversation, and usable as a decision filter for product and GTM choices.

Repeatability means a buyer can explain the company in one sentence without needing a follow-up call. Defensibility means the story has a sharp tradeoff that rules out a credible alternative, not just a “better” version of the same approach. Usability means the story tells the team what to say no to, even when the opportunity looks tempting.

If any one of those tests fails, the narrative might still sound good, but it won’t steer the company. And when the story doesn’t steer the company, the market ends up steering it.

Step-by-step playbook (4–7 numbered steps)

  1. Name the change, not the trend.
    Start with a market shift that changes what buyers can do, not a buzzword they’ve already heard. “AI is everywhere” isn’t a shift. “Decision-making moved from dashboards to workflows, so the UI is no longer the product” is a shift. If the shift can’t be linked to a concrete before-and-after in the buyer’s day, it’s too abstract.

  2. Pick a single enemy the buyer already hates.
    The enemy is rarely “competition.” It’s the costly behavior the buyer is stuck in: manual reconciliation, long security reviews, spreadsheet approvals, brittle integrations, or the constant swivel-chair between tools. Don’t describe the enemy as incompetence. Describe it as an outdated default that smart teams still fall into because incentives and tooling push them there.

  3. Define the wedge as an unfair tradeoff.
    A wedge isn’t a small market. It’s a small promise that can be proven quickly. The wedge should include a tradeoff competitors won’t match without breaking their model: setup time vs control, speed vs customization, self-serve vs compliance, automation vs explainability, or breadth vs depth. If there’s no tradeoff, the wedge is just a niche label.

  4. Write the “because” sentence.
    Create one sentence that ties the shift to the wedge:
    “For [ICP], the old way fails because [enemy], so [company] wins by [wedge mechanism], which shows up as [measurable outcome].”
    This sentence becomes the spine for the deck’s problem slide, solution slide, and why-now slide. It also keeps messaging from drifting into feature tours.

  5. Prove the wedge with one flagship moment.
    Pick a single moment that makes the wedge tangible: a 10-minute onboarding, a “first report” delivered in a day, a security review completed with one evidence pack, or a workflow that closes the loop without handoffs. That moment should be demonstrable live. It’s okay if the rest of the product is still evolving, but that flagship moment can’t be fuzzy.

  6. Connect early proof to a believable expansion path.
    Investors and buyers will ask, “What happens after the wedge works?” The answer shouldn’t be “we’ll go upmarket” or “we’ll add features.” It should be a sequence: adjacent user, adjacent workflow, adjacent buyer, adjacent channel. That sequence keeps the long-term vision intact without claiming every customer on day one. If the expansion path can’t be described in three steps, it’s too loose.

Deep dive: tradeoffs and examples

A wedge story often breaks in two predictable ways. The first is when the narrative promises a platform but the wedge only delivers a tool, so the buyer hears “extra risk.” The second is when the wedge is real but framed as a category that’s too broad, so the company picks a fight with incumbents before it has proof.

One way to keep the narrative honest is to separate “vision language” from “wedge language.” Vision language explains the direction of travel and the future default. Wedge language explains what ships now, why it’s different, and what it replaces first. The deck and website can hold both, but the opening must lead with wedge language or the meeting turns into a debate about market size instead of execution.

For an investor-facing example of keeping ambition while tightening the first claim, adapt the narrative discipline used in Series A investor expectations. The story earns attention by making the first proof point concrete and then letting the category expansion read as a consequence, not a hope.

For a customer-facing example, a wedge narrative gets stronger when it ties to ROI and pricing reality instead of generic efficiency claims. The thinking behind AI ROI and pricing reality maps well here because it forces a “what replaces what” answer and a measurable outcome that a buyer can defend internally.

For a category narrative example, it helps to study how large players frame “owning the stack” to justify focus, sequencing, and why-now. Even if the product is different, the narrative mechanics in owning the stack as strategy can inspire a clearer cause-and-effect chain between wedge, control points, and long-term leverage.

What changed lately 

More founders are competing in crowded markets where surface-level differentiation disappears fast, especially in AI-enabled categories. That’s pushed investors to look harder for what Andreessen Horowitz describes as an “earned secret,” meaning a differentiated approach and head start that isn’t available to every fast follower with the same tools.

Alongside that, the wedge conversation has matured. The most credible wedge pitches aren’t “smaller versions of the end state.” They’re deliberately chosen entry points that set the competitive arena by choosing words, scope, and the first buyer where winning is plausible, a point emphasized in a16z Speedrun guidance on finding a wedge.

The practical implication is simple. Positioning work is shifting from clever taglines to proof-backed narrative choices: a narrower first promise, a clearer tradeoff, and a sharper explanation of why the new default should exist now, not someday.

Risks and what to watch next 

A wedge story can become a trap if it’s optimized only for fundraising. If the wedge doesn’t map to a repeatable acquisition channel and a repeatable activation moment, the company can win meetings and still lose quarters.

Another risk is “vision inflation,” where the story keeps expanding to avoid saying no. That can quietly reset the competitive set from “small and winnable” to “broad and crowded,” which slows down learning and makes every objection feel valid. A useful corrective is the reminder to sell the wedge that can be proven, not the empire that might exist later.

Watch for one operational signal. If sales calls and product decisions keep requiring exceptions to the narrative, the narrative isn’t acting as a filter, and the wedge likely isn’t sharp enough to defend.

For a fast rewrite that turns the current deck and website into one coherent story, use the framework above and then book a call to pressure-test the wedge, tradeoffs, and flagship proof moment against real investor and buyer objections.

A narrative that compounds doesn’t need to be loud. It needs to be specific, provable, and consistent across every touchpoint, so the market starts repeating it for you.

Share:

Primer - How To Prioritize Customer Requirements using MoSCoW Framework

What is MoSCoW Framework? What are the Pre-Requisites before MoSCoW Framework can be implemented?How to Determine Priority of Requirements? Why MoSCoW

The MoSCoW Framework to Align Customer Requirements with Value

Questions Addressed by this Primer:

  • What is MoSCoW Framework?
  • What are the Pre-Requisites before MoSCoW Framework can be implemented?
  • How to Determine Priority of Requirements?
  • What is difference between MoSCoW and Agile Frameworks?
  • When to Use the MoSCoW Framework?

What is MoSCoW Prioritizing Methodology?

The MoSCoW method is a popular prioritization technique for managing requirements, aligned with value driven outcome. Software development expert Dai Clegg created the MoSCoW method while working at Oracle. He designed the framework to help his team prioritize tasks during development work on product releases. Detailed account of using MoSCoW prioritization in the Dynamic System Development Method (DSDM) handbook.


Video summary of the article:

The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won’t-have. Some companies also use the “W” in MoSCoW to mean “wish”.

1. Must-have initiatives are “musts” for your team. They represent non-negotiable needs for the project, product, or release in question. For example, if you’re releasing a healthcare application, a must-have initiative may be security functionalities that help maintain compliance.

2. Should-have initiatives are just a step below must-haves. They are essential to the product, project, or release, but they are not vital. If left out, the product or project still functions. However, the initiatives may add significant value.

3. Could-have initiatives would be nice to have but are not essential.

4. Won’t-have (this time) initiatives are those that are not essential and can be excluded from the project without jeopardizing its success.

What are the Pre-Requisites before MoSCoW can be implemented?

Before running a MoSCoW analysis, a few things need to happen. First, key stakeholders and the product team need to get aligned on objectives and prioritization factors. Then, all participants must agree on which initiatives to prioritize. At this point, the team should also discuss how they will settle any disagreements in prioritization. If you can establish how to resolve disputes before they come up, you can help prevent those disagreements from holding up progress. Finally, you’ll also want to reach a consensus on what percentage of resources you’d like to allocate to each category.

How to Determine Priority of Requirements?

With the groundwork complete, you may begin determining which category is most appropriate for each initiative. To choose an objective ranking or scoring system for MoSCoW prioritization, you will need a separate ranking methodology. You can choose from many, such as:

1. Weighted Scoring: A prioritization method that assigns scores to initiatives based on their importance and impact.

2. Value vs. Complexity: A prioritization method that evaluates initiatives based on the value they provide and the complexity of implementing them.

3. Kano Model: A prioritization method that evaluates initiatives based on their ability to satisfy customers.

4. Buy-a-Feature: A prioritization method that involves customers or stakeholders in the decision-making process by giving them a budget to "buy" the features they want.

5. Opportunity Scoring: A prioritization method that evaluates initiatives based on their potential to generate revenue or achieve strategic goals.

Scenario: How do Apply MoSCoW to a Software Release?

Here is an example of how a tech company might apply the MoSCoW method to prioritize features for a new software release:

1. Must-have: These are non-negotiable requirements that the software must have in order to function. For example, compatibility with the latest operating systems and security features to protect user data.

2. Should-have: These are important features that add significant value to the software but are not vital for its basic functionality. For example, integration with other commonly used software or improved performance and speed.

3. Could-have: These are desirable features that would enhance the user experience but are not essential. For example, a new user interface design or additional customization options.

4. Won't-have (Wish): These are features that are not essential and can be excluded from the current release without jeopardizing its success. For example, support for less commonly used languages or niche functionality.

The tech company would gather all the requirements for the new software release and evaluate their value and urgency vs the value they create. Each requirement would then be assigned to one of the four MoSCoW categories using clear and objective criteria.

MoSCoW vs Agile Methodology:

The MoSCoW method and Agile methodology are not directly comparable as they serve different purposes. The MoSCoW method is a prioritization technique that can be used within Agile methodology to help manage requirements.

Agile methodology is a project management approach that emphasizes flexibility and customer satisfaction. It involves iterative development, where requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams.

Here are 2 pros and cons of each:

MoSCoW method:

Pros:

  1. Easy to use and understand.
  2. Helps resolve disputes and form agreements with stakeholders.

Cons:

  1. Can be subjective as it relies on the team's judgment to categorize initiatives.
  2. May not work well for complex projects with many interdependent tasks.

Agile methodology:

Pros:

  1. Emphasizes flexibility and adaptability to changing requirements.
  2. Encourages customer involvement and feedback throughout the development process.

Cons:

  1. Can be challenging to implement in organizations with rigid hierarchies and processes.
  2. May require more time and effort for planning and communication.

Conclusion:

The MoSCoW method is a prioritization technique that can be used to manage requirements. It is generally used in Agile project management and software development companies, but the principles can be useful for helping any business to prioritize tasks.

You can use the MoSCoW method when you need to:

  • Prioritize tasks or initiatives within a project.
  • Resolve disputes and form agreements with stakeholders.
  • Ensure a minimum viable product is produced.
  • Set priorities at different levels of the development pipeline. 

Share:

Primer - What is a Business Model and How to Write One

What is a Business Model? How to write a Business Model? What are the key tenants of a Business Model? What are examples of Business Models? SaaS

What is a Business Model and How to Write one

Questions Addressed by this Primer:

  • What is a Business Model?
  • How to write a Business Model?
  • What are the key tenants of a Business Model?
  • What are examples of Business Models?
  • What should a Business Model cover?
  • How to write a Business Model for a SaaS?

What is a Business Model?

A business model, in general, is a blueprint for how a company intends to produce and capture value. This might encompass anything from the items or services the company intends to offer to the target market to whom the company intends to sell to the method by which the company intends to earn income.

What are the key tenants of a Business Model?

One of the first stages in beginning a business is to develop a business model. This is because the business model will define many critical aspects of the firm, such as the revenue streams and operational expenses. Businesses should begin by thinking all of the numerous ways they may potentially generate value and so make money. After they have a clear knowledge of the many revenue sources accessible to them, they can begin to narrow down which options are the most viable and would work best for their firm.


After a company has decided on a few prospective income streams, it should consider its target market. Who are the customers most likely to purchase the products or services offered by the company? What are the clients' needs that the company can meet? Addressing these questions will assist the company in tailoring their products or services to better fit the demands of their target market, increasing the likelihood of sales.


After deciding on a target market and identifying a few prospective income sources, the following stage is to develop a strategy for generating money. This strategy should include how the company will promote and sell its products or services, as well as the prices for these items or services. The strategy should also contain a budget for the marketing and advertising activities that the company will need to conduct in order to reach their target market.

How to Apply a Business Model to a SaaS Offering?

Now let's apply this high-level framework to a "Software as a Service (SaaS)" Offering:

What is a SaaS?

SaaS business models are focused on offering software on a subscription basis. The price model is often subscription-based, with consumers paying a monthly cost for access to the software. Businesses must have a clear grasp of their value proposition, target market, and pricing strategy before developing a SaaS business model.

Value Proposition: 

Your value proposition is why your target market should purchase your software. What will your software provide for your consumers that they won't be able to find anywhere else? How would it improve their lives? Once you've developed a solid value proposition, you may consider your target market, pricing approach, and go-to-market (GTM) plan.

Target Market: 

Who are you going to sell your software to? What are the market's demands that your program can meet? What are the market's demographics? What are the rivals' pricing strategies in this space? You may begin to develop your pricing plan once you have a solid grasp of your target market.


Pricing Strategy: 

There are several price models available for SaaS firms, and the one you pick will be determined by your target market and value offer. Subscription-based, pay-as-you-go, and usage-based pricing schemes are the most frequent.

Customers pay a monthly price for access to your product when you use subscription-based pricing. This is the most prevalent pricing plan used by SaaS companies. Customers that utilize pay-as-you-go pricing pay only for the resources they use. This pricing model is frequently employed by enterprises with varied consumption patterns.

Customers that pay on a usage basis pay for your program each time they use it. This pricing model is frequently employed by enterprises with high-volume usage or that need to track consumption for invoicing purposes.

When you've decided on your price model, you should think about your marketing strategy. How will you reach out to your target audience? What marketing and sales strategies would you use for your product?

There are several potential go-to-market tactics for SaaS companies. Direct sales, collaborations, and resellers are all typical methods of distribution. Each of these techniques has advantages and downsides, so you must carefully assess which one is best for your company.

You may begin to build out your SaaS business model once you have a firm grasp on your target market, value offer, and pricing plan. You'll be able to take your company to the next level if you have a well-defined business plan.


Since the early 2000s, SaaS has been a popular business model for many companies. Salesforce, HubSpot, Workday are success stories of companies using SaaS, whilst three companies – Basecamp, clubhouse, and Teespring – have all failed after using the SaaS business model.

Developing a business model is an essential step for any company, large or small. It will aid in determining the viability of the firm and provide the owners with a better grasp of the various methods they might generate money. Businesses may boost their chances of success and be better prepared for the difficulties that lie ahead by taking the time to develop a business model.
Share:

Primer - What is a Business Plan and How to Write it

What is a Business Plan? Why is it important to Write a Business Plan? How to write a Business Plan to secure loans (SBA)? How to write a Business Plan for any business? What are the Elements of a Business Plan? Who can Write a Business Plan? What is a Business Plan used for?

What is a Business Plan and How to Write it

Questions Addressed by this Primer:

  • What is a Business Plan?
  • Why is it important to Write a Business Plan?
  • How to write a Business Plan to secure loans (SBA)?
  • How to write a Business Plan for any business?
  • What are the Elements of a Business Plan?
  • Who can Write a Business Plan?
  • What is a Business Plan used for?

A business plan is a written document that outlines a company's goals and how it plans to achieve them. It is a road map for businesses, outlining where they want to go and how they plan to get there.

McKinsey & Company, a leading global management consulting firm, defines a business plan as 'a formal statement of a set of business goals, the reasons why they are believed attainable, and the plan for reaching those goals. It may also contain background information about the organization or team attempting to reach those goals.'

Why is a Business Plan important?

A business plan is important for a number of reasons. First, it can help entrepreneurs to clarify their business idea and ensure that it is feasible. Second, it can be used to secure funding from investors or lenders. Third, it can help businesses to track their progress and performance over time.

What are the Elements of a Business Plan?

A good business plan should include:

  • An executive summary

The executive summary is a brief overview of the business plan, and should include the company's mission statement, a brief description of the products or services offered, the target market, the company's competitive advantage, and the company's financial goals.

  • A description of the business

The description of the business should include the company's history, if any, as well as a description of the company's current products or services. This section should also describe the company's manufacturing or production process, if applicable.

  • The market opportunity

The market opportunity section should describe the size and growth potential of the target market, as well as the company's competitive position within that market.

  • The company's competitive advantage

The company's competitive advantage should be described in detail, highlighting the unique selling points of the products or services offered.

  • The company's goals and objectives

The company's goals and objectives should be realistic and achievable, and should be aligned with the market opportunity and the company's competitive advantage.

  • A marketing plan

The marketing plan should outline the company's marketing strategy, including the target market, the company's marketing mix, and the company's sales and marketing objectives.

  • A financial plan

The financial plan should include a detailed description of the company's financial goals, as well as a pro forma income statement, balance sheet, and cash flow statement.

  • A detailed description of the product or service

The detailed description of the product or services should clearly articulate what the product or service is and how it creates value for the customers.

How to Write a Business Plan?

The first step in writing a detailed business plan is to conduct a thorough market analysis. This will help you to understand the potential customer base for your product or service, as well as the competition you may face. Once you have a good understanding of the market, you can then start to develop your business plan.

One of the most important aspects of your business plan is your financial projections. This section should include a sales forecast, as well as information on your operating expenses. It is important to be realistic when developing your financial projections, as this will help you to secure funding.

Once you have developed your business plan, you can then start to implement it. This may involve setting up a website, developing marketing materials, and securing funding. However, it is important to remember that your business plan is a living document, and it should be updated as your business grows and changes.

What is the Business Plan used for?

The business plan is used by entrepreneurs to secure funding from investors or banks, and to provide a roadmap for the business's growth. It is also used to assess the feasibility of a new business and track its progress over time. On the other hand, The business plan helps potential investors or lenders understand the company's goals, how it plans to achieve those goals, and the risks involved. 

Summary:

No matter what kind of business you want to start, you need a business plan. A good business plan is essential for any business, whether you're just starting out or you've been in business for years. It's especially important if you're seeking financing from investors or lenders.

A business plan is your roadmap to success. It outlines your business goals, strategies, and how you plan to achieve them. It also includes your marketing plan and financial projections.

If you're not sure where to start, there are plenty of business plan examples and templates available online. You can also hire a professional business plan consultant to help you create a winning plan.

About Us:

MD-Konsult.com, is a Startup and Small Business Focused Consulting Firm. We have a Business Planning templates, that we use with our clients to ensure our clients tee off on the right footing towards success.

Share: