I started building FlowState because of something I watched happen to someone I love.
My wife Shannon is a mortgage lender. She's exceptional at it: genuinely skilled, deeply attentive to her clients, the kind of professional who makes the biggest financial decision of someone's life feel navigated rather than survived. And when I sat down one evening to watch her work, not to evaluate it, just to understand it, what I saw was a person drowning. Not in complexity she couldn't handle. In a system that refused to tell her what mattered.
She was on the phone with a borrower, mid-conversation, toggling between three screens to find a single answer. This was at a Fortune 500 company with supposedly state-of-the-art infrastructure. The client on the other end, the one making the biggest purchase of their life, had to wait while Shannon navigated a workflow that treated every task, every notification, every screen as equally important. Nothing was prioritized. Everything was loud.
She wasn't struggling because she lacked skill. She was struggling because no one had built a tool that respected her time, her judgment, or her intelligence. When she left that company to start her own practice, the problem didn't go away. It got worse. Now she was the operator, the marketer, the administrator, and the relationship manager, all at once, with no system underneath any of it.
That experience is where FlowState started. Not with a market analysis. Not with a pitch deck. With watching a talented person spend her best hours on the wrong things, and knowing the tools were the reason.
She wasn't struggling because she lacked skill. She was struggling because no one had built a tool that respected her time, her judgment, or her intelligence.
The principle underneath
The Pareto Principle, the observation that roughly 20% of inputs generate 80% of outputs, is one of those ideas that most people encounter as a productivity tip. Prioritize the important stuff. Focus on what matters. It sounds obvious enough that it barely registers.
But it's not a tip. It's a structural truth about how value distributes in complex systems. And in mortgage lending, the distribution is sharp enough to measure.
A working loan officer might carry 30 to 50 active relationships at any given time: prospects, pre-approvals, files in processing, closings on the calendar, referral partners at various stages of warmth. Each of those generates tasks. On a Monday morning, the list might include a rate lock expiring tomorrow, three document follow-ups, two loans entering underwriting, five client calls, a Realtor lunch to confirm, and a new lead from overnight. All of it feels important. All of it generates urgency.
Most of it is not in the 20%.
The 20% is the subset of activities that actually move the pipeline forward, that build the relationships which generate referrals, that create the compounding returns a business grows on. The other 80% is real work. It needs to happen. But it doesn't compound. It maintains the status quo. And the challenge is that the 80% is almost always louder than the 20%. The expiring rate lock screams. The referral partner you haven't called in six weeks is silent. The overdue document follow-up triggers anxiety. The past client whose situation has changed triggers nothing at all.
Every existing tool in the mortgage space sorts by urgency. Due dates, overdue flags, notification counts. This is just another way of ensuring the loud, immediate, and small consistently wins over the quiet, strategic, and important. Not because loan officers make bad choices, but because the systems present a flat list and call it a workflow.
What the top 20% actually looks like
It's easy to talk about "focusing on what matters" in the abstract. It's harder to name concretely what the top 20% of a mortgage business consists of. But the loan officers who operate at the highest level, the ones whose businesses grow even in flat markets, tend to converge on a similar set of activities.
They spend time on scenarios, not just running them, but running them with clients in real time. Collaborative analysis that positions them as advisors rather than order-takers. This is a trust-building activity. It compounds through referrals.
They invest in their existing book. Not through generic quarterly check-ins, but through specific, data-informed outreach. The past client whose rate is now well above market. The one whose equity position has shifted enough to change their options. Reaching out with a reason, not just a reminder.
They manage their referral relationships with intention rather than reaction. Understanding which partnerships generate the most value, which ones are cooling, where a lunch or a phone call will have the highest return on relational investment.
They protect time for the work that doesn't have a deadline. Pipeline review. Business development. Strategic thinking about where their next ten loans are coming from, not just the next one.
None of this is revolutionary. Most loan officers would look at this list and say, yes, that's what I should be doing. The gap is not awareness. The gap is that the daily mechanics of origination make it almost impossible to consistently prioritize these activities over the urgent, reactive work that fills every available hour. The intention is there. The infrastructure isn't.
Why the tools are the bottleneck
This is the part that took me the longest to understand, and it's the conviction FlowState is built on.
The problem is not that loan officers don't know what's important. Most of them can articulate it clearly. The problem is that their tools actively work against them. A CRM that presents every contact with equal weight. A task list sorted by due date, which is just another name for sorting by urgency. A notification system that interrupts for everything, which means it distinguishes nothing.
These tools were designed to make sure nothing falls through the cracks. That sounds like a virtue. In practice, it means the loan officer opens their laptop Monday morning and faces a wall of tasks, all presented as equally important, with no guidance on where to start. So they start with whatever is oldest, or whatever is screaming, or whatever is easiest to check off, and they work reactively through the morning until the energy is gone. The important-but-quiet items, the ones in the 20%, get pushed to tomorrow. And tomorrow, the same thing happens.
When the system presents everything at the same volume, urgency wins every time. That's not a failure of discipline. It's how attention works.
This is not a character problem. It is a design problem. The human brain is not built to resist urgency under pressure. When the system presents everything at the same volume, urgency wins every time. That's not a failure of discipline. It's how attention works.
The tool should be the thing that solves this. The tool should know the difference between a task that's urgent and one that's important. It should surface the 20% at the top, with a clear explanation of why, and it should give the loan officer permission to defer or ignore the rest. Not because the rest doesn't matter, but because doing the important thing first is how a business compounds instead of just persisting.
That's what FlowState is built to do. Not to add another dashboard or another notification layer or another list to manage. To answer, every morning, the one question that actually matters: what is the most valuable thing I can do in the next hour, and why?
The feeling underneath the math
There's a version of this argument that's purely quantitative. Focus on the 20%, capture more revenue, grow faster. That version is true and it's not the whole story.
The loan officers I've talked to, the ones who feel the weight of this problem most acutely, don't describe it in terms of revenue. They describe it as a feeling. The sense that they're working incredibly hard and can't quite explain why the results don't match the effort. The Sunday night anxiety about Monday morning. The nagging suspicion that they're spending their best hours on the wrong things but not knowing what the right things are, specifically, concretely, on any given day.
Shannon described it to me once as the feeling of being busy without being productive. Not lazy. Not disengaged. Busy. Fully committed, fully exhausted, and unable to point to the thing that moved the needle. That description stayed with me because I think it's the experience of most loan officers who are honest with themselves about it. Not a lack of effort. A lack of clarity about where the effort should go.
That clarity is what FlowState exists to provide. Not in the abstract, not as a principle on a poster, but as a specific, daily, operational answer. Your four focus tasks for today. Three and a half hours. $47,500 in pipeline value. Start with this one, because here's why it matters most.
The math underneath that is real. But the feeling, the shift from surviving the day to knowing you spent it on what actually matters, is the product. Everything else is implementation.