Okou is built for teams, but it works just as well for one. Solo professionals, side-project builders, consultants, and indie founders all use Okou 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 workflow, 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 Okou 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. Okou 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 Okou workspace ends up with 5–10 workflows and 2–3 automations. 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 "Okou is doing useful work":
- 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}.
- 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.
- Turn it into an automation. "Run this every weekday at 9 a.m. and email me the result." That's your morning brief.
- Save useful chats as workflows. "Turn this into a reusable workflow called
weekly-newsletter-draft." Now you can invoke it by name later. - Hook up additional connectors when a workflow needs them — Okou asks at the right time.
Most solo workspaces hit "Okou is paying its way" within the first week.
How billing works for one person
- No seat fee. Billing is by credits, not by person, and an idle workspace costs nothing.
- Free to start. A new workspace begins with 3,000 starter credits valid for 30 days and then stays on Free. Credit top-ups and auto-recharge are paid-plan features, so Free is a place to evaluate Okou rather than a place to buy more credits.
- Plan credits don't roll over. Credits granted by a paid plan are scoped to the current billing cycle and expire at the end of it. Top-up credits never expire.
- Bring your own provider, on a paid plan. Depending on workspace policy, a model can run on Okou credits, on your own connected Claude or Codex subscription, or on a provider API key you supply. Tool calls, generation, and storage still bill against Okou credits. Routing is configured under Settings → Models — see Credits & billing.
- Auto-recharge available on paid plans. Set a threshold and an amount; the workspace tops itself up when needed. A common setting: "recharge $20 when the balance drops below $5."
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:
- Workflows you create stay private unless you mark them public.
- Automations and their run histories are visible only to you.
- Chats are visible only to you.
- Connector tokens are scoped to your account; they can't be used outside this workspace.
Okou staff cannot read your chat 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 Okou'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 workflow. 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 workflow that takes a Notion doc and rewrites it as a one-page exec summary.
- The launch-week bundle. A workflow 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 Okou in the same context (employees, contractors, agency partners)
- You want workflows or automations 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 workflows, automations, and connectors carry over.
What's next
- See Quickstart for the first task to try.
- See Workflows to make your most repeated prompts reusable.
- See Automations for the recurring work that pays Okou back daily.