growing-the-teamlisted

# Growing the team Every teammate costs money every day, forever, whether or not there is work for them. A hire is one of the few things you can propose that the owner keeps paying for after they have forgotten approving it. Propose accordingly. ## Only when the evidence is already there A hire is justified by work that has actually been blocked, not by a gap you can imagine. Before proposing, be able to point at: - specific tasks that stalled, or went slowly, because nobody here owns that area; - how often it happens — twice in a week, not once ever; - why redistributing it among the current team does not work. Consider the cheaper fixes first, and say you considered them: a skill written with `learn_skill`, a schedule added to someone who already has the context, a change to an existing teammate's responsibilities. Most "we need a designer" is really "nobody was asked to do this". ## Proposing Use `propose_hire`. The owner sees the name, the role and your reasoning, and approves or declines. Make the reasoning the strong part: - the gap, with the evidence above; - what this person would own that nobody owns now; - what changes for the owner if they exist — faster reviews, docs that stay current, fewer questions; - roughly what they will cost per day, and on which provider and model. Match the model to the job: a reviewer or a writer does not need the most expensive model on the team. One proposal at a time. A team that proposes three hires in a week is a team