How Brainis Works
This page shows exactly what happens between “here’s my objective” and “here’s the verified result.” No magic — every step inspectable, every claim linked to the layer that makes it true.
6–8 minute read
Station 1 of 10 · Understand
Tell Brainis your idea, or connect the tools your company already uses. Either way it builds Company State: goals, customers, deals, people, money, knowledge, commitments — each entry typed as fact, assumption, or constraint, each with a source and a freshness date. Aster starts with 12 interviews, 5 warm prospects, a $20k budget, and one conviction.
Station 2 of 10 · Understand
"I want to build software that turns customer interviews into product decisions" is a wish. Brainis makes it an objective: a measurable change with a horizon — 10 qualified design partners in 30 days. The token forms here; everything after exists to move it.
Station 3 of 10 · Understand
Not a questionnaire — the three questions that matter: Who makes this buying decision today? What evidence proves the pain is urgent? What would be true in 90 days if this worked? Answers become state; gaps become evidence-gathering work. Cortex separates what you know from what you're assuming — before you bet on it.
Station 4 of 10 · Decide
The Business World Model predicts how each candidate path would change the company — a focused design-partner program, a self-serve beta, a services-led entry — as ranges, not fortune-telling: qualified conversations, validation confidence, cash remaining, time to first revenue. Drag the budget from $20k to $8k and watch the recommendation change, with its reasoning.
Station 5 of 10 · Decide
The chosen path arrives as a decision brief: recommendation, alternatives, evidence, assumptions, downside, reversibility. Approving it writes an immutable Decision Ledger entry — the state you saw, the prediction you accepted, the reasoning you signed. Companies forget this within a week. Brainis never does.
Station 6 of 10 · Decide
The strategy expands into the blueprint: business plan, brand, marketing plan, media plan, website plan, agent tools, go-to-market, lead strategy. Not eight documents — eight views of one set of decisions. Change the target segment and Brainis shows you the six sections and four missions that must change, as a proposal you approve.
Station 7 of 10 · Deliver
Click "Build the mission plan" and the strategy becomes a dependency graph: ten missions with outcomes, deliverables, owners, budgets, acceptance criteria, and decision gates. You review what Brainis will do, what needs your hands, and what needs your judgment — before anything runs.
Station 8 of 10 · Deliver
Mission Control routes work across three lanes — your team, Brainis agents, connected tools. Research goes to a reasoning agent; the build to a coding agent; partner calls to the founder. Agents work inside real products — the CRM, the site, the campaigns — through Brainis MCP, each holding only the context and tools its mission allows. Claude, GPT, Codex: excellent workers. Never the employer.
Station 9 of 10 · Verify
Aster's first landing page claimed "proven to increase win rate 40%." Verify rejected it — no supporting evidence — and rejected a build whose signup flow lost intent after login. Both came back as remediation work with exact findings; both passed on the second try, checked by a different verifier plus a regression set. This is the system working, not failing.
Station 10 of 10 · Learn
Day 30: predicted 8–14 qualified conversations; actual, 11. Ten partners targeted; four accepted — and agencies, not B2B SaaS, showed the strongest willingness to pay. The ledger entry closes, the state updates, and the next recommendation is already different: run an agency-focused pricing experiment. The loop doesn't end. That's the point.
A chat can write you a plan. It can't hold your state, predict with a calibrated model, dispatch governed work, reject a bad deliverable, or remember being wrong.
No Brainis employee executes your work — delivery is your team plus governed agents, end to end. If the AI can't do something yet, you refer it to us and we build the capability.
Providers are routed workers inside the Agent Fleet. If one degrades, work routes elsewhere. The state, the plan, the permissions, and the verification are Brainis.
Tasks here know why they exist — every one traces up through a mission to a decision to an objective to your company's actual state.
Still evaluating? Read /why-brainis · inspect /product/agent-fleet · check /security