# how-we-work

## How working with Bleu works

You bring the context. We do the work required to understand the real problem, take ownership, and get it into good shape.

- **You bring the context**: You do not need a perfect spec. We need enough context to understand what matters and where the drag is showing up.
- **We get close to the work**: We review the relevant systems, talk to the right people, and figure out what the problem depends on.
- **We define the path**: We tell you what we think the real problem is, what we would do about it, and what kind of engagement fits best.
- **We take ownership**: Once the work starts, our job is to reduce load on your side, not create more of it.
- **We leave it in good shape**: The outcome has to work in production and be maintainable after us.

## Ways to work with Bleu

Each engagement has a different entry point and shape. The path depends on where you are.

- **Assessment**: A technical review of an existing system. Produces a clear diagnosis: what the current state is, where the risk is, what needs to change, and in what order.
- **Sprint**: A focused delivery on a specific, well-defined problem. A stuck integration, a feature under pressure, a component that needs to be rebuilt.
- **Squad**: An embedded product team — PM, design, engineering — working inside your product on an ongoing basis. For when the work is continuous and context matters.