An assistant answers when questioned. An agent completes a task you hand it. A cofounder owns a function continuously and is accountable for a measurable outcome. The three are not points on one scale of cleverness — they differ in who starts the work and what counts as failure.
The sentence worth keeping: an agent is the mechanism, a cofounder is the job. Almost every AI cofounder is built out of agents. That tells you how it works, not what it is for.
The three
Assistant
You ask, it responds. The unit of work is a reply. It has no standing brief, no memory of what it was supposed to be achieving, and no reason to do anything between your messages. A chat window that writes ad copy on request is an assistant, however good the copy is.
Agent
You give it a goal, it plans, calls tools, and comes back with the thing done. The unit of work is a task. It can take many steps without you, which is the part that feels new, but it still starts when you start it and stops when the task is finished.
Cofounder
Nobody hands it the task. It has a standing brief, decides what this week's work should be, does it, and is judged on a number rather than on whether the work got done. The unit of work is an outcome. Most of the time it is built out of agents — that is the mechanism — but the mechanism is not what makes it a cofounder.
Side by side
Why it matters
The distinction sounds academic until you notice which one solves your problem. If the complaint is “writing ad copy takes me two hours”, an assistant fixes it. If the complaint is “I keep having to research competitors before I can write anything”, an agent fixes it. If the complaint is “another month went by and we published nothing”, neither one helps, because the missing thing is not speed on a task — it is that nobody owns the function.
It also changes what going wrong costs. An assistant giving a bad answer costs you the time to ask again. An agent failing a task costs you a rerun. Something that owns a budget and acts on its own has already spent money by the time it is wrong, which is why the interesting engineering in this category is not the reasoning — it is the ceilings, the approval queue, and how fast it cuts its own losers.
Related: what an AI cofounder actually is and whether an AI can be a legal cofounder.
Questions
An agent is the mechanism; a cofounder is the job. An agent completes a task you hand it and stops. A cofounder holds a standing brief, decides what the work should be without being asked, and is accountable for a measurable outcome rather than for finishing tasks.
Architecturally it usually is. The difference is not in the parts — it is that something has to decide what the agents should be working on, hold the goal across weeks, and be judged on a result. Chaining agents without that layer gives you a faster task-runner, not an owner.
An assistant produces a response and waits for you again. An agent takes multiple steps on its own — planning, calling tools, checking its work — before it comes back. The dividing line is whether it can act, not just answer.
If the problem is that a specific task takes you too long, an agent is the right shape and cheaper. If the problem is that nobody is doing the function at all — nothing gets published, nothing gets tested, weeks pass — then the gap is ownership, and a faster task-runner does not fill it.
Not necessarily in any given moment. Autonomy is a setting, and a cofounder can be run in a mode where it publishes nothing without your approval. What separates it is scope — it decides what to work on — not how much it is permitted to do unsupervised.
Founding cohort seats include the first month and a written teardown of your current funnel.
Claim a seat100 seats. No card. We tell you on day 14 whether it worked.