Tyler Krichbaum
Loan Servicing Manager at Mobilization Funding. The power user who stress-tested the mobile app from the field, caught edge cases no one else found, and pushed the platform to handle the real-world complexity of construction loan servicing.
The Arc
Every software platform has two kinds of users. There are the people who click through it during a demo and say “looks great.” And then there are the people who use it eight hours a day, five days a week, under real conditions, with real borrowers on the phone, real deadlines bearing down, and real money on the line. Tyler Krichbaum is the second kind.
As Loan Servicing Manager at Mobilization Funding, Tyler is the person who lives inside the platform every day. He processes disbursement requests. He manages draw schedules. He coordinates with borrowers, subcontractors, and inspectors. And when Cloud Nimbus built the Maximus mobile app and customer portal, Tyler was the one who tested it from the field — not in a conference room, not on a staging server, but from actual job sites where construction lending actually happens.
He found bugs that no automated test suite would ever catch. The kind that only surface when you're trying to approve a disbursement while standing on a construction site with three bars of signal and a borrower waiting for an answer. That's not QA. That's combat testing.
What Tyler Brings
Field Testing & Mobile QA
Tyler didn't test software from a desk. He tested the Maximus mobile app from job sites, in the field, under real conditions — spotty signal, mid-conversation with a borrower, one hand on his phone and the other on a stack of draw requests. That's how you find the bugs that matter.
Loan Servicing Operations
Managing the full lifecycle of construction loans — disbursement requests, draw schedules, lien waivers, inspection coordination. Tyler understands the operational reality of every dollar that moves through the pipeline, because he's the one moving it.
Borrower Relations
Tyler is the person borrowers talk to every day. He knows their frustrations, their workflows, their pain points. When a portal feature doesn't work the way a borrower expects, Tyler is the first to hear about it — and the first to escalate it.
Edge Case Discovery
The bugs that slip past QA teams, automated tests, and demo environments? Tyler finds them. He has an instinct for the weird sequence of actions, the unusual data combination, the thing no one thought to test because no one actually uses the system that hard.
Process Optimization
Tyler doesn't just find problems — he thinks about how the workflow should work. His feedback isn't “this is broken.” It's “this is broken, here's why it matters, and here's what borrowers actually need it to do.”
By the Numbers
2+
Years of Daily Platform Use
100s
Edge Cases Reported
2
Platforms Stress-Tested
Daily
Borrower Interactions
From the Field
Testing software where construction lending actually happens
The Maximus Mobile App
When Cloud Nimbus built the Maximus mobile app for iOS and Android, Tyler was the first person to take it into the field. Not a simulated field. The actual field — job sites, borrower meetings, on-the-go servicing workflows. He tested disbursement approvals, document uploads, status updates, and communication features under the conditions they'd actually be used in. The bugs he caught weren't theoretical. They were the kind that would have frustrated every borrower who downloaded the app.
The Customer Portal
The Mobilization Funding customer portal handles disbursement requests, document management, loan status tracking, and borrower communication. Tyler tested every workflow from the servicing side — the side that has to process requests quickly, accurately, and at volume. He found edge cases in the disbursement request flow that only appear when you're processing dozens of requests with varying conditions, different document requirements, and borrowers who don't always follow the happy path.
The Feedback Loop
Tyler's process was what every developer dreams of. He'd find an issue, document it clearly with steps to reproduce, explain the business impact, and then retest once the fix was deployed. No vague “it's broken” tickets. No guessing games. Clear, actionable feedback from someone who understood both the technical behavior and the business context. That's the rarest thing in software — a power user who can articulate exactly what's wrong and exactly why it matters.
How I Know Tyler
The person who uses your software harder than you designed it for
I built the systems Tyler uses every day. The Maximus mobile app, the customer portal, the disbursement workflows, the servicing tools — Cloud Nimbus LLC built all of it for Mobilization Funding. And Tyler is the person who told me, through his testing and his daily use, whether what I built actually worked.
Not “worked” in the sense of passing a test case. “Worked” in the sense of a Loan Servicing Manager being able to process a disbursement request while a borrower is on the phone asking when their funds will hit. “Worked” in the sense of the mobile app loading fast enough on a construction site with unreliable Wi-Fi. “Worked” in the sense of handling the messy, unpredictable reality of construction lending — not the clean, predictable world of a product demo.
Tyler is the kind of user that makes you better as a developer. He doesn't just find bugs — he finds the gaps between what you designed and what the real world demands. He pushes the software to its limits because his job requires him to. And every edge case he reported, every workflow issue he flagged, every piece of feedback he gave made the platform stronger for every borrower and every operator who uses it.
If you're building software and you don't have a Tyler Krichbaum using it every day, you don't actually know if it works. You just think it does.
Why He Matters
There's a mythology in tech that the developers are the heroes. They write the code, they ship the features, they deploy the platform. But the truth is that software doesn't become real until someone uses it under pressure. Someone who has to rely on it. Someone whose job depends on it working correctly, every time, in conditions the developers never fully anticipated.
Tyler Krichbaum is that person. He's the front-line operator who took a platform built in a development environment and proved it could survive the real world of construction lending. He didn't just use the software — he made it better. Every bug report was a gift. Every edge case was a lesson. Every piece of feedback was a roadmap for what to build next.
The Mobilization Funding platform is bulletproof today because Tyler Krichbaum used it like his livelihood depended on it — because it did. That's the highest compliment a builder can receive: someone who trusts your work enough to bet their career on it, and cares enough to tell you when it falls short.
Get Glen's Musings
Occasional thoughts on AI, Claude, investing, and building things. Free. No spam.
Unsubscribe anytime. I respect your inbox more than Congress respects property rights.
Keep Exploring
Brianna McDonald
Another key player at Mobilization Funding. The operations mind behind the lending machine.
Read moreJose Santiago
Mobilization Funding team member. Part of the crew that makes construction lending work.
Read moreRobert Bench
Mobilization Funding team. Another person who helped shape the platform from the inside.
Read moreMobilization Funding
The full Cloud Nimbus case study. 2+ years building a digital construction lending platform.
Read more