An Aloan implementation takes most lenders 2 to 4 weeks from the kickoff meeting to go-live, in six phases: kickoff, configuration, training, validation, expansion and go-live. Aloan configures the system to your credit policy, memo template and document checklist. Your team trains on it, then your underwriters run live deals both ways and log the time, the discrepancies and their overrides on each one, and your credit lead signs off before Aloan becomes the way you underwrite. A larger scope takes longer. An integration with your LOS or core is a separate project, and a borrower-facing application flow adds configuration work; both add time. The same six phases apply whether Aloan runs as your commercial loan origination system or beside one you already own.
Implementation carries a one-time onboarding fee alongside the annual subscription, both quoted for your institution; see Aloan pricing. What Aloan does once it is live is on the commercial lending product page.
Six phases
What Aloan onboarding includes, step by step
Both teams work from one plan in the Onboarding Hub inside Aloan. Every lender starts from the same template, and each task is tagged as waiting on your team, on Aloan or on a third party, so anyone can see whose turn it is.
-
01 Kickoff
A working session that walks the plan and confirms who sits in each seat on your side: an executive sponsor, the credit lead who owns the memo standard, an onboarding champion who drives the day to day, the underwriters who will run the first deals, and someone from IT. You agree which loan types go first and which completed deals Aloan will calibrate against, and Aloan asks for the items in the table below. Your users can be invited before the call, so they arrive with a login.
The phase is done when the plan, the roles and the first loan types are agreed.
-
02 Configuration
Aloan reads your credit policy and turns it into the rules every deal is checked against, such as a minimum DSCR. Aloan switches off rules that are unclear or cannot be measured, and your team reviews which ones are on. Aloan builds your credit memo template so new memos come out in your committee's format, and sets up the document requests for each loan type. If a borrower application flow is in scope, it is configured here too. Then Aloan runs a few of your completed deals and compares its spreads and memo with the ones your team finished.
Configuration ends when the output matches your finished work on those deals and both sides sign off.
-
03 Training
Training runs in separate sessions for underwriters, relationship managers and admins. Underwriters work a deal end to end, from document upload through spreading to the memo, checking the source citations as they go. Relationship managers get a walkthrough of how a deal moves. Admins learn user management and roles. Every new user also gets an onboarding email sequence that links to the Aloan Academy videos.
The phase is done when the first group of users is trained.
-
04 Validation
Your underwriters run live deals through Aloan alongside their normal process. For each deal they log the time each way, every discrepancy between Aloan and the manual work (marked material if it would change the credit decision, immaterial if it is rounding or formatting), every override and why, and a confidence rating from 1 to 5. Aloan reads the logs every week and ships fixes for what they show.
Validation closes once material discrepancies stay under the threshold you agreed, the underwriters say they trust the output, and no critical issue is open.
-
05 Expansion
More loan types are added beyond the first ones, and the rest of your underwriters come on.
Expansion is finished when the whole team is underwriting in Aloan.
-
06 Go-live
Aloan becomes the default way your team underwrites the loan types in scope. Underwriters review and approve the spread and the memo rather than build them from scratch.
Go-live happens when your credit lead signs off.
Inputs
What your team provides
Aloan asks for these at kickoff. Configuration works from them, so the sooner they come in, the sooner your underwriters have output to check.
| Item | Who on your side | Why Aloan needs it |
|---|---|---|
| Credit policy and underwriting guidelines | Credit lead | Aloan turns the policy into the rules each deal is checked against, so a breach is flagged against your own wording. |
| Current credit memo template, and the annual review template if you use one | Credit lead | New memos come out in the format your committee already reads. |
| Document checklist by loan type | Credit or loan operations | It sets the document requests for each loan type. If you have no written checklist, Aloan starts from its default and tunes it with you. |
| A few completed deals from the first loan types | Underwriters | Calibration: Aloan's spreads and memo are compared with your finished work before anyone relies on them. |
| Named users and an admin | Executive sponsor or credit lead | The admin invites users and sets each one as an admin or a member. |
| Application questions by loan type, if a borrower application flow is in scope | Whoever owns the application today | The borrower-facing flow asks your questions and requests your documents. |
IT
What your IT team does
Your team uses Aloan in a web browser over HTTPS, so there is nothing to install on a workstation. The IT work is access control: configuring single sign-on, an IP allowlist and user accounts with Aloan. Someone from IT joins the kickoff, and an integration, if you want one, has its time scoped as a separate project.
Single sign-on, if you want it
SAML or OIDC through WorkOS with your identity provider, including Microsoft Entra ID. Aloan configures the connection for your institution during onboarding, and your MFA and access policies then apply. Without single sign-on, your users sign in with MFA.
IP allowlisting
Access to your institution's Aloan instance can be limited to your own IP ranges, so users sign in only from your network or VPN. Aloan sets the allowlist with your IT team.
User provisioning
Your institution decides who gets an account. Your admin invites users and sets each as an admin or a member.
No integration is required to start. Aloan can integrate with your existing stack through a REST API and webhooks; each integration is scoped with your team. An integration is a separate project beside the six phases, with its own owner on each side, and it is one of the scopes that takes longer than 2 to 4 weeks. Your developers can read the Aloan API reference before that conversation.
Deployment
Running Aloan alongside your LOS, or as your LOS
Run Aloan as your commercial LOS, or alongside the one you already have. The six phases are the same in both modes; the configuration differs.
Alongside an LOS you own, that system stays the record of the booked loan and nothing has to be migrated out of it. Your team does the work of the file in Aloan, and the finished memo leaves as a Word or PDF download for an approval path that runs outside Aloan. If you later want data to move between the two automatically, that is the separate integration project described above. How lenders split the work between the two systems is laid out in the LOS integration architecture guide.
As your commercial LOS, the rollout also covers the borrower application, the portal and approval routing. The borrower application and portal are configured in the configuration phase, which is why a borrower-facing flow adds time. Approval routing is switched on per lender by setting up your approval chain. Aloan as your commercial lending system of record covers that mode in full.
Vendor management
Security review
The SOC 2 Type II report, the penetration test report, the due diligence questionnaire and the subprocessor list are in the Trust Center at trust.aloan.ai, and Aloan completes your institution's own questionnaire. How Aloan handles your loan data is on the Aloan security page. For what to read first in a SOC 2 Type II report, see the SOC 2 Type II guide for commercial lending.
Support
After go-live
Weekly check-ins run through onboarding. Support continues after go-live, and about 60 days in, Aloan and your team hold a review.
New hires get the same onboarding email sequence and Aloan Academy videos as the first users. When your credit policy changes, your team uploads the new version against the existing policy, Aloan keeps the version history, and you choose which rules are on. Every change to a rule is logged with who made it, what changed, when and why.
Method
Planning your own rollout
If you are writing an internal plan for any AI underwriting tool, including the files to test, how long to run in parallel and what to measure, start with the AI underwriting implementation guide. It is vendor-neutral and has a 30/60/90 checklist.
Aloan implementation: FAQ
How long does an Aloan implementation take?
Most lenders are live 2 to 4 weeks after the kickoff meeting. The rollout runs in six phases: kickoff, configuration, training, validation, expansion and go-live. A larger scope takes longer. An integration with your LOS or core is a separate project, and a borrower-facing application flow adds configuration work; both add time.
What does our team need to provide?
Your credit policy and underwriting guidelines, your current credit memo template (and your annual review template if you use one), a document checklist by loan type, a few completed deals for calibration, and the names of your users and an admin. If you have no written document checklist, Aloan starts from its default checklist and tunes it with you.
Does our IT team need to build anything?
No. No integration is required to start; your team uses Aloan in a web browser. IT is usually involved for single sign-on (SAML or OIDC, including Microsoft Entra ID), restricting access to your IP ranges, and deciding who gets an account. Aloan can integrate with your existing stack through a REST API and webhooks; each integration is scoped with your team.
How much IT time does an Aloan rollout take?
Aloan does not publish an hours figure. The IT work is a defined list: someone from IT joins the kickoff, then single sign-on if you want it, an IP allowlist, and deciding who gets an account. Your team uses Aloan in a web browser, so nothing is installed. An integration, if you want one, is a separate project scoped with your team.
Can we start with one loan type?
Yes, one or a few. You agree the first loan types at kickoff, the calibration deals come from those types, and your underwriters validate on them. More loan types and more of the team come on in the expansion phase.
What does an Aloan implementation cost?
There is a one-time onboarding fee alongside an annual subscription. Aloan quotes both for your institution.
What happens if our credit policy changes after go-live?
Your team uploads the new version against the existing policy, Aloan keeps the version history, and you choose which rules are switched on. Every change to a rule is logged with who made it, what changed, when and why.