{"meta":{"title":"Squad | A team owning a product area | Bleu","description":"A stable team taking responsibility for a product or infrastructure area over time."},"hero":{"headline":"A team owning a critical part of your product","subhead":"Best fit when the work is ongoing, tightly connected to the system, and too important to keep staffing ad hoc."},"problem":{"title":"When the work is not really a project","description":"Some problems are too large, too connected, or too persistent to treat as a short engagement. They need a team that can stay close to the system, make decisions with context, and keep improving the area over time."},"solution":{"title":"Bleu Squad","description":"A stable team with ownership of a product or infrastructure area your users depend on.","benefits":["Not staff augmentation","Stable ownership over time","Continuous product and engineering progress without heavy management overhead"],"investment":"Investment on demand","minimum":"Recommended minimum: 3 months"},"whatSquadDoes":{"title":"What a Squad typically owns","items":["A product surface or workflow your users depend on","A critical internal system or data layer","The backlog around a neglected but high-value area","The reliability, performance, and maintainability of that area over time","Documentation and clean knowledge transfer as the work evolves"]},"cta":{"title":"Need a team to own a product area?","button":"Bring us the problem"}}