Building an LLM Council: Stress-Test Startup Ideas
Learn how to build an LLM Council based on Andrej Karpathy's concept to stop AI from blindly validating your startup and software ideas.

Stock photo for illustration only, not from the actual event
- Overcome AI sycophancy by deploying a multi-model LLM Council.
- Assign skeptical roles like investor, security engineer, and frustrated customer.
- Follow a 3-stage process: Independent opinions, anonymized peer review, and synthesis.
- Bypass limitations caused by AI agreeableness training and confirmation bias.
A few weeks ago, a waste management startup team in Ghana was completely stuck after spending weeks circling the same concepts, including gamified recycling rewards and route optimization, without reaching any consensus. While the team was full of enthusiasm, they lacked a reliable way to critically test their own thinking before committing another month to building the wrong product.
This represents a common failure point for founders and engineers: opening ChatGPT, asking whether an idea is good, and immediately receiving three paragraphs of validation. This phenomenon happens because single large language models (LLMs) are trained to provide the exact responses users want to hear, finding something positive to say about almost everything and rarely pointing out fundamental flaws.
This behavior stems from agreeableness training, which makes a single LLM a poor instrument for the rigorous, adversarial critique that founders genuinely need to stress-test their startup concepts and software proposals.
The deadlock broke when the team ran their disagreements through a structured multi-model critique workflow known as an "LLM Council," modeled on an approach popularized by Andrej Karpathy, former Director of AI at Tesla and OpenAI founding member. Each model adopted a skeptical persona—such as an investor, a security engineer, a frustrated customer, or a competitor—to expose crucial trade-offs that are easily missed by a single agent.

Stock photo for illustration only, not from the actual event
Following the framework published by Andrej Karpathy in late 2025, the system operates across three distinct stages:
- Stage 1: Independent Opinions. The identical query is sent to every council member in parallel without sharing other responses, preventing models from converging on the loudest answer.
- Stage 2: Anonymized Peer Review. All responses have their identities stripped and are labeled as Response A, B, and C so that each model can critique and rank them without family bias.
- Stage 3: Chairman Synthesis. A designated chairman model reviews all feedback to produce a single final verdict while highlighting unresolved disagreements.
Asking a single model whether an idea is viable introduces severe reliability issues, including confirmation bias where the AI simply mirrors the user's prompt framing, and mode collapse where post-training RLHF tuning narrows outputs into overly cautious, noncommittal responses. Implementing a multi-agent council effectively resolves these critical blind spots.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment