# Home

## Built to own the problem,

When critical work is stuck and your team can't afford to keep managing it, Bleu steps in to understand the real problem and own it end to end.

For software companies and DeFi teams with work that's hard to delegate

- Not staff augmentation
- You don't need a perfect spec to start
- Production-ready delivery, documentation, and handoff

- **CoW Protocol**: high-context product and tooling work
- **Perk**: ongoing product development partner
- **Silo Finance**: data infra owned without pulling core team off protocol

## Social Proof

> "You don't wait for a super complete specification. You build the plan on your own and do research."
> — Sasha, CoW Protocol

> "Easy to work with. Take ownership, which is not easy. Can be trusted to deliver, also not easy."
> — Siros, Silo Finance

> "What you wished your last team was."
> — Taylor, Perk

## When teams bring in Bleu

- **Something important has been stuck for too long.** — An integration, migration, legacy surface, or product area that keeps surviving the roadmap.
- **The core team could do it, but not without slowing something more visible.** — The work matters. Pulling senior people into it means something else stops.
- **The work needs judgment, not just execution.** — The problem is still taking shape. Someone has to understand it and keep moving without constant direction.
- **You want a clear recommendation before committing to the wrong fix.** — Build, fix, re-scope, or stop. You want a diagnosis, not a proposal.

## What owning the problem looks like

The request is often only part of the problem.

- **What most vendors do**: Build the SDK they were asked for. Ship the ticket. Mark the work as done.
- **What Bleu finds first**: The SDK wasn't the real blocker. The API exposed too much internal complexity, the docs assumed context outside developers didn't have, and the onboarding path didn't exist.
- **What Bleu actually ships**: A reworked API surface, the missing docs, and tooling around the onboarding path. Integrations started moving because the whole handoff became usable — not just the SDK.

## Proof in production

- **30+** months with CoW Protocol
- **16+** initiatives shipped
- **3+** years with Perk
- **3** active partnerships over 1 year

- **CoW Protocol**: SDKs, tooling, integrations, governance and user-facing product work across the ecosystem.
  - Result: CoW offloaded high-context ecosystem work without slowing the core team or adding management overhead.
  - Duration: 30+ months (ongoing)
- **Perk**: Product, design, engineering, infra, and platform evolution across multiple launches.
  - Result: Perk kept shipping launches while strengthening the platform underneath — without managing another vendor.
  - Duration: 3+ years (ongoing)
- **Silo Finance**: Subgraphs, multichain APIs, data validation, and the product layer built on top of them.
  - Result: Silo gained production-grade data infrastructure without diverting the core team from protocol work.
  - Duration: 1+ year (ongoing)

## How working with Bleu works

The point is to reduce load, not create another team you have to manage.

- Stop pulling senior people into neglected work
- Stop managing a vendor through every unknown
- Stop guessing whether the rebuild is even the right move

- **You don't need a perfect spec to start**: Bleu resolves what it can without turning every unknown into a dependency.
- **Updates when they matter, not constant overhead**: You get visibility into progress and decisions, not a daily standup to run.
- **The work ends in production-ready shape**: Code, documentation, and handoff. Maintainable after us.

- Assessment
- Sprint
- Squad

- Unclear problem → Assessment
- Clear bounded problem → Sprint
- Ongoing critical area → Squad

## When Bleu fits

### Bleu is a good fit when

- A real problem is stuck, fragile, or outside core team bandwidth
- You need a team that can work from partial context and fill in the gaps
- The work needs judgment, not just hands
- You want a clean handoff when the job is done

### Bleu is not the right fit when

- You want staff augmentation against a fixed spec
- You need to approve every step before the team can move
- There is no clear owner on the client side
- The cheapest delivery option matters more than the quality of the outcome

## How we engage

Different entry points. Same level of ownership.

### Items

#### Assessment

A technical and product read on what's going on, what is causing drag, and what the cleanest next step is.

#### Sprint

A bounded engagement for a problem that needs end-to-end ownership: integrations, migrations, legacy rebuilds, production features, internal tooling.

#### Squad

A stable team taking responsibility for a product area that matters.

## Sprint #0

We select one project per month to start for real. One week of work, on us, before any contract.

One project per month