What is fundamental starting position?

“Fundamental starting position” sounds like a philosophy term, but in startup work it has a very practical meaning: it’s the baseline state you’re starting from—your constraints, assumptions, and initial choices—so you can make consistent decisions instead of improvising every day.

For technical, medical, and scientific founders, this matters because you can be “right” scientifically and still fail commercially if you never define the business baseline: who you’re serving, what problem you’re solving, what you’re not doing (yet), and what evidence would change your mind.

What “fundamental starting position” means (in plain startup language)

Your fundamental starting position is the minimum coherent snapshot of your startup at time zero. It answers: “Given what we know today, what are we building, for whom, and why is it plausible?”

It’s not a full business plan. It’s closer to a working baseline you can test. In practice, it includes:

• Context: your current resources and constraints (time, money, team, access to users, regulatory burden, data availability).
• Assumptions: beliefs you’re acting on (e.g., “clinics will pay for X,” “integration with Y is feasible,” “users will switch from spreadsheets”).
• Initial choices: the first market, first use case, and first distribution channel (how you’ll reach customers).
• Success criteria: what “good” looks like in the next 30–90 days (evidence, not vibes).

Think of it like setting initial conditions in an experiment. Without initial conditions, you can’t interpret results.

Why founders need it: it prevents “random walk” building

Early-stage startups fail less from a lack of intelligence and more from incoherent iteration: building features, pitching different audiences, and changing pricing weekly without a stable baseline.

A clear starting position helps you:

• Choose what to ignore: You can’t pursue every promising application. Your baseline defines “not now.”
• Run cleaner tests: If you change the target customer and the product at the same time, you can’t learn what caused the outcome.
• Align a team: Even a 2-person team needs shared assumptions to avoid duplicated work and conflicting priorities.
• Communicate to outsiders: Advisors, early hires, and investors can only help if they know your current thesis.

For STEM founders, this is the business equivalent of writing down your hypothesis and protocol before you run the study.

The 7-part checklist for a strong fundamental starting position

If you write nothing else, write these seven items in one page. Use concrete nouns and numbers.

1. Customer: Who exactly is the user and who is the buyer? (In B2B, they’re often different.) Example: “Operations manager at a 20–200 person manufacturing plant” or “Clinic administrator at a multi-site outpatient practice.”
2. Job-to-be-done: The specific task they’re trying to accomplish. (This is the Jobs To Be Done framing: customers “hire” products to make progress.) Example: “Reduce no-show rates without adding staff time.”
3. Pain + current workaround: What do they do today? Spreadsheets, manual calls, a competitor, or “nothing.” If the workaround is “nothing,” ask why.
4. Value metric: The measurable outcome you improve (time saved per week, error rate reduction, revenue recovered, cycle time). Pick one primary metric.
5. Offer: What you’re selling in one sentence. Example: “A lightweight dashboard that flags X and triggers Y.” Avoid “AI platform” unless you can finish the sentence without buzzwords.
6. Distribution (go-to-market): How you’ll reach them first. “Outbound email to 50 clinics,” “partner with billing consultants,” “sell via app marketplace,” etc. Go-to-market means the path from “nobody knows you” to “customers pay you.”
7. 90-day proof: What evidence would validate the direction? Examples: “10 problem interviews,” “3 paid pilots,” “$2k MRR,” “integration completed with system Z,” “users complete workflow in under 5 minutes.”

If you can’t answer one of these, that’s not failure—it’s a signal of what to investigate first.

Examples: fundamental starting position in different startup types

Example A: B2B SaaS (operations tool)

• Customer: Warehouse supervisors at regional distributors (50–300 staff).
• Job: Reduce picking errors and rework.
• Workaround: Paper checklists + end-of-shift reconciliation.
• Value metric: Picking error rate per 1,000 items.
• Offer: Mobile checklist + exception alerts.
• Distribution: Outbound to 30 warehouses via LinkedIn + referrals from WMS consultants.
• 90-day proof: 2 pilots with measured error reduction and a signed letter of intent (LOI). LOI is a non-binding document that signals intent to buy if conditions are met.

Example B: Med/health-adjacent (without assuming regulatory specifics)

• Customer: Practice manager (buyer) + front-desk staff (users).
• Job: Reduce time spent on insurance eligibility checks.
• Workaround: Manual portal logins and phone calls.
• Value metric: Minutes per eligibility check.
• Offer: Workflow tool that centralizes checks and logs outcomes.
• Distribution: Start with 10 local practices; sell as a monthly subscription.
• 90-day proof: 3 paid trials and documented time savings; confirm willingness-to-pay range.

Note: regulatory and compliance requirements vary by product and geography. Your starting position should explicitly state what you’re assuming and what you’re deferring.

Common mistakes (especially for technical founders)

• Starting with the technology: “We have a model” is not a starting position. The starting position begins with a customer and a job-to-be-done.
• Too broad a customer: “Hospitals” or “researchers” is not a customer definition. Narrow by role, setting, and size.
• No distribution hypothesis: If you can’t name how you’ll reach the first 20 customers, you don’t have a starting position—you have a wish.
• Confusing interest with commitment: “This is cool” is not validation. Look for time, data access, pilots, or payment.
• Undefined time horizon: A starting position should be testable in weeks, not years.

What to do next

1. Write your one-page baseline using the 7-part checklist above (customer, job, workaround, value metric, offer, distribution, 90-day proof).
2. Run 10 problem interviews with the exact customer role you named; document the current workaround and what they’ve tried before.
3. Define one measurable success metric for a pilot (e.g., minutes saved per task, error reduction) and how you’ll measure it.
4. Pressure-test your distribution plan by attempting to book 5 calls this week using your chosen channel.
5. Use a structured startup template to keep assumptions explicit: fill out /basics_form and compare your positioning against competitors in /Competitor_study.