DEV Community

Johnata Moreira
Johnata Moreira

Posted on Originally published at johnatamoreira.com.br

The Solo AI Stack: How a Solo Founder Orchestrates 5 AI Models to Ship Real Software

#ai #software #architecture #productivity

The Solo AI Stack: How a Solo Founder Orchestrates 5 AI Models to Ship Real Software

Most developers try to use AI by asking a single chatbot for ready-to-run code in one giant prompt. They usually end up with subtle bugs, hallucinated APIs, or architecture drift.

While building Mishyo (a private family-memory and genealogy app developed openly in Belo Horizonte, Brazil), I stopped treating AI as a "magic code generator" and started treating it as a specialized engineering department.

Instead of one model doing everything poorly, I orchestrate 5 distinct AI models and agents, each with a strictly enforced contract of inputs and outputs.

Here is the exact breakdown of The Solo AI Stack running in production today.

1. Claude: The Product Architect & Strategist

When you jump straight into code with an LLM, you inherit technical debt immediately. In our stack, Claude writes zero production code on day one.

  • Role: Product requirements, domain modeling, and technical specifications.
  • How we use it: Before any feature is developed, Claude generates a rigorous specification doc detailing:
    • Acceptance gates and non-negotiables
    • Data schema changes and privacy guardrails (such as LGPD compliance)
    • UI state machines and fallback behavior
  • Rule: If a feature cannot be proven in a written spec first, it does not get coded.

2. NotebookLM: The Grounded Knowledge Repository

As a codebase and business logic grow, prompt contexts get polluted with obsolete decisions.

  • Role: Centralized repository of authoritative facts and company memory.
  • How we use it: We feed NotebookLM with our raw system architecture, brand tone guidelines, legal compliance frameworks, and past post-mortem audits.
  • The advantage: NotebookLM only answers based on the uploaded sources, eliminating hallucinations when we need to cross-reference business constraints or verify edge-case policies.

3. Antigravity + Codex: The Software Factory & Code Review

Once the specification from Claude is verified against our NotebookLM repository, the development pipeline takes over.

  • Role: Full-stack implementation and automated code auditing.
  • How we use it:
    • Antigravity executes the end-to-end coding tasks in the repository, following the exact contract defined in the spec.
    • Codex runs cross-model audits and code review, scanning diffs for security regressions, edge cases, and performance bottlenecks before changes merge.

4. Manus AI: Autonomous Deep Research & Trend Recon

Building solo means you do not have a dedicated market intelligence or user research team.

  • Role: Asynchronous, end-to-end web research and trend exploration.
  • How we use it: Manus runs autonomous research tasks:
    • Deep scans of relevant open-source libraries and benchmarks
    • Cultural and behavioral trend discovery across international communities
    • Competitive UX analysis without context-switching our local development loop

5. Gemini: The Real-Time Ecosystem & Operations Orchestrator

While other models plan or write code, someone has to run the company's live systems and verify data in the real world.

  • Role: Real-time ecosystem operations, database inspections, and cross-platform automation.
  • How we use it: Connected directly to production services via tool protocols and Composio:
    • Inspects Supabase databases and Cloudflare configurations
    • Audits live analytics from Google Search Console, Meta Ads, and social metrics
    • Orchestrates multi-channel content engines, dispatching verified assets and updating queue states

Key Takeaways for Solo Builders

  1. Never ask for code before you have a specification. Code is easy; architectural clarity is hard.
  2. Assign single responsibilities to models. A model acting as both architect and auditor will agree with its own mistakes.
  3. Connect AI to your actual infrastructure. Automations that live only in chat windows create friction. Connect them to your databases, cloud drives, and deployment queues.

The superpower of a solo founder in 2026 is not working 80 hours a week—it is orchestrating AI models as an aligned, disciplined engineering team.

Written by Johnata Moreira — builder of Mishyo in Belo Horizonte, Brazil. Let's connect on LinkedIn.

Top comments (0)