Cofounder Docs
Cofounder Docs

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

Design Onboarding

Design onboarding helps your workspace leave setup with a usable brand direction, not just a blank Design Agent.

During design onboarding, you can choose a starting vibe, add reference images, describe what the brand should feel like, and generate a brand kit. You can review earlier brand-kit versions before locking one in.

When the brand kit is ready, you can copy or download the brand-kit image. Cofounder saves the design context for future Design Agent work and then moves you into the first Canvas handoff.

If you need to move on before brand setup is complete, you can skip design onboarding and come back to design work later.

Current App Platform Support

Today, the managed platform mainly supports web apps built with Next.js.

That is the default path for the app repository, Vercel deployment flow, Supabase wiring, previews, publishing, and Engineer Agent verification.

Mobile app functionality is currently being implemented through React Native and Expo integration. Until that support is fully available, treat mobile app builds as in-progress platform support rather than the same mature path as Next.js apps.

Multiple Organizations

Multiple organizations are available on paid subscriptions. Each organization requires its own subscription.

The $15 free credit applies only to the first organization on your account. If you create or join additional organizations, those organizations do not receive a separate $15 free credit.

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

What Agents Actually Do Next

Once onboarding is complete, the normal flow is:

  1. Open Canvas.
  2. Check the Company view to understand stack status, active agents, and any available metrics.
  3. Use the Roadmap or suggested next tasks when you want a guided next step.
  4. Go to the department that owns the job.
  5. Choose the agent with the right scope.
  6. Give it a concrete task.
  7. Review the result from the task detail page or the Canvas attention queue, then refine the setup if needed.

Next Steps