Business Decisions
📊 Strategic analysis for business owners, founders, and executives.
Business decisions benefit from structured reasoning because they involve multiple stakeholders, uncertain outcomes, and significant resources.
Common Business Questions
“Should I start this business?”
rk-core think "I want to start a SaaS business in project management space. Market seems crowded but I have a unique angle. Worth pursuing?" --deep
“Should I raise funding or bootstrap?”
rk-core think "My startup is doing $20K MRR after 1 year bootstrapped. VCs are interested. Should I raise?" --paranoid
“Should I hire this person?”
rk-core think "Candidate is brilliant but has job-hopped 4 times in 3 years. Red flag or okay?" --balanced
“Should I pivot or persist?”
rk-core think "6 months in, $50K spent, no traction. 3 users give great feedback but can't get more. Pivot or persist?" --deep
Example Analysis
Question: “Should I launch my product now (80% done) or wait until 100%?”
rk-core think "Product is 80% complete. Launch now and iterate, or wait 2 more months for polish?" --balanced
╔════════════════════════════════════════════════════════════╗
║ BUSINESS ANALYSIS: Launch Timing ║
╚════════════════════════════════════════════════════════════╝
┌────────────────────────────────────────────────────────────┐
│ 💡 GIGATHINK: 10 Perspectives │
├────────────────────────────────────────────────────────────┤
│ 1. MVP PHILOSOPHY: Launch early, iterate with feedback │
│ 2. FIRST IMPRESSION: You only launch once │
│ 3. COMPETITIVE: What are competitors doing? │
│ 4. CASH FLOW: 2 months = 2 months more burn │
│ 5. MARKET TIMING: Is there a window closing? │
│ 6. TEAM MORALE: Is team ready to ship? │
│ 7. CUSTOMER: Are beta users asking to pay? │
│ 8. PERFECTIONISM: Is "100%" a moving target? │
│ 9. LEARNING: What will you learn from launch? │
│ 10. REVERSIBILITY: Can you iterate after launch? │
└────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────┐
│ ⚡ LASERLOGIC: Reasoning Analysis │
├────────────────────────────────────────────────────────────┤
│ FLAW: "80% complete" │
│ → 80% by whose standard? │
│ → The last 20% often takes 80% of the time │
│ → "2 more months" is almost certainly wrong │
│ │
│ FLAW: "Polish before launch" │
│ → You don't know what to polish until users tell you │
│ → You're polishing based on guesses, not data │
│ → Effort likely wasted on wrong features │
│ │
│ FLAW: "You only launch once" │
│ → False for software; you can iterate indefinitely │
│ → First users are usually early adopters who forgive │
└────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────┐
│ 🪨 BEDROCK: First Principles │
├────────────────────────────────────────────────────────────┤
│ CORE QUESTION: │
│ Can someone pay you money for this today? │
│ │
│ If YES: Launch. Everything else is premature optimization│
│ If NO: What's the minimum needed to get there? │
│ │
│ THE 80/20: │
│ • 80% of value comes from 20% of features │
│ • The 20% you're missing may not be in that 20% │
│ • Real usage data > your assumptions │
└────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────┐
│ 🔥 BRUTALHONESTY: Reality Check │
├────────────────────────────────────────────────────────────┤
│ UNCOMFORTABLE TRUTH: │
│ "Waiting for polish" is often fear of rejection. │
│ If you're afraid to launch, that fear won't go away │
│ when you reach "100%" - the bar will just move. │
│ │
│ UNCOMFORTABLE TRUTH: │
│ Most products fail because of bad product-market fit, │
│ not because of missing features. Launching tells you │
│ if you have PMF. Not launching keeps you guessing. │
│ │
│ HONEST QUESTION: │
│ What specifically are you afraid will happen if you │
│ launch today? │
└────────────────────────────────────────────────────────────┘
SYNTHESIS:
Launch now unless there's a specific, critical blocker.
"Polish" is a trap. Real user feedback is more valuable
than hypothetical improvements. The market will tell you
what's actually missing.
Business-Specific Profile
[profiles.business]
tools = ["gigathink", "laserlogic", "bedrock", "proofguard", "brutalhonesty"]
gigathink_perspectives = 12
laserlogic_depth = "deep"
proofguard_sources = 3
brutalhonesty_severity = "high"
timeout = 240
Business Framework Integration
ReasonKit complements standard business frameworks:
| Framework | ReasonKit Enhancement |
|---|---|
| SWOT Analysis | GigaThink expands perspectives |
| Porter’s Five Forces | LaserLogic validates logic |
| Lean Canvas | BrutalHonesty stress-tests assumptions |
| OKRs | BedRock ensures first-principles alignment |
Common Business Biases
| Bias | Business Context | ReasonKit Response |
|---|---|---|
| Sunk cost | “We’ve invested too much to stop” | Future-focused analysis |
| Optimism | “Our projections are conservative” | Base rate comparison |
| Groupthink | “Everyone on the team agrees” | Contrarian perspectives |
| Survivorship | “Successful startups did X” | Full dataset analysis |
Tips for Business Analysis
-
Include financials — Numbers matter; include them
-
Specify timeline — “Should I hire?” vs “Should I hire this quarter?”
-
Name competitors — Generic questions get generic answers
-
Use paranoid for big bets — Funding rounds, pivots, major hires
-
Revisit decisions — Run analysis again as conditions change