machine viewenglish onlyraw: /index.md
Bleu — product engineering for software work that's hard to delegate
[Cases](/cases) · [How we work](/how-we-work) · [Assessment](/offerings/assessment) · [Sprint](/offerings/sprint) · [Squad](/offerings/squad) · [Contact](mailto:jose@bleu.builders)
Built to own the problem, not just the ticket
For teams with engineering work that's hard to delegate. 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.
You don't need a perfect spec to start
Not staff augmentation
Production-ready delivery, documentation, and handoff
Contact: [jose@bleu.builders](mailto:jose@bleu.builders) · book a 15-min call with José Ribeiro, CEO: [cal.com/jose-ribeiro/15min](https://cal.com/jose-ribeiro/15min) Machine-readable twin of this site: [/index.md](/index.md) · agent onboarding: [/agents.md](/agents.md)
Built to own the problem,
not just the ticket.
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 teams with engineering work that's hard to delegate
How we engage
Different entry points. Same level of ownership.
Assessment (1-3 weeks) — diagnosis + recommendation. A technical and product read on what's going on, what is causing drag, and what the cleanest next step is.
Sprint (2-8 weeks) — one real problem taken off your plate. A bounded engagement for a problem that needs end-to-end ownership: integrations, migrations, legacy rebuilds, production features, internal tooling.
Squad (3+ months) — dedicated team owning a product area. A stable team taking responsibility for a product area that matters.
Paths: unclear problem → Assessment · clear bounded problem → Sprint · ongoing critical area → Squad
Sprint #0 — one project per month
Every month, we select one company to start working with before signing anything. One week of real work — both sides learn whether it makes sense to continue. Apply: [cal.com/jose-ribeiro/15min](https://cal.com/jose-ribeiro/15min)
Different entry points.
Same level of ownership.
Proof in Production
Months with CoW Protocol: 30+
Initiatives shipped: 16+
Years with Perk: 3+
Uptime on the M&M's launch: 99.984%
See all [Cases](#cases)
Proof in Production
30+
Months with CoW Protocol
16
Initiatives shipped
99.984%
Uptime on the M&M's launch
3+
Years with Perk
SELECTED CASES
CoW Protocol
CONTEXT
Developer tooling, integrations, and product work kept piling up outside the core team's focus.
WHAT BLEU OWNED
A Python SDK built from scratch (cow-py), the TypeScript SDK re-architected around Viem — bundle down 32% — the CoW AMM Deployer Safe App shipped in 2 weeks, and the Dune governance dashboard.
WHAT CHANGED
16 initiatives across protocol tooling, frontend infrastructure, developer experience, and governance. 30+ months and counting — without slowing the core team or adding management overhead.
Selected cases
CoW Protocol
Context: developer tooling, integrations, and product work kept piling up outside the core team's focus.
What Bleu owned: a Python SDK built from scratch (cow-py), the TypeScript SDK re-architected around Viem (bundle down 32%), the CoW AMM Deployer Safe App shipped in 2 weeks, and the Dune governance dashboard.
What changed: 16 initiatives across protocol tooling, frontend infrastructure, developer experience, and governance. 30+ months and counting — without slowing the core team or adding management overhead.
Other cases
Perk: Bleu strengthened the platform while Perk kept shipping — 3+ years, 12k+ commits, 16 apps in production, and the M&M's launch at 99.984% uptime.
Silo Finance: Bleu owns Silo's data layer end to end — V2 subgraph, multichain APIs across 4+ chains, infrastructure costs cut 80% — while the core team stays on the protocol.
Grants: 4 Optimism grants (all milestones approved) · 9 Balancer grants (delivered on scope and on time).
Current cases
Tegra (agritech, Squad, Feb 2026 → present): from a WhatsApp sales operation to a working carcass marketplace, validated in the field before a single line of production code. Pilot live; 26 slaughterhouses in pipeline; marketplace validation decoupled from AI camera training (0 weeks waiting).
Corbellini (geology/environmental consultancy, Sprint Zero → platform, ongoing): the ask was automation, the real problem was structural — a four-decade operation running on people, not systems. New platform monitors the official gazette and the regulator daily; the team learns about deadlines before publication. Legacy migration underway.
Pike (DeFi lending protocol, product team, 2025): audited contracts, three launch attempts in eight years. Bleu absorbed frontend, backend, infra, and analytics as one coordinated squad; the founder called the result the best consumer-facing product they'd ever shipped.
What clients say
> "Easy to work with. Take ownership, which is not easy. Can be trusted to deliver, also not easy."
Siros — Silo Finance
Ongoing infrastructure partnership
Siros
Silo Finance
ONGOING INFRASTRUCTURE PARTNERSHIP
WHAT CLIENTS SAY
“Easy to work with. Take ownership, which is not easy. Can be trusted to deliver, also not easy.”
What owning the problem looks like
The request is often only part of the problem.
The Bleu method:
What most vendors do: build the SDK they were asked for, ship the ticket, mark the work as done.
Find the real blocker: the SDK wasn't it. The API exposed too much internal complexity, the docs assumed context developers didn't have, and the onboarding path didn't exist.
Own the fix end to end: a reworked API surface, the missing docs, and tooling around the onboarding path.
Result: integrations started moving because the whole handoff became usable — not just the SDK.
What owning the
problem looks like
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.
How working with Bleu works
The point is to reduce load, not create another team you have to manage.
Engagement steps:
01 — You don't need a perfect spec to start: Bleu resolves what it can without turning every unknown into a dependency.
02 — Updates when they matter, not constant overhead: you get visibility into progress and decisions, not a daily standup to run.
03 — The work ends in production-ready shape: code, documentation, and handoff — maintainable after us.
Stop pulling senior people into neglected work
Stop managing a vendor through every unknown
Stop guessing whether the rebuild is even the right move
Get to production faster than a 6-month hiring cycle — and reverse if it's not the right fit
How working
with Bleu works
The point is to reduce load, not create another team you have to manage.
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.
When Bleu fits
Who Bleu is for — and who it isn't.
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
Hiring would take 6 months and you need progress in weeks
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
When Bleu fits
Bleu is a good fit when
Bleu is not the right fit when
Common questions
Is this staff augmentation?
No. We take ownership of the problem end to end — diagnosis, plan, delivery, handoff. We don't sit inside your Jira backlog waiting for tickets.
What's Sprint #0?
One project per month, one week of real work, on us. A shared codebase and a concrete plan — not a slide deck. You see how we think before you commit to a contract.
How fast can we start?
Assessment kicks off in 1-2 weeks. A Sprint typically starts 2-3 weeks after alignment. Sprint #0 can move faster when the scope is clear.
What stack do you work in?
Ruby on Rails, Next.js and React, GraphQL, TypeScript, Python for AI pipelines. On Web3: EVM protocols, Solidity integration, subgraphs, multichain data infrastructure.
Who owns the code?
You do. All code, documentation, and infrastructure is yours. Handoff includes everything a new team needs to continue without us.
How does pricing work?
Fixed-scope Sprints for bounded problems. Dedicated Squads for ongoing areas, billed monthly. No hourly rates. Ranges shared after the first call.
Do you work with companies outside of Brazil?
Yes. Most of our partnerships are US- and EU-based. CoW Protocol (30+ months), Silo Finance, Perk, Balancer — all remote, English-speaking engagements.
What happens if the engagement isn't a fit?
We say so. Assessment exists to answer that question honestly. If we're not the right team, we tell you — and often point you to who is.
Common questions
No. We take ownership of the problem end to end — diagnosis, plan, delivery, handoff. We don't sit inside your Jira backlog waiting for tickets.
One project per month, one week of real work, on us. A shared codebase and a concrete plan — not a slide deck. You see how we think before you commit to a contract.
Assessment kicks off in 1-2 weeks. A Sprint typically starts 2-3 weeks after alignment. Sprint #0 can move faster when the scope is clear.
Ruby on Rails, Next.js and React, GraphQL, TypeScript, Python for AI pipelines. On Web3: EVM protocols, Solidity integration, subgraphs, multichain data infrastructure.
You do. All code, documentation, and infrastructure is yours. Handoff includes everything a new team needs to continue without us.
Fixed-scope Sprints for bounded problems. Dedicated Squads for ongoing areas, billed monthly. No hourly rates. Ranges shared after the first call.
Yes. Most of our partnerships are US- and EU-based. CoW Protocol (30+ months), Silo Finance, Perk, Balancer — all remote, English-speaking engagements.
We say so. Assessment exists to answer that question honestly. If we're not the right team, we tell you — and often point you to who is.
Have a problem that's hard to delegate?
Bring us the context. We'll tell you whether Bleu is the right fit, and what the cleanest next step is.
If the answer is no, we'll say that clearly.
Contact: [jose@bleu.builders](mailto:jose@bleu.builders) (response within 24 business hours) · book a 15-min call: [cal.com/jose-ribeiro/15min](https://cal.com/jose-ribeiro/15min)
Have a problem that's
hard to delegate?
Bring us the context. We'll tell you whether Bleu is the right fit, and what the cleanest next step is.
IF THE ANSWER IS NO, WE'LL SAY THAT CLEARLY.