View contents
Article
OpenSeed Product Guide

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

2026.08.15·8 min·OPENSEED
MENTORING KNOWLEDGE FORMarket AnalystProduct MentorChief Analyst

'Good idea — so why did it get rejected?' usually comes down to two missing answers: whether the team can actually build it, and whether customers can actually be reached once it's built. OpenSeed looks at these through two separate evaluation lenses. Even for the same plan, the answers to these two questions can diverge significantly — and which one is missing determines the direction of improvement.

Intro.

#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 evaluation lenses, applied together by the Market Analyst, the Team Evaluator, and the Chief as they read your document. 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?' If one of the two lenses is much weaker than the other, that is a signal it is raising the risk of the entire business.

02

#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.

Review DimensionStrength SignalWeakness Signal
Team-Domain FitFounder and team experience directly tied to the product domainNo relevant experience — plan relies entirely on outsourcing
Milestone SpecificityQuarterly deliverables with named ownersVague timelines like 'planned for H2 release'
Resource-Budget AlignmentPersonnel and contractor costs linked to specific timeline phasesBudget spreadsheet and execution plan are disconnected
Risk AwarenessTech or staffing risks described with mitigation plans'No significant risks' or section omitted entirely

A typical 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.

03

#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 aren't the criterion for this lens. No matter how large the total addressable market, it gets flagged as a weakness if there's no concrete path to reach it.

Review DimensionStrength SignalWeakness Signal
Initial Channel ClarityClear description of where and how the first 100 users will come from'We'll promote through social media'
Channel Cost RationaleEstimates grounded in comparable cases or test dataClaiming 1,000 monthly users with no supporting evidence
Customer Segment SpecificityPersona defined by behavior and contextDemographic-only definition like 'women ages 20–30'
Early Customer ValidationInterviews, pre-registrations, or pilot sales already completed'Can't verify until the product is finished'

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

04

#3 Patterns Flagged as Weaknesses — and How to Fix Them

Three patterns are consistently flagged as weaknesses 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 flag it. 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.

05

#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.
Summary.

#Frequently Asked Questions

Q. Do the two lenses appear as separate items in the report?

No separate items or numbers are shown. The two lenses are the perspectives the Market Analyst, the Team Evaluator, and the Chief apply as they read your document. Any weaknesses they find appear in the report as each mentor's comments, together with evidence excerpts.

Q. If my Execution Feasibility is weak, is it still fine if my Customer Reach is strong?

The two lenses are examined separately, but if either is largely empty, it raises questions about overall business viability. The report flags which specific statements are missing from the weaker lens in each mentor's comments.

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 automatically flagged as a weakness. 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 reduce what gets flagged on the Customer Reach lens.

CTA
Check your current business plan to see which is weaker — Execution Feasibility or Customer Reach. OpenSeed's AI review delivers per-capability diagnoses, evidence excerpts, and improvement prescriptions from up to 17 evaluation roles. Single review: ₩9,900.
Advertisement

Review Your Business Plan Now

Start your AI business plan review now — ₩9,900 per review.

Pre-submission business-plan review with clear service limitations

Start OpenSeed Review →

관련 AI 피드백 서비스.

AI 피드백
사업계획서 AI 추천 →
AI 피드백
사업계획서 피드백 →
AI 피드백
초기창업패키지 점검 →
RELATED · Related pagesOpenSeed Product Guide
Business Plan Evidence Workflow — How to Separate Claims from Supporting Files and Earn Reviewer Trust2026.11.14 · 5 minHow to Upload Your HWP·HWPX Business Plan Without Converting to PDF2026.11.13 · 4 minWhat the Judge Prep Sheet Shows Mentors2026.10.28 · 5 minMentorship Eligibility Pre-Check Workflow — Why You Should Check Industry and Business-Age Conditions First2026.10.27 · 5 minHow to Prove 'It Will Sell' Without a Product — Diagnosing WTP, Channel Fit, and Business Model Viability2026.10.18 · 6 min
← Back to Wiki