Frequently asked questions about the Boots AI platform, architecture, and capabilities

Frequently Asked Questions

How long does AI proposal generation take?
The TypeScript worker generates a proposal in 15-30 seconds using Claude Sonnet. The full brain pipeline (7 agents) takes 60-120 seconds depending on research complexity. Users see real-time progress updates via Supabase Realtime.
Why Python for the brain when everything else is TypeScript?
The brain orchestrates 7 agents with complex state management, async execution, and structured JSON output. Python's Anthropic SDK, asyncio, and the ML ecosystem are significantly more mature for this. TypeScript handles web, API, and simple jobs. They communicate via Supabase as shared state — no direct HTTP calls.
How does the intelligence get smarter over time?
Every proposal triggers a memory write: client psychographics (tone, themes, strategy) and a deal history entry are stored with a 1536-dimensional embedding. Future proposals for the same or similar clients retrieve this context via pgvector cosine similarity search. The more proposals you create, the more personalized they become.
What happens if the brain service goes down?
The TypeScript worker continues processing simple jobs (contracts, text extraction). Brain proposals stay in "queued" status until the brain comes back. No data is lost — Supabase is the system of record. Users can still use the standard AI generation path via the worker.
How is this different from PandaDoc or Proposify?
Those are template-filling tools. Boots generates proposals from scratch using AI that knows your business (org brain), remembers your clients (intelligence), and learns from outcomes (deal tracking). It's an AI-native proposal generator, not a document template editor.
Can this be self-hosted?
The architecture supports it. Next.js runs anywhere Node.js runs. The worker and brain are Docker containers. Supabase can be self-hosted. You'd need to manage your own Stripe, Anthropic, and OpenAI API keys. Not currently offered as a product, but architecturally feasible.
How are secrets managed?
17 environment variables across three deployment targets. Vercel manages web app secrets. Fly.io manages worker and brain secrets separately via fly secrets set. No secrets in source code, no .env files committed. Sensitive vars in Vercel cannot be viewed after setting.

Ready to create AI-powered proposals?

Start Free