The OpenV2 AI team
Most AI app builders give you one agent that does everything. OpenV2 has Team mode: six specialists who research, scope, design and build your app together, and hand work to each other where you can see it. If you only want to build, Solo mode is one engineer.
Why a team beats a single prompt box
A single agent has to guess your market, your scope and your architecture while it writes code. In Team mode each job has an owner:
- The research is done before the first screen, with sources.
- The scope is a short MVP, not everything at once.
- The architecture is decided before the data model is written.
- The code is written by one engineer, so changes stay consistent.
- The numbers are read by someone who checks them.
Meet the six specialists
| Specialist | Role | What they do for your app |
|---|---|---|
| Ethan | Team Leader | Understands your request, decides who does what and keeps everyone on track. Every message goes to Ethan unless you choose someone else. |
| Clara | Deep Researcher | Researches the market, competitors and what users say, with verifiable sources. Separates evidence from inference and states the limits of what she found. |
| Maya | Product Manager | Turns your idea into a short MVP: the screens, the key features and what waits for later. |
| Oliver | Architect | Designs how the app works inside: data, notifications, sync and risks, before the code is written. |
| Leo | Engineer | Writes the code in Swift and SwiftUI or Kotlin, builds the app, makes the images and the app icon, runs the build check and fixes what breaks. |
| Sofia | Data Analyst | Reads your data and metrics, checks the numbers and tells you what they mean. |
Only Leo changes your app. The others read, research and plan, and can write short notes in your project's docs folder. Their tools stop anything else, so research and planning can never overwrite your code.
How a request moves through the team
- A new app goes Ethan, then Maya, then Leo. Maya writes a short MVP scope in plain words and hands it to Leo to build.
- A small change or a fix goes straight to Leo.
- Research first goes to Clara.
- Hard technical designs bring in Oliver.
- Questions about data and metrics bring in Sofia.
Each specialist says what they are doing and then hands off. The handoff appears as a compact Brief for card that you can open to read exactly what the next specialist received.
Deep research before you build
Clara works in three steps. She first writes a research plan (the objective, the key questions and the sources she proposes) without touching your app. You review the plan and approve it. Then she researches and delivers a brief with sources, findings, charts and diagrams. The plan and the brief are saved as Markdown files in your project's docs folder, so the whole team can use them. See Deep research.
You stay in control
- Choose who answers. Click a specialist on the dashboard, use the team picker next to the chat box, or write
@Oliver, how should sync work?. - Answer short questions. If a request is unclear in a way that changes what gets built, a specialist asks you one to three multiple-choice questions in a card. Answer or skip.
- Switch modes any time. Solo is one engineer (Leo) doing everything; Team brings in the other five.
An example
You write: "A habit tracker with streaks and reminders."
- Ethan takes the request and sees it is a new app.
- Maya writes the MVP: today screen, habit list, streak view, reminders; sharing waits for later.
- Oliver decides how habits, streaks and notifications are stored and synced.
- Leo builds it, makes the icon and the images, and checks the build.
- You test it in the cloud simulator and ask for changes. Small fixes go straight to Leo.
- Later, Sofia reads your usage data and tells you which habits people drop first.
Team mode and usage
Messages that build something (code, images, the icon, backend setup) use your plan's usage. Plain conversation, such as questions and advice, does not. Research uses usage like other work that creates files. See Plans and usage.
Read more
- Solo and Team in the docs
- Deep research
- OpenV2 vs Rork, OpenV2 vs Lovable and all comparisons
- AI app builder and iOS app builder
Frequently asked questions
What is Team mode in OpenV2?
Team mode puts six AI specialists on your app: Ethan (Team Leader), Clara (Deep Researcher), Maya (Product Manager), Oliver (Architect), Leo (Engineer) and Sofia (Data Analyst). They hand work to each other and you can see every handoff.
Who actually changes my code?
Only Leo, the engineer. The other specialists read, research and plan, so their work cannot overwrite your app.
What is the difference between Solo and Team?
In Solo mode one engineer, Leo, does everything: code, images, icon and the build check. In Team mode six specialists share the work.
Can I talk to one specialist directly?
Yes. Pick one on the dashboard or with the team picker, or write @ and a name in your message.
Does Team mode cost more?
Messages that build something use your plan's usage, in both modes. Plain conversation does not count. A bigger task uses more than a small edit.
Do other AI app builders have a team?
Many work through a single agent. See our comparisons for what we found on each product's public pages.