Find your first customer before you build

The first customer is the real paperwork

You have an idea, no company, no product, and no revenue. Before you file paperwork or pitch investors, find one person who will pay for the job you're solving.

Most early founders assume money is the missing piece. At the minimum viable product stage, with a basic version but no finished product, 40% of surveyed founders named financing as their main obstacle, while 25% named customer acquisition. Among surveyed startups with recurring revenue, 47% identified customer acquisition as the main constraint, while 13% identified financing.

Among surveyed startups that had generated revenue, 76% said they reached first revenue within one year. The rest of the timing is less comfortable: startups often need two to three times longer than expected to validate market demand, and that delay can cause premature scaling or failure. About 90% of startups fail, and a meaningful share of those failures stems from weak demand or difficulty raising capital.

The first customer tests whether the problem is painful enough, whether the buyer has budget, and whether you can explain the offer clearly enough to get a yes.

Run the five checks before you build

Do these before you spend on a logo, a deck, or a polished app. Each one should take minutes, not weeks.

• Pick one painful job. Write one sentence: A [person] needs [task] when [trigger]. Without a person, task, and trigger, you are still describing a vibe.
• List 20 named prospects. Put real names, roles, and companies in a spreadsheet. A category alone is not a buyer.
• Offer a manual concierge version. Show a manual service you will do by hand for a small number of people. An offer that requires a finished product before anyone can say yes is too far from the customer.
• Collect a deposit or pre-order. Have a payment link, a signed pilot, or a refundable deposit ready. A buyer who will not move money has not shown enough pain.
• Write down the exact ask that produced it. Repeat the message, email, or call script that got the yes. The path is not repeatable until you can repeat the ask.

A yes needs money, a date, and a name

A warm intro is useful, but it does not prove the job is painful. A named contact is the person who can say yes. A signed pilot is stronger than a compliment. A refundable deposit is stronger than a promise to think about it.

Keep the first offer narrow: one buyer, one task, and one deadline. When a buyer asks for a discount, ask what they will do differently at the same price. When a buyer asks for a feature, ask which part of the job they will pay for first.

Do not let the first customer become a free consulting project. Set a scope, a price, and a delivery date. When the work is too broad, shrink it until you can finish it by hand.

Make the ask repeatable before you raise

Incorporation is easier after you know who pays. When you need to form a company, do it after the first deposit, not before. That way the paperwork matches the business you actually have.

At the seed stage, investors focus on the team, early user engagement, and signs of product-market fit, the point where users want the product; at Series A, they look for unit economics, or the cost and revenue math of one customer, plus scalable revenue and a repeatable way to acquire customers. Before revenue, startups can show traction with active-user metrics, user stickiness, waitlist interest, pilot agreements, partner relationships, and team strength.

The exact ask matters because it is the first test of a path to customers. Once you can write the ask, you can test it again with the next prospects. Keep the version that worked, and note the one detail that changed the answer.

Do not build the full product until the ask has worked at least once. Build the smallest thing that lets you deliver the manual version, collect the deposit, and learn what the customer actually pays for.

When early conversations produce no payment, change the job, the buyer, or the offer. When they produce payment, keep the ask and repeat it until you have a pattern you can explain.