Eureka Case 30 min Undergrad

Risco-AI Integration

You are Rafael Furtado-Albuquerque, 44, Chief Product Officer at Lumibrá Pagamentos, a São Paulo-based B2B-payments SaaS unicorn. Last Wednesday Lumibrá closed the $42M acqui-hire of Risco-AI, a 16-person fraud-detection-ML startup. Your CEO asked you to design the integration. The signed deal documents leave the architecture open: you have 30 days.

The situation

Lumibrá Pagamentos is a B2B payments-orchestration platform (~700 staff, $1.8B last valuation, $240M ARR, 32% YoY). Its existing fraud product — Lumibrá Risk Shield — is rule-based, in-house, three years old, decent. Lumibrá acquired Risco-AI for $42M ($28M cash close + $14M earn-out across 30 months tied to founder retention and ARR milestones). Risco-AI brings 12 engineers, 4 ML researchers, 2 founders (Bruno Cavalcanti the CTO, Mariana Soares the CEO/product), real-time payment-fraud ML models in production, $4M ARR across ~80 mid-market customers — and a reputation in São Paulo's fintech community for hiring better than anyone else.

The deal documents are deliberately silent on architecture. Three real designs are on the table — full integration, standalone product unit, or acqui-hire with product sunsetting. Each implies different earn-out economics, different engineer retention, different customer outcomes, and a different fraud-AI roadmap for Lumibrá. Your CFO wants cost synergy quickly; your CTO wants the ML talent integrated into the platform team; Mariana wants to keep the brand and the customers; Bruno wants the team intact. The 30-day integration committee meets weekly.

Your job in this case: design the integration. You are buying an organism (engineers + product + customers + IP + roadmap), not just sixteen résumés. Pick a structure that respects what you bought, and present it to the integration committee with the staffing diagram, the customer-migration plan, and the founder-retention design.

The decision

What integration design do you present to the committee?

  • A · Full integration: kill the Risco-AI brand, fold engineers into Lumibrá Risk Shield
  • B · Standalone product unit inside Lumibrá (24-month horizon)
  • C · Acqui-hire only; product sunset over 6 months

The rest of the case is locked

The data, the calculations, the decision itself and what happens next open with your institution's access code.

Have an access code?

No code yet?

Instructors can request access for a course. Tell us who you are and which course it is for, and we will send your institution a code.

Run it live in class: every student decides and justifies, and the whole class sees how it splits. How Eureka Case works →