Cofounder Docs
What Happens After Onboarding
Understand what Cofounder sets up during onboarding and how your workspace is organized once you are ready to start work.
Your Workspace Is Already Structured
After onboarding, Cofounder should feel like a working company system, not a blank sandbox.
After onboarding, your workspace already has departments for the parts of the business you want to run, agents inside those departments, and the core infrastructure those agents need.
What Onboarding Sets Up
Every onboarded workspace gets:
- an app GitHub repository for the main app codebase
- a marketing GitHub repository for the site, launch pages, and growth surface
- corresponding Vercel projects so app and marketing work can ship to the right deploy target
- a managed Supabase project for the organization's database and backend operations
- starter departments and agents aligned to the way the company runs
- a shared Library for files that agents and users need to reference across work
How That Maps To Departments
Cofounder organizes work through departments.
A department owns a slice of the company, and the agents inside that department inherit the context, tools, and scope that make sense for that lane of work.
For example:
- the Engineering or Product department might contain agents that can work in the app repo, inspect PRs, and reason about the main app
- the GTM or Marketing department might contain agents focused on launches, messaging, campaigns, and the marketing repo
- infrastructure-aware agents can work against the org's Vercel and Supabase setup when the task needs deploy or backend context
What Agents Actually Do Next
Once onboarding is complete, the normal flow is:
- Open Canvas.
- Go to the department that owns the job.
- Choose the agent with the right scope.
- Give it a concrete task.
- Review the result, then refine the setup if needed.