machine viewenglishraw: /cases/pike.mdbuild: d68074d2026-08-05T14:02Z
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/)
Financial infrastructure · THE PROTOCOL’S PRODUCT TEAM · 2025
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.
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
Overview
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.
Our role
Bleu came in as Pike’s product team: product, design, frontend, backend, automation, and analytics, owning everything outside the contracts.
“You guys are a professional organization. You guys do care. That’s the biggest difference.”
What changed
The app, backends, liquidation, analytics, and design shipped as one product, documented around the audited contracts:
- The dApp the founder called the best version in eight years
- A coordinated delivery template for how non-contract work should run
- A documented, reliable path from blockchain data to product screens
- Launch timing stayed a business-side decision on their end — said plainly
“This is how a team that is focused on delivery is supposed to function.”
Terry
Pike
CLOSEOUT CONVERSATION
What we've shipped
Five integrated systems, one team — everything a lending product needs outside its financial contracts.
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
Areas we run
THE TRUST ARC
A technical disagreement made the decision criteria explicit.
Why the API stayed open
Their smart-contract lead interviewed us before the contract and stayed close to the early work. When requiring authentication for the API came up, we showed what the protocol would lose: every integrator would need permission first. The API stayed open, and the criterion behind that call guided the rest of the project.
- Direct technical review early in the engagement
- A disagreement resolved through explicit tradeoffs
- Shared criteria for the decisions that followed
ONE TEAM, FOUR SQUADS OF SCOPE
The entire non-contract surface, under one roadmap.
The five systems
Frontend dApp, liquidation bot, two backend systems on an indexer, points integration, and analytics — coordinated as one team while the contracts were still moving under audit.
- Embedded product and design, with engineering in the room
- A sprint cadence that adapted as the contracts kept changing
- Big-picture goals aligned with the client; minor decisions owned by us
RELATED OFFERING
See how Bleu structures this kind of work
The case shows what happened in one partnership. The offering explains the entry point, scope, and first delivery.
Bring us the problem.
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.