F
Financial Advisor
Observation
quantitative • measured
“Don't quit until you have 18 months of runway saved. Your burn rate matters more than your excitement.”
Confidence
85%
Coming Soon
Stop trusting AI blindly.
See how it thinks.
The mental models powering your Claude—now with visual reasoning traces, multi-agent debates, and async workflows. No more black boxes.
The Difference
What if AI actually challenged your assumptions?
Same question. Radically different depth. (Click cards to explore)
Generic AI
chatgpt.com
Should I quit my job to start a startup?
It depends on your situation. There are pros and cons to consider.
Pros of quitting:
- • You can focus full-time on your startup
- • More time to dedicate to building your product
- • Shows commitment to investors
Cons of quitting:
- • Loss of stable income
- • Risk to your financial security
- • Stress of uncertainty
You should think about your financial situation, your risk tolerance, and whether you have a good idea. It's a personal decision that only you can make.
I'd recommend talking to people who have done it before and weighing your options carefully.
Follow-up questions:
What's your current financial situation?How much runway do you have saved?What industry is your startup in?
“That tells me nothing I didn't already know...”
think-mcp council
claude.ai + think-mcp
Should I quit my job to start a startup?
S
Startup Founder
Challenge
narrative • energetic
“I quit too early and regretted it. Build nights and weekends first. Validate with paying customers before you leap.”
References:
financial-advisor-1
Confidence
90%
C
Career Coach
Question
questioning • empathetic
“What are you running FROM vs. running TOWARD? If it's escape, fix that first. Startups amplify your problems.”
Confidence
78%
R
Risk Analyst
Insight
analytical • precise
“Your opportunity cost isn't just salary—it's 401k matching, healthcare, career momentum, and optionality. The real number is 2-3x your salary.”
References:
financial-advisor-1career-coach-1
Confidence
88%
Council Synthesis
Consensus Reached
- ✓Validation before quitting is essential
- ✓Understand your motivations clearly
- ✓Calculate true opportunity cost, not just salary
Key Insights
- →Revenue validation > pure runway savings
- →Running from something ≠ running toward something
- →Opportunity cost is 2-3x visible salary
Still to Clarify
- ?What's the specific startup idea?
- ?What's your current runway?
- ?Have you tested demand with real customers?
Recommendation
Don't quit yet. Instead: (1) Build nights and weekends for 3 months, (2) Get 3 paying customers, (3) Save 12 months runway, (4) Then make the leap with evidence.
“Now I can actually make an informed decision.”
This is just one of 11 thinking tools.
Explore all tools→The Toolkit
11 Tools for Every Thinking Challenge
Grouped by what you're trying to accomplish, not technical jargon.
Think It Through
Step-by-step reasoning and visualization
Trace
Chain of Thought
Dynamic reasoning that can revise, branch, and evolve. Perfect for exploring complex problems step-by-step.
Best for: Breaking down complex problems
Learn more
Map
Visual Thinking
Create flowcharts, concept maps, and diagrams to visualize relationships and systems.
Best for: Visualizing relationships
Learn more
Get Perspectives
Multiple viewpoints and challenges
Council
Expert Collaboration
Simulate a panel of experts with diverse backgrounds, biases, and perspectives debating your problem.
Best for: Gathering diverse viewpoints
Learn more
Debate
Dialectical Reasoning
Thesis, antithesis, synthesis. Stress-test ideas through formal argumentation.
Best for: Challenging assumptions
Learn more
Make Decisions
Structured evaluation and confidence
Fix Problems
Systematic investigation and testing
Debug
Systematic Debugging
Binary search, divide and conquer, cause elimination—structured methodologies to find bugs.
Best for: Finding bugs systematically
Learn more
Hypothesis
Scientific Reasoning
Formulate hypotheses, design experiments, analyze results. Apply the scientific method.
Best for: Testing assumptions
Learn more
Choose Approaches
Frameworks, patterns, and paradigms
Model
Mental Models
Apply proven frameworks: First Principles, Pareto, Occam's Razor, and more.
Best for: Applying proven frameworks
Learn more
Pattern
Design Patterns
Software design patterns for architecture, API integration, state management.
Best for: Architecture decisions
Learn more
Paradigm
Programming Paradigms
Choose between functional, OOP, reactive, declarative—find the right approach.
Best for: Choosing coding approaches
Learn more
Chain tools together:
CouncilDebateDecide
Tool Combinations
Chain tools for complex workflows
Individual tools are powerful. Combined, they handle the messiest real-world problems. Select a workflow pattern to see how tools work together.
Architecture Decision
Design major system components with expert input and structured analysis
Outcome: Documented architecture decision with rationale
Pro tip: Click any tool in the chain to see its detailed demo and usage guide.
Get Started
One URL. Zero Setup.
Add Think to any MCP-compatible client in seconds. No installation, no dependencies, no configuration.
MCP Server URL
https://think-mcp.vercel.app/api/mcpPro tip: In Claude Desktop, go to Settings → Developer → Add MCP Server → paste the URL above. That's it—all 11 tools are now available.
Works with any MCP-compatible client
Claude Desktop
Cursor
VS Code
Windsurf
Questions? Check the GitHub repo or learn about MCP
The Story
Built by Someone Who Was Tired of Repeating Themselves
The Frustration
I kept typing the same prompts over and over. "Think step by step." "Consider multiple perspectives." "What are the tradeoffs?" Every conversation, the same scaffolding.
The Realization
These weren't just prompts—they were thinking tools. Mental models I'd internalized over years of problem-solving. Why was I teaching them to AI every single time?
The Solution
So I codified them. Chain of thought became Trace. Expert panels became Council. Decision frameworks became Decide. 11 tools, each encoding a different way of thinking.
The Result
Now instead of prompting, I just call the tool. The AI already knows the structure. I focus on the problem, not the scaffolding. Every conversation starts smarter.
“The best tools disappear into your workflow. You stop thinking about the tool and start thinking about the problem.”
— The philosophy behind Think