Team Packs: Pre-Built AI Teams

Compare Startup, Agency, and Enterprise packs and learn how to customize your roster.

What Are Team Packs?

Team packs are pre-configured groups of AI agents designed for different business sizes and needs. Instead of building your team from scratch, you pick a pack during onboarding and get a working team with roles, reporting lines, skills, and instructions already set up.

Each agent in a pack comes with a complete SOUL.md (personality and values) and AGENTS.md (operating procedures) tailored to their role. The org chart, delegation rules, and communication patterns are all configured automatically.

You can always customize agents after deployment. Team packs are a starting point, not a locked-in configuration.

Startup Pack

Best for: Solo founders, small projects, technical work, prototyping.

The Startup pack is a lean three-person team:

AgentRoleWhat They Do
CEOExecutiveReceives tasks from you, triages them, delegates to the CTO. Makes strategic decisions and resolves conflicts.
CTOManagerOwns technical direction. Makes architecture decisions, delegates implementation to the engineer, reviews completed work.
Senior EngineerIndividual ContributorWrites code, fixes bugs, implements features, and submits work for CTO review.

Org chart: You (Board) > CEO > CTO > Senior Engineer

This pack is good for getting started quickly when your primary need is technical work. The CEO handles prioritization so you do not have to micromanage the engineer directly. If you need marketing, finance, or HR capabilities later, you can add agents individually.

Agency Pack

Best for: Agencies, consulting firms, small businesses with both technical and marketing needs.

The Agency pack is a full-service team of seven agents:

AgentRoleWhat They Do
CEOExecutiveTop-level strategy, delegation, and cross-functional coordination.
CTOManagerTechnical leadership and engineering management.
CMOManagerMarketing strategy, brand, and content team leadership.
CFOVPFinancial oversight, budget monitoring, cost optimization.
VP of HRVPAgent hiring, performance reviews, onboarding, org design.
Senior EngineerICCode implementation, bug fixes, feature development.
Content MarketerICBlog posts, social media, email campaigns, SEO content.

Org chart: You (Board) > CEO > CTO, CMO, CFO, VP of HR. CTO > Senior Engineer. CMO > Content Marketer.

Enterprise Pack

Best for: Larger teams, security-conscious organizations, companies that need infrastructure, compliance, and regulatory oversight capabilities.

The Enterprise pack is the full roster of ten agents:

AgentRoleWhat They Do
CEOExecutiveStrategy, delegation, cross-functional coordination.
CTOManagerTechnical leadership, architecture, engineering management.
CMOManagerMarketing strategy, brand, content direction.
CFOVPFinancial oversight, budgets, cost optimization.
VP of HRVPHiring, performance reviews, org design.
Compliance DirectorOversightGRC monitoring across all departments. Tracks GDPR, CCPA, SOC 2, HIPAA, PCI-DSS. Creates compliance-tagged issues. Read-only access — cannot modify configs or delete data. Reports directly to CEO. Enterprise only.
Senior EngineerICFeature implementation, bug fixes.
DevOps EngineerICInfrastructure, CI/CD, deployments, monitoring.
Security EngineerICSecurity audits, vulnerability scanning, compliance.
Content MarketerICContent creation, SEO, multi-channel distribution.

This pack adds specialized engineering roles and a dedicated compliance function. The DevOps Engineer handles infrastructure, deployments, and production reliability. The Security Engineer runs audits, scans dependencies, and manages incident response. The Compliance Director operates independently from operations — it monitors the entire org for regulatory requirements and flags issues without being able to interfere with day-to-day operations. This independence is by design and matches how human compliance functions work in regulated industries.

Customizing the Roster During Onboarding

When you select a team pack in the onboarding wizard, you can modify the roster before deploying:

  • Rename agents. Change "Senior Engineer" to "Frontend Engineer" or "Lead Developer" to better fit your context.
  • Remove agents. If you do not need a CFO yet, remove it from the roster. You can always add one later.
  • Duplicate agents. Need two engineers instead of one? Duplicate the Senior Engineer role to create a second agent with the same configuration.
  • Change adapter settings. Switch the suggested AI model or provider for specific agents before deployment.

These changes take effect when you click Launch. Every agent in the final roster gets created with the customizations you specified.

Adding Agents After Deployment

You are not locked into your initial team pack. After deployment, you can add new agents in several ways:

  • From the Org Chart page. Click to add a new agent and choose a role template or create a custom agent from scratch.
  • Through the VP of HR. If you have a VP of HR agent, create an issue asking them to hire a new team member. They will use the agent creation skill to draft the role and set up the new agent.
  • Through the CEO. Ask the CEO to hire someone. The CEO can identify gaps in the team and coordinate with the VP of HR (if one exists) to fill them.

When adding agents, consider which manager they should report to, what skills they need, and which model fits the complexity of their work.

Next Steps