Execution Feasibility & Customer Reach Lenses — Why OpenSeed Separates the Two Questions

#Why the Two Lenses Are Separate

Business plans often bundle execution planning and customer acquisition strategy into the same section. When one is strong, the other's weakness gets buried in the average. In practice, these two issues fail independently. A team with real capability can still miss customers if they have no channel; a well-defined market can still produce no product if there's no one to build it. The two failure types have different root causes and different fixes.

OpenSeed handles them as two distinct review lenses. The Execution Feasibility lens asks: 'Can this team actually execute this plan?' The Customer Reach lens asks: 'If they execute, can they actually reach customers?' A wide gap between the two scores is a signal that the weaker lens is dragging down the entire business risk profile.

#Execution Feasibility Lens — What It Looks For

The Execution Feasibility lens checks whether the timeline, team, and budget described in the plan can realistically fit together. Even a great idea stays on paper if the execution conditions aren't in place. There are four key dimensions this lens examines.

The most common issue flagged by this lens is a timeline with no owner. A plan might say the app launches in three months, but there's currently no developer on the team — or the developer is tied up on another project.

#Customer Reach Lens — What It Looks For

The Customer Reach lens asks how you'd acquire your first customers — and at what cost — assuming the product is finished. Market size numbers don't factor into this score. No matter how large the total addressable market, the score suffers if there's no concrete path to reach it.

Scoring well on this lens requires more than 'we'll market after launch.' The plan needs evidence of customer contact before launch — or a concrete path to that contact.

#3 Patterns That Hurt Your Score — and How to Fix Them

Three patterns consistently produce low scores across both lenses. Each has a different symptom and a different fix.

1. Pattern 1: The entire execution plan relies on outsiders — Development, design, and marketing are all planned externally, with no internal capability. The Execution Feasibility lens flags this as outsourcing dependency risk. Fix: If contractors are already lined up, provide evidence (signed agreements or documented conversations) and include a roadmap for building capability in-house.
2. Pattern 2: Large market, no first touchpoint — Market size numbers are specific but there's no description of where the first 100 customers come from. The Customer Reach lens flags this as channel absence. Fix: Identify a reachable group of potential customers right now — a community, industry association, or existing network — and write one to two paragraphs on how you'd approach them.
3. Pattern 3: Both lenses are purely forward-looking — Execution and customer reach are described entirely in future tense, with no current validation on record. Both lenses accumulate deductions. Fix: Document anything you've already done — five customer interviews, responses to a pre-registration form, a pilot sale — and add it to the plan.

All three patterns share the same core weakness: 'What do you have right now?' is underdeveloped. A business plan describes the future, but the review lenses judge future potential through present-day evidence.

#Checklist for Passing Both Lenses

Use this checklist when writing a business plan that satisfies both the Execution Feasibility and Customer Reach lenses. Any item you can't check off is the first place to strengthen your plan.

• Each team member's name, role, and relevant experience are connected to the product domain.
• Every milestone has a named owner and a clear completion criterion (deliverable).
• Budget line items are linked to specific phases of the execution timeline.
• At least one tech, staffing, or market risk is described with a corresponding mitigation plan.
• The specific channel and approach for acquiring the first 100 customers is written out.
• Customer segments are defined by behavior and context, not just demographics.
• At least one pre-launch customer validation activity (interview, pre-registration, or pilot) is documented.
• Channel cost estimates are backed by comparable cases or direct test results.

#Frequently Asked Questions

Q. Can I see my scores for both lenses directly?

OpenSeed's review report displays Execution Feasibility and Customer Reach as separate line items. Each item includes a reviewer comment explaining the reasoning behind the score.

Q. If my Execution Feasibility score is low, does a strong Customer Reach score still help the overall score?

The two lenses are evaluated independently, but if either falls below a threshold, it raises questions about overall business viability. The report flags which specific statements are missing from the weaker lens.

Q. What if I'm at such an early stage that I have no customer validation history at all?

Having no validation history isn't an automatic penalty. But the less history you have, the more specifically you need to describe how you'll reach your first customers. Even a planned interviewee list, an outreach approach, or a pilot operating plan can raise your Customer Reach score.