ArticlesComparison
C² vs Shape Up: from human teams to human + AI teams
Shape Up shaped a generation of product teams. C² rebuilds its best instincts for teams that include AI agents.
Shape Up, from Basecamp, is the clearest pre-AI thinking on how to scope and bet on work: fixed appetites, outcome focus, six-week cycles, and a firm rejection of sprint theatre. It's also the closest ancestor to C². If you already think in Shape Up terms, C² will feel familiar — and the differences are exactly the things AI changes. Here's the head-to-head from someone who built C² and ships with it daily.
What Shape Up got right
Shape Up's instincts hold up, and C² keeps all of them:
- Appetite over estimate. Decide how much a problem is worth, then fit the solution to the budget — not the other way round.
- Outcomes over output. Bet on shipped value, not story points.
- No sprint theatre. Drop the ceremonies that exist to make humans feel busy.
Where it diverges is that Shape Up was designed for humans directing humans — and the team has changed. None of what follows is a knock on Shape Up; it's what a method built in 2018 had no reason to include.
What AI changes
An AI-native method needs four things Shape Up has no equivalent for:
- A contextbase that compounds. Shape Up's pitches and cycles live in Basecamp, for humans, and go quiet once a cycle ends. C² keeps a version-controlled contextbase — briefs, patterns, gotchas, decisions — that the agent reads before it acts, and that accrues: every session commits what was learned, so the next one starts ahead. Documents inform a cycle; a contextbase is an asset that keeps paying.
- A router. C² has one file the agent reads first, that lazy-loads exactly the context a task needs. Shape Up has no machine-readable entry point.
- An execution contract. C²'s autonomous brief specifies exact files and acceptance criteria so an agent can run unattended. Shape Up trusts a human to figure out the approach.
- Session memory. C²'s session brief is written memory across the gap between sessions — a gap AI agents have and humans don't.
The throughline: Shape Up tells you what to bet on; C² gives the agents the memory and the contract to build it — and it holds the same shape from a solo founder on one product to a team running many apps across multiple locations.
Side by side
| Shape Up | C² | |
|---|---|---|
| Era | Human teams (pre-AI) | Human + AI teams |
| Scoping | Appetite / betting | Appetite-style, plus a brief cascade |
| Cadence | Six-week cycles | Continuous, session by session |
| Documentation | Basecamp (for humans) | Repo-native markdown (humans and agents) |
| Knowledge | Tribal, fades after a cycle | Contextbase in git — compounds, self-improving |
| Execution | Human figures out the approach | Brief specifies it; agent can run autonomously |
| Range | Product team in one place | Solo founder → multi-app, multi-location |
| Human role | Shaper | Pilot |
When to use which
- Shape Up is still excellent for the betting layer — deciding what's worth doing and how much appetite it gets. If your team is mostly humans, it remains a great fit.
- C² is for the execution layer when AI agents are doing the building. It assumes the codebase has a parallel contextbase the agent reads first, and it compounds that context as you go.
The cleanest setup, honestly, is both: keep Shape Up's appetite and betting to decide what to build, and run C² underneath to direct how the agents build it — and to make sure what they learn doing it sticks. Shape Up shapes the work; C² gives it a contextbase that compounds.
Read the C² method, or compare it to Agile and the other AI methodologies — including the head-to-head with BMAD.
FAQ
- Can you use Shape Up with AI agents?
- Yes — for the betting layer. Shape Up's appetite-based scoping still decides what's worth building and how much to spend on it. What it lacks is anything for AI execution — no contextbase, no router, no agent contract — so you pair it with an AI-native method like C² underneath.
- Is Shape Up still relevant in 2026?
- Yes, as a way to decide what to build. Its instincts — appetite over estimate, outcomes over output, no sprint theatre — hold up. For building with AI agents, layer an AI-native method like C² beneath it for execution.
- What does C² add that Shape Up doesn't have?
- Everything an AI agent needs to execute: a version-controlled contextbase it reads before acting and that compounds across sessions, a router as its entry point, an execution contract for autonomous work, and a session brief that carries memory across the gaps between sessions. Shape Up never needed these — it was built for humans directing humans.
Related
An honest comparison of the methodologies for building with AI agents — native rule files, BMAD, HumanLayer's ACE, Matt Pocock's workflow, Packmind, Shape Up, AWS AI-DLC, and C² — with a side-by-side table and guidance on which to choose.
An alternative to Agile for AI-native teamsAgile coordinated human teams at human speed. With AI agents in the loop, the constraint moves from execution to direction — and agile's ceremonies turn into drag. Here's the alternative, and what to keep.
C² vs BMAD: two ways to build with AI agentsBMAD and C² both add discipline to building software with AI agents — but BMAD orchestrates specialised personas through a heavier SDLC, while C² is a lighter, agent-agnostic method centred on a version-controlled contextbase that compounds. A head-to-head.