What is a pack?

A pack is your starter team in a box. When you create a new workspace, picking a pack installs the agents, the projects, the folders, and a few sample artifacts so day one isn't a blank canvas.

This article covers what's inside a pack, how packs differ from page templates, and how the catalog is organized. If you're ready to pick one, see Install your first pack.

The blank-canvas problem

An empty workspace is hard to start from — nothing to react to, nothing to open, no folders to put things in. A pack solves that at workspace creation. The workspace fills with a working starter set so your first hour is about understanding what's there, not building it.

What's inside a pack

A pack drops four things into your workspace. Using Daily Office — the pack everyone gets if you say "Just exploring" at signup — as the example:

• A team of agents. Five to eight per team, with Job Titles and instructions tuned to the work. Daily Office gives you Alex the Morning Briefer plus an Inbox Assistant, Calendar Optimizer, Meeting Prepper, Notes Taker, and Weekly Reviewer.
• One or more projects with tasks ready to go. The tasks come with the right agent already assigned and a suggested cadence on the task card — "Daily," "Weekly," "Monthly." You activate the AI Schedule on the task itself when you're ready.
• Knowledge-base folders. Structured around the work the team produces — "Notes," "Briefs," "Reports," and so on.
• A handful of sample artifacts. Real-looking demo pages — a Morning Brief, a Weekly Status — labelled [Demo] so you can see what good output looks like.

Bigger packs install two or three teams — Workflow Automation and SaaS Growth, for example, put 10–20 agents into the workspace at once.

Demo content vs your content

The [Demo] pages and tasks a pack ships are samples, not your real work. Every demo has a "delete me when you're done" callout at the top. Read them, get the model of what the agents can do, then delete them. Your real outputs land in the same folders as your agents run.

Nothing the pack installs is read-only. Rename agents, edit instructions, restructure projects, rename folders, or delete anything entirely — the pack is a starting point, not a constraint.

Packs vs page templates

Easy to confuse, easy to keep straight:

• A page template is one document — useful when you want a single page (a meeting agenda, a one-pager format) with a head start.
• A pack is the whole scaffolding around the work — agents to do it, projects to track it, folders to file it. Different order of magnitude.

One document? Pick a page template. A hired team? Install a pack.

How the catalog is organized

The pack list during signup wasn't random. The first signup question — "What brings you here?" — maps directly to a pack category:

• My day-to-day work → packs for individual contributors and team leads (Marketing, Sales Pipeline, Product & Engineering, and others).
• Running a team or business → packs for founders and owners (Solo Founder, Agency, SaaS Growth, and others).
• Personal productivity → packs for life and learning (Student, Life OS).
• Just exploring → Daily Office, the safe default.

If you know your segment, the pack is downstream. See The pack catalog for the full list.

Tips and gotchas

• Everything a pack installs is yours — editable, deletable, renamable. Don't treat the demo content as canonical.
• Each workspace runs one pack. To use a different pack, create a new workspace from the workspace switcher and pick it at the pack-picker step — your existing workspace stays untouched.
• The suggested cadence on a task card is a hint, not a live schedule. The task starts recurring when you set its AI Schedule.

Related

• Install your first pack
• The pack catalog
• Customizing a pack