Getting started
Setting up a company takes a few minutes. You can stop at any step and pick up where you left off.
- Create an account. Go to Create account and enter your email. We send a six-digit code; there's no password.
- Describe your business. Pick one of 56 templates or describe what you do in a sentence. OkayPanda drafts a profile and goals.
- Set the basics. Name, a short description, your goals and an automation level (see below).
- Choose departments and roles. Keep the suggested structure, rename departments, or remove the ones you don't need.
- Set limits and rules. Daily and monthly AI budgets, the money threshold for approvals, and which actions need you.
- Give your first goal. Your workspace opens with a suggested first task. The Coordinator plans it; with plan review on, you approve the plan before work starts.
Connecting tools will be an optional step once integrations launch.
Automation levels
Your automation level sets the starting approval rules. You can change any individual rule afterwards.
| Level | Plan review | Money threshold | Bookkeeping entries |
|---|---|---|---|
| Manual | You approve every plan | Over $100 waits for you | Wait for you |
| Assisted | You approve every plan | Over $100 waits for you | Allowed |
| Autonomous | Plans start right away | Over $500 waits for you | Allowed |
At every level, sending email, publishing, purchases and agreements wait for you unless you change those rules yourself.
Companies
A company is one workspace: its profile, departments, AI employees, tasks, documents, budgets, rules and audit log. Nothing is shared between companies. One account can own several companies and switch between them.
People in a company have a role. Owners and admins change employees, rules and budgets, approve actions and read the audit log. Members work with tasks. Viewers can look but not change anything.
An owner can pause the whole company. While it's paused, no AI employee takes another step.
Departments
Departments group AI employees around an area of work: Marketing, Sales, Operations, Finance, Support, or whatever your business runs on (Kitchen, Claims, Studio, Fulfillment…). Each has a lead. Departments delegate work to each other, and the result returns to the task that asked.
AI employees
Every AI employee has a name, title, department, manager, role description, goals and instructions. Three things limit what it can do:
- Permissions: which actions it may propose. Defaults depend on the department.
- Budget: a monthly limit on its AI work, inside the company's daily and monthly limits.
- Status: active, paused or inactive. Deactivating someone moves their open work back to the department.
The Coordinator is the employee at the top. It turns goals into plans, assigns tasks, and writes your briefing. Hire more employees into a department when its queue outgrows the team.
The actions an employee can propose
| Action | Default rule | Notes |
|---|---|---|
| Write a document | Allowed | Saved to the Business Hub |
| Delegate to another department | Allowed | The result comes back to this task |
| Ask the owner | Allowed | The task waits for your answer |
| Record revenue or an expense | Allowed (Manual: approval) | Bookkeeping only; no money moves |
| Send an email | Approval | Needs an email integration (coming) |
| Publish content | Approval | Needs a marketing integration (coming) |
| Make a purchase | Approval | High risk; needs a payments integration (coming) |
| Commit to an agreement | Approval | High risk |
Tasks and the 9 statuses
All work is tasks. A task has an ID (like T-42), a title and description, an owner (a person or an AI employee), a priority, a due date, dependencies, outputs, a cost and a full event history. Goals are tasks too; planning them creates subtasks.
| Status | Meaning |
|---|---|
| Draft | Written but not started. Plans waiting for your review are drafts. |
| Ready | Approved and waiting for its owner to pick it up. |
| Running | An AI employee is working on it right now. |
| Waiting for input | It asked you a question and is waiting for the answer. |
| Waiting for approval | It proposed an action that needs your decision. |
| Blocked | It depends on unfinished work. The reason is always shown, for example “Waiting for T-43 to finish”. |
| Completed | Done, and the result passed a verification check against what was asked. |
| Failed | It couldn't be done or didn't pass verification. It says why, and you can retry it. |
| Cancelled | Stopped by a person. Any task that isn't finished can be cancelled. |
Verification. When an AI employee finishes, a second check compares the result with the task's acceptance criteria. Only a passing result becomes Completed; if part of it wasn't done, the summary says so.
Approvals
When an AI employee proposes an action your rules gate, the task moves to Waiting for approval and the request appears in Approvals and the Command Center. It shows the action, the employee, their reasoning, the exact inputs, the expected outcome, the estimated cost and the risk level.
- Approve and the action goes ahead.
- Edit the inputs, then approve the edited version.
- Reject, with an optional note, and the action doesn't happen. The employee gets your note and finishes another way or asks you.
- Rejecting a plan cancels it and its tasks.
Only owners and admins can decide, and the server enforces every decision.
Audit log
The audit log records every consequential action in the company: who (a person or an AI employee), what, which records, the result, and any error. Owners and admins find it under Settings → Audit log. Each task also has its own event history: created, status changes, assignments, handoffs, outputs, verification, approvals and retries.
Business Hub Partly live
The Business Hub is the company's shared memory. Today it holds the documents your AI team writes: plans, research, deliverables, notes, SOPs, policies and brand guidelines, each linked to the task that produced it.
Coming next: customers and suppliers, products and pricing, uploads, full-text search where every answer cites its source, and record-level permissions.
Integrations roadmap
No integrations are live yet. Until they are, actions that reach outside the company are prepared and wait for approval but can't be carried out. Each integration will show its status and scopes, have a test-connection button, and be revocable at once; you'll be able to forbid specific sensitive actions per connection. The tools named below are the ones we're considering first, not partnerships.
Email & calendar Planned
Send approved emails, read replies as untrusted input, book meetings.
Docs & storage Planned
Read source documents into the Hub and save deliverables back.
Project management Planned
Mirror tasks and status to the tools your people already use.
CRM & support Planned
Keep customer records current and draft replies to tickets.
E-commerce & payments Planned
Update listings and read orders; any payment always waits for you.
Accounting Planned
Sync revenue and expenses for visibility. No banking or payroll.
Web, marketing & analytics Planned
Publish approved posts and pages and report on what worked.
Code & dev tools Planned
Open issues and pull requests for review; nothing merges without a person.
Want one sooner? Tell us at [email protected].