--- # Bleu — product engineering for software work that's hard to delegate [Cases](https://bleu.builders/cases) · [How we work](https://bleu.builders/how-we-work) · [Assessment](https://bleu.builders/offerings/assessment) · [Sprint](https://bleu.builders/offerings/sprint) · [Squad](https://bleu.builders/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](https://bleu.builders/index.md) · agent onboarding: [/agents.md](https://bleu.builders/agents.md) --- ## 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) --- ## 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](https://bleu.builders/#cases) --- ## 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. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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 --- ## 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. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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 Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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 Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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) --- ## Case study — CoW Protocol CoW offloaded high-context ecosystem work — SDKs, tooling, governance, user-facing product — so the core team stayed focused on the protocol. 30+ Months of partnership · 16 Initiatives shipped · 32% TS SDK bundle size cut · 2 Weeks to ship the AMM Deployer CoW Protocol is a core piece of DeFi infrastructure, providing MEV protection, programmable orders, and AMMs used by a growing ecosystem of developers, integrators, users, and DAO participants. As the protocol matured, the main challenge shifted from correctness to accessibility and adoption. Powerful infrastructure existed, but using it — or building on top of it — required deep protocol knowledge and specific technical choices. Shipped: - cow-py — Python SDK: Built from scratch with full feature parity with the JS SDK - TypeScript SDK re-architecture: Rebuilt around Viem with adapters for Ethers v5, Ethers v6, Viem, and Wagmi - CoW AMM Deployer Safe App: Deploy and manage AMMs without touching contracts — shipped in 2 weeks - Safe Watch Tower: Auto-submits EIP-1271 signed orders once the signing threshold is reached - Dune governance dashboard: Governance participation in one transparent view - AI agent skills + MCP server: Five skill packs teaching coding agents the CoW stack Outcome: By offloading hard-to-delegate technical work without adding management overhead, CoW was able to expand its ecosystem, improve developer and user experience, and strengthen long-term protocol maintainability — while keeping the core team focused on advancing the protocol itself. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Case study — Silo Finance The entire data layer owned end to end — subgraphs, multichain APIs across 4+ chains — with infrastructure costs cut 80%. 4+ Chains served by one API · 80% Infrastructure costs cut · 5 Build phases from subgraph to multichain API · 99.9% Uptime SLA target Silo is a permissionless lending protocol where each market is an isolated silo — lenders and borrowers interact within contained risk environments. Running it takes a data layer that keeps up with the protocol: indexers, APIs, and liquidation infrastructure across every chain the protocol reaches. Shipped: - V2 subgraph: The indexing layer the protocol's apps are built on - Multichain API: One API across 4+ chains, built in 5 phases from subgraph replacement on - Liquidation infrastructure: Monitoring and execution built for market stress - Chain integrations: New chains brought online on launch timelines - GraphQL API + docs: The data layer, documented for integrators Outcome: Silo ships a multichain lending protocol while Bleu keeps the data layer running underneath it — end to end, across every chain, at a fraction of the original cost. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Case study — 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. 3+ Years of partnership · 12k+ Commits shipped · 16 Apps in production · 99.984% Uptime on the M&M's launch Perk is a white-label loyalty platform consumer brands plug into for rewards, quizzes, receipt scanning, and product discovery. Bleu has been embedded for 3+ years — operating like an in-house product team, not a vendor. Shipped: - M&M's global program: Enterprise launch served at 99.984% uptime - Receipt scanning: Smarter flows for the platform's highest-friction input - Admin dashboard rebuild: The operations surface, rebuilt for the platform Perk is becoming - NFT marketplace: Full-stack marketplace with fiat-to-crypto checkout - AI-powered onboarding: Brand sites scraped into ready-to-run programs Outcome: Perk gets an engineering team that compounds — 3+ years of platform context, enterprise launches that hold, and a codebase that stays ready for where the product goes next. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## 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. Process: - 01 — 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. - A focused first call - Business and technical context - What is blocked, fragile, or hard to delegate - 02 — We get close to the work: We work from the real system, not the deck. Code access and a few direct conversations beat weeks of discovery. - Access to the relevant code and environments - Conversations with the people closest to the work - Fast context-building, not endless discovery - 03 — We define the path: You get a clear recommendation — what we'd do, what it costs, and what we'd explicitly not do — before anything is committed. - Clear recommendation - Scope and tradeoffs made explicit - No vague proposal language - 04 — We take ownership: We run the work end to end. You get visibility into progress and decisions, not a daily standup to run. - Regular async updates - Direct access to the people doing the work - Escalation only when a decision needs you - 05 — We leave it in good shape: The work ends in production-ready shape — code, documentation, and handoff. Maintainable after us. - Production-ready delivery - Technical documentation - Clean handoff to your internal team when needed ## Ways to work with Bleu Each engagement has a different entry point and shape. The path depends on where you are. - [Assessment](https://bleu.builders/offerings/assessment): Technical clarity in 1–3 weeks. For teams that know something is off and want a clear read before committing to the wrong fix. - [Sprint](https://bleu.builders/offerings/sprint): One real problem solved in 2–8 weeks. For teams that need a real problem taken off their plate — owned end to end, not staffed. - [Squad](https://bleu.builders/offerings/squad): A team owning a critical part of your product. Best fit when the work is ongoing, tightly connected to the system, and too important to keep staffing ad hoc. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## We take ownership of work that's hard to delegate Bleu works with software companies and DeFi teams when the job calls for understanding the problem, making good decisions, and carrying it through. ## Why Bleu exists Bleu came out of a pattern we kept seeing: critical work delayed, over-scoped, or built around the wrong problem. The issue was rarely effort — it was ownership. Somewhere between the request and the build, the real problem stopped being examined. So we don't treat the brief as untouchable. We question the problem, understand what success depends on, and move from there. Then we do the work well and leave it strong enough to hold up in production. ## What working with us feels like Trust isn't declared. It accumulates through practices that keep the work visible: - Status without prompting: We initiate updates. Clients should never have to ask. - No allocation surprise: If capacity or scope shifts, you hear it before it affects delivery. - A named owner: One person accountable per engagement. You know who. - Recentering when something feels off: If the outcome feels uncertain, we start the conversation. We don't wait for you to. - We don't overcomplicate. - We care about the outcome - We integrate, we don't hover - We take responsibility for the outcome ## Team A small senior team, no rotating cast. The people on this page are the ones in your Slack, your codebase, and your reviews. - José Ribeiro — CEO · Co-Founder - Fábio Mendes — Product Engineer · Co-Founder - Luiza Kataoka — Software Engineer - Victoria Fracari — Product Manager - Etore Grande — Product Designer - Bibiana Corrêa — Product Designer - João Victor Assis — Software Engineer - Jean Neiverth — Software Engineer ## Who leads Bleu José Ribeiro built Bleu after seeing the same failure mode too many times: the work was technically strong, the team was capable, but somewhere between the request and the build, the real problem stopped being examined closely enough. The fix was not better process. It was building a company where the people doing the work treat the outcome as their responsibility, and have enough context and judgment to catch problems early, before they become expensive. ## Born in Floripa. Building Everywhere Bleu is built from Florianópolis — an island that quietly became one of Brazil's strongest tech hubs. It's where we found people who could have taken jobs anywhere and chose to stay somewhere worth staying. That matters more than it sounds. The work we take on is long, ambiguous, and high-context — it needs people who aren't burning out or job-hopping every 18 months. Floripa is part of how we keep them. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Bleu Assessment — Technical clarity in 1–3 weeks For teams that know something is off and want a clear read before committing to the wrong fix. When something is off but the fix isn't obvious: Teams usually arrive mid-symptom: velocity dropped, an area nobody wants to touch, a rebuild that keeps being proposed. Before committing to any of it, the problem needs an honest diagnosis. A technical and product read on what's going on, what is causing drag, and what the cleanest next step is. - A diagnosis, not a proposal - Direct read of code, architecture, and process - A recommendation you can act on — with or without us - Investment: Scoped in the first conversation. - Length: Typical length: 1–3 weeks What an Assessment covers: - Where the drag is actually coming from - Architecture and code health around the problem area - What's worth fixing, rebuilding, or leaving alone - Scope, tradeoffs, and sequencing for the next step - A clear recommendation before you commit to the wrong fix Selected work: - [CoW Protocol](https://bleu.builders/cases/cow-protocol): CoW offloaded high-context ecosystem work — SDKs, tooling, governance, user-facing product — so the core team stayed focused on the protocol. - [Silo Finance](https://bleu.builders/cases/silo-finance): The entire data layer owned end to end — subgraphs, multichain APIs across 4+ chains — with infrastructure costs cut 80%. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Bleu Sprint — One real problem solved in 2–8 weeks For teams that need a real problem taken off their plate — owned end to end, not staffed. When a real problem needs to leave your plate: Bounded, high-stakes work the core team keeps deprioritizing: integrations, migrations, legacy rebuilds, production features, internal tooling. It needs end-to-end ownership, not another body on the team. A bounded engagement for a problem that needs end-to-end ownership: integrations, migrations, legacy rebuilds, production features, internal tooling. - One problem, owned end to end - Senior people from day one - Production-ready is the definition of done - Investment: Scoped in the first conversation. - Length: Typical length: 2–8 weeks What a Sprint takes on: - An integration or migration that keeps slipping - A legacy surface that needs a careful rebuild - A production feature the core team can't staff - Internal tooling that would unblock other teams - The documentation and handoff that make it stick Selected work: - [CoW Protocol](https://bleu.builders/cases/cow-protocol): CoW offloaded high-context ecosystem work — SDKs, tooling, governance, user-facing product — so the core team stayed focused on the protocol. - [Perk](https://bleu.builders/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. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Bleu Squad — A team owning a critical part of your product Best fit when the work is ongoing, tightly connected to the system, and too important to keep staffing ad hoc. When the work is not really a project: 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. A stable team with ownership of a product or infrastructure area your users depend on. - Not staff augmentation - Stable ownership over time - Continuous product and engineering progress without heavy management overhead - Investment: Scoped in the first conversation. - Minimum: Recommended minimum: 3+ months What a Squad typically owns: - 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 Selected work: - [Silo Finance](https://bleu.builders/cases/silo-finance): The entire data layer owned end to end — subgraphs, multichain APIs across 4+ chains — with infrastructure costs cut 80%. - [Perk](https://bleu.builders/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. Contact: [jose@bleu.builders](mailto:jose@bleu.builders) --- ## Bleu Product engineering for software work that's hard to delegate. We'll never compete with you. ### Offerings - [Assessment](https://bleu.builders/offerings/assessment) - [Sprint](https://bleu.builders/offerings/sprint) - [Squad](https://bleu.builders/offerings/squad) ### Company - [How It Works](https://bleu.builders/how-we-work) - [About Us](https://bleu.builders/about) - [Cases](https://bleu.builders/cases) ### Contact - [Contact](mailto:jose@bleu.builders) - [jose@bleu.builders](mailto:jose@bleu.builders) Social: [GitHub](https://github.com/bleu) · [X](https://x.com/bleubuilders) · [LinkedIn](https://www.linkedin.com/company/101019721/) © 2026 BLEU LTDA. All rights reserved.