The First Customer Decision: Land or Anchor?
The first customer decision is whether to acquire customers who represent your eventual target market or to acquire customers who are available and willing to pay but are not representative of the market you want to build for. Landing customers who represent the target market validates the product for the right audience. Anchoring on customers who are accessible but non-representative creates revenue that disguises a product that is not suited for the intended market. The choice is consequential and often made without recognizing it as a choice.
Written by Yashveer Singh, founder of Yashveer Labs.
What you actually need to know
- The first three customers are the most important signal about whether the product is solving the right problem for the right buyer. Choose them deliberately.
- An anchor customer is any customer who pays but does not represent the target market. Anchor revenue is real but anchor feedback is misleading.
- The first paying customer is not validation. The tenth paying customer who looks like the first one is validation.
- The company that optimizes for early revenue often finds, at Series A due diligence, that the customer base is not representative of the market the investors are funding.
- Saying no to an anchor customer -- even one who is willing to pay -- is sometimes the highest-leverage decision an early-stage founder can make.
| Customer Type | Revenue Value | Validation Value | Risk |
|---|---|---|---|
| Landing: exact target market | Medium (may be harder to sell) | Very high | Takes longer to acquire |
| Near-miss: adjacent market | Medium | Medium | Product drift toward adjacent market |
| Anchor: non-representative | High (often more willing to pay) | Low | Product built for wrong customer |
| Vanity: prestigious but wrong | High | Very low | Organizational attention on wrong problems |
The core argument
Every founder who has built a product that found customers different from the intended market has experienced this decision point, often without recognizing it. The first customer is willing to pay. They are accessible. They validate the product and provide the revenue that lets the team keep going. They are exactly what the company needs right now. The problem is that they are a 200-person manufacturing company and the product is designed for 10-person SaaS startups.
Over the next 18 months, the product roadmap is shaped by this customer's requests. Features are added for the specific workflows of a 200-person manufacturing company. The pricing structure is calibrated for the budget cycles of a manufacturing company. The sales motion is built for the 90-day evaluation process of a manufacturing company. When the founder goes to pitch to 10-person SaaS startups, the product is wrong for them in multiple subtle ways, and the pricing and sales motion are misaligned.
This is the anchor customer trap. The customer is real, the revenue is real, and the feedback is honest -- it is just feedback from the wrong customer. The product that results from following that feedback is a product for that specific customer's context, not for the intended market.
The landing customer produces a different outcome. They look exactly like the customer the company intends to build for. Their feedback makes the product better for subsequent customers who look the same. Their willingness to pay validates that the target market has budget for the solution. Their reference -- "this product is solving our exact problem" -- is the reference that lands subsequent customers who look like them. Each landing customer makes the next landing customer easier to acquire.
Identifying the right landing customers
The landing customer profile is more specific than "someone who will pay." It includes: the type of organization (size, industry, stage), the specific role that experiences the problem and has authority over the purchase, the specific variant of the problem the product solves, and the expected relationship between the product and the customer's workflow.
Writing this profile before the first outreach is the discipline that most founders skip. Without the profile, the first customer who is willing to pay becomes the default definition of the target market. With the profile, the founder can evaluate each potential customer against the profile and recognize when a potential customer is an anchor before the relationship is established.
The profile is a hypothesis. The first three to five customers refine it. If the first five customers who meet the profile all value the product and provide consistent feedback, the profile is approximately correct. If they provide inconsistent feedback or find different value in different aspects of the product, the profile needs refinement.
When to take anchor customers
There are situations where taking anchor customers is the right strategic decision.
The first is survival. A startup that will run out of runway in 60 days needs revenue, and the customer who is willing to pay now takes priority over the customer who is a better fit but needs three months to close. Take the anchor customer. Survive. Then resume the deliberate pursuit of landing customers.
The second is learning. An anchor customer in an adjacent market sometimes reveals an unexpected demand that is larger than the intended market. The 200-person manufacturing company that is willing to pay for the SaaS-startup product might be evidence that the product solves a problem that is not SaaS-specific. This is worth investigating before dismissing as an anchor.
The third is the reference. A prestigious anchor customer whose name carries weight in the target market is a deliberate strategy. The customer is not representative, but their imprimatur opens doors with landing customers who are.
In each of these cases, the anchor customer is taken with awareness of the trade-off. The mistake is taking anchor customers without recognizing them as such and treating their feedback as if it were representative.
The signal that anchoring is happening
The clearest signal that a company has anchored on the wrong customer type: the product roadmap is dominated by requests that are specific to one or two customers rather than by needs that are common across all customers. When the roadmap is being driven by "Customer A needs X" rather than "we are seeing X as a consistent need across multiple customers," the company is building for anchors.
The second signal: the sales motion has been calibrated for the anchor customers' procurement process, and new prospects who represent the target market find the process misaligned. The company that developed a 90-day evaluation process for enterprise sales because the first three customers were enterprises will struggle to sell to startups who want to make a purchasing decision in a week.
The third signal: the pricing structure reflects the anchor customer's budget rather than the target market's willingness to pay. A product priced for a 500-person company is priced out of the market for the 20-person company the founder originally intended to serve.
Common mistakes founders make with first customers
- Treating "any paying customer" as validation. Paying customers validate that someone will pay for the product. They do not validate that the target market will pay for it.
- Not documenting the landing customer profile before starting sales. Without the profile, the first paying customer becomes the default profile by accident.
- Letting anchor customers dominate the product roadmap. Tracking which customers are anchor customers and weighting their feedback accordingly is the discipline that prevents anchor-driven product drift.
- Saying yes to prestigious anchor customers without a plan for managing their influence. A well-known brand as a customer is valuable for social proof. It is a liability if the product team builds for their specific needs at the expense of the target market.
- Not recognizing the transition point when anchor revenue is large enough to become the business. The company that was originally targeting startups and is now 80 percent dependent on enterprise revenue has changed markets. This transition should be made deliberately, not discovered accidentally.
Where to start: a 3-step landing customer acquisition
Step 1: Write the landing customer profile. Who is the ideal customer? What type of organization, what role, what specific problem, what does success look like for them with the product? Write this before the first sales outreach. The profile is a hypothesis; refine it based on what you learn.
Step 2: Evaluate each potential customer against the profile before investing in the relationship. For customers who meet the profile, invest fully. For customers who are anchors -- they will pay but do not meet the profile -- decide explicitly whether to pursue them and, if so, how to weight their feedback.
Step 3: Track the composition of the customer base by customer type. What percentage of customers are landing customers? What percentage are anchors? If the anchor percentage is growing, the product is serving the wrong market and the go-to-market motion needs to be re-evaluated.
The Customers That Define the Company
Yashveer Singh. Founder of Yashveer Labs. The first customers for each of my products were chosen with this distinction in mind. For Prominence Football Academy, the landing customer was the academy director who wanted to track player development digitally. Every early customer had to fit that profile. The anchor customers who wanted a more general sports management tool were declined. The product that resulted was right for the landing customer and needed minimal adjustment for subsequent landing customers. That is the payoff.
Related reading
Frequently asked
About me and why that should matter to you
Yashveer Singh. Full stack developer. Founder of Yashveer Labs. Based in New Delhi. The reason it should matter to you is that most engineers writing about this topic have not actually done it. I have. The code is on GitHub. The systems are on real URLs. The portfolio has the proof. The contact channel is Instagram. If the work needs to get done, that is how you reach me.
Posts that line up with this one.
- Founder Decision Frameworks
The Decision to Add Enterprise Sales
When to build an enterprise sales motion, what it costs to run it, and the signals that tell you the timing is right.
- Founder Decision Frameworks
The Decision to Build a Channel Partnership
When channel partnerships create distribution leverage and when they create dependency on a partner who has different incentives than you do.
- Founder Decision Frameworks
Should You Build a Marketplace, a SaaS, or a Service Business?
Three business models, three very different bets. Here is how to pick the one that matches your actual situation.
- Founder Decision Frameworks
Should You Build a Mobile App at All?
A mobile app adds cost, complexity, and app store friction. Here is when it is actually worth it.