Eleven functions, one ranking
Departments are useful lenses, but they do not get separate priority systems. Casa names the problem that can kill the company at its current stage and puts the functions that resolve it in the lead.
The eleven
| Department | Owns |
|---|---|
| Strategy | Venture viability, business-model selection, pricing, stage gates |
| Brand | Naming, positioning, entity formation prep, brand system |
| Product | MVP scope, feature priority, roadmap, product and design specs |
| Engineering | Stack, deployment, observability, security baseline, incident response |
| Data | Event taxonomy, dashboards, attribution, north-star measurement |
| Growth | Experiments, channels, funnel and CRO, traction loops, lifecycle |
| Sales | Prospecting, pitch, pricing positions, deal management |
| Success | Onboarding, retention and winback, expansion, health scoring |
| Finance | Unit economics, runway, cap table, model, fundraising materials |
| Operations | Hiring and org design, process, vendor strategy |
| Legal | Compliance roadmap and the actions that must never run unattended |
Lead, support, or wait
The binding constraint decides posture. If activation is the constraint, Product and Growth lead, Data supports with instrumentation, and Sales waits, no matter how full its backlog looks. Readiness gates prevent out-of-order work across functions.
CASA 04DEPARTMENT BOARD STUDY11 FUNCTIONS / ONE RANKING
BINDING CONSTRAINTFirst repeatable acquisition pathLEAD / SUPPORT / IDLE
01StrategyLEAD
02BrandIDLE
03ProductLEAD
04EngineeringSUPPORT
05DataSUPPORT
06GrowthLEAD
07SalesIDLE
08SuccessSUPPORT
09FinanceIDLE
10LegalSUPPORT
11OperationsIDLE
COMPANY PRIORITYDEPARTMENT POSTURE FOLLOWS THE CONSTRAINT
Note: Approve-first by default
Every department starts at approve-first autonomy. You dial up automation per department as trust builds. See Governance and gates.