How Gwen starts

Getting started with Gwen is not a setup project. There is no model to choose, no template to pick, and no configuration to complete before you can do anything useful.

You describe what you want, Gwen runs a free first pass so you can see the quality, and from there a Work Budget funds continued work. Below is what that looks like step by step.

The homepage is the front door. You simply tell Gwen the outcome you want — a site, an app workspace, a content system, a CRM follow-up, a research brief, a support workflow, a software task, or anything else.

There is no form to fill in first. The conversation is the interface, and your first message is enough to begin.

When your request should become real work, Gwen asks you to sign in — inside the chat, at the moment it matters, not as a gate before you have seen anything.

Your original request is saved across sign-in, so nothing is lost. The workspace that gets created already knows what you came to do.

After you create an account or sign in, Gwen opens your workspace, restores your request, sets up the first mission, and routes you straight into the first action.

You pick up exactly where you left off. The sign-in is a step in the flow, not a reset.

For eligible first work, Gwen runs a complete first pass at no cost. Depending on what you asked for and what is connected, that might be a hosted website preview, a content or research artifact, a code or repository review, an inbox preview, or a durable project workspace.

This is the moment to judge Gwen on real output. You see the quality before you commit any budget.

Once you have seen the first pass, a Work Budget funds everything after it: continued edits, publishing, hosting, connected tools, longer runtime, exports, deployments, and paid missions.

You pay for work, not seats. Budget is prepaid, auto top-up is authorized explicitly at checkout and can be paused later, and unused credit expires after extended workspace inactivity. See Pricing and the Gwen Work Budget for the details.

As you work, Gwen accumulates context: memory, mission history, artifacts, and the patterns behind repeated work, which can become reusable skills, workflows, and playbooks.

That is what makes the second request easier than the first. The more you use Gwen in a workspace, the more it already knows when you ask for the next thing.

If you are not sure where to start, pick something real and bounded that you would genuinely use — a landing page for a current project, a first draft of a campaign, a research brief on a decision you are weighing.

The free first pass is designed for exactly this: a low-risk way to see what Gwen does with a real job, in your context, before you spend anything.