- The Gap Between the Booth and Monday Morning
- Why the First 14 Days After MBA Annual Matter
- How to Evaluate What You Saw: A Vendor-Vetting Framework
- Audit Your Own Encompass Environment Before Buying Anything
- The SDK-to-API Deadline: An Operational Checklist for Year-End
- Where AI Belongs — and Where It Does Not
- Your 30/60/90-Day Action Plan After MBA Annual
- How Lender Toolkit Fits Into This Plan
- The Industry Party: Where the Real Conversations Happened
- Frequently Asked Questions
- What Comes Next
Meta description: MBA Annual26 is over. Here is a practical plan for Encompass lenders to evaluate what they saw, audit their stack, and act before year-end.
The show floor at the Hyatt Regency Chicago cleared out on October 14, 2026. Badges went into laptop bags. Booth banners came down. And somewhere between the flight home and Monday morning's inbox, every lender who walked #MBAAnnual26 faced the same quiet challenge: figure out what to do after MBA Annual with everything they saw, heard, and promised to follow up on.
This article is for Encompass® administrators, VPs of Mortgage Operations, and Directors of Loan Production who came back from MBA Annual26 with a stack of business cards, a head full of "AI-powered" pitches, and a team waiting for direction. What follows is a clear, practical plan for the next 90 days.
The Gap Between the Booth and Monday Morning
Every vendor at MBA Annual26 said some version of the same thing: their platform uses AI, their automation is seamless, and their Encompass integration is native. Some of those claims were accurate. Many were not.
That is not cynicism. It is the predictable result of a market where "AI-powered" has become a marketing adjective rather than a technical description. When every solution carries that label, the phrase stops carrying information. What matters is the specific work the AI is doing, where it sits in your loan lifecycle, who reviews its output, and what happens when it is wrong.
The first thing to do after MBA Annual is give yourself two or three days before acting on any of it. Not because urgency is bad, but because decisions about automation infrastructure shape your operations for years. A debrief before a decision is not delay. It is discipline.
Why the First 14 Days After MBA Annual Matter
The window between a conference and the next operational sprint is short. Your team is back at their desks. Loan volume does not pause. And the vendors you met are already in your inbox.
Use the first 14 days to do three things before you schedule a single demo.
Consolidate what you actually saw. Pull together notes, brochures, and any recorded demos. Identify the three to five solutions that addressed a real problem you have — not a problem that sounded interesting from the stage.
Separate the problem from the pitch. For each vendor you are considering, write one sentence describing the operational problem they claim to solve. If you cannot write that sentence clearly, the pitch was not specific enough to act on.
Pressure-test the Encompass claim. "Integrates with Encompass" and "built natively inside Encompass" are not the same thing. Before any demo, ask whether the solution runs inside Encompass or alongside it, whether it requires middleware, and whether your Encompass administrator can configure it without developer support.
How to Evaluate What You Saw: A Vendor-Vetting Framework
Not every solution that looked good on the show floor will hold up under operational scrutiny. Here is a framework for evaluating mortgage AI and automation vendors after MBA Annual26.
Native Inside Encompass vs. Middleware
A solution that runs natively inside Encompass by ICE Mortgage Technology keeps your data in one place, reduces sync errors, and does not require a separate login or a parallel workflow. Middleware solutions can work, but they introduce latency, data mapping risk, and additional failure points. Ask vendors specifically where their solution lives in your tech stack.
Full Loan Lifecycle vs. Narrow Slice
Some tools solve one problem well. Others are designed to work across the full loan lifecycle — from application through post-closing. Neither is inherently wrong, but you need to know which you are buying. A point solution that does not connect to your broader workflow can create new handoff problems even as it solves the original one.
Admin-Configurable vs. Developer-Dependent
If your Encompass administrator cannot configure, adjust, or troubleshoot the solution without filing a support ticket or engaging a developer, your operational agility is constrained. Ask vendors what a configuration change looks like in practice and who has to do it.
API-Ready vs. SDK-Dependent
This one is time-sensitive. ICE Mortgage Technology has set a December 31, 2026 deadline for the transition from the Encompass SDK to the Encompass Partner Connect API. Any vendor still running on SDK-dependent architecture is operating on borrowed time. More on this below.
Auditability and Governance
ICE Mortgage Technology has been explicit about its AI philosophy: assistive, explainable, and transparent, with humans in the loop. That framing is not just a product positioning choice — it reflects the compliance reality of mortgage lending. The Urban Institute has noted that AI governance has arrived in mortgage finance, and that lenders need clear frameworks for how automated decisions are reviewed, documented, and audited. Before you buy any AI-powered solution, ask how its outputs are logged, how exceptions are flagged, and who is accountable when the system is wrong.
Audit Your Own Encompass Environment Before Buying Anything
The most common mistake lenders make after a conference is adding new tools before they understand what they already have. Before you evaluate a single new vendor, spend time inside your own Encompass environment.
Map your current business rules. Identify which rules are active, which are outdated, and which are missing entirely. Business rules are the foundation of Encompass automation — if they are incomplete or inconsistent, any new tool you add will inherit those problems.
Inventory your plugins and custom code. Know which plugins you are running, which are actively used, and which were built for a workflow that no longer exists. Custom code in particular can create hidden dependencies that surface at the worst possible time.
Document your manual touchpoints. Walk through conditions management, disclosure workflows, post-close tasks, and data entry. For each manual step, ask whether it is manual by necessity or by default. Most lenders find more of the latter than they expect.
This audit is not glamorous work. But it is the difference between adding automation that compounds your existing capability and adding automation that compounds your existing problems.
The SDK-to-API Deadline: An Operational Checklist for Year-End
The December 31, 2026 deadline for the Encompass SDK-to-API transition is not a distant concern. It is a year-end operational requirement, and if you have not started, the time is now.
Here is what that work looks like in practice.
Inventory every SDK-dependent plugin and integration. This includes both third-party tools and any custom-built functionality your team or a previous consultant developed. If you do not have a complete list, start there.
Map each item to an API-native or Encompass-native replacement. Some replacements are straightforward. Others require configuration work, vendor coordination, or a decision about whether the functionality is still needed at all.
Build in testing time before December 31. Do not plan to complete the transition on the deadline. Plan to complete it with enough runway to test in a non-production environment, validate outputs, and train your team on any workflow changes.
Treat the transition as a cleanup opportunity. SDK-dependent tools that have been running for years often include logic that was built for a previous version of your workflow. The transition is a natural moment to retire what no longer serves you and rebuild what does — more cleanly.
If you are not sure where to start, this is exactly the kind of work Lender Toolkit's Professional Services team handles. We have been inside Encompass environments long enough to know where the hidden dependencies tend to live.
Where AI Belongs — and Where It Does Not
This is the section that most post-conference recaps skip. It is also the most important one.
AI is genuinely useful in mortgage operations. It is not useful everywhere. The difference between a lender who gets real value from mortgage AI and one who buys a problem they did not have comes down to understanding where AI belongs in the loan lifecycle.
Where AI Adds Real Value
Repetitive, rules-heavy work. Condition clearing, data validation, document classification, and disclosure timing are all areas where AI can reduce manual touchpoints without introducing judgment risk. The work is defined, the rules are known, and the output can be reviewed by a human before it affects the loan.
Document-heavy processing. Income calculation is a good example. Pulling figures from pay stubs, W-2s, and tax returns, standardizing them, and flagging inconsistencies is exactly the kind of work that benefits from AI assistance — not because the AI replaces the underwriter's judgment, but because it reduces the time the underwriter spends on mechanical extraction before they apply that judgment.
Queue management and prioritization. AI can help surface which files need attention, which conditions are outstanding, and where a loan is at risk of falling outside SLA. That is useful operational intelligence, not a credit decision.
Where AI Does Not Belong
Credit judgment. The decision about whether a borrower qualifies — weighing compensating factors, evaluating unusual income patterns, assessing layered risk — requires mortgage expertise. It cannot be automated. Any vendor claiming otherwise is either describing something narrower than they are implying or selling you something you should not buy.
Compliance interpretation. Regulatory requirements change. Edge cases exist. A rule-based system can enforce known compliance logic, but interpreting ambiguous situations requires trained human judgment. AI can support that work. It cannot replace it.
Relationship-dependent decisions. Loan officers build borrower relationships. Underwriters develop institutional knowledge about specific loan types, markets, and borrower profiles. That expertise is not a workflow — it is a capability. Automation should protect the time your people spend on that work, not attempt to replicate it.
ICE Mortgage Technology has framed this clearly: AI in mortgage should be assistive, explainable, and transparent, with humans in the loop at every meaningful decision point. That is not a limitation. It is the right design.
Why Expertise-First Automation Outperforms Tool-First Automation
A lender who buys an AI tool and then tries to fit it into their workflow is solving the wrong problem first. A lender who starts with a clear understanding of their workflow, their manual touchpoints, and their compliance requirements — and then selects AI tools that address specific gaps — gets compounding returns.
Mortgage expertise is not a constraint on automation. It is the foundation that makes automation work. The lenders who get the most out of tools like Prism are the ones who already understand their conditions management process well enough to know exactly where the manual work is happening and why.
Your 30/60/90-Day Action Plan After MBA Annual
The following plan is designed for Encompass lenders who want to move from conference energy to operational progress without making expensive decisions too quickly.
Days 1–30: Debrief, Audit, and Prioritize
- Complete your internal debrief. Document what you saw, what problems it addressed, and what questions remain.
- Conduct your Encompass environment audit: business rules, plugins, custom code, manual touchpoints.
- Begin your SDK-to-API inventory. Know what you have before the deadline pressure intensifies.
- Narrow your vendor list to two or three solutions that address documented problems in your current workflow.
Days 31–60: Evaluate and Test
- Schedule demos for your shortlist — but structure them around your specific workflow, not the vendor's standard presentation.
- Ask each vendor for a technical walkthrough of how their solution runs inside Encompass, who configures it, and how outputs are logged.
- For any AI-powered solution, ask specifically how exceptions are handled and what the human review process looks like.
- Begin SDK-to-API remediation work on your highest-priority dependencies.
Days 61–90: Decide and Implement
- Make implementation decisions based on your audit findings and vendor evaluations, not on conference momentum.
- Complete SDK-to-API testing before December 31.
- Identify one or two automation improvements you can implement before year-end that will have immediate impact on your team's manual workload.
- Set a Q1 2027 review point to assess what changed and what to address next.
How Lender Toolkit Fits Into This Plan
We were the first ICE Mortgage Technology partner — more than a decade ago — and we have been building inside Encompass ever since. That history matters not as a credential to display, but as a practical reality: we have seen more Encompass environments, more workflow configurations, and more automation failures than most vendors who exhibited at MBA Annual26.
Our platform is built exclusively for lenders running Encompass. We do not serve other loan origination systems. That focus means our tools are designed around how Encompass actually works, not how a middleware layer interprets it.
Prism
Prism is our end-to-end Encompass automation platform, covering loan conditions, underwriting support, and AI-driven income calculation through Prism Income. Prism Income standardizes income data from source documents — reducing the mechanical extraction work that slows underwriting — while keeping the underwriter's judgment at the center of the credit decision. For pricing and configuration options, contact us directly.
Disclosure Automation
Disclosure Automation handles disclosure timing and delivery inside Encompass, reducing the manual coordination that creates compliance risk and delays. For pricing, contact us directly.
Post-Close Automation
Post-Close Automation addresses the conditions, tasks, and data entry that accumulate after closing — work that is easy to deprioritize and expensive to let pile up. For pricing, contact us directly.
PowerTools
PowerTools is our suite of more than 40 pre-built Encompass plug-ins, available at three tiers: Free ($0/month standalone), Expert ($795/month), and Optimized ($1,495/month), with Enterprise pricing available for larger configurations. PowerTools is a practical starting point for lenders who want to extend Encompass functionality without custom development.
Professional Services
Our Professional Services team handles Encompass configuration, gap analysis, compliance remediation, and custom workflow builds. If your SDK-to-API transition needs hands-on support, or if your Encompass environment audit surfaces more complexity than your internal team can address before year-end, this is where we can help directly.
We are also an ICE Gold Partner, an ICE Consulting Partner, and hold ISO/IEC 42001 certification for AI management — credentials that reflect the governance standards we apply to our own tools and the work we do inside client environments.
The Industry Party: Where the Real Conversations Happened
Before the show floor opened, Lender Toolkit co-sponsored The Industry party on Sunday, October 11 at Untitled Supper Club in Chicago. It was the kind of event where the conversations were less scripted than anything that happened in a booth — the kind of conversations that actually move things forward.
If you were there, you know. If you were not, the relationships built that evening are continuing. We are happy to pick up any conversation that started at MBA Annual26, whether it was at the party or on the show floor. You can learn more and connect at lodestar.regfox.com/the-industry-chicago.
Frequently Asked Questions
What should I actually do after MBA Annual26?
Start with a debrief, not a demo. Give yourself one to two weeks to consolidate what you saw, separate the real problems from the interesting pitches, and audit your current Encompass environment before adding anything new. The vendors will still be there. Your operational clarity will determine whether their solutions are actually useful to you.
How do I evaluate mortgage AI vendors after a conference?
Ask four questions: Where does the solution run — natively inside Encompass or alongside it? What specific work does the AI do, and who reviews its output? How are exceptions handled and logged? And is the solution API-ready, or is it still running on SDK-dependent architecture? If a vendor cannot answer those questions clearly, that is information.
Is AI safe to use in Encompass workflows?
AI is appropriate for specific, well-defined tasks — document classification, income data extraction, condition tracking, queue prioritization — where the output is reviewed by a trained person before it affects the loan. It is not appropriate for credit judgment, compliance interpretation, or any decision that requires weighing factors a rule cannot fully capture. ICE Mortgage Technology has been explicit that AI in mortgage should be assistive, explainable, and transparent, with humans in the loop. That framing is the right standard to apply when evaluating any AI-powered tool.
What happens if I miss the SDK-to-API deadline?
The Encompass SDK-to-API transition deadline is December 31, 2026. Plugins and integrations still running on SDK-dependent architecture after that date will face operational risk. The practical consequence is disruption to workflows that depend on those tools. If you have not inventoried your SDK dependencies, that is the most urgent item on your post-conference list.
Does Lender Toolkit replace Encompass?
No. Lender Toolkit is built on top of Encompass — it extends and automates what Encompass does, it does not replace it. Our tools are designed to reduce the manual work that happens inside Encompass workflows, not to create a parallel system. If you are running Encompass, our platform adds automation capability without requiring you to change your core LOS.
How long does it take to implement Lender Toolkit solutions?
Implementation timelines vary depending on the product and the complexity of your Encompass environment. PowerTools can be deployed quickly. Prism and our automation products involve configuration work that we scope during the consultation process. The best starting point is a conversation about your current environment and what you are trying to solve.
What Comes Next
MBA Annual26 is over. The pitches have been made, the cards have been exchanged, and the follow-up emails are already arriving. What separates lenders who leave a conference with better operations from those who leave with a longer vendor list is the discipline to evaluate before they decide.
Mortgage expertise cannot be automated. It has to be the foundation that automation is built on. The lenders who get the most out of tools like Prism are the ones who already understand their workflows well enough to know exactly where the manual work is happening — and why it does not need to be.
If you are ready to have that conversation, we are ready to have it with you.
Schedule a Free Consultation to talk through your Encompass environment, your SDK-to-API readiness, and where automation can reduce your team's manual workload before year-end.
Download Free PowerTools and start extending your Encompass functionality today — no commitment required.
