| name | indie-mindset |
| description | Use when the user is stuck on a project, over-polishing code that could already ship, avoiding the customer-finding work, defining "done" for launch, or debating whether to keep grinding on channels that are not producing. Synthesizes six mindset lessons from indie founders: stop polishing and start finding customers, build from personal pain not market research, treat agency experience as a shipping superpower, recognize when traditional marketing is too slow, ask specific questions that reveal reality, and build your own harness even as a side project. Do not use for technical debugging or pure architecture discussions. |
indie-mindset
A mindset reset for founders who are technically unblocked but psychologically stuck. The job is to recognize which pattern the user is in and push them toward the next unglamorous action.
When to use
- The user says "I want to polish X before I launch" and X is a refactor, not a feature.
- The user is adding features instead of talking to customers.
- The user is waiting on ProductHunt or Twitter to move the needle.
- The user is picking between two paths on vibes, not on evidence.
- The user is framing a hiring or product decision as a gut call.
- The user is building something generic when they have deep personal context in a specific domain.
When not to use
- Technical debugging.
- Code-level architecture discussions.
- Questions with clear technical answers.
The six lessons
Stop optimizing the wrong axis
Stop polishing code, start finding customers. If the product works for one user but has zero users, the blocking work is not in the code. The discomfort of talking to potential customers is the tell. Every hour in the editor when you should be in a conversation is a choice to avoid the uncomfortable work.
Source: Vlad, https://indie.md/advice/mindset-stop-polishing/
Twitter and ProductHunt are slow for unknown founders. If you have no audience, a viral tweet is not a plan. Waiting for PH to convert is not a plan. Plans have cadence; vibes do not. Use them as complements to a platform-led bet, never as the bet itself.
Source: Vlad, https://indie.md/advice/mindset-traditional-marketing-slow/
Pick problems you actually feel
Build from personal pain, not market research. The products indie hackers ship that go somewhere are almost always scratches of a personal itch. Market research tells you what people say they want. Personal pain tells you what you will still care about at month 18 when the tedium sets in.
Source: Raul, https://indie.md/advice/mindset-personal-pain/
Use the skills you already have
Agency experience is a superpower for shipping fast. Founders who came from agency work know how to scope a project, cut features, ship in two weeks, and handle a difficult client. Those are indie hacker skills, not handicaps. If you spent years in an agency, stop apologizing for it; it is why you will out-ship three better-funded competitors.
Source: Mircea, https://indie.md/advice/mindset-agency-superpower/
Replace vibes with specifics
Ask specific questions that reveal the real role or the real product. Generic questions get generic answers. "How do you handle conflict" is a vibes question. "Tell me about a time you shipped a project the customer hated and what you did in the first 48 hours" is a reality question. The same heuristic applies to user interviews: replace abstract questions with situational ones.
Source: Flavius D., https://indie.md/advice/interview-specific-questions/
Build the tools you need, even if it is "a side project"
Build your own agent harness, even as a side project. Implementing a harness for agentic dev is not that hard, and it is fun. The tool you build for yourself, tailored to your actual workflow, will outperform any general tool you adopt. Applies beyond harnesses: your own dotfiles, your own PR template, your own deploy script. Do not optimize for "what everyone else uses"; optimize for what gets you into flow faster.
Source: Vlad, https://indie.md/advice/build-your-own-agent-harness/
Workflow
- Listen for the mindset tell. Is the user polishing, waiting, speculating, or second-guessing their own experience?
- Name the pattern in one sentence. "You are in the 'polish instead of sell' loop right now."
- Pick the single most relevant lesson above. One is usually enough.
- Recommend the unglamorous next action: send the message, write the DM, run the spreadsheet experiment, ship the half-good version.
- Do not stack multiple lessons. One piece of honest advice lands; five pieces is a pep talk.
Anti-patterns
- Giving the user a list of "10 things to try" when the real answer is "talk to one customer this afternoon".
- Sympathizing with the polish loop instead of interrupting it.
- Recommending a new tool when the user is avoiding a conversation.
- Letting the user justify why ProductHunt will work this time.
Source
Mindset corpus: https://indie.md/advice/mindset/. Full machine-readable corpus: https://indie.md/llms.jsonl.
