The broker doesn't own inventory, set prices, or control delivery — she resells the same Cury Construtora launches, from the same PDFs, as every other broker in Rio. The only real differentiation available is the buyer's experience. And in Minha Casa Minha Vida specifically, the anxiety was never 'which apartment' — it's 'do I actually qualify' — yet almost every listing site in the segment answers the apartment question first and leaves credit for a phone call.

Prumo puts the credit question first. A six-step pre-qualification flow gives an instant, honest verdict — one of five outcomes, not a binary yes/no — with zero bureau lookups and zero document uploads. Every policy-sensitive number behind it (MCMV income brackets, subsidy rates, the Rio locality ceiling) lives in a CMS global instead of in code, flagged as an illustrative suggestion until the broker confirms it against Caixa's current tables. The proposal she eventually sends a qualified lead freezes its own commercial numbers at the moment it's created and refuses outright to generate if the underlying price table has expired.

Each layer has one job. Read it top to bottom — that's roughly the path a request takes through the system.

• A hard gate — an expired table blocking generation outright — beats a warning nobody reads, on the one number in the product where the mistake is expensive.
• Flagging an unconfirmed number as a suggestion, rather than leaving it empty, is what actually gets it corrected: the broker can see and fix it instead of it silently gating an entire surface.
• A regulatory boundary (what needs consent, what needs zero persistence) makes a better design constraint than a technical one — it decided the pre-qualification's entire data flow before any state-management code was written.