Almost every Emergent project starts the same way: one person, one idea, one evening. The tool is built for that and it is very good at it.
The stage nobody plans for is the one after it works. A second person needs to change something. Somebody in finance asks what this costs. Somebody in security asks where the data lives. None of those questions are about building an app, and all of them arrive at once.
The free tier is a demo, not a starting point
Emergent's Free plan gives you 10 credits a month and access to the platform's essential features, including web and mobile building and one-click LLM integration. What it does not include is GitHub integration or private project hosting — both of those start at Standard, at $20 a month ($17 billed annually) with 100 monthly credits.
This matters more than it looks. Without GitHub integration there is no version history, no branch, no route by which a second person picks the project up in their own environment, and no export path if you decide to leave. A project built entirely on the Free tier is a project that exists in one place.
If there is any chance the thing you are building will outlive the evening, start on Standard. It is the cheapest decision in this article and the only one that is painful to reverse.
What Pro is actually for
Pro is $200 a month ($167 annually) with 750 credits, and the credits are not the interesting part. The tier adds a 1M context window, an "Ultra thinking" mode, System Prompt Edit, custom AI agents, high-performance computing and priority support.
System Prompt Edit is the one worth understanding, because it changes the tool's category. On lower tiers you are asking a product to build something. With editable system prompts you are configuring how the agents behave — house conventions, framework choices, things they should never do — and that is what makes output consistent across a team rather than varying by whoever typed the prompt.
The honest read: Pro is priced for people whose time is expensive, and the jump from $20 is steep enough that you should reach it because you hit a specific wall, not on the assumption that more credits will help.
Business is where multiple people become supported rather than tolerated
Business is custom-priced and adds the things that make shared work function: role-based access control, single sign-on, shared team workspaces and real-time co-editing.
Two of those are collaboration features and two are control features, and teams usually arrive for the first pair and stay for the second. RBAC is what lets you separate the person who can change production from the person who is exploring an idea. SSO is what makes offboarding a single action instead of a checklist.
If you are running a shared account with shared credentials right now — and many small teams are — that is the thing this tier fixes, and it is worth fixing before somebody leaves rather than after.
Enterprise is a compliance answer
Enterprise adds user-level credit limits, audit logs, self-hosted database support, a priority SLA, VPC deployment and usage analytics.
Read that list as a set of answers to questions somebody else will ask you. Audit logs answer "who changed this". User-level credit limits answer "how do we stop one person consuming the budget". Self-hosted database and VPC deployment answer "where does our data actually live", which is the question that decides whether a regulated industry can use the tool at all.
You do not need this tier until someone asks, and when they ask, nothing below it will do.
Three questions to answer before person two arrives
None of these require a plan change to answer, and answering them badly is what makes the plan change urgent later.
- Where does the code live outside Emergent? If the answer is "nowhere", fix that first — GitHub integration from Standard up is the mechanism, and the code is yours to download, modify and host wherever you choose
- Who is allowed to change the deployed version? Answer it out loud before two people are editing, not after the first accidental overwrite
- What is the monthly credit burn, and who watches it? A monthly bucket shared between two people runs out roughly twice as fast, which is obvious and still surprises everyone