One Person Unicorn

You’re the CEO. Everyone else is an agent.

Not a chatbot you prompt. A company you run. Its agents have names, roles and a chain of command that ends at you. They plan the work, do it, and prove it. You make the calls that are actually yours.

Create your companySee how it works

Acme, a drawn company

The idea

Every AI tool makes you the worker. This one makes you the boss.

You prompt. You paste. You check. You are the bottleneck with better autocomplete. A company works the other way round: work flows down, and only decisions flow up.

You

  • Set the goal
  • Approve the hire
  • Answer the question only you can
  • Grant the access
  • Merge the pull request

Everyone else

  • Write down what the company is
  • Put a number on the goal
  • Propose who to hire, and why
  • Capture the work as tasks
  • Write the acceptance criteria
  • Plan the approach
  • Split the work and hand it down
  • Clone the repository
  • Write the code
  • Run the checks your repository declares
  • Hand the work in
  • Try to prove it isn’t done
  • Cite the evidence, criterion by criterion
  • Open the pull request
  • Enrich the leads
  • Draft the emails in your voice
  • Reconcile the payouts
  • Fire the standing work on schedule
  • Keep every prompt, call and cost on the record
  • Ask, when they truly must

Your Chief of Staff

One conversation runs the company.

Opu ships with every company and is already at their desk when you arrive. Say what you are trying to do. Opu asks two or three sharp questions, writes down what the company is, puts a number on the goal, and proposes who to hire.

  • A sharp operator, not a chatbot.
  • Decides the small things. Brings you the calls that are yours.
  • Reachable where you already are: the console, Slack, WhatsApp.
Meet Opu

The work

An agent saying “finished” counts for nothing.

Every task runs as three separate sessions: one plans, one executes, one tries to prove it failed. Done is a verdict, and a verdict has to cite its evidence.

  1. 01

    Plan

    A fresh session reads the task and writes its contract: acceptance criteria, each one checkable cold, and what is out of scope.

  2. 02

    Execute

    A new session does the work in a sandbox of its own, on its own branch, and runs the checks your repository declares. It cannot mark its own work done.

  3. 03

    Verify

    A third session, with no memory of the work, is told to assume it is not done and to find the criterion it fails. A pass must cite a recorded call for every criterion, or it is refused by name.

When the verdict is a pass, the app opens the pull request. No agent can push. Merging is yours.

Your inbox

Three decisions. Not three hundred notifications.

Your inbox holds the calls only you can make, and the list of what can land there is short. Everything else the company handles, records, and keeps moving.

  1. A run reaches a real question
  2. A tool that writes wants your approval
  3. An agent asks for a capability it lacks
  4. A task runs out of attempts
  5. A session reaches its limit

A proposed hire waits for your yes too, on the agent’s own record. Work parked on you holds no compute at all, however long you take.

An illustration of the approvals inbox with three decisions waiting: a question from Mira, a tool approval for Ivo, and a capability request from Sol. The buttons work. Answer a decision and it becomes one line on the record, and the count of open decisions goes down.

Approvals

  • Question · MiraACM-145

    Should customers already on monthly see the annual offer, or only new signups?

    The brief says not to touch anyone already subscribed. Showing them an offer is not touching them, but it is your call.

    Answered by you. Mira resumed where it stopped.Answered by you. Mira resumed where it stopped.

  • Tool approval · IvoACM-147

    Approve tool call: send_email

    Resend · writes · the first-touch email to one of the 14 leads enriched this morning.

    Approved by you. The call ran, and Ivo resumed where it stopped.Cancelled by you. Nothing was sent.

  • Capability request · SolACM-151

    Sol asks for list_payouts, on Stripe

    To reconcile August payouts against the bank. It reads, and changes nothing. The request itself grants nothing.

    Accepted by you. The tool is bound to Sol, live at its next step.Rejected by you. Nothing was granted.

  • Nothing waiting on you. The company is still working.

Go on, make a call. The buttons work.

The workforce

Write the job. Approve the hire.

Tell Opu what is missing and it proposes a hire: a name, a position, a reporting line. Nothing starts until you approve. Opu’s own rule is to hire only for a capability nobody has, and never for throughput.

An illustration of an agent’s record: Ivo, in growth, reporting to Opu. It shows the role, voice and rules you set, and a list of tools from the Intercom and Resend connectors, each with a working switch. The reading tools are bound, and so is send_email, which writes and so asks you before each call. create_contact, which also writes, is not bound until you switch it on.

Ivo Active

Growth · reports to Opu

Talk to Ivo

Identity

Edit
Role
Finds the clinics worth talking to, and gets a demo on the calendar.
Voice
Plain and short. Writes like a person who has run a clinic, never like an ad.
Rules
Never emails anyone twice in a week. Never promises a price.
Model
Company standing model
  • search_contactsIntercom
    Read-only
  • get_companyIntercom
    Read-only
  • list_emailsResend
    Read-only
  • create_contactIntercom
    Writes
  • send_emailResend
    Writes

A tool that writes asks you before each run, until you tell its connector otherwise.

Tools

  • An identity you can edit

    Role, voice, rules, model, and how many tasks it takes at once. Change a line and it is live in the agent’s next conversation.

  • Capability, one tool at a time

    A connector’s tools arrive individually and bind to one agent on their own. Reading tools just work. Tools that write ask you first.

  • It asks. Only you grant.

    An agent that lacks something requests it, and says why. A request can grant nothing, by any path.

Capabilities

All the reach. None of the keys.

118 connectors and 371 models, every tool bound to one agent at a time. You sign in on the provider’s own screen, hand over a key, or install its app. The platform keeps what comes back, and the agent gets the ability to act and never the credential.

connectors
118
models
371
platform tools
67

Every capability, by name

A day at your company

It’s 3 a.m. Your company is working. You’re not.

Standing work fires on its schedule. Tasks plan, run and verify themselves. Across this whole day, the company needed you three times.

Yours alone

Your company isn’t a row in someone else’s database.

Name it and it is built for you: a project, a database, a private file store and an address of its own, with a spend ceiling in place before it can spend a cent.

  • Single-tenant, all the way down. No shared table, no tenant column.
  • Credentials live with the platform. No agent ever sees one.
  • Only the Google account that created it is admitted.
How isolation works

Building acme.opu-inc.com

about 150 seconds
  1. Registering your company
  2. Creating your project
  3. Opening your project's health checks
  4. Attaching your address
  5. Creating your database
  6. Connecting your database
  7. Creating your file storage
  8. Connecting your file storage
  9. Reading your database identity
  10. Writing your configuration
  11. Setting your spend ceiling
  12. Building and deploying
  13. Checking it answers

Notice the order: the spend ceiling is set before the deploy that makes spending possible.

Who it’s for

Companies you could run.

For founders, solo experts and small teams who want to run bigger than their headcount. Every company starts the same way, with Opu and nothing else, and takes its shape from what you ask of it.

  • You build software

    The studio of one

    You, then Opu, then Engineering, QA, Support.

    First goalShip the paid plan this month

  • You sell what you know

    The consultancy of one

    You, then Opu, then Research, Proposals, Finance.

    First goalTwo proposals out a week

  • You sell things

    The shop of one

    You, then Opu, then Listings, Support, Finance.

    First goalEvery customer answered inside an hour

  • You make things for clients

    The agency of one

    You, then Opu, then Research, Writing, Outreach.

    First goalFour pieces published a week

Blueprints, not customers. Positions are yours to name.

Two lines it won’t cross

Autonomy is granted here. Never assumed.

  • A chain of command, not a swarm.

    Work flows down a reporting line and decisions flow up it. There is no committee of agents debating what to do next, and no agent that answers to nobody.

  • The business calls stay yours.

    Agents advise, with evidence. You decide. Work that reaches the world outside the company — an email, a payment, a merge — waits for your word, unless you have told that connector it needn’t.

Fair questions

Straight answers.

Is this a chatbot with extra steps?

No. A chatbot waits for a prompt and forgets. This is an org chart with a record: agents hold roles, tasks carry contracts, and every run is kept word for word.

What happens when an agent gets it wrong?

The verifier fails the criterion and the task goes back to be executed again, with the verifier’s findings opening that run. It costs a strike. Three strikes and the task stops and lands in your inbox. It never quietly carries on.

Can it run up a bill?

Every company gets a spend ceiling before its first deploy, so there is no moment in which it exists unbudgeted. When the ceiling is reached, dispatch pauses and the company tells you.

Who else is in my company?

Nobody. It is a deployment of its own with a database and a file store of its own. There is no shared table and no tenant column, and only the Google account that created the company is admitted.

Do I need to be technical?

No. You talk to Opu in plain language. If the work is code, the company works in your GitHub repository and hands you pull requests to merge.

Name your company. Watch it come into existence.

One name is all it takes. What comes back is a company of your own, at an address of its own, with your Chief of Staff already at their desk.

Create your companySee how it works