Standard, Deep analysis, and Build

Every exploration runs in one of three modes. The mode shapes Ronja’s personality, her tools, and how much rigor she applies — so choosing well at the start matters.

The billing pages use different names

The billing and Control Center surfaces group these modes into two lanes: Analyst (Standard + Deep analysis — asking questions in chat) and Builder (Build). Same modes, different labels — if you see “Analyst mode” or “Builder mode” on an admin page, that’s what they mean.

Choosing a mode

On a fresh, empty exploration, the owner sees a segmented mode control with up to three segments, labeled exactly as they appear on screen: Standard, Build (shown only if you have build access), and Deep analysis.

The mode picker appears only on an empty exploration, and only for its owner.

Once the first message is sent, the mode is fixed for that conversation — the product refuses later changes with “mode can only be changed before the first message” — with one exception: Ronja can request a switch to Build (below). Explorations in Deep analysis or Build mode carry a persistent header stamp (“DEEP ANALYSIS” or “BUILDER”) so you always know which lane you’re in.

Standard

The default. Ronja answers questions, queries and charts your data, and explains what she finds — the everyday analysis conversation. No stamp, no extra ceremony. Most explorations are Standard.

Tip

Reach for Standard when you have a question to ask, and switch to Build only when you actually want Ronja to create something durable. Build mode does more work and costs more — save it for when you’re building, not asking.

Deep analysis

For questions where you need to trust the answer, not just receive one. In the product’s own words: “A rigorous, methodology-first investigation — Ronja designs the approach, validates the data can support a trustworthy answer, and explains how it reaches every finding.”

Deep analysis uses the same analysis toolset as Standard — it does not build resources — but works with extra rigor and extended thinking. Its signature artifact is the Methodology: a living research document covering the goal, hypotheses, method, feasibility and data quality, and validation, which Ronja maintains as she works. The Methodology panel opens automatically on its first write and stays reachable from the exploration’s ledger.

Deep analysis is available to everyone, but you choose it up front — on the start screen, or when picking a mode for a tangent. An existing conversation can never switch into it.

Build

Build mode is the solutions architect. Ronja designs and creates durable resources — tables, workflows, data apps, notes, and more — writing an implementation Plan first and keeping it up to date as she goes. A Build status dock on the right tracks what’s in progress and what’s been built. The header stamps “BUILDER” with the subtitle “extended thinking”.

Who gets Build

Build access is granted per account. Without it, the Build segment simply doesn’t appear — and the server independently enforces the same rule, refusing with “Build mode is disabled for your account. Contact an administrator to request access.” Administrators manage who has build access; see Govern AI spend.

Three ways in

1. The start screen — pick Build before the first message.
2. Mid-conversation — Ronja herself may ask to switch when a Standard conversation turns into a build job. This arrives as an approval strip reading “Enter builder mode” that you must approve, and it is one-way: the exploration stays in Build mode from then on.
3. A tangent — when forking a tangent, you pick the branch’s mode; Build is offered if you have access.

Start with the plan

The first thing Ronja does in Build mode isn’t build — it’s plan. She sketches a short implementation plan in a Plan panel on the right and uses it to confirm the scope with you before creating anything. Think of it as a mini-PRD: the shape of what she’s about to build, written down so you can react to it. The panel opens automatically on the first plan write and stays up to date as the work proceeds.

Read it, and steer it. Approving the plan first — correcting a wrong assumption, cutting something you didn’t ask for, adding a constraint — is the single highest-leverage thing you can do in a Build session:

• Better-built resources — Ronja builds against a scope you’ve agreed on, not one she guessed.
• Fewer credits — Build mode is the most credit-intensive work in Ronja, so catching a wrong turn in the plan is far cheaper than unwinding finished resources afterward.

Ronja writes the plan first — read it and steer it before she starts building.

For more habits that get the most out of Ronja, see Getting the most out of Ronja.

Approval gates apply in every mode

Build mode changes what Ronja can make — it doesn’t bypass who approves it. Consequential actions still pause on the approval strip, and edits to shared resources travel as drafts and proposals through review. See Versions, drafts, and approvals.

Note

Mode changes are asymmetric: a Standard exploration can become a Build one (only via the agent’s approved request), but nothing ever becomes Deep analysis after the first message. If you want the methodology-first treatment, choose it up front.