How OpenLabor works

The whole platform in one mental model — five words and how they fit together.

The steps

You hire employees, not prompts — An **employee** is an AI worker with a role, its own memory, its own files and its own connected accounts. You don't configure it — you hire it from the job board, and it arrives knowing its job. The CMO knows marketing frameworks; the Accountant knows a chart of accounts. You talk to it in plain language, the way you'd talk to a new hire.
Superpowers turn a form into a finished document — A **superpower** is a framed run: you fill in a short form, and a few minutes later you get a finished document — a competitor map, a cold-email sequence, a cash-position report. It's the fastest way to get value on day one, because there's nothing to set up and nothing to phrase. The result is a document you review; a superpower never sends, posts or pays anything on its own.
Apps are the accounts they work with — An **app** is a real account you connect — Gmail, Shopify, HubSpot, Notion. Until you connect one, your employee works from what you tell it and what's in its files. Once connected, it reads and acts on the real thing. You connect apps when a piece of work asks for them, not upfront.
Jobs repeat, triggers react — A **job** is work on a schedule: every Monday, write the KPI digest. A **trigger** is work that starts when something happens: a webhook fires, a form is submitted, an email arrives. Anything you find yourself asking twice should become one of the two.
Everything lands where you can see it — Runs, questions and approvals show up in your **Inbox**. Documents land in **Files**. When an employee needs your sign-off before acting, that's a notification — nothing outbound happens without you until you decide it should. Credits pay for the work; you can see what every run cost.

You should see

You can now read the rest of the product: every screen in the dashboard is one of these five words.

The OpenLabor Academy