A live cohort for leads who write their team’s AI playbook.
Software Factory Buildcamp is a live cohort for product and engineering leads. Each lead writes the rules, skills and checks for their own team, in their own repo, with feedback from the founder and from leads at other companies.
Written feedback each week from the founder, a former Head of Software Engineering.
An example cohort. Each colour is a different company.
Writes the rules for what agents may touch in their codebase, and who signs off on the rest.
playbook/rules/ agents.md playbook/rules/ agents.md playbook/rules/ agents.md
Writes how a ticket becomes a spec an agent can work from, and what done means for the team.
playbook/skills/ spec.md playbook/skills/ spec.md playbook/skills/ spec.md
Writes the checks every pull request passes before a person reads it.
playbook/checks/ gates.md playbook/checks/ gates.md playbook/checks/ gates.md
Writes the context agents read first: the architecture, the decisions, the parts nobody should touch.
playbook/context/ architecture.md playbook/context/ architecture.md playbook/context/ architecture.md
Every seat leaves with a playbook folder in their own repo, reviewed by the founder and by leads from the other companies.
Why do leads stall after the tutorials?
The tutorials teach one engineer to use an agent. A lead has to decide how a whole team works with one.
Tutorials end at your laptop. They show what one person can do in a clean repo. Nobody shows you how to write it down so ten people do it the same way.
Nobody checks your rules. Inside one company everyone makes the same assumptions. A lead from another company asks the question your team never thought to.
The playbook never gets written. There is always a release this week. Without a session that ends in homework, the rules stay in someone’s head.
The cohort gives each lead a weekly session, homework in their own repo and readers from other companies, so the playbook gets written and checked.
What each lead writes
The cohort works in each lead’s own repo. By the last session the playbook folder is theirs, reviewed by people who have no reason to be polite.
Agents know what they may change on their own.
playbook/rules/says what needs a reviewer and what agents never touch.Your team ships the same way each time.
playbook/skills/holds how a ticket becomes a spec, how a pull request is reviewed and how a release ships.Review starts at intent.
playbook/checks/lists what every change passes before a person reads it.Leads from other companies check your rules.
Each week you get written feedback from the founder and comments from leads who are not your colleagues.
You write the rules your team works by,
and leads from other companies check them every week.
How the cohort runs
Before, during and after, so the time goes into your repo.
1Before
Book a fit call about your team and your repo, so the homework fits the work you have.
2During
Join a live session each week, then do the homework in your own repo. You get written feedback from the founder and comments from the other leads.
3After
Keep the playbook folder in your repo with your name on the rules. Teams that want help spreading it can move to a rollout.
“You work with the person who does the work. No handoff, no juniors, no account manager.”
Paramanantham HarrisonFounder, KaaS.team
- Former Head of Software Engineering
- 14 years building production software
- Architect of the pivot behind an €11.6M Series A
Questions about the Buildcamp
What is the Software Factory Buildcamp?
A live cohort for product and engineering leads. Each lead writes the rules, skills and checks for their own team, in their own repo, with feedback from the founder and from leads at other companies.
Who is the Buildcamp for?
Heads of product or engineering who will own the rules, team leads whose squads already use AI every day, and staff engineers who hold the context everyone else asks about.
Who is this not for?
Leads who want an advanced tactics course. If you are after new prompt tricks, a tutorial is faster. It is also the wrong fit if you want to watch the sessions without writing anything, since every session ends in homework in your repo, or if you have no team to bring the playbook back to.
How do I enrol?
Enrolment runs here on kaas.team. Book a fit call, tell us who would join, and we send the dates and the joining details.
When does the next cohort start?
Dates are set per cohort. Book a fit call, tell us who would join, and we send the next dates and the joining details.
Can several leads from one company join?
Yes. Two or three leads from one company works well: they write one playbook between them and bring it back together.
What if a whole department needs it?
When every lead needs the same setup at once, a Claude Code rollout installs it for them on your code.
How is it different from Claude Code training?
Training teaches a whole team on your repo. The Buildcamp is for the lead who will keep it running, and it puts them next to leads solving the same problem somewhere else.
How much time does it take each week?
A live session and the homework that follows it, done in your own repo. The cohort is small enough that every lead gets written feedback each week.
What is settled before you join
Fit check first. If the cohort is wrong for you, we'll say so on the call.
You get the dates and the joining details before you commit.
The playbook folder is in your repo and stays there after the cohort ends.
Bring us the bottleneck.
A 30 minute call with the founder about where work is stuck.
- Spec
- Build
- Review
- Release
- Where work is stuck
- Spec, build, review or release: wherever changes wait longest.
- What exists today
- The AI tools your teams use and the rules around them, if any.
- What the next quarter needs
- The launch or deadline the work has to hit.
- 1
Call
We find where the work waits and whether we can help.
- 2
Fixed scope
You get a written scope and a fixed quote before anything starts.
- 3
Kickoff
Work starts with your product and engineering leads.
If we're not the right fit, we'll say so.
Pick a time
Open the calendar and choose any free slot. You get an invite with a video link.