Brent Haskins / Applied AI
Real-time status beats socket theater for most SaaS
Not every live update needs WebSockets. Brent Haskins ships borrower and broker flows with clear status timestamps, incremental fetch, and UI that admits delay—cheaper to run and easier to debug than always-on sockets for low-frequency events.
Founders ask for “real-time” when they mean “I do not want to refresh the page.”
That is a UX problem with multiple fixes—most cheaper than a socket cluster.
Frequency reality check
Mortgage leads update a few times a day per file. Training progress moves when a learner finishes a module. Socket infrastructure for those cadences is often resume- driven architecture, not user value.
Patterns that work
Short polling with backoff on the detail view only.
SSE for server-push status when you control one direction of traffic.
Optimistic UI only when rollback is obvious.
Pair with dashboard empty states so zero and stale are designed, not accidental.
Display semantics
“Updated 2m ago” beats a green dot with no meaning. When another user changes a record, show who and when if your permissions allow it.
Debugging wins
HTTP requests appear in normal logs. WebSocket bugs reproduce at 4pm on hotel Wi-Fi. Support teams feel the difference.
Where Brent has applied this
/projects/loan-finder — borrower/lender visibility. /projects/rally — lead pipeline. Training analytics on /projects/smart-mortgage-training.
Choose transport after you write the user story in seconds, not milliseconds.
FAQ
Questions people ask about this topic.
When are WebSockets worth it in B2B SaaS?
Use WebSockets when multiple users edit the same record concurrently, when sub-second fan-out is a core promise, or when chat is the product. For lead status, course progress, or notification badges, polling or SSE with backoff is often enough. Simpler transport reduces ops burden and avoids reconnect bugs on mobile networks.
What should users see when data is stale?
Show last updated time, a manual refresh control, and subtle polling in the background. If the API fails, say so. Do not animate fake live dots. Operations users trust honesty more than shimmer.
Sources