Before You Build: A Manifesto for the Strategic SaaS Founder

As you read this manifesto, I am going to introduce three connected ideas.

Build-First Blindness.

Before You Build.

And the person capable of putting both ideas to work, the Strategic SaaS Founder.

None of these ideas are complicated.

But together, they offer a different way to think about building software at a time when AI has made building easier, faster, and more accessible than ever.

Some of what follows may sound contrarian.

We live in a culture that celebrates the launch, the speed of the build, the number of features, and the founder who turned a prompt into a product over the weekend.

I want to talk about everything that should happen before that.

The thinking.

The choices.

The customer.

The reason anyone would choose what you are about to create.

And the business that must eventually exist around the software.

Because building is the easy part now.

Building something people want to buy is not.

So settle in.

This is a manifesto for founders who want to do more than launch.

It is for founders who want to build something worth selling.

TL;DR

• AI has removed many of the barriers that once forced founders to think carefully before building software.
• The easier building becomes, the easier it becomes to build the wrong thing.
• Build-First Blindness happens when founders move into tools, prompts, developers, and features before they have made the business decisions that should guide the build.
• A working SaaS is not the same as a SaaS that sells.
• Positioning, differentiation, distribution, trust, and sales are not tasks to bolt onto a finished product. They should influence the product from the beginning.
• Before You Build is the discipline of deciding what is worth building, who it is for, why those people would choose it, and what must be true for it to become a business.
• A Strategic SaaS Founder does not need to write the code. The founder must know how to direct the build and connect every important decision to the customer and the sale.
• The goal is not to discourage founders from moving quickly. It is to help them move quickly in a direction worth committing to.
• Building something that works is an accomplishment. Building something people choose, buy, use, and continue paying for is the business.

The Great Acceleration

Not long ago, building a software product required considerable commitment.

You needed a technical cofounder, a development team, an agency, or enough money to hire people who could turn your idea into software.

Even a relatively simple product could take months.

That delay was frustrating. It prevented many good ideas from ever being built.

But the delay also forced a conversation.

What exactly are we building?

Who is going to use it?

How much will it cost?

What belongs in the first version?

Is this idea worth the commitment?

The expense of building forced founders to confront those questions, even if they did not always answer them well.

AI has changed the sequence.

A founder can now describe an idea and watch a prototype appear within hours. Interfaces can be generated. Code can be written. Workflows can be connected. Content can be produced. Problems that once required a team can sometimes be handled by one determined person with the right tools.

This is extraordinary.

It is one of the greatest openings for nontechnical founders that I have seen in my career.

But every new advantage changes the kinds of mistakes people make.

When building was difficult, many founders never started.

Now that building is easy, many founders start too soon.

The barrier did not disappear.

It moved.

The hard part is no longer turning an idea into software.

The hard part is deciding whether the idea deserves to become software in the first place.

What Hundreds of SaaS Products Taught Me

I have spent years working between business ideas and the people who turn those ideas into software.

I have helped companies define products, plan complex platforms, evaluate technical approaches, prepare projects for development, and decide what should happen before a team commits months of work.

I have also evaluated hundreds of SaaS and AI products, including products preparing to launch through AppSumo.

When you examine that many products, patterns become difficult to ignore.

Some products are technically impressive but difficult to explain.

Some have dozens of features but no convincing reason to choose them over the alternatives.

Some are built for an audience so broad that nobody feels the product was made specifically for them.

Some solve a problem that customers can already handle with a familiar tool, a simple process, or a few AI prompts.

Some founders have spent nearly all their energy getting the product to work and almost none deciding how customers will discover it, trust it, buy it, and stay.

The technology is not always the main issue.

Many of these products were built competently.

The bigger issue began earlier.

The founder started building before making the decisions that should have guided the build.

Once I understood that pattern, I started seeing it everywhere.

I gave it a name.

Build-First Blindness

Most founders fall into Build-First Blindness. They rush into tools, developers, and AI before they have decided what is worth building, who it is for, why anyone would choose it, and what would make it obviously better than the alternatives. By the time they confront those questions, they may already have spent months and thousands of dollars building a product that is difficult to explain and even harder to sell.

Build-First Blindness does not come from a lack of intelligence or ambition.

It usually comes from excitement.

You have an idea.

You can already picture the product.

You open an AI builder, hire a developer, or begin assembling tools.

Soon you have a login page.

Then a dashboard.

Then features.

Every visible addition feels like progress, and the existence of the product makes the original idea feel increasingly valid.

But software can become more complete while the business remains undefined.

You may still not know:

• Who wants this badly enough to pay for it.
• What those buyers are using today.
• Why they would leave that familiar alternative.
• Which outcome they care about most.
• What would make your product obviously better for them.
• How you will reach those people consistently.
• What will help them trust a new company.
• What will keep them paying after the novelty disappears.

Those are not marketing questions to answer after launch.

They are the decisions that determine what the product should become.

The Old Way: Build Now, Figure Out the Business Later

The familiar founder playbook looks something like this:

1. Have an idea.
2. Choose the tools.
3. Build an MVP.
4. Add the features that competitors have.
5. Polish the interface.
6. Launch.
7. Start asking how to find customers.

It feels sensible because every step produces something visible.

But the sequence is backward.

The founder makes hundreds of product decisions before making the few business decisions that should govern all of them.

By launch, the product has acquired weight.

Money has been spent.

Features have been promised.

The founder has become attached to the original idea.

Changing direction now feels like wasting the work already completed.

So the founder reaches for better copy, more content, paid advertising, a redesigned homepage, or another collection of features.

Sometimes those things help.

But promotion cannot permanently compensate for a product that was never given a compelling reason to be chosen.

And adding more cannot fix a product that does not know what it is trying to become.

A SaaS That Works Is Not the Same as a SaaS That Sells

This is the distinction at the center of everything I do.

A product can work exactly as intended and still fail to become a business.

It can be fast.

It can be attractive.

It can contain useful features.

It can receive compliments from friends, early users, and other founders.

None of that guarantees that enough people will choose it and pay for it.

Customers do not evaluate your product in isolation.

They compare it to the software they already use.

They compare it to doing the work manually.

They compare it to hiring someone.

They compare it to ignoring the problem.

And increasingly, they compare it to asking ChatGPT, Claude, Gemini, or another general AI tool to produce a similar outcome.

This is why your competition is rarely limited to the companies listed on a comparison page.

Your product must earn its place among every reasonable way the customer can get the job done.

That requires more than functionality.

It requires a reason to choose you.

What If We Changed the First Question?

Founders usually begin by asking:

How can I build this?

What if we began with a different set of questions?

What is worth building?

Who is it worth building for?

Why would those people choose it?

What would make it worth paying for?

What must we build to deliver that advantage?

Only then do we ask how to build it.

This is the change in sequence I am arguing for.

I call it Before You Build.

Before You Build

Before You Build is not hesitation disguised as strategy.

It is not endless research.

It is not waiting until every unknown has disappeared, because that day never comes.

It is the discipline of making the most important decisions before they become expensive to change.

It means defining the opportunity before defining the feature list.

It means choosing the customer before filling the roadmap.

It means deciding why someone would choose you before writing the homepage.

It means understanding the path to customers before celebrating the launch.

And it means building the smallest version capable of testing whether your business thinking is correct, not simply proving that the software can function.

Before You Build asks the founder to make four connected decisions.

1. The Opportunity

Every product begins with an opportunity, but not every interesting idea contains one.

An opportunity exists when a specific group of people has a meaningful problem, desire, cost, inconvenience, or unfinished job that deserves a better answer.

The founder must understand what is happening in the customer’s life or work before deciding what the software should do.

How often does the problem occur?

What does it cost them?

How are they handling it now?

Why have the existing answers failed to satisfy them?

What has changed that makes a new answer possible or necessary?

The opportunity is not the software.

The opportunity is the opening the software may be able to serve.

2. The Customer

“Small businesses,” “creators,” “marketers,” and “anyone who needs this” are not customers.

They are crowds.

A useful customer definition tells you who feels the need most, what they are trying to accomplish, what they already understand, what they can afford, and why the problem is important to them now.

The more clearly you choose the customer, the more intelligently you can shape the product around them.

You can decide which features belong.

You can remove the ones that do not.

You can design the experience around familiar workflows.

You can write in language the customer recognizes.

You can reach them in places where they already spend time.

Choosing a customer does not make the opportunity smaller.

It makes the product more valuable to the people most likely to buy it.

3. The Reason to Choose You

Founders often think differentiation means adding a unique feature.

Sometimes it does.

But a product can become meaningfully different through the customer it serves, the outcome it prioritizes, the process it simplifies, the expertise contained inside it, the experience it creates, the way it fits into existing work, or the combination of these choices.

Differentiation is not decoration.

It is not a clever sentence created after the product is complete.

It is a deliberate reason for a particular customer to say:

This was made for someone like me.

This helps me in a way the alternatives do not.

This is worth changing what I do today.

The best time to create that reason is before you build.

4. The Path to a Business

A product does not become a business merely because it exists online.

The founder needs a credible path from attention to purchase and from purchase to continued value.

How will the right customers discover you?

Why will they trust you?

What will help them understand the value?

What will make the decision feel worthwhile?

How quickly will they experience the outcome they came for?

Why will they keep using and paying for the product?

These decisions affect onboarding, pricing, features, support, integrations, content, proof, and the promise you make.

Selling is not what happens after building.

Selling is one of the forces that should shape what gets built.

The ChatGPT Question

AI founders now have an additional question to confront:

Can the main outcome of this product be recreated with a few ChatGPT prompts?

If the answer is yes, you may have created a useful feature without yet creating a product worth paying for every month.

That does not automatically make the idea worthless.

It tells you where the work begins.

Perhaps the value comes from a dependable workflow, accumulated history, proprietary knowledge, collaboration, integrations, automation, accountability, personalization, or an experience that removes work the customer would otherwise have to manage.

The answer will be different for every product.

But there must be an answer.

A thin AI wrapper can be built quickly.

It can also be replaced quickly.

The Strategic SaaS Founder looks beyond what AI can generate and asks what the customer will continue valuing after the novelty is gone.

The Strategic SaaS Founder

The nontechnical founder is often told that the missing piece is technical knowledge.

I disagree.

You need enough technical understanding to make informed choices, ask useful questions, and avoid becoming dependent on people or tools you cannot evaluate.

But your job is not to become the best developer in the company.

Your job is to make sure the company is building the right product for the right customer, for reasons that can become a business.

The Strategic SaaS Founder:

• Does not confuse the ability to build with the readiness to build.
• Does not treat a prototype as proof that customers will pay.
• Does not copy a competitor’s feature list and call it validation.
• Does not postpone positioning, distribution, trust, and sales until launch.
• Uses AI to increase what can be accomplished without allowing AI to choose the direction.
• Understands the customer well enough to decide what belongs in the product.
• Builds differentiation into the experience from day one.
• Knows that removing an unnecessary feature can be a better decision than adding another one.
• Connects the roadmap to the reason customers will choose, buy, and stay.
• Builds with the sale in mind without allowing the sale to compromise the customer.

This founder may never write a line of production code.

That does not make the founder less capable.

It means the founder must become excellent at something different.

Direction.

Priorities.

Tradeoffs.

Customer understanding.

Differentiation.

And turning a collection of software features into something people want to buy.

Build Something Worth Selling

I am not against building quickly.

I am against treating speed as proof that the direction is correct.

I am not against MVPs.

I am against using “MVP” as permission to release a vague product for an undefined customer and hope the business appears later.

I am not against AI builders, agencies, developers, or no-code tools.

I have spent much of my career working with the people and technologies that create software.

I am against asking any of them to make business decisions the founder has avoided.

A developer can build what you request.

An agency can organize a project.

AI can generate an extraordinary amount of output.

None of them can decide what deserves your commitment unless you have done the thinking.

The purpose of Before You Build is not to keep ideas trapped inside documents.

It is to give good ideas a better chance of becoming good businesses.

Then, when it is time to build, build with confidence.

Build quickly.

Build carefully.

Build only what supports the advantage you intend to create.

Build something worth selling.

Then learn how to sell what you build.

The Work I Am Doing Here

This manifesto is the foundation of my work.

I work with founders before they build, helping them define the opportunity, decide who the product is for, why those customers would choose it, and what needs to be built before committing time, capital, or code.

Then I help turn that thinking into something people want to buy, a product that is obviously better, differentiated from day one, and built to speak directly to the right customers.

Through my writing, evaluations, and work with founders, I will continue exploring the questions that live between an idea and a successful SaaS company.

How do you identify an opportunity worth pursuing?

How do you choose the right customer?

How do you create an advantage that belongs inside the product?

How do you decide what the first version must prove?

How do you use AI without creating another interchangeable tool?

How do you earn attention and trust?

How do you turn a product that works into a product that sells?

Those questions are the territory of the Strategic SaaS Founder.

They are the territory I intend to explore here.

A Different Kind of Founder

AI is going to produce more software than the world has ever seen.

More apps.

More features.

More copies of products that already exist.

More founders discovering that launching software and building a business are two very different achievements.

We do not need to add more software simply because we can.

We need founders who can decide what deserves to be created.

Founders who care about the customer as much as the technology.

Founders who choose an audience before chasing one.

Founders who build differentiation before writing claims about it.

Founders who think about the sale before the launch, and the customer after the sale.

Founders who understand that being nontechnical does not prevent them from leading a software company thoughtfully.

Founders who want to create something useful, desirable, valuable, and worth paying for.

If that describes the founder you want to become, then you are exactly who I am writing for.

Welcome.

There is much more to build.

But first, we think.

Before you build.