Most founders launch their product too early or too late; never on time.

Launching a startup from the ground up creates an experience where the founder has to deal with managing risk and complexity of uncertainty.

Today's entrepreneurial environment is saturated with cookie-cutter ideas, which include an unending cycle of "Just ship it" mantras, paired with overly complex and often convoluted business strategies.

Both extremes are not representative of the reality of being an early stage founder.

Launching a startup is significantly more than just releasing a product, it is a well thought out, disciplined approach to managing the risk of a start-up company.

The validation of a new product created through theoretical data will be superseded by cold and hard data once the product launches.

When launching without an actionable framework, the founder is essentially betting against themselves.

Often times, founders will burn a year of their runway, wear down the morale of their team, and spend a lot of money to create a product that should never have advanced past the wireframe stage.

Early stage teams would benefit most from a well-defined evaluation process, in addition to a combination of risk, product and go-to-market viability metrics, as stated in this article.

The Evaluation Matrix will remove the start-up buzzword terminology and replace the traditional list of generic questions, including the clarity of an actionable method for measuring risk, product scope and go-to-market viability.

To summarize: Pre-launch framework

Before coding, building and/or spending marketing dollars related to the launch of your start-up, the launch path must have been de-risked across three core areas.

First, market validation: The pain point at which you want to solve for and the value proposition associated with how much users will pay for the solution.

The growth of a startup is governed by certain restrictions such as:

1) The MVP must be brutally simple (i.e., the startup must create a minimal viable product that simply delivers the core utility of the product while creating a price structure); 

2) For the startup to prepare for operational readiness, it must have only one channel to acquire customers through (the startup should have defined runway and a known failure signal to limit excessive pivots).

It is essential to focus on evidence, not gut instinct to determine whether a startup has potential.

Market validation & demand realities

Decision 1: Pain point threshold

Many founders become enamored by providing elegant solutions for problems that do not actually exist (i.e., the entrepreneur believes they have created a new solution when it is likely just a re-engineering of an existing solution).

Therefore, determining if a problem is minor or major pain point will be the first step of judging the potential viability of a startup.

If a target market is not suffering enough from the pain point to change their behavior or to shift budget dollars away from existing solutions, there is limited potential for a startup in that target market.

To make this determination, the founding team should analyze the pain points and flaws associated with existing solutions.

If the target users of the potential startup solution are actively trying to engineer poor solutions by piecing together numerous disparate software tools, utilizing spreadsheets, or using a manual process, there is a very high likelihood that the existing problem is a significant pain point.

Conversely, if the potential users of the product simply voice their discontent with existing solutions and display no desire to take action to solve the problem, the demand for the solution is illusory.

To validate the pain point, a startup founder must be able to provide copies of at least 20 customer discovery calls (or some other evidence) where customers discussed this specific pain point in their own words.

Sign of Failure: Customers will provide a high degree of passive complimentary feedback (e.g., "Oh, that's a great idea") but will show zero willingness to prepay, sign letters of intent, or participate in a demanding pilot program.

When the pain point does not cross the threshold, the startup founder should immediately abandon that concept and pivot to addressing the current problem that these users are spending either money or time on to fix.

Decision 2: Specify the antipersona

Knowing who to build for is important.

However, equally as important is knowing who you will choose to ignore while developing your initial product.

Products that are developed as "products for everybody" at launch actually end up being products for nobody.

It is the responsibility of startup founders to create a clearly defined subset of the early adopter group, which will endure through the challenging iterations of your product until it reaches Version 1 (the core utility is very valuable to that user).

To accomplish this it is necessary for the startup founder to create an antipersona that describes the types of users that the company will purposefully exclude in the initial launch of the product.

For example, let us consider a B2B workflow tool.

If the founding team builds their product to target enterprise compliance officers as well as freelance graphic designers simultaneously, the product roadmap will fracture as the needs of each of those user groups is drastically different.

Both of these users will require two very different solutions.

The enterprise user will need a complex set of permission layers as well as SOC2 compliance, while the freelance graphic designer will need extreme simplicity and fast checkout.

Focusing on an extremely defined niche will enable the startup to gain momentum.

Green Light: You're able to identify the exact job title, size of the company, and specificity of the daily workflow for your target users, and you feel completely comfortable turning away any users outside that exact description.

Decision 3: True demand vs. market size

The Total Addressable Market (TAM) is a commonly cited metric in pitch decks to entice venture capitalists.

True demand is the actual revenue that you will take in the next month.

It is necessary for founders to determine whether they are entering an existing market to take market share from existing players or if they are attempting to create an entirely new consumer behavior.

Taking market share from a competitor requires either offering a superior product or proving better distribution capabilities, whereas changing a consumer behavior will require a significant capital barrier, and years of consumer education efforts.

Many of the startups working on new products haven't started raising any capital either; therefore, most lack adequate funds to educate their target market about the new product they intend to launch.

In order to identify if you have sufficient demand for your new product offering, you should be able to identify the number of people searching for information on how they can solve their current problem(s).

You should also search for social media platforms like reddit and/or Facebook where you can find people actively asking others for ideas on how to solve their problem(s).

A distorted perception of your potential market size provides an unrealistic level of confidence in terms of the feasibility of your new product.

Locating the initial 100 customers for your new product will be much easier than trying to find 100 customers after first attempting to estimate how big your overall market will be.

Product limitations & trade-offs

Decision 4: Defining the scope of your Minimum Viable Product (MVP)

What is the bare minimum of functionality necessary for customers to perceive value?

The most common mistake founders make is equating their mvp with their minimum viable product or simply a poorly-executed version of the final product.

An MVP is designed to demonstrate the essential elements of value, not to include every conceivable feature, capability or enhancement.

Product design mistakes are made when companies "fluff" or inflate their support for their MVP by adding unnecessary "fluff" (features) to the initial offering.

A scheduling tool does not need extensive custom scheduling themes, social media capabilities, and advanced statistical analysis.

The primary goal of a scheduling application is to book a meeting without the user double booking his/her appointment.

Any additional capabilities or features will simply increase the time to market, deplete the project budget, and result in the addition of new bugs.

Decision Threshold: Will your customer achieve his/her primary goal within the first five minutes of using the app?

If the answer is yes - your definition of your MVP is accurate.

If the answer is no, your app is either too complex, or the value proposition of the app is buried in the engineering. Keep cutting until the core utility of your product cannot be missed.

Decision 5: Pricing and monetization model of the product launch is critical

Monetization should not be an afterthought that gets tacked on just before launching the product.

If the founders want to generate revenue before launching the product, they must first determine how they want to charge their customers.

The monetization model must match their customer acquisition cost (CAC) and overall go-to-market strategy.

Options available to the founders include: subscription, freemium, pay-per-usage, and high-ticket enterprise sales.

Freemium pricing is frequently misrepresented as a pricing model; in fact, freemium pricing is an acquisition channel.

If a startup creates and releases a freemium tier for its product without incorporating a built-in viral network effect, it will essentially pay for the ongoing costs of maintaining the tier with the customer acquisition costs associated with providing a free tier to its customers.

By charging customers from the very start, the founders will be intellectually honest.

This type of model will automatically screen out those who are merely curious from those who are true potential customers.

A founder will provide the evidence of the need for the product by performing a pricing trial and providing landing pages for the pricing.

The failure signal is: Relying on cheap paid advertising to sell a $5-monthly product with a significant expectation of high churn; the math simply cannot work.

Decision 6: Early defensibility strategy

What prevents a competitor with ample resources from replicating this product in an extremely short timeframe?

This is probably the most brutal part of the decision-making process for a founder.

Software features are not a defensible moat; they can be cloned.

The user interface can be copied.

The founders of a startup must determine what their true unfair advantage will be prior to entering the marketplace.

There are typically four areas that will provide a startup with their defensibility at launch.

These include: proprietary data that no one else has access to, an already-established and active community that supports the founder, a team of experienced advisors that has access to significant networks and connections, and existing products that serve as an anchor or point of reference.

The startup can utilize operational efficiency to successfully undercut competitors by maintaining operational efficiencies that allow them to operate profitably while undercutting their competition, or they can create a user expérience that exploits the network effect advantage inherent in their product.

If the only advantage the startup has for its product is a superior user interface, it will be at risk of failure.

Therefore, a startup must know where its competitive advantage (moat) is located, and aggressively invest the resources required to expand it.

Go-to-market and growth financial model

Decision 7: Select the one scalable acquisition channel

The only scalable channel available at the startup's early stage is one channel.

A common early-stage mistake made by many startups is to adopt a shotgun approach to their marketing strategy, where founders try to pursue multiple acquisition channels at the same time (e.g., SEO, PPC, cold outbound emails, and TikTok campaigns), and as a result, are not able to realize success from any of them.

Startups need to define which acquisition channel corresponds best to the user's intent and the startup's available resources.

When the product solves an urgent, immediate pain point for the user (i.e., fixing a broken computer hard drive), the best acquisition channel to pursue is through paid search because the user is highly motivated and has an incredibly high level of intent.

Conversely, if the product is highly visual and appeals to the consumer demographic, then the best acquisition channel would be through utilizing a visual platform, such as TikTok.

Choose one acquisition channel only.

Learn the unit economic model for that acquisition channel. Then, move on to other channels after the startup has achieved its initial revenue goal.

Decision 8: Sequence the launch strategy

Will the startup pursue a rolling launch strategy, a closed beta, or a large-scale public release?

The tech industry places a high premium on the successful "big bang" launch strategy.

In this model, founders will often spend months leading up to one day of significant promotion on Product Hunt or Hacker News with the hope of attracting a flood of traffic that will validate their existence.

There is a tendency for people launching new applications to receive a significant amount of attention from unqualified users when the application first becomes available.

This leads to an immediate drop in user activity after the initial spike in interest.

Instead of gaining this early attention, companies that take a rolling launch approach benefit from the ability to collect data on real user workflows and to fix critical bugs, make changes to the onboarding processes, and gather insights into how users interact with their product all without the pressure of a public audience.

Most importantly, rolling launches help startups preserve the integrity and reputation of their brand by allowing them to gather critical data, learn from failures, and improve their product chances of success without any significant long-term damaging effects to their brand.

The tradeoff for the rolling launch is that the quicker you can get feedback from users, the more likely it is that the brand can achieve the same level of credibilities, as if it had launched to the public.

Operational reality and readiness

Decision 9: Runway and financial

What will the average length of time and amount of money a startup can burn through before achieving true product-market fit?

This is a mathematical decision, not an emotional decision.

All founders should establish their personal and corporate burn rate limits prior to starting any work on their product.

Hope is not a valid financial strategy.

If a startup is aiming at enterprise B2B customers, the sales cycle will typically take 6 to 9 months to complete — if a startup only has 4 months of runway, it is mathematically "dead in the water" even before it gets launched.

Companies should determine exactly how much money it will take to keep servers operational and feed staff through the designated pre-launch "sprint", as well as the subsequent six months of iterative product-testing, etc.

Green Flag — A startup has prepared a worst-case scenario budget, drastically cut its personal expenses, and still has enough financial runway to endure a minimum of three product pivots post-launch.

Decision 10: How to determine when an idea has failed

When is there an undeniable signal for the end of an idea?

Many startups have failed ideas that keep going because there was never a decision made about when to stop.

The founders hold out hope that maybe the idea will take off because they have some paying customers, however small, or they received positive responses to their idea.

Startups are often referred to as "zombies," where they continue to drain a founder's time and financial resources over several years without ever getting anywhere near profitability or scale.

The last decision to make before launching is to set objective, unemotional guidelines to define failure.

Set the kill switch earliest.

A good example of a threshold would be: "If we don't get 100 paying customers at our desired price point within 90 days after beta launch and/or our CAC is three times greater than our LTV, we will stop selling the product and/or do a major pivot."

By making these guidelines when all parties are rational, it helps eliminate any future emotional attachment to and inhibits the potential for a stellar business opportunity from developing.

Final thoughts on how founders escape the pre-launch phase

Planning can be a very sophisticated way for founders to procrastinate.

It is as dangerous to launch without a plan as it is to spend too much time finding out what competitors are doing and making plans about product features.

Startup founders need to do this pre-launch phase as a time-limited sprint.

Use the ten decisions above as a checklist in order to establish operational guidelines.

Get concrete evidence for every assumption made about your startup.

Help founders to face the harsh realities surrounding the size of the potential market, the appropriateness of pricing structures, and how to actually distribute the product through the existing channels.

The end of the preparation segment in preparing for market entrance is achieved once the founders have developed their first core utilities, identified a defined audience, and developed a means of measuring failure.

The idea factory, often referred to as the "echo chamber" of pre-launch theory has little if any value at this point.

It is time for product release, accept input information, and make adjustments as necessary.

Q&A before launch (Most common questions)

Should founders do pricing tests prior to having a fully developed MVP?

Yes! Waiting until the MVP has been created before testing pricing is one of the biggest strategic blunders founders can make.

Founders can easily verify that someone is willing to pay for the service, by designing a high-fidelity landing page, with several pricing tiers.

They should drive highly relevant traffic to the landing page and track the number of "Intent to Buy" click-throughs.

This gives the founder the data needed to determine if they are entering the market with a viable business model before investing in product engineering.

What is the standard timeframe for completing a validation sprint?

The ideal pre-launch validation time frame will be 30–45 days MAXIMUM.

If a founding team is unable to identify a painful problem, identify the right target persona and provide qualitative evidence of demand to support that persona, within a 6-week timeframe, there is a good chance the core concept will be too general in nature. 

There is also a danger of the founding team falling into the "endless market research cycle" unless they set a deadline for completing this phase and use the deadline to force themselves into taking swift action.

What do founders typically do just before launch that causes the greatest issues?

The most common mistake is expanding the MVP description, for instance, the Founder becomes anxious, believes the product can't compete without adding "just one more feature."

This creates interference with production timelines, may introduce unexpected bugs and conflicts with the MVP's core value proposition.

Founders need to maintain focus on their original MVP level of simplicity and defend that simplicity against unintended feature expansion during the pre-launch time period.