Beginner mode

How agntdata adapts the Builder for users who want agents built for them, not API access.

When you sign up, agntdata asks one question before the rest of the onboarding form:

What’s your style?

• I want agents built for me — I want to deploy agents that handle my workflows — no code required.
• I build things myself — Give me the API and infrastructure — I’ll build on top of it.

That choice is stored on your profile as experience_level (beginner or experienced) and threads through the Builder, the welcome flow, and the post-onboarding greet. It doesn’t lock anything down — you can use every API on either path — it just changes what the Builder says first.

What changes

Surface	Beginner	Experienced
Onboarding redirect	Land in a fresh meta-agent chat session that greets you as your “AI GTM engineer” and pitches concrete starter agents.	Same destination, but the synthetic greet introduces the self-service API surface and asks what platform you’re building on.
Welcome modal	The “Your API key is ready” modal is suppressed — beginners don’t need to be confronted with bearer tokens.	The welcome API key modal pops on first dashboard load.
Builder opening line	”Tell me about the work you’d like to automate."	"What are you building?” + a quick map of the API surface.
Sub-agent pitch	The Builder leads with two or three starter workflows tailored to the user’s stated agent_types answer.	The Builder leads with capability discovery (list_agent_capabilities) and asks which platform the user already builds on.

Both paths use the same meta-agent (supr_agnt), the same tools, and end up in the same /dashboard/chat/<session_id> view. The difference is entirely in the synthetic system message that pre-seeds the conversation.

Where it’s wired

• The onboarding form lives at /onboarding; it writes profiles.experience_level and profiles.onboarded_at.
• After form submit, the dashboard creates a fresh meta-agent session with onboarding_greet_variant: 'beginner' | 'experienced' and routes to it.
• The chat page fires the post-onboarding greet on first mount. The variant is read from the session row and dispatches one of two synthetic prompts in apps/api/src/services/meta-agent/post-onboarding.ts.
• welcome-api-key-modal.tsx reads experience_level and renders only when it’s experienced.

DFY (done-for-you) signups

A separate DFY funnel skips the experience-level question entirely. Users who arrive via the DFY landing page check out into a paid setup engagement, and the onboarding form is bypassed — the agent gets built for them out-of-band and lands in their workspace pre-deployed. From the dashboard’s point of view a DFY user looks like a beginner who already has agents.

Changing it later

There’s no in-dashboard toggle to flip between beginner and experienced — the choice is just a hint for the first conversation. If you want the experienced flow on an account that picked beginner, ask the Builder directly: it will adapt mid-session.

Next steps

The Builder

What the meta-agent actually does in either mode.

Multi-workspace

Switching workspaces and the personal-workspace lifecycle.