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.
machine viewenglishraw: /about.mdbuild: d68074d2026-08-05T14:02Z
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/)
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.
The proposal names the people leading and doing the work, along with the time each person is expected to spend on it.
Before starting, we agree who can cover critical responsibilities, who needs access, and what a handoff must include.
Before pricing a backlog, we inspect the workflow, code, data, and constraints around it.
The people leading delivery join the client conversations and can change the plan.
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.

MADE IN FLORIPA
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.
Tell us what is going on. After you send it, the calendar opens so you can choose 15 minutes.
15 MINUTES · A CLEAR NEXT STEP.