TruHome’s operating model introduces change management and workflow complexity that most lenders don’t face. With 60 brands inside a single Encompass environment, rolling out new technology requires phased adoption, repeated training cycles, and tight alignment across internal teams and partner credit unions.

As Brad Sikes put it:

“If I had one brand, I could have rolled out this whole thing by now. But I have 60 brands in my Encompass environment.”

TruHome needed to solve for:

• Inconsistent income calculations between origination and underwriting
• Heavy back-and-forth that slowed files and increased touches
• Underwriting bandwidth consumed by income calculation requests that could be resolved upstream
• Manual “stare and compare” document review that made scaling difficult

TruHome didn’t evaluate Prism as a standalone income calculator. The deciding factor was the broader Prism platform and the ability to standardize decisioning and workflow across major roles.

Brad summarized the value succinctly:

“Prism gets you away from documents in favor of data, and allows all of the major roles to use the same tools all the way through the process.”

What stood out:

• Data-first workflow: Extracting and presenting usable data instead of forcing users to interpret documents manually
• Consistency across roles: Loan officers and underwriters can work from the same framework, reducing friction and rework
• Front-loading outcomes: Helping origination anticipate underwriting conditions without building extensive Encompass-only rules
• Encompass-connected approach: Compared to tools TruHome evaluated that lived “outside” Encompass and didn’t write meaningful results back into the file

TruHome followed a deliberate rollout strategy: adopt Prism with underwriters first, then use that momentum to bring origination teams onboard.

“We started with the underwriters and got them kind of addicted to it. And then… it was a little bit easier to get the loan officers’ buy-in.”

Why this mattered:

• Underwriters became internal champions early
• Origination teams understood Prism outputs were now part of underwriting expectations
• The workflow shifted toward: origination completes more upfront, underwriting confirms instead of recreating

“All they would have to do is just kind of confirm, ‘Hey, I agree with this.’”

TruHome has been careful not to overstate time savings because true time-in-file is difficult to measure precisely in Encompass, and real work often includes pauses, multitasking, and queue time.

Instead, early outcomes are showing up as reduced manual effort and fewer avoidable underwriting touches, which often matters more than a simple per-file estimate.

What TruHome is seeing early:

Reduced effort on income-driven files

For loans that require income calculations, Prism is already helping underwriters complete analysis faster—especially where the alternative is manual review and repeated checks on complex scenarios.

Brad offered a conservative ballpark estimate for certain files, but the more meaningful story is that Prism reduces the “assembly work” and re-checking that consumes underwriting capacity.

Fewer unnecessary requests entering the underwriting queue

A major early benefit is preventing work from reaching underwriting in the first place. TruHome saw instances where income calculation requests were submitted to underwriting, and underwriting managers recognized they were avoidable if Prism had been run upstream.

“If you would have just ran this through Prism, you didn’t even have to send this to us. It would have given you exactly what you’re looking for.”

This shift drives outsized value because it reduces:

• Queue volume
• Back-and-forth handoffs
• Repeat touches and resubmissions
• Downstream delays tied to waiting for underwriting capacity

As rollout expands across credit union partners, TruHome expects these outcomes to become more visible in operational indicators (touch counts, fewer income calc requests, and smoother pipeline flow).

TruHome anticipated that loan officers would require enablement and support—especially because income calculation has inherent learning curves regardless of tool.

“They’re loan officers, so they’re resistant to change… any income calc has its own learning curve.”

A key tactic that accelerated adoption: a dedicated Teams support channel during rollout.

“We created a Teams group… if you have questions, ask… and then very quickly… loan officers started answering other loan officers’ questions.”

Why this worked:

• Faster answers than ticket-only support
• Peer-to-peer credibility
• Reduced friction as common questions repeated across teams

Brad also noted Prism’s UI as a differentiator versus prior tools TruHome tried to roll out.

One of TruHome’s biggest surprises was how smoothly implementation went—especially compared to vendors where project teams lacked mortgage domain expertise or weren’t prepared for common pitfalls.

“My biggest pleasant surprise was how smoothly the implementation… went…you guys guiding us through every step… having all of the pitfalls already figured out.”

Brad contrasted this with other vendor experiences where:

• TruHome was an early adopter and the vendor lacked mature implementation “pitfalls” knowledge
• Project teams were strong PMs but weak on mortgage workflow realities

“Having someone… that knows what it can, can’t, and shouldn’t do… that was the difference maker.”

TruHome is moving toward a future where loan officers can complete more work upstream, including pre-approvals powered by underwriting-aligned condition sets.

“One of the reasons… we were able to sell it was the prospect of being able to have loan officers do their own pre-approvals.”

TruHome is finalizing condition building and preparing to onboard the next group of loan officers into that workflow.