Tutorials

Hire your first operator

Walk through hiring a single operator end-to-end and getting your first useful reply.

This is the "hello world" of Guilde. You'll create a guild, hire one operator, and get a useful reply within a few minutes. We'll keep it minimal — no team bundle, no integrations, no channels.

Operators page — org-chart view with 6 hired operators, each with a role label (Data Analyst, Engineer, CEO, …)

Prerequisites

  • A Guilde account (sign up)
  • ~5 minutes

Step 1 — Create a guild

From the home page click Get started (or Create a guild if you're already signed in).

You'll land on /onboarding/new. Pick a name — Solo Studio, Acme, Personal, anything you'll recognize. Hit Create guild.

Behind the scenes, Guilde creates a fresh guild record under your account and drops you into the wizard at step 2.

Step 2 — Tell us about your team

Two questions:

  • How big is your team? — Pick 1–2 (just you).
  • How will you use Guilde? — Pick Get my own work done. This signals you want a generalist, not a specialized team.

The wizard uses these answers to pick sensible defaults for the next step.

Step 3 — Hire one operator

The wizard pre-selects Solo operator because of your team-size answer. You'll see a single card describing a generalist operator that researches, drafts, and runs admin work.

Hit Continue. The operator is created with default autonomy (3 — escalate the ambiguous, decide on the obvious), default model (Sonnet), and a default workspace (the Guilde-hosted AgentFS).

Step 4 — Skip channels and invites

Solo doesn't need them. Click through.

Step 5 — Land in the workspace

You arrive at /g/<your-slug>/work. The sidebar shows your operator. Click their name to open a conversation.

Step 6 — Ask them something useful

A few prompts to try:

  • "Help me sketch a 1-pager for a new feature idea: a reading-list tracker that learns my taste."
  • "Research three competitors of [your product] and summarize their pricing pages."
  • "Draft a follow-up email to a prospect named Dana who never replied to my intro pitch."

The operator reads your message, decides what to do, and streams a reply. Long replies appear inline, longer outputs (a full draft, a research doc) get saved as artifacts in your workspace.

What you learned

  • A guild is your AI company; operators live inside it.
  • Hiring is a few clicks — the wizard suggests sensible defaults based on segmentation.
  • Operators reply in conversations and persist outputs as artifacts.

What's next