Every software pitch ends the same way: a beautiful dashboard, a login page, and a quiet prayer that your team will form a brand new habit because your vendor needs them to.
They will not. We have watched it happen from the inside. The dashboard gets a flurry of logins in week one, a trickle in week three, and by month two it is a very expensive bookmark.
So when a private credit firm asked us to fix their deal flow, we made a decision that felt almost too stupid to say out loud: no new interface. The interface is WhatsApp, because that is where the deals already were.
Meet people where the work already happens
In this corner of finance, brokers do not fill in forms. They fire off a voice note at a traffic light: the asset, the borrower, the number, half the story. The other half arrives as a PDF three days later with an apology.
The old workflow was a human reading all of that, retyping it into a spreadsheet, and hoping nothing fell through the gaps between inbox, group chat, and memory.
The new workflow is a Moron sitting in the same chats:
- A broker messages a deal in. The Moron captures it, structures it, and it is in the pipeline before anyone opens a laptop.
- Documents land in the chat. They get parsed, filed, and pulled into the underwriting pack.
- Someone asks "where are we on the Manchester deal?" and gets the actual status, not "let me check and come back to you."
- The portfolio gets watched overnight, and the humans wake up to a briefing instead of a backlog.
Zero training sessions. Zero adoption curve. The team's behaviour did not change at all, which was precisely the point. The system changed around them.
"But WhatsApp isn't a real interface"
Correct. It is better than that. It is the interface your clients already check forty times a day, voluntarily, with notifications on.
The dashboard mindset assumes the work should come to the software. We think the software should go to the work. A maintenance request from a tenant, a deal from a broker, an approval from a director stuck in an airport lounge: all of it is one message, not one login.
To be clear, there is still a serious system behind the chat. Pipelines, document stores, underwriting logic, audit trails, approval gates. The engineering did not get simpler because the interface got smaller. It got harder, because chat is unstructured, and turning unstructured noise into structured operations is the actual job.
That trade is the whole product: the machine absorbs the complexity so the humans can stay in their group chat.
The test we now apply to everything
Before we build any interface, we ask: what would this look like if the user never had to go anywhere new?
Sometimes the answer genuinely is a product with a screen. We built a broker-facing origination product for a bank, because a regulated lending process needs structure at the front door. Fine. But that is a choice you should have to argue for, not a default you inherit because every SaaS deck has a dashboard slide.
Most of the time, the honest answer is that the interface already exists. It is in everyone's pocket. It has a green icon. Your move.