Deciding with facts not opinions means separating verified data from advocacy before any argument begins. The Council enforces this by having eleven neutral analysts build a sourced Fact Ledger first, then handing it to eight judges who argue and vote from that shared evidence. No analyst casts a vote, no judge conducts research. In a real estate SaaS test, this structure surfaced fatal unit economics and an API revocation trap that would have depleted capital within four months, producing an unconditional kill verdict before a single line of code was written. The full deliberation runs in about 30 minutes inside your local Claude terminal, with your data never leaving your machine.
Most business decisions are not made with facts. They are made with enthusiasm and blind hope. You bring an idea to your team or advisors and everyone nods because nobody wants to be the negative voice in the room. You end up launching something based on consensus rather than reality. Then the market introduces you to the facts and it costs you thousands of dollars. We built The Council to solve this exact problem by forcing rigorous multi-round deliberation before you spend a dime.
The Flaw in How Business Decisions Get Made
Traditional business meetings suffer from an invisible bias toward agreement. When founders present a new concept to advisors or internal teams, social pressure suppresses dissent. People offer polite encouragement instead of rigorous pushback. This collective optimism masks fatal flaws in unit economics, market timing, or technical feasibility until it is too late.
When everyone in the room shares your enthusiasm, your blind spots become invisible. The person who spotted the pricing leak kept quiet because they did not want to rain on your parade. Consensus is comfortable and it is also expensive. You need a mechanism that separates emotional attachment from hard data. You need a room full of specialists whose only job is to tear the idea apart using precedent, math, and first principles.
What Is The Council and How It Runs Locally
The Council is a licensed Model Context Protocol skill that operates inside your local workspace via Claude Desktop. You install it once, type a simple command in your terminal, and watch a structured executive board meeting execute right inside your chat interface. It uses your subscription and never sends your questions to external servers.
A run starts with eleven neutral analysts who research the facts, pull real data, and cite sources without casting any votes. Once the briefing is complete, eight named judges step up to argue opposing viewpoints, cross-examine each other, and vote. The session concludes with a definitive verdict of SHIP, PIVOT, or KILL along with specific conditions and kill triggers that tell you exactly when to walk away.
The Innovation: Separating Facts from Opinions
The single biggest failure mode in artificial intelligence reasoning and human committees is confirmation bias. When the same voice gathers information and argues for a conclusion, facts quietly bend to support the preferred outcome. The Council eliminates this distortion by erecting a strict firewall between research and advocacy.
The eleven analysts include specialists in finance, law, competitive intelligence, market research, and user experience. Their only job is to establish what is true, verify sources, and write a shared briefing that every judge reads. Only then do the eight judges step in to fight over what to do. The judges never conduct research and the analysts never cast a vote. This separation prevents the quiet bending of facts toward a preferred conclusion.
Proof in Practice: The Real Estate SaaS Verdict
To prove how this works in the real world, we ran a test case on a proposed real estate follow-up software startup. The concept seemed bulletproof on paper by promising automated texting for agents. What followed was a brutal and multi-round dissection that exposed fatal market traps and hidden unit economic flaws.
The analysts surfaced raw market data and pricing benchmarks for the real estate follow-up software concept. Then the judges went to work. The Skeptic and the CFO dismantled the unit economics, noting that sub-six-dollar acquisition costs were mathematically impossible in a saturated market. The Red Team flagged the impending Zillow API revocation trap that would cut off core data access overnight.
What Was the Verdict: Pivot or Die?
The verdict delivered by the panel was an unconditional kill order based on fatal unit economic flaws. The judges proved that customer acquisition costs exceeded lifetime value by three hundred percent in saturated markets. Launching this product would have depleted capital reserves within four months without achieving sustainable traction.
The founder initially resisted the verdict because the prototype looked sleek and modern. However, examining the cold math revealed that customer acquisition economics were completely broken. Accepting the decision early prevented a six-figure financial disaster.
Stay Ahead
Mind Your Business Newsletter
Business news that doesn't put you to sleep. Weekly insights, strategies, and what's actually moving the needle — delivered straight to your inbox.
What Were the Kill Conditions That Saved the Founder?
The primary kill condition established by the board was any customer acquisition cost exceeding one hundred and twenty dollars combined with sub-ten-percent monthly retention. These specific thresholds forced the founder to abandon the project before writing code, saving thousands of dollars in development costs and months of wasted operational effort.
Having clear boundaries transformed subjective anxiety into objective clarity. When the data confirmed the thresholds were breached, closing down the project felt like a victory rather than a defeat.
Who Is Sitting in Your Virtual Boardroom
You do not need to assemble a board of advisors or pay thousands of dollars in consulting fees to get elite executive scrutiny. The Council includes nineteen distinct personas ranging from ruthless financial officers to paranoid competitor analysts. Each member brings a specific lens and a distinct point of view to your business model.
Meet a few key members who participate in every major session:
- The Skeptic: Focuses on hidden flaws, market saturation, and structural risks.
- First Principles: Strips away industry dogma to examine foundational physics and economics.
- The CFO: Analyzes cash burn, customer acquisition cost, and unit profitability.
- Red Team: Actively tries to break your product strategy and expose security or operational vulnerabilities.
- The Customer: Represents end-user pain points, buying friction, and realistic willingness to pay.
Integrating artificial intelligence systems into your decision workflow allows you to consult these distinct perspectives whenever you evaluate a new product launch.
The Fact Ledger: Evidence Before Argument
The most distinctive element of a Council deliberation is the Fact Ledger produced by the neutral analysts before any judge speaks. This document contains only verified data sources, industry benchmarks, competitor pricing, and known precedent. It contains no opinions, no recommendations, and no conclusions. The judges receive the same ledger and must argue from it.
In the real estate SaaS test, the analyst round produced five pages of raw data. The Financials Analyst pulled actual CAC benchmarks from public SaaS filings showing that no company in the space had achieved sub-six-dollar acquisition costs in the previous four years. The Competitive Landscape Analyst documented thirteen competing products with similar feature sets and their exact pricing tiers. The Legal and Compliance Analyst flagged the Zillow terms of service language that made the API revocation trap predictable from publicly available documents. Every claim in the ledger included a direct source citation.
This discipline forces the entire deliberation to be grounded in what is actually true rather than what the founder hopes is true. When a verdict arrives, it can be traced back to a specific number on a specific page of the ledger. You do not have to trust the conclusion. You can verify the facts that produced it.
How to Run Your First Local Deliberation
A full Council deliberation runs for about 30 minutes from command to verdict. That same 30 minutes spent in a traditional meeting would produce polite nods while everyone avoids telling you your idea has fatal flaws. The Council uses that half hour to surface structural blind spots that human advisors miss entirely because they are too polite, too busy, or too biased to speak the truth. Thirty minutes of machine-led rigor beats thirty hours of consensus-driven meetings.
Getting started takes less than five minutes of setup. Because The Council operates as a lightweight Model Context Protocol skill running directly inside your local Claude terminal, your data stays private and your queries never leave your machine. You simply invoke the command, drop your business idea, and watch the board deliberate in real time.
Type `/council` followed by your question to convene the full panel of all nineteen members. Use `/council facts` when you only need the neutral analysts to brief the question without delivering a verdict. Use `/council scoped` to summon just the judges and analysts your specific question requires, whether that is pricing, architecture, or go-to-market strategy. The deliberation runs entirely inside your own local Claude environment.
Explore The Council MCP skill to learn more about installation and licensing options.
Decide with facts, not opinions.
Get lifetime access to The Council skill for just $9.99 per month. Cancel anytime with no lock-in. Install it into your Claude workspace today and run your first executive deliberation before you spend another dollar on a flawed idea. Visit council.goodfellastech.com to get started.
Frequently Asked Questions About decide with facts not opinions
What is a fact-based decision?
A fact-based decision relies on verified data, benchmarks, and documented evidence rather than enthusiasm, gut feeling, or group consensus. You gather what is objectively true first, then argue about what to do with it. This separation prevents the natural human tendency to bend information toward the outcome you already want, which is the core discipline The Council enforces through its analyst-then-judge structure.
Should opinions be based on facts?
Yes, but most business opinions are not. The problem is that when the same person gathers information and argues for a conclusion, facts quietly bend to support the preferred outcome. A structured process forces the fact-gathering to happen first, in isolation, so that when opinions and arguments follow, they are anchored to a shared, verified briefing that everyone in the room has read.
How do you differentiate between facts and opinions?
A fact is a specific detail that can be verified against an objective source, a public filing, a pricing benchmark, or a documented term of service. An opinion is a judgment or interpretation of those facts. The Council keeps these two things in separate hands: eleven neutral analysts own the facts, and eight judges own the opinions. Neither group crosses into the other’s role.
What is a famous quote about facts and opinions?
Ray Dalio put it plainly: most people do not look thoughtfully at the facts and draw conclusions by objectively weighing the evidence. Instead, they make decisions based on what they want to be true. That observation is the exact failure mode The Council is designed to fix, by building a hard structural separation between the people who find the facts and the people who argue from them.
Why do business decisions fail when they rely on opinions instead of facts?
Social pressure in meetings suppresses dissent. When a founder presents an idea with enthusiasm, advisors tend to offer polite encouragement rather than rigorous pushback. The person who spotted a pricing leak stays quiet to avoid being the negative voice in the room. This collective optimism masks fatal flaws in unit economics, market timing, or technical feasibility until the market reveals them at significant cost.
What is the Fact Ledger and why does it matter?
The Fact Ledger is a document produced by The Council’s eleven neutral analysts before any judge speaks. It contains only verified data sources, industry benchmarks, competitor pricing, and known precedent, with no opinions or recommendations included. Every judge must argue from the same ledger. This means every verdict can be traced back to a specific number on a specific page, so you can verify the facts that produced the conclusion rather than just trusting it.
What verdicts can The Council return and what do they mean?
The Council returns one of three verdicts: SHIP, PIVOT, or KILL. Each verdict comes with specific conditions and kill triggers that tell you exactly when to walk away. In the real estate SaaS test case, the panel returned an unconditional kill order after proving that customer acquisition costs exceeded lifetime value by three hundred percent in a saturated market, with capital reserves projected to deplete within four months.
How does The Council prevent confirmation bias in AI reasoning?
The Council erects a strict firewall between research and advocacy. The eleven analysts gather data and write the shared briefing without casting any votes. The eight judges argue, cross-examine each other, and vote without conducting any research. When the same voice gathers information and argues for a conclusion, facts bend toward the preferred outcome. Keeping those roles in separate hands eliminates that distortion entirely.
How long does a full Council deliberation take?
A full Council deliberation runs for about 30 minutes from the moment you invoke the command to the moment the verdict is delivered. Setup takes less than five minutes because The Council runs as a lightweight Model Context Protocol skill inside your local Claude terminal. Your data stays private and your queries never leave your machine, so there is no external server sending your business idea anywhere.
What commands do you use to run The Council?
Type ‘/council’ followed by your question to convene the full panel of all nineteen members. Use ‘/council facts’ when you only need the neutral analysts to brief the question without a verdict. Use ‘/council scoped’ to summon only the analysts and judges your specific question requires, whether that covers pricing, architecture, or go-to-market strategy. All three commands run entirely inside your own local Claude environment.
