Back to docsWho it's for

For individuals

Zero for solo professionals, consultants, and side-project builders.

Last updated May 27, 2026 · 5 min read

Zero is built for teams, but it works just as well for one. Solo professionals, side-project builders, consultants, and indie founders all use Zero the same way: as a personal AI teammate that gets actual work done across the tools you already use.

The team-vs-individual distinction is mostly about billing and visibility, not capability. A solo workspace has access to every skill, every connector, and every channel the largest workspace has — minus the multi-member overhead.

Common solo use cases

What individuals reach for most, in roughly the order they tend to adopt:

  • Inbox and calendar discipline. A daily morning brief + an evening inbox cleanup. The two highest-leverage automations for anyone whose calendar fills up faster than their attention.
  • Research and reading. A weekly competitor or industry digest. Account briefs before sales calls. Quick "what is this thing" lookups during the day.
  • Content production. Blog drafts, social posts, newsletters. Individuals lean on Zero heavily for the first pass — it doesn't replace voice, but it skips the blank-page step.
  • Side-project automation. Building, shipping, and monitoring a small product. Zero handles the GitHub side: triage, small fixes, release notes, deployments through Vercel.
  • Personal accounting and admin. Receipts in, categorized out. Tax-time prep. Invoicing follow-ups for consultants.
  • Customer-facing work for solo consultants. Reply drafts, scheduling, contract drafts, follow-ups.

A typical solo Zero workspace ends up with 5–10 skills and 2–3 schedules. That's enough to take a meaningful chunk of work off your plate without becoming a thing you maintain.

Setup: a half hour to fully operational

A pragmatic path from sign-up to "Zero is doing useful work":

  1. Connect 2–3 core tools. Whatever your work mostly lives in. For most people: Gmail or Outlook, a calendar, and one of {Notion, Linear, GitHub, Slack}.
  2. Write your first prompt as a chat. Something concrete: "Summarize my unread inbox and tell me what needs a reply today." Iterate until the result is useful.
  3. Turn it into a schedule. "Run this every weekday at 9 a.m. and email me the result." That's your morning brief.
  4. Save useful chats as skills. "Turn this into a reusable skill called weekly-newsletter-draft." Now you can invoke it by name later.
  5. Hook up additional connectors when a workflow needs them — Zero asks at the right time.

Most solo workspaces hit "Zero is paying its way" within the first week.

How billing works for one person

  • Pay-as-you-go credits. No seat fee, no minimum, no commitment. Buy credits when you need them; idle workspaces cost nothing.
  • Starter credits on signup. Enough to set up a few workflows and run them for a week. No credit card.
  • BYOK if you prefer. Bring your own Anthropic, OpenAI, or Google API key and route inference through your provider account. Tool calls and storage still bill against VM0 credits. See Credits & billing for the math.
  • Auto-recharge available. Set a threshold and an amount; the workspace tops itself up when needed. The most common setup: "recharge $50 when balance drops below $20."

The typical individual user spends a few dollars to a few tens of dollars a month depending on workflow mix. Heavy media generation (video, image) costs more; pure text and tool calls cost less.

Privacy

A personal workspace is yours alone. There are no teammates, no admins, no shared visibility:

  • Skills you create stay private to your workspace.
  • Schedules and their run histories are visible only to you.
  • Sessions are visible only to you.
  • Connector tokens are scoped to your account; they can't be used outside this workspace.

VM0 staff cannot read your session content; the platform has admin tools but they're scoped to billing, abuse detection, and explicit support requests you initiate.

A few patterns that work especially well solo

  • The standing morning brief. It's the gateway drug. Once it works, the rest of Zero's value is easier to see.
  • The weekly newsletter draft. Email creators love this. Topic from research, draft from your past pieces, scheduled for Friday afternoon review.
  • The expense-report skill. Forward a receipt, get a properly categorized expense logged to your accounting tool. Tax season becomes a non-event.
  • The "explain like I'm running" task. For founders and PMs: a skill that takes a Notion doc and rewrites it as a one-page exec summary.
  • The launch-week bundle. A skill that produces blog post + LinkedIn + X thread + social cards + email all from one input. A solo founder's launch day in one prompt.

When to graduate to a team workspace

The signals:

  • More than one person needs to call Zero in the same context (employees, contractors, agency partners)
  • You want skills or schedules visible to others
  • You need consolidated billing and reporting
  • You want admin controls on connectors (who can connect what)
  • Compliance asks for audit logs across multiple users

Migrating from individual to team is one click — your existing skills, schedules, and connectors carry over.

What's next

  • See Quickstart for the first task to try.
  • See Skills to make your most repeated prompts reusable.
  • See Schedules for the recurring work that pays Zero back daily.