01
Keep the system that works
Automate the analysis without a CRM or LOS migration.
Resources
CRM and LOS integration buyer guide
Underwriting software that works with your existing CRM or LOS (2026)
Underwriting software connects to the systems you already run in one of three ways. Platforms such as Abrigo, LoanPro, nCino, and Aloan in standalone mode become the system of record, and your CRM feeds them. Platform-native apps such as nCino and Fundingo on Salesforce, or LeasePath on Microsoft Dynamics, work well if you already run that platform. Underwriting layers such as Kaaj, Heron Data, Ocrolus, and Inscribe analyze the borrower package and write the results back into the CRM or LOS you keep, by API, webhook, CRM button, or email intake. If your CRM or LOS works and the slow part is reading packages, a layer is usually the faster path: Kaaj writes KYB, bank statement analysis, fraud signals, spreads, and a credit memo into Salesforce, HubSpot, Dynamics, LeasePath, LTi Aspire, or any LOS by API, and a typical integration goes live in two to three weeks.
Short answer
Underwriting software connects to the systems you already run in one of three ways. Platforms such as Abrigo, LoanPro, nCino, and Aloan in standalone mode become the system of record, and your CRM feeds them. Platform-native apps such as nCino and Fundingo on Salesforce, or LeasePath on Microsoft Dynamics, work well if you already run that platform. Underwriting layers such as Kaaj, Heron Data, Ocrolus, and Inscribe analyze the borrower package and write the results back into the CRM or LOS you keep, by API, webhook, CRM button, or email intake. If your CRM or LOS works and the slow part is reading packages, a layer is usually the faster path: Kaaj writes KYB, bank statement analysis, fraud signals, spreads, and a credit memo into Salesforce, HubSpot, Dynamics, LeasePath, LTi Aspire, or any LOS by API, and a typical integration goes live in two to three weeks.
At a glance
How the options compare
| Vendor | How it connects | Your CRM or LOS stays the record? | Integration methods |
|---|---|---|---|
| Kaaj | Underwriting layer | Yes | REST API, webhooks, CRM button, email and drive intake; named overlays for Salesforce, HubSpot, Dynamics, LeasePath, LTi Aspire |
| Heron Data | Intake and analysis layer | Yes | Email, API, and portal intake; syncs to Salesforce, HubSpot, Zoho, LendSaaS, Orgmeter, Centrex |
| Ocrolus | Document analysis layer | Yes | API with signed webhooks; Encompass plugin; MeridianLink (beta) |
| Inscribe | Document fraud layer | Yes | API and partner integrations (Alloy, Taktile, Oscilar, Plaid) |
| Crediflow AI | Credit analysis layer | Yes | Lists nCino, Salesforce, HubSpot, accounting software, and bureaus |
| Aloan | AI commercial LOS or layer | Either | Standalone LOS, or REST APIs and webhooks into your LOS and core |
| nCino / Fundingo | Salesforce-native platform | Becomes the record on Salesforce | Built on Salesforce |
| LeasePath | Dynamics-native equipment finance LOS | Becomes the record on Dynamics | Built on the Microsoft Power Platform |
| Abrigo / LoanPro | Lending platform | No, the platform becomes the record | APIs to push CRM data in and board loans out |
Start with the boundary
What this category includes—and what it does not
Category labels overlap. A buyer asking for software may be solving an intake problem, a credit-analysis problem, a full origination problem, or a servicing problem. Define the job before comparing vendors.
- System of record
- The system that holds the official deal: parties, documents, conditions, the decision, and its history. For most lenders this is the CRM, the LOS, or both.
- Underwriting layer (overlay)
- Software that reads the borrower package, analyzes it, and writes the results into your CRM or LOS without becoming the system of record.
- Platform-native app
- Software built on a CRM platform such as Salesforce or Microsoft Dynamics. It fits if you already run that platform, and it ties you to that platform.
- Write-back
- Sending analysis results into the fields, objects, and files your team already uses, instead of a separate tab or portal.
- Webhook
- A message the vendor sends to a URL you control when work finishes, so your CRM does not have to wait on a long API call or keep polling.
Buyer jobs
Buy the outcome, not the label
The most useful vendor conversation starts with the work your team wants to make faster, safer, or easier to defend.
02
Stop rekeying
Application and package data should land in the right fields once.
03
Results where underwriters work
KYB, cash flow, fraud, spreads, and the memo inside the deal record.
04
Control what runs and when
Choose which deals and which checks run, and avoid paying twice.
05
Go live without a long project
A pilot on your own deals in weeks, not a multi-quarter implementation.
Evaluation criteria
Questions to take into every demo
Use the questions below to make vendor answers comparable. A feature that cannot be tested with your files and controls is not yet a buying decision.
| Criterion | Ask | Why it matters |
|---|---|---|
| Write-back | Do results land in the objects and fields we already use? | Ask to see output mapped into your own Salesforce, Dynamics, HubSpot, or LOS fields, not only a link to the vendor's portal. You should own the field map. |
| Triggers | What starts the analysis? | Look for a choice of API, webhook, a CRM button, and email or drive intake. A button lets you run analysis only on deals you pick, and separate buttons per check give you spend control. |
| Async completion | How do results come back? | Package analysis takes minutes. A webhook that posts results when work finishes avoids CRM API timeouts and constant polling. |
| One deal, one record | How do you stop duplicate applications? | When deals arrive by email and from the CRM, agree one unique key (CRM record ID, EIN plus application, or a subject token) and one channel that creates the record. |
| New documents | What happens when a borrower sends more documents later? | Later documents should attach to the same application and update the results, not open a second file. Ask whether a rerun costs extra. |
| Document storage | Where do the files live? | CRM file storage is expensive. Many lenders keep files in the vendor's platform or SharePoint and write only structured fields and links into the CRM. |
| Sandbox and access | Can we test before production? | Expect a sandbox, a least-privilege integration user, and a test run on production-like packages before go-live. |
| Rollout control | Can we route some deals and run the old process in parallel? | Route by product, channel, or ticket size, keep a manual trigger for the first week, and run the old process in parallel until results match. |
| Security | How are the integration and the data protected? | Ask for SOC 2 Type II, webhook authentication (a token, custom header, or IP restriction), SSO, and a clear data-use policy. |
| Data you already buy | Will it double-pull credit or replace tools you pay for? | Credit pulls, KYB, and bank data should run once per deal. Check how the vendor uses your existing bureau credentials and avoids duplicate soft pulls. |
Workflow map
Trace the work from intake to an operable decision
A vendor should be able to show where evidence enters, where judgment remains, and what gets written back to your system of record.
- 01
Pilot on your own deals
Run a handful of real packages, including messy ones, and compare the output with your analysts' work.
Output: Fit confirmed
- 02
Sandbox and integration user
Set up a CRM or LOS sandbox and a least-privilege integration user; complete the security review.
Output: Safe test environment
- 03
Field map and unique key
Map outputs to your objects and fields, and agree the key that joins records.
Output: Agreed field contract
- 04
Manual trigger first
Run analysis from a button on chosen deals while the team learns the output.
Output: Adoption without surprises
- 05
Automate
Turn on API, webhook, or email triggers for the deals you route.
Output: Hands-off intake
- 06
Cut over and monitor
Switch off the old process, often after hours, and watch the first week closely.
Output: Live integration
System boundaries
When a focused layer is enough—and when it is not
The right architecture may be one platform, a focused layer, or a combination. Make the boundary explicit before a pilot.
System of record
Kaaj / focused layer: Kaaj is not your CRM or LOS. It writes underwriting output into the record you keep.
Other system: Salesforce, HubSpot, Dynamics, LeasePath, LTi Aspire, or your in-house LOS holds the deal, pipeline, documents, and decision.
Field map
Kaaj / focused layer: Kaaj returns structured outputs, evidence links, and the memo.
Other system: Your team decides which objects and fields receive them, and owns permissions.
Credit decision
Kaaj / focused layer: Kaaj applies your credit rules and shows which are met or not met.
Other system: Your underwriters decide, in your CRM or LOS.
Evidence-based landscape
A starting set of vendors to investigate
This is an illustrative landscape, not a ranking, review, or endorsement. The descriptions below summarize each vendor’s public positioning and link to its official site; they do not independently verify performance, pricing, customer results, or fit.
| Vendor / type | Publicly described focus | Reading the claim |
|---|---|---|
| KaajUnderwriting layer for your CRM or LOS | Reads packages from email, broker portals, drives, the API, or a CRM button; verifies the business in all 50 states; analyzes bank statements (99.7% parsed without a material dollar error) and financials; checks fraud; applies your credit rules; drafts the memo in 5–7 minutes. Writes results into Salesforce, HubSpot, Microsoft Dynamics, Pipedrive, Zoho, LeasePath, LTi Aspire, Mortgage Automator, or any LOS by REST API and webhooks (token, custom header, or IP restriction), with sandbox testing first. A typical integration goes live in two to three weeks. | Disclosure: Kaaj publishes this guide. This entry describes our own product. |
| Heron DataIntake and analysis layer | Heron Data says submissions arrive by forwarded email, API, or portal, and that it syncs approvals and declines to the CRM. Its site lists LendSaaS, Zoho, Orgmeter, TaskSuite, HubSpot, Salesforce, and Centrex for funders and brokers. | Vendor description. |
| OcrolusDocument analysis layer | Ocrolus documents an API with organization- and account-level webhooks signed with HMAC SHA-256, an Encompass integration, a MeridianLink integration in beta, and Plaid JSON ingestion. | Vendor documentation. |
| InscribeDocument fraud layer | Inscribe says it integrates into loan origination systems, orchestration platforms, and the rest of the stack through its API and partner integrations including Plaid, Alloy, Taktile, Oscilar, and AWS. | Vendor description. |
| Crediflow AICredit analysis layer | Crediflow AI lists connections to nCino, Salesforce, and HubSpot, accounting software (QuickBooks, Xero, Sage), Google Drive and SharePoint, and credit bureaus. | Vendor description. |
| AloanAI commercial LOS or layer | Aloan describes two modes: run the full workflow as the LOS, or send extracted data, spreads, risk flags, and credit memos into your existing LOS and core through REST APIs and webhooks. It says most lenders are live within 2–4 weeks. | Vendor description; built for community banks and credit unions. |
| nCinoSalesforce-native bank LOS | nCino describes a commercial loan origination system spanning onboarding, origination, underwriting, document management, and approvals. It is built on Salesforce, so it fits banks already on that platform. | Vendor description. |
| FundingoSalesforce-native lending platform | Fundingo describes a lending operating system built on Salesforce to originate, underwrite, and service loans in one platform. | Vendor description. |
| LeasePathDynamics-native equipment finance LOS | LeasePath describes origination and servicing for asset finance built on the Microsoft Power Platform, so Dynamics stays the CRM spine. | Vendor description. |
| AbrigoBank lending platform | Abrigo's developer documentation covers pushing data from a CRM or other platform into Abrigo to start a Dynamic Application, and boarding loans to the core from Sageworks. Abrigo becomes the lending system of record. | Vendor documentation. |
| LoanProAPI-first origination and servicing platform | LoanPro describes an API-first origination and servicing platform whose API gives third-party tools such as decision engines and CRMs real-time access to loan, application, and customer data. | Vendor description. |
Best fit by lender type
Shortlists for the file you actually underwrite
Lenders on Salesforce
Analysis in existing Salesforce objects, without a new LOS.
Shortlist: An overlay such as Kaaj or Heron Data; nCino or Fundingo if you want the LOS itself on Salesforce.
Equipment finance on Dynamics or LeasePath
Credit data, memo, and documents in the LeasePath or Dynamics record.
Shortlist: Kaaj beside LeasePath; LeasePath alone if you mainly need the LOS.
Brokers and MCA funders on HubSpot, Zoho, or LendSaaS
Fast package review that updates the CRM deal.
Shortlist: Kaaj or Heron Data writing into the CRM you already use.
Equipment lessors on LTi Aspire, Odessa, or Solifi
Underwriting in front of a lease platform you are not replacing.
Shortlist: An API-based layer such as Kaaj, scoped against the platform's own interfaces.
Lenders with an in-house LOS
JSON results and webhooks your developers can map.
Shortlist: API-first layers such as Kaaj, Ocrolus, or Inscribe.
Community banks and credit unions
Bank-grade LOS plus faster spreading and memos.
Shortlist: nCino, Abrigo, or Aloan as the platform; a layer beside it for messy packages.
Decision checklist
What to verify before you sign
Turn the guide into a procurement artifact. Assign an owner to each question and write down what counts as evidence.
- Name your system of record for the deal, the documents, and the decision.
- Ask each vendor to map its output into your own CRM or LOS fields, in your sandbox.
- Pick the triggers you want: button, API, webhook, email, or drive.
- Agree the unique key that stops duplicate applications.
- Decide where documents live and what goes into the CRM.
- Ask what happens, and what it costs, when new documents arrive.
- Plan a week of manual triggering and a parallel run before cutover.
- Confirm SOC 2 Type II, webhook authentication, and SSO.
- Check that credit pulls and KYB run once per deal.
- Get a dated plan: pilot, sandbox, field map, go-live.
What customers say
Equipment Finance Application Intake Into Salesforce in 2 Minutes | Quality Equipment Finance
Patrick O'Connor, Head of Sales at Quality Equipment Finance, on using Kaaj to turn broker and vendor applications into Salesforce records: contact, account, opportunity, and asset. Kaaj also pulls the SOS and SAFER reports and researches the vendor, business, and borrower. What took a rep about 15 minutes per application now takes a couple, and reps see about 20 applications a day.
In this video
- Why Quality EF brought in AI
- Applications straight into Salesforce
- Know your vendor, business, and borrower
- No more re-keying
- 15 minutes → 2, twenty times a day
Answers for the buying team
Frequently asked questions
These answers are intentionally scoped. If a vendor uses the same term differently, ask it to demonstrate the boundary in your workflow.
Can we add AI underwriting without replacing our CRM or LOS?
Yes. Underwriting layers such as Kaaj read the borrower package and write KYB, cash flow, fraud signals, spreads, and the memo into the CRM or LOS you already run. Your system stays the record of the deal.
What is the difference between a Salesforce-native app and an API integration?
A Salesforce-native app is built on Salesforce and lives inside your org, so it only makes sense if Salesforce is your platform for good. An API integration keeps the vendor's processing outside your CRM and writes the results into the fields you map, so the same vendor works with Salesforce, Dynamics, HubSpot, or an in-house LOS, and survives a later CRM change.
How long does it take to integrate underwriting software with a CRM?
For an underwriting layer, weeks. Kaaj integrations typically go live in two to three weeks, and Aloan says most of its lenders are live within two to four weeks. Sandbox access, the security review, and field mapping set the real calendar. Replacing an LOS usually takes months.
Should results come back by webhook or by polling the API?
Use a webhook when you can. Package analysis takes minutes, which is longer than many CRM API calls allow. A webhook posts results to a URL you control when the work finishes; polling works for low volume but adds load and delay.
How do we avoid duplicate applications when deals come in by email and through the CRM?
Pick one channel to create the application and one unique key, such as the CRM record ID, the EIN plus application, or a token in the email subject. Everything else attaches to that record instead of opening a new one.
Can documents stay out of Salesforce?
Yes. A common pattern is intake from Salesforce or email, files stored in the underwriting platform or SharePoint, and only structured fields and links written back to Salesforce, Dynamics, or the LOS.
What happens when the borrower sends more documents after the first analysis?
With Kaaj, documents sent later reference the same application, so results update the existing record instead of creating a second file. Ask every vendor how reruns work and whether they are billed.
Can we send only some deals to the new system?
Yes. Many lenders route by product, channel, or ticket size, and start with a manual CRM button so analysis runs only on chosen deals before switching on automatic triggers.
Should we finish a CRM migration before adding underwriting automation?
Usually not. Integrate with the system you run today. If you later move from Dynamics or another CRM to Salesforce, the same output can be mapped to the new objects.
Do we need to connect our accounting software or bank feeds?
Not with Kaaj, which works from the documents in the package and also accepts Plaid JSON exports. Some tools, such as Crediflow AI, also connect to accounting software like QuickBooks and Xero if you want that data.
Which systems does Kaaj integrate with?
Salesforce, HubSpot, Microsoft Dynamics, Pipedrive, Zoho, LeasePath, LTi Aspire, Uptiq, and Mortgage Automator, plus a REST API and webhooks for any other CRM or LOS, email and drive intake (OneDrive, SharePoint, Google Drive, Dropbox), and SSO. Solifi is documented as a coexistence path, not a certified connector.
Methodology and sources
How this guide was assembled
This guide was written for buyers, not as a vendor ranking. It combines the category questions surfaced in the Kaaj research brief with public first-party product pages and official industry or regulatory guidance. Vendor descriptions are attributed to their own public materials. No prices, ratings, customer outcomes, performance figures, or independent market-share claims are included here.
Editorial record
- Last reviewed
- Author
- Kaaj editorial team
- Scope
- Operations, credit, and IT leaders at SMB lenders, equipment finance companies, MCA funders, brokers, and community banks who want to automate underwriting without replacing their CRM or loan origination system
Kaaj integrations — Kaaj
Kaaj integration methods and named overlays.
Kaaj API documentation — Kaaj
REST API and webhooks.
Heron Data — Heron Data
Vendor product description.
Ocrolus documentation — Ocrolus
API, webhooks, and integrations.
Inscribe — Inscribe
Vendor product description.
Crediflow AI — Crediflow AI
Vendor product description.
Aloan — Aloan
Vendor product description.
Commercial loan origination system — nCino
Vendor product description.
Fundingo — Fundingo
Vendor product description.
Leasepath — Leasepath
Vendor product description.
Abrigo developer documentation — Abrigo
CRM integration and loan boarding APIs.
Origination Suite — LoanPro
Vendor product description.
Keep researching
Related Kaaj resources
Make the next workflow measurable
Bring one representative file and map it end to end.
A useful evaluation starts with the documents, policy questions, handoffs, and exceptions your team sees every week.
Book a workflow review