machine viewenglishraw: /index.mdbuild: d68074d2026-08-05T14:02Z
[Cases](https://bleu.builders/cases/) · [How we work](https://bleu.builders/how-we-work/) · [Legacy Modernization](https://bleu.builders/offerings/legacy-modernization/) · [AI in the Operation](https://bleu.builders/offerings/ai-transformation/) · [1 → 100](https://bleu.builders/offerings/1-to-100/) · [0 → 1](https://bleu.builders/offerings/0-to-1/) · [Contact](https://bleu.builders/contact/) · [Agent onboarding](https://bleu.builders/agents.md)
Bleu takes products and systems from the first decision through production — including the infrastructure and the handoff.
You don't need a perfect spec to start
Not staff augmentation
Production-ready delivery, documentation, and handoff
---
Four situations clients bring us into.
**[Legacy Modernization](https://bleu.builders/offerings/legacy-modernization/)** — Modernize a critical system in production, part by part, while the operation keeps running.
**[AI in the Operation](https://bleu.builders/offerings/ai-transformation/)** — Put AI into one of your workflows, connected to company data, rules, and systems, with visible cost and controlled access.
**[1 → 100](https://bleu.builders/offerings/1-to-100/)** — Give a live product area one team that decides, builds, and ships.
**[0 → 1](https://bleu.builders/offerings/0-to-1/)** — Launch a new product in 1–2 months without assembling the whole team first. Bleu runs product, engineering, and infrastructure until it is in use.
---
Four engagements in day-to-day use. The case pages show what each number counts.
R$1B+ — In client mining revenue exposed to the deadlines the system tracks. 4,000+ mining and environmental processes monitored.
99.984% — Uptime during a global launch. Perk / M&M’s · marketing technology for 1.5M people.
80% — Lower infrastructure cost. Silo Finance · financial infrastructure.
16 — Initiatives shipped. CoW Protocol · 30+ months of partnership.
[See the Cases](https://bleu.builders/cases/)
---
From a global M&M’s launch to mining and financial infrastructure: critical legacy, data, and product work, where understanding the problem matters as much as shipping it.
[Financial infrastructure — CoW Protocol](https://bleu.builders/cases/cow-protocol/) — Everything around the protocol, off the core team's plate. WHAT CHANGED: One team delivered developer tools, governance tooling, and user-facing products from the first decision to real-world use.
[Marketing technology — Perk](https://bleu.builders/cases/perk/) — The whole product team behind Perk’s platform. WHAT CHANGED: 16 apps in production for global brands including M&M’s and Pedigree.
[Financial infrastructure — Silo Finance](https://bleu.builders/cases/silo-finance/) — The data layer, owned end to end. WHAT CHANGED: One team runs the data layer end to end: indexing, APIs, monitoring, and infrastructure cost control.
[Mining and environment](https://bleu.builders/cases/geology-consultancy/) — Regulatory operations that act before a deadline becomes a problem. WHAT CHANGED: A critical operating system is being modernized in stages while the daily operation continues.
[Animal protein](https://bleu.builders/cases/animal-protein/) — From WhatsApp sales to a marketplace validated in the field. WHAT CHANGED: A field-validated marketplace, with quality-analysis AI advancing in parallel.
[Financial infrastructure — Pike](https://bleu.builders/cases/pike/) — “Our best product in 8 years”. WHAT CHANGED: Product, design, frontend, backend, automation, and analytics moved on one roadmap.
CoW Protocol, in depth:
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. 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.
Perk × M&M’s — A global brand launch at 99.984% uptime: A global brand launch to 1.5M people on Perk’s loyalty platform — 99.984% uptime under enterprise load.
Also: 4 Optimism grants, all milestones approved
9 Balancer grants, delivered on scope and on time
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Tell us what is stuck. In 15 minutes, we’ll tell you whether we can help and how we would start.
No. Bring a problem, a hypothesis, or something that stopped moving. The conversation separates what needs a decision from what is ready to deliver.
Someone from the team that does the work — there is no sales handoff before that conversation. In 15 minutes we understand the context and say whether Bleu is a fit.
You do. The code, the documentation, and the infrastructure are yours, and the handoff includes what your team needs to continue the work.
You may leave with a recommendation to investigate further, a proposal for the work, or the conclusion that Bleu is not the right team. In every case, you know the next step.
What is stuck is enough to start.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Tell us what is going on. After you send it, the calendar opens so you can choose 15 minutes.
Products, systems, and AI that hold up in production.
15 MINUTES · A CLEAR NEXT STEP.
Contact: [Start a conversation](https://bleu.builders/contact/) — send two sentences on the problem.
---
Industry: Financial infrastructure
CoW Protocol is financial infrastructure in web3 — a decentralized trading system. Over 30+ months, Bleu has shipped 16+ initiatives around it: SDKs that opened the protocol to more developers, governance tooling, and user-facing products.
30+ Months of partnership · 16 Initiatives shipped · 32% TS SDK bundle size cut · 2 Weeks to ship the AMM Deployer
CoW Protocol is core DeFi infrastructure: MEV protection, programmable orders, and AMMs. As the protocol matured, the challenge shifted from correctness to adoption. The infrastructure worked; building on it still required deep protocol knowledge and specific technical choices.
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
Related offering: [1 → 100](https://bleu.builders/offerings/1-to-100/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Industry: Financial infrastructure
Infrastructure costs cut 80% and one API serving 4+ chains. Bleu owns the entire data layer of Silo, a lending platform — indexing, multichain APIs, liquidation — while Silo’s team keeps building the product.
80% Infrastructure costs cut · 4+ Chains served by one API · 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.
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
Related offering: [1 → 100](https://bleu.builders/offerings/1-to-100/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Industry: Marketing technology
1.5M people at 99.984% uptime on the global M&M’s launch. Bleu has been the product team behind Perk — the loyalty platform for brands like M&M’s and Pedigree — for 3+ years, with 16 apps in production.
1.5M People at the M&M’s launch · 99.984% Uptime on the M&M’s launch · 3+ Years of partnership · 16 Apps in production
Perk is a white-label loyalty platform consumer brands plug into for rewards, quizzes, receipt scanning, and product discovery. Bleu has been its product team for 3+ years: the people building the platform, not a vendor on the side.
M&M’s global program: Enterprise launch served at 99.984% uptime
Receipt scanning: Members turn a store receipt into points with a photo: the platform’s highest-friction input, redesigned end to end
Admin dashboard rebuild: The console Perk’s own team uses to run every program, rebuilt for the platform’s next phase
NFT marketplace: Full-stack marketplace with fiat-to-crypto checkout
AI-powered onboarding: Brand sites scraped into ready-to-run programs
Related offering: [1 → 100](https://bleu.builders/offerings/1-to-100/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
A company in the animal-protein industry is building a marketplace for meat sales. It can walk into an investor room with a working product: a slaughterhouse that ran the pilot, sellers who used it, buyers who responded.
200 Carcasses a day at the pilot facility · 1 Field-validated pilot · 2 Squads running in parallel
The first slaughterhouse partner processes 200 carcasses a day and sells to butcher shops, supermarkets, and restaurants across southern Brazil. The entire sales operation ran through a small team making calls, sending carcass photos over WhatsApp, and pushing weekly promotions by hand.
Carcass marketplace: Live storefront with photos, prices, and orders. No more back-and-forth
Controlled inventory model: Buyers see carcasses; the slaughterhouse keeps allocation control
AI quality-analysis system: OAK-1 devices analyze each carcass’s quality and feed the storefront
Internal operations layer: Stock, order flow, and allocation rules the internal team runs day to day
Related offering: [AI in the Operation](https://bleu.builders/offerings/ai-transformation/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
For mining and environmental work, we built a radar that tracks signals from public agencies at every level, identifies the affected processes, and puts the next action in front of the team, without relying on manual checks.
R$1B+ In client mining revenue exposed to the deadlines the system tracks · 4000+ Mining and environmental processes tracked · 1 Daily regulatory monitor in use · 7 Operational flows mapped
This is a case in the mining sector, covering environmental work as well: licenses, conditions, requirements, and deadlines that cannot be missed. Knowledge about those requirements sat with a few people. The system carrying the operation had to change without stopping the work.
Regulatory monitor: DOU and SEI read daily; requirements from SEI surface before publication in the gazette
The new platform: Designed on the mapped flows — the DOU monitor and SEI integration born inside it
Layered migration: Mining cases and client records leaving the legacy, reviewed base by base
Decision document: Diagnosis, seven flows, nine pains, four named problems, prioritized fronts
Related offering: [Legacy Modernization](https://bleu.builders/offerings/legacy-modernization/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Industry: Financial infrastructure
Pike is a web3 lending protocol with audited contracts — and it needed the product around them. One Bleu team shipped the app, backends, liquidation, analytics, and design on a single roadmap. The founder called the result the best version in eight years.
8 Years of Pike — the founder calls this the best version · 1 Team across product, design, and engineering · 5 Integrated systems shipped · 12 Months to full delivery
Pike combines an exchange and a lending market on the same blockchain. The financial core — the smart contracts, audited by third parties — already existed. The challenge was everything between that code and a person actually using the product: interface, data, automation, and design.
Lending and exchange app: Unified dashboard with net yield, strategies, charts, and history
Liquidation bot: Automation that protects the protocol when positions run out of collateral — researched jointly, then built for production
Two backend systems: The layer that reads the blockchain and serves ready data to the app — where there had been no backend at all
Points program: Rewards for protocol users, wired into the product
Analytics dashboards: Protocol health and KPIs on Dune and internal panels
Related offering: [0 → 1](https://bleu.builders/offerings/0-to-1/)
Contact: [Start a conversation](https://bleu.builders/contact/)
---
You bring the context. We understand the system, recommend a path, and own the delivery, including documentation and handoff.
Process:
01 — You bring the context: You do not need a closed scope. Tell us what is happening and why it matters to the business.
A focused first call
Business and technical context
Expectations, risks, and responsibilities still open
Output: Field notes on the problem and its impact
02 — We step inside the operation: We inspect the code, the environments, and the workflows currently running the operation, talking with the people who do the work day to day — confidentiality preserved at every step.
Access to the relevant code and environments
Conversations with the people doing the work
Confidentiality preserved across every access
Output: A map of the systems and workflows involved
03 — We define the action plan: Before the work starts, you get our recommendation in writing: what we would do, what it costs, what is included, and what is not.
Clear recommendation
Scope, priorities, and boundaries made explicit
Acceptance criteria defined
Output: A prioritized action plan — scope, limits, price, and decisions recorded
04 — We run the work end to end: After the decision, the execution is ours. Progress shows up as working versions on an agreed cadence, not as status reports.
A delivery cadence set in the action plan
Progress visible in working versions
We escalate decisions that require your business context or change the agreed cost, scope, or risk
Output: Delivered in production, on the agreed cadence, with decisions recorded
05 — We plan what comes next: After delivery, we define the next step together: Bleu keeps maintaining and evolving the system, a new scope is defined, or your team takes over when it makes sense.
Ongoing maintenance and evolution with Bleu
A new scope defined from what went live
A clean handoff to your team when it makes sense
Output: Continuity decided: evolution with Bleu, a new scope, or handoff to your team
The people doing the work stay in the conversation. Decisions, risks, and next steps remain visible.
> "Easy to work with. Take ownership, which is not easy. Can be trusted to deliver, also not easy." — Siros, Silo Finance (ongoing infrastructure partnership)
> "They operate like they’re part of our team. Pick up context fast, make decisions, and ship without needing to be managed." — Taylor, Project lead, M&M’s program (3+ YEAR PARTNERSHIP)
THREE WORKING AGREEMENTS:
Decisions and next steps stay clear. Every update records the decision, the risk, and what happens next.
We handle normal delivery problems. We involve you when a decision changes the business risk, cost, or agreed boundaries.
You talk to the people who answer for the result. No management layer in between: the conversation is with the people who decide and deliver.
Full process: [How we work](https://bleu.builders/how-we-work/) Contact: [Start a conversation](https://bleu.builders/contact/)
Four situations clients bring us into.
**[Legacy Modernization](https://bleu.builders/offerings/legacy-modernization/)** — Modernize a critical system in production, part by part, while the operation keeps running.
**[AI in the Operation](https://bleu.builders/offerings/ai-transformation/)** — Put AI into one of your workflows, connected to company data, rules, and systems, with visible cost and controlled access.
**[1 → 100](https://bleu.builders/offerings/1-to-100/)** — Give a live product area one team that decides, builds, and ships.
**[0 → 1](https://bleu.builders/offerings/0-to-1/)** — Launch a new product in 1–2 months without assembling the whole team first. Bleu runs product, engineering, and infrastructure until it is in use.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Bleu steps in when a critical system, an AI initiative, or part of a product needs to move.
Bleu started with a problem we kept running into: the people deciding what to build were too far from the people building it. That gap gets expensive when a system cuts across product, engineering, and operations.
The brief gets us started. From there, we look at the code, talk to the people who run it, and trace the workflows. The same team helps choose the path and ships the work. What we hand back has to make sense to the people who will keep it running.
Bleu is a small company. You know from the start who owns the relationship and how the work continues if someone leaves the project.
José Ribeiro — Founder & CEO
José joins the first conversation, decides whether Bleu is the right team, and remains responsible for the client relationship. The proposal names the people who will lead and do the work.
You meet the team before starting: The proposal names the people leading and doing the work, along with the time each person is expected to spend on it.
Someone else can step in: Before starting, we agree who can cover critical responsibilities, who needs access, and what a handoff must include.
Problem before scope: Before pricing a backlog, we inspect the workflow, code, data, and constraints around it.
Decisions close to the work: The people leading delivery join the client conversations and can change the plan.
Progress in the product: Reviews start with working software, open risks, and unresolved decisions.
Understand before estimating.
Decide close to the people doing the work.
Put it to work.
Hand back a system your team can operate.
Bleu started in Florianópolis in 2022. The name — and the blue — came from here.
The company is still based on the island. This is where we work with clients.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Two things live on this page: how to report a security problem to us, and how security is agreed when we work inside a client’s systems. Anything specific to one project — controls, evidence, access — is reviewed during diligence, not published here.
Which repositories, infrastructure, and accesses Bleu will touch is defined per engagement — there is no standard setup. Before granting anything, you can go through the proposed setup with us and see which controls apply to your work, and which gaps remain.
During diligence, and where the client allows it, we can show evidence from the project itself: repository settings, delivery checks, access records, dependency scans, handoff procedures. What we show from one project is evidence about that project — not a claim about every project.
Bleu cannot deliver security alone. The outcome depends on your environment, the access you give us, and the controls both teams run. The contract should say who is responsible for what, who to call in an incident, and which of your policies apply to us.
Email security@bleu.builders about this website, our public code, or a system Bleu operates. In the first message, please leave out credentials and working exploit details, and don’t access personal data or disrupt a service to prove the point. We confirm receipt and agree on next steps with you.
Machine-readable contact: /.well-known/security.txt
---
This notice covers what this website collects — through contact forms, job applications, scheduling, and analytics — and what happens to that data. Data inside client projects is governed by each client’s contract, not this page.
The controller is BLEU LTDA, CNPJ 32.895.825/0001-08, Florianópolis, SC, Brazil. José Ribeiro is the privacy contact for this website: privacy@bleu.builders.
Contact forms: name, work email, optional phone number, company, selected situation, and message.
Job applications: the contact and application information submitted for an open role.
Scheduling: information submitted to the calendar provider after a contact form.
Abuse prevention: temporary request and network information used to rate-limit public forms.
Analytics: aggregate visit information collected through Umami, plus website-interaction data such as clicks, scrolls, heatmaps, and session recordings collected through Microsoft Clarity. When a website experiment is running, analytics also records the website experiment assignment shown to that visit. Clarity masks sensitive page content by default. Apollo records company-level visit activity, including pages viewed, to identify organizations visiting the site.
We use this information to answer you, prepare the conversation you asked for, evaluate applications, keep the website running, and protect the public forms from abuse. In LGPD terms, contact-form data is processed as a preliminary step toward a possible contract, at your request (art. 7, V). No form on this site makes automated decisions about you.
Cloudflare hosts the website and handles form traffic and stored contact records.
Commercial contacts may be sent to HubSpot.
Job applications are sent to Bleu’s recruitment system.
Scheduling and business email use the configured calendar and email providers.
Umami processes aggregate website analytics.
Microsoft Clarity processes clicks, scrolls, heatmaps, and session recordings so we can understand how people use the website; it masks sensitive page content by default.
Google Ads receives the accepted lead identifier and a hashed email address to improve advertising conversion measurement.
LinkedIn processes advertising measurement and audience data (Insight Tag); when the contact form is submitted, it may also receive a hashed email address, an advertising click identifier when present, and the submission time to measure an advertising conversion.
RB2B processes visitor identification data to tell us which companies visit the site.
Apollo processes company-level website visit data, including visited pages and visit activity, so we can identify organizations showing interest in Bleu.
Your browser keeps a local record of how you first arrived at the site (campaign link, referrer) for up to 90 days; it never leaves your device unless you submit the contact form. The contact record stored at Cloudflare expires within 30 days. If your contact becomes a commercial lead in HubSpot, it stays there for as long as its business purpose and the law require. Some of these providers process data outside Brazil. To see what we hold about you, or have it deleted, write to privacy@bleu.builders.
The LGPD gives you the right to know whether we process your data, see it, correct it, have it anonymized or deleted where applicable, know who we share it with, and withdraw consent. One email to privacy@bleu.builders starts any of these. Do not send identity documents in the first message.
---
Experienced product, software, and AI people who want to take a problem from its messy start to work people use. You will be expected to make decisions, ship the work, and handle difficult client conversations yourself.
No open positions at the moment. Check back soon!
We may not have a role open right now, but we keep in touch with experienced people whose work we would want on a future project. Send us your details.
Submit your details through the application form on the Careers page.
We pay US$ 2,000 for successful referrals after 90 days.
[Refer someone](mailto:careers@bleu.builders?subject=Referral)
---
Describe the problem your way. After you send it, the calendar opens so you can choose 15 minutes.
The form starts with one of four situations — Review a decision · Get it approved internally · Run the execution · Something else — followed by one short description, name, email, optional phone number, and optional company. Sending it opens a 15-minute booking slot with the context prefilled.
No project yet? Write anyway.
---
We replace it in stages while it stays in use, with validation and contingency defined before each stage.
Change the system without stopping the operation: The system runs the operation and holds years of business rules, and every change has become business risk. Modernization happens in stages so the work never stops.
Selected work:
[Mining and environment](https://bleu.builders/cases/geology-consultancy/): For mining and environmental work, we built a radar that tracks signals from public agencies at every level, identifies the affected processes, and puts the next action in front of the team, without relying on manual checks.
We choose one important path through the operation, move it end to end, prove it in production, then take the next.
The first deliverable is the map: what changes first, in which order, and why. It stays with you.
Deadlines stay visible, customers stay served, and the operation keeps running throughout the migration.
Piece by piece: Each new piece runs next to the old one until it handles production load. Only then does the old path go away.
Contingency is defined before advancing: Before each stage, we define how it will be validated and what recovery looks like if it cannot continue.
Out of one person’s head: The knowledge behind the system gets mapped, documented, and rebuilt in a form the team can use.
Your team can carry it: In the end the system is yours: understandable, extendable, maintainable without us.
Sharing the context each change needs
Validating one stage before moving to the next
Planning improvements with risk and impact visible
The system can be replaced without affecting the operation.
The work is only a hosting move, with no change to the system.
The deadline requires a complete replacement at once. In that case, we flag it before proposing the project.
The business does not have to stop to leave the old system.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
We connect AI to the company’s data, rules, and systems, starting with one measurable workflow.
Every page on this site is also available as structured Markdown for evaluating agents — the same approved content, without scraping the interface.
Every public page has a .md twin
Accept: text/markdown serves it directly
/agents.md shows an evaluating agent how to navigate the site
[Open /agents.md](https://bleu.builders/agents.md) · [Open this page as Markdown](https://bleu.builders/offerings/ai-transformation.md)
Which work should AI take on first?: We start with one concrete routine, connect the data and systems it needs, and define what AI can do on its own and when it must bring someone in.
Selected work:
[Animal protein](https://bleu.builders/cases/animal-protein/): A company in the animal-protein industry is building a marketplace for meat sales. It can walk into an investor room with a working product: a slaughterhouse that ran the pilot, sellers who used it, buyers who responded.
[Mining and environment](https://bleu.builders/cases/geology-consultancy/): For mining and environmental work, we built a radar that tracks signals from public agencies at every level, identifies the affected processes, and puts the next action in front of the team, without relying on manual checks.
We start with a routine whose current cost can be measured — hours spent, backlog, error rate, or response time. We connect the systems it needs, define where a person must approve, and compare performance before expanding it.
The first deliverable is the map: what is already in use, what it costs, and where AI can take on work. It stays with you.
The team delegates work to AI, and control stays with you. The build has to do both.
Assistants grounded in your data: It answers from the documents and systems you connect, cites its sources, and follows the same access rules as the user asking.
Agent workflows across systems: Multi-step work a person used to shuttle between tools — triage, drafting, reconciliation, follow-up — delegated to agents that act, log what they did, and stop when they are unsure.
Boundaries on what agents do: Who can do what, where agents act on their own, and where they stop and ask. Each action records what the agent did, which information it used, and where a person approved or changed the result.
Cost you can see: Spend per workflow and per task, visible from the first week. Expanding AI becomes a budget decision.
How to turn a pilot into a routine the team uses
Which tools access company data and under which rules
Where engineering time pays off and where an existing tool is enough
If the need is only a demonstration, a smaller project is enough.
If the work is training foundation models, we recommend a team specialized in model research.
If the problem is still broad, we begin with the workflow consuming the most time today.
First, one measurable workflow. Then, the decision to expand.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
We own one complete product area while your team stays on the priorities it already leads.
One product area needs an owner: The roadmap has gained new areas, but the current team is already focused on the work only it can lead. Bleu takes responsibility for one product area without adding management load.
Selected work:
[Marketing technology — Perk](https://bleu.builders/cases/perk/): 1.5M people at 99.984% uptime on the global M&M’s launch. Bleu has been the product team behind Perk — the loyalty platform for brands like M&M’s and Pedigree — for 3+ years, with 16 apps in production.
[Financial infrastructure — Silo Finance](https://bleu.builders/cases/silo-finance/): Infrastructure costs cut 80% and one API serving 4+ chains. Bleu owns the entire data layer of Silo, a lending platform — indexing, multichain APIs, liquidation — while Silo’s team keeps building the product.
We take one product area from direction through production. Once the working relationship proves itself, the same team can take the next.
It starts with one product area shipped whole and live: enough work to prove the model, without handing us the roadmap.
A live product area needs someone who answers for it, and your core team is already full. At Perk, a loyalty platform, Bleu has been the whole product team for 3+ years. At Silo, a lending platform, the entire data layer sits with us while Silo’s team keeps building the product.
Whole surfaces, not tickets: A product area with a clear outcome. You set the destination; the path, the surprises, and the shipping are ours.
Decisions where the work is: Partial direction is enough. We bring you the calls that need your context and decide the rest.
Speed that holds up: Releases include monitoring, documentation, and fixes, so the next quarter does not begin with a cleanup project.
Handoff when you want it back: When an area returns to your team, it comes back documented and ready to run.
Writing detailed tickets to keep an external team moving
Interviewing for months while the roadmap grows
Choosing between shipping features and the work underneath
A product that hasn't shipped yet. That's 0 → 1.
Loose tickets and fragments. The model needs a whole area to own.
A fixed spec that only needs throughput. The value is the decisions with the delivery.
One more pair of hands inside your process. Not staff augmentation.
This model is for a complete product area, not a queue of tickets.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
The typical timeline is 1–2 months: we define the first release and run it, from product decisions to infrastructure, until it is in use.
You do not need to arrive with the whole product defined: You do need a real opportunity, someone who can make the business decisions, and access to the people who will use it. Everything else is defined inside the engagement by the same team that builds and launches it.
Selected work:
[Animal protein](https://bleu.builders/cases/animal-protein/): A company in the animal-protein industry is building a marketplace for meat sales. It can walk into an investor room with a working product: a slaughterhouse that ran the pilot, sellers who used it, buyers who responded.
[Financial infrastructure — Pike](https://bleu.builders/cases/pike/): Pike is a web3 lending protocol with audited contracts — and it needed the product around them. One Bleu team shipped the app, backends, liquidation, analytics, and design on a single roadmap. The founder called the result the best version in eight years.
The same team defines what the first release must prove, puts working parts in front of people early, and carries the product through launch.
In the first weeks, we talk to users, settle the decisions that would change the product, and put the first complete flow in front of them. The same engagement continues through launch.
Discovery and construction happen in the same engagement. The same team defines what the first release needs to prove and carries it through production.
The first release is a complete job: We define the first release around the smallest complete job a user needs to finish, after mapping the surrounding workflow and the assumptions that would materially change the product.
One question for the first release: The first release needs to produce enough evidence for the next business decision. Anything that does not help do that waits instead of competing with launch.
Product and infrastructure on one plan: The core flow, data, integrations, environments, monitoring, and error handling move together. Launch does not depend on a second project to prepare production.
Handoff begins during the build: Decisions, documentation, and walkthroughs follow the work as it happens. When your team takes over, it receives both the system and the context to continue.
A complete internal product, engineering, and infrastructure team
A closed specification for every flow and decision
A separate prototype that must be rebuilt for production
The product still needs an internal go-ahead before work can begin.
You only need a demonstration for a presentation.
The product is already live and one area needs more capacity. That is 1 → 100.
You need people to execute tickets under your management. Bleu does not do staff augmentation.
The first release goes live ready for use, with a documented path for the team that carries it forward.
Contact: [Start a conversation](https://bleu.builders/contact/)
---
Software, product, and AI engineering — from definition to real use.
[Legacy Modernization](https://bleu.builders/offerings/legacy-modernization)
[AI in the Operation](https://bleu.builders/offerings/ai-transformation)
[How We Work](https://bleu.builders/how-we-work)
[About Us](https://bleu.builders/about)
Social: [GitHub](https://github.com/bleu) · [X](https://x.com/bleubuilders) · [LinkedIn](https://www.linkedin.com/company/bleu-builders/)
© 2026 BLEU LTDA. All rights reserved.
SOFTWARE, PRODUCT & AI ENGINEERING
We build products, modernize systems and put AI to work.
Bleu takes products and systems from the first decision through production — including the infrastructure and the handoff.
CHOOSE A STARTING POINT
What needs to move?
Four situations clients bring us into.
WHAT IS ALREADY WORKING
What changed after the work shipped.
Four engagements in day-to-day use. The case pages show what each number counts.
See the Cases
Decisions are part of delivery.
Tell us what is stuck. In 15 minutes, we’ll tell you whether we can help and how we would start.
No. Bring a problem, a hypothesis, or something that stopped moving. The conversation separates what needs a decision from what is ready to deliver.
What problem needs solving now?
Tell us what is going on. After you send it, the calendar opens so you can choose 15 minutes.
Products, systems, and AI that hold up in production.
15 MINUTES · A CLEAR NEXT STEP.