Back to the episode map

Evergreen

How to Build a Founder Motivation Record

Create a private, dated founder motivation record covering mixed motives, ordinary work, behavior, costs, affected people, support, limits, and stop conditions.

Aug 4, 20266 min readBy Dalton Anderson

How to Build a Founder Motivation Record

A founder motivation record is a private, dated account of why you want to begin, what keeps the ordinary work meaningful, who bears the cost, what support exists, and which conditions should cause you to continue, pause, or stop.

Motives can be mixed and can change. Money, autonomy, impact, mastery, curiosity, frustration, responsibility, and identity can coexist. The question is what behavior they sustain and what costs they justify.

Write for the decision, not the founder story

The public story usually becomes cleaner over time. The private record should become more accurate.

Start with the decision in front of you. Are you exploring a problem, continuing a side project, committing more time, considering a role change, or deciding whether to keep going after new evidence?

Then write the reason in plain language. Avoid phrases prepared for investors, customers, or social media.

"I want freedom" becomes more useful when it names the decisions you want to own and the constraints you expect customers, partners, employees, regulation, and capital to create. "I want impact" becomes more useful when it names the user behavior or condition that should change.

Map several motives

Do not force the record to discover one pure reason.

MotiveEvidence from recent behaviorDistortion to test
UserReturning to the user's actual workflow and consequencesAdmiring the mission while avoiding support
CraftBuilding, operating, or improving the core workEnjoying ideas while avoiding execution
AutonomyWanting responsibility for named decisionsEscaping one manager while ignoring new obligations
FinancialA realistic outcome, probability, and time horizonTreating a possible exit as dependable income
LearningSustained effort on specific skills or questionsUsing the company mainly as a credential
ImpactObservable benefit for a named userReplacing evidence with scale language
FrustrationMoving toward a problem worth solvingBuilding only to flee a temporary situation
IdentityWork that remains meaningful without recognitionWanting the title more than the work
ResponsibilityWillingness to own uncertainty, failure, and correctionGlorifying avoidable harm or endless endurance

Money is not automatically a bad motive. It is unreliable when an uncertain outcome is treated as a promise or when it is used to silence the costs borne by the founder and other people.

YC's Michael Seibel presents one attributed founder perspective in "Why should I start a startup?". Use it as a prompt, not as an eligibility test or outcome model.

Describe an ordinary week

Motivation for a launch is not the same as motivation for company work.

Describe a week containing user conversations, sales, rejection, support, debugging, documentation, budgeting, compliance, hiring, difficult decisions, and repetitive operations. Adapt the mix to the business.

Mark which work creates energy, which is tolerable, which requires a teammate, and which crosses a limit.

Then compare that description with recent behavior. Did you make time for users? Did you return after a failed test? Did you avoid the part of the work that carries the value? Did new evidence change your plan?

Behavior does not reveal a fixed identity, but it is stronger than a statement about who you hope to be.

flowchart TD
    A["Current decision"] --> B["Mixed motives"]
    B --> C["Ordinary-work description"]
    C --> D["Recent behavior"]
    D --> E["Costs and affected people"]
    E --> F["Support and limits"]
    F --> G["Continue, pause, or stop conditions"]
    G --> H["Next step and review date"]

Separate moving toward from moving away

A person may want to build because a problem is compelling and because the current job is painful. Record both.

Then test whether another action could address the situation with less risk. A different role, employer, manager, schedule, location, team, consulting path, or health intervention may change the pressure without requiring a company.

This is not an argument against starting. It prevents the company from becoming the only imagined exit from an unrelated problem.

YC's guide for students considering startups includes both reasons to start and reasons not to, along with working at a startup as an alternative. The broader principle applies beyond students: compare real paths, not virtue labels.

Record the cost and who shares it

Keep sensitive answers private.

Name the expected time, money, attention, uncertainty, health, sleep, relationship, career, and location cost. Identify who may absorb each cost.

Do not turn another person's support into assumed consent. Record what they know, what remains uncertain, what commitment they made, what would require another conversation, and how they can raise a concern.

Founder ambition does not cancel household, care, health, employment, immigration, or legal realities.

Define support and limits

Support might include a co-founder, household agreement, savings plan, health care, professional advice, community, childcare, part-time path, exercise, protected time, or a defined spending ceiling.

Limits should be observable. "Do not burn out" is hard to act on. "If sleep remains below the agreed threshold for two weeks, pause the launch schedule and review workload" creates a decision.

Resilience should mean recovering, adapting, asking for help, changing tactics, and responding to evidence. It should not mean persisting through every cost.

The official Startup School video index preserves YC's current public routes to founder and company-building talks. That advice comes from YC's venture context. It does not override a reader's health, family, finances, or professional obligations.

Write four sets of reasons

Write reasons to begin. These should explain why the problem and work deserve an initial test.

Write reasons to continue. These should rely on evidence from users, behavior, learning, team work, and manageable cost.

Write reasons to pause. These might include missing support, unresolved employment or legal questions, health strain, unclear user access, or a test that needs redesign.

Write reasons to stop. These should include disconfirming demand, unacceptable harm, exhausted resources, repeated boundary violations, a relationship decision, or a better alternative.

Stopping conditions protect judgment from the identity pressure to continue at any cost.

Review after real work

Choose a review date after enough user, building, sales, or operating work to create evidence.

Do not review only during excitement or exhaustion. Compare the current entry with earlier ones. Ask which motives strengthened, which weakened, which costs changed, and whether the next step still fits the evidence.

End with one proportionate action, one support action, one limit, one stop condition, and the next review date.

This page was developed with AI assistance from the E056 transcript and linked primary sources, then structured for human founder, health-boundary, personal-boundary, and editorial review. It is not a psychological assessment, crisis resource, or individualized financial, legal, employment, immigration, or health recommendation.

Sources

Follow the evidence.

  1. ycombinator.com: startups for students guideycombinator.com
  2. census.gov: cbbcensus.gov
  3. SBA: Market Research and Competitive Analysissba.gov
  4. ycombinator.com: harj taggarycombinator.com
  5. sba.gov: launch your businesssba.gov
  6. ycombinator.com: why should i start a startupycombinator.com
  7. sus-raw-sso-authenticated.ycombinator.com: faqsus-raw-sso-authenticated.ycombinator.com
  8. sba.gov: write your business plansba.gov
  9. ycombinator.com: startup school videosycombinator.com
  10. youtu.be: Um09r7L0IJ8youtu.be
How to Build a Founder Motivation Record