Ryan Singer's *Shape Up* (2019) documented how Basecamp builds product. It introduced concepts that influenced the entire indie software world: 6-week cycles, appetite, shaping, the bet, the cool-down, hill charts. *Shape Up* is the most influential product methodology of the post-Agile era.
Singer's core insights are right:
- Don't estimate work; bound it ("this is worth 6 weeks, no more")
- Shape work before betting on it (define problem, solution, rabbit holes upfront)
- Cycles, not sprints. Cool-down, not perpetual urgency.
- Track progress on a hill chart (uphill = problem-solving, downhill = execution)
The methodology assumes a team. A team of designers and engineers cycling together. A leadership group betting on cycles. Cool-down periods for the team to choose what to work on. The whole vocabulary is built for a small product company with multiple people.
But the indie founder, the solo builder, the consultant working on multiple projects — they read *Shape Up* and recognize the principles are right, but the implementation needs translation. There's no "team" to cycle. There's no "betting table." Cool-down becomes "the week I had no specific deadline."
The Shape Up community has done some of this translation. There are blog posts about "solo Shape Up." There's a small ecosystem of attempts. But the rituals that give Shape Up its discipline (the bet, the kickoff, the hill chart review) are inherently social. A solo person trying to run them on themselves often loses the discipline.
What if the rituals could be enforced by the system?
AskRobots' angle on Shape Up isn't to argue with the methodology. It's to operationalize the rituals for solo and small-team builders:
- **Cycle tracking.** Six weeks is the unit. AskRobots tracks where you are in the current cycle, what's committed, what's deferred to cool-down.
- **Appetite enforcement.** When you start work, you set an appetite (1 week, 2 weeks, 6 weeks). When you blow through it, AI flags it. The "kill the project" decision becomes deliberate, not drift.
- **Shaping templates.** AskRobots has templates for the shaping document — problem, appetite, solution, rabbit holes, no-gos. Fill it out before you start the cycle.
- **Hill chart for solo work.** A simple uphill/downhill view that shows where you actually are. AI infers position from your activity (lots of new files = uphill problem-solving; lots of edits = downhill execution).
- **Cool-down forcing.** AI insists on cool-down weeks. No new cycles can start during them. The discipline is built into the system, not your willpower.
The discipline of Shape Up — bound work, shape before betting, cycle with cool-down — stays exactly the same. The team rituals get translated into solo rituals that the system enforces.
There's also a multi-cycle view that pure Shape Up doesn't address. Most builders are running 2-3 things in parallel: a main project on a 6-week cycle, a side project on a 2-week appetite, a maintenance backlog. AskRobots can hold all of these and apply Shape Up's discipline at each level.
The biggest Shape Up failure mode for solo builders isn't running over appetite — it's never declaring an appetite at all. Work just happens. There's no shape, no bet, no end. AI can prompt the shaping at the start ("what's your appetite for this?"), enforce it during the cycle ("you're at 80% of appetite, half the work is left"), and force the cool-down at the end ("six weeks done — take a week before starting the next cycle").
Singer wrote Shape Up for a team. The methodology is bigger than the team — it's a way of thinking about work that anyone can use, if the rituals are operational.
If you've read *Shape Up*, agreed with all of it, and never figured out how to apply it as a solo builder — this is what's different now.