Founder Mindset

Activate when: user says 'founder mindset' or 'founder mode'; asks 'default alive or default dead'; says 'do things that don't scale'; says 'am I avoiding the hard thing'; is deciding whether to hire/fire/pivot/raise/cut burn at an early-stage company; feels comfort-seeking creeping in; cannot tell if they are on the path to success or slow death. Do NOT activate when: user is running a mature well-understood business (manager frameworks apply); user is an employee within a startup with fixed scope; the decision is purely tactical (which CRM, which button color).

Overview

A specific cognitive mode for running an early-stage company — different from manager mindset (optimizing known systems) and employee mindset (executing within fixed scope). Founders search for the system itself under conditions of extreme uncertainty, asymmetric risk, and personal execution bottlenecks. The two load-bearing disciplines: Default Alive or Default Dead (Graham 2015) and doing things that don't scale (Graham 2013).

Compose: first-principles on inherited assumptions about how companies operate · regret-minimization for the decision to start or quit · inversion to surface failure paths founders underweight · lean-startup + mvp operationally · metacognition to catch monitoring lapses under founder stress.

When to Use

Apply when: running an early-stage company (hire/fire/pivot/raise/cut burn decisions) · comfort-seeking is creeping in · cannot tell if on path to success or slow death · team is scaling prematurely · a specific hard problem has been on the list > 2 weeks · someone says "founder mindset," "founder mode," "default alive or default dead," "do things that don't scale," "am I avoiding the hard thing?"

When NOT to use: mature well-understood business · employee within a startup · purely tactical decision · "founder mindset" as performative identity.

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a specific founder-mode decision → run the Founder-Mode Audit directly.
• Coach mode: vague situation or unfamiliarity → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. What-it-is. Founder mindset = running an early-stage company under extreme uncertainty. Two hardest moves: (a) doing things that don't scale, (b) asking Default Alive or Default Dead early enough to act.
2. Check fit. Mature business → manager frameworks. Employee scope → most doesn't transfer. Tactical decision → too small.
3. Elicit the specific situation. "I'm a founder" is too vague — need a specific decision or pattern.

[WAIT — do not advance until user responds]

4. Run The Process one step at a time with their input.

[WAIT — do not advance until user responds]

5. Close by naming the one founder-mode move they have been avoiding.

[WAIT — do not advance until user responds]

The Process

Run the Founder-Mode Audit: Default Alive math → avoiding-the-hard-thing → don't-scale-yet → personal-stress check.

1. Compute Default Alive vs Default Dead. Take current revenue growth, expense growth, and bank cash. Will the company reach profitability before cash runs out without raising? If yes → Default Alive. If no → Default Dead. Re-run quarterly minimum. Founders systematically misclassify themselves as Default Alive when they are Default Dead.
2. Name the hard thing you are avoiding. What specific painful action has been on your list for > 2 weeks? Difficult customer call, needed firing, co-founder misalignment conversation. Write it down. Schedule the action within 7 days.
3. Check what you are scaling prematurely. Hiring, automation, infrastructure, or paid acquisition that requires something underneath to be proven first but isn't yet. Common: VP of Sales before founder has closed 20+ deals; paid acquisition before organic conversion is solid.
4. Check what you are not doing that doesn't scale. Who would you talk to personally? Which customer would you visit physically? The unscalable thing the founder is not doing is often more diagnostic than the strategy on the slide deck.
5. Personal stress / pattern check. Avoidance · delegation to nobody-in-particular · excessive meeting attendance · comfort-seeking on optimization tasks. Name which pattern is present. Naming is the first move.
6. Founder-mode action selected. From steps 2–5, pick ONE action for the next 7 days you have been avoiding. Not three; one.
7. Re-run weekly until shipped. Schedule for every Monday — without the ritual, the avoidance pattern reasserts within ~10 days.

Output: the Founder-Mode Audit

markdown

# Founder-Mode Audit: <date>
Default Alive ☐ / Default Dead ☐ — cash $<X>, burn $<Y>/mo, runway <N>mo, rev growth <Z>%MoM
Hard thing avoided: <action> | on list <N weeks> | scheduled <date within 7 days>
Premature scaling: <area> | what must be proven first: <…> | action: <revert/pause>
Not doing (unscalable): <action> | who to talk to / visit: <…>
Stress pattern: <avoidance / over-meeting / over-optimizing> — <one sentence>
ONE action next 7 days: <single specific action>
Re-audit: every Monday

→ Method in Action: Paul Graham's Essays and the YC Portfolio (2005–2024)

Founder Packs

Founder mindset operates the same across industries; the specific hard things differ by company type.

• B2B SaaS: unscalable = founder-led sales for first ~$1M ARR; premature = VP of Sales before 20+ personal closes.
• Consumer app: unscalable = founder physically watching users; premature = paid acquisition before organic retention is solid.
• Marketplace: unscalable = manually matching supply/demand in first city; premature = multiple geographic launches simultaneously.
• Deep-tech / hardware: unscalable = founder personally handling first customer integrations; premature = mass manufacturing before first 100 units perform reliably.

Applying It Well

• Run Default Alive monthly. Founders misclassify ~3 months earlier when running monthly vs quarterly.
• The avoided thing IS the signal. Deferring > 2 weeks almost certainly means that action is the founder-mode move.
• Founder mode is uncomfortable on purpose. If the audit feels good, it isn't working.
• Unscalable is a bridge, not a destination. Automate once the pattern is proven.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake move	Reality
[D] Default Alive self-deception	Expense growth exceeds revenue growth but founders feel fine. Do the math; trust the spreadsheet over the gut.
[D] "We'll address that after the next milestone"	The next milestone is the next reason to defer. Schedule it now.
[D] "We need a VP of Sales now"	The VP cannot prove a motion that doesn't exist. Founder-led sales until 20+ deals close repeatably.
[D] Skipping customer conversations because "we have AEs"	AEs scale bandwidth; they don't replace the founder's information flow. 5 founder calls/week is the minimum.
[D] "Founder mode" as performative identity	Saying "I'm a founder type" while running an OKR review is theater. Founder mode is operational, not identity.
[D] Excessive internal process optimization	Visible outputs without customer risk — a near-perfect signal of manager mode creeping in.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags

• Default Alive / Default Dead has not been computed in the last 60 days
• A specific painful action has been on the list for > 2 weeks
• Founder calendar shows < 10% customer-facing time
• A VP-level hire was made before the founder personally proved that function's work
• Internal-process improvement projects are getting more attention than customer-facing work
• The same hard problem keeps appearing in weekly priorities but never moves
• "Founder mode" is being used as identity rather than checked as operational discipline

Verification

• Default Alive vs Default Dead computed this month
• At least one avoided hard thing named and scheduled within 7 days
• Specific premature-scaling areas identified and reverted to manual where needed
• Unscalable actions the founder should be doing personally are named
• Current stress pattern named (avoidance / over-meeting / over-optimizing / etc.)
• ONE concrete founder-mode action committed for the next 7 days
• Re-audit scheduled (weekly, every Monday)

---

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.