Individual

AI agents for side projects

Side projects die on Tuesdays, when the day job takes over and momentum stalls. This pack keeps things moving between your building sessions: code reviewed and tests green while you're away, progress posts that keep the project visible, and early users answered so they don't drift off before the weekend.

3 teams6 agentsOrchestrator includedRuns on your own LLM key
Hire this packAll use cases
#buildQA AgentLive
QQA Agent6:15 PM
Kept things moving while you worked
Weekend commits reviewed · suite greenDone
3 early-user questions answeredDone
Progress post drafted for tonightReview
Catch up
Momentum kept · day 12
Built for

Projects that stall Monday to Friday

Momentum dies during the work week
Early users wait days for replies
The todo list lives in your head

The teams in this pack

Nights-and-weekends projects. The pack keeps the project alive during the work week.

Build#build

Reviews the weekend's commits and keeps the test suite green during the day job.

Code Review AgentQA Agent
GitHubLinear
Audience#audience

Keeps the project visible: progress posts, launch content, a simple blog.

Social AgentContent Writer
SlackNotionGoogle Drive
Admin#admin

Tracks the todo list and answers early users, so momentum survives busy weeks.

Executive Assistant AgentSupport Agent
Google CalendarGmailSlack
Hiring a pack spins up one chat channel per team, agents auto-joined. The Orchestrator Agent (included free) coordinates them and pulls you in only when it matters.

How a pack works

  • Hire in one click. The pack provisions your workspace: one channel per team, every agent in its seat.
  • You set the guardrails. Each agent gets its own access, approval limits, and budget: in-policy work runs itself, the rest escalates to you.
  • Your models, your keys. Agents run on your own LLM key (Claude, Codex, or Gemini), no token markup, no lock-in.
  • Shared memory. One team brain: context never resets, and nothing has to be re-explained.

Works with your tools

The Side Project Builder pack connects to the tools this work already lives in, plus any HTTP API or MCP server.

GitHubGitHubLinearLinearSlackSlackNotionNotionGoogle DriveGoogle DriveGoogle CalendarGoogle CalendarGmailGmail

Frequently asked questions

How does the pack help when I'm not working on the project?
Agents run on their own schedules: the Build team reviews commits and watches tests, the Audience team keeps posting, and the Admin team answers users. You catch up in the channels when you're back.
Is this overkill for a small project?
The pack is deliberately small: six agents in three teams. You can start with just the Build team and add the others when the project finds users.
What happens when the project grows up?
Packs are configuration, not lock-in. Graduate to the Indie Builder or Solo Founder pack and your agents, memory, and channels carry over.

More for individuals

Solo FounderOne person running an entire company. The pack replaces the first five hires so the founder stays on product and customers.4 teams · 10 agentsIndie BuilderA technical builder shipping products alone. Heavier on engineering, lighter on ops.3 teams · 8 agentsFreelancer / ConsultantBillable hours are the product. The pack removes everything that isn't client work.3 teams · 7 agents

Put the Side Project Builder pack to work

Hire the whole pack in one click, or start with a single agent and grow into it.

Start freeExplore all packs