Shaping the company
How the canonical software-company package grows, shrinks, and reshapes its optional team-based structure over time.
When to reshape
A company using this package may revise its selected shape as its work changes. Common moments to reshape include:
- A class of work is becoming permanent — You keep getting the same kind of work item across different teams without a clear owner. That’s a signal you’re missing a team. See Working with teams.
- The company needs a new capability — A new tool, a new integration, a new data source. Component packages and providers extend what the exocorp can do without making it native. See Components & providers.
- A team isn’t earning its place — A team that’s consistently degraded, repeatedly failing, or producing weak work. Either its mandate is wrong or it should be retired.
- A bet you made didn’t pan out — The work tied to it should wind down. Promises need closure. Memory needs to register what was tried and why it stopped.
Who proposes changes
In this package, reshaping can come from either direction. Either you propose a change in the CEO chat (“I want a customer support team”), or the CEO surfaces a proposed change to you (“the marketing team should split into retention and acquisition”). Either way, structural changes need your sign-off.
What you approve is real: mandates that don’t apply to existing workflows; teams that don’t exist; components the operating graph does not select. The CEO won’t reshape the company through a memo. Once you sign off, the actual workflows, agents, and authority surfaces change.