Pipedrive
Same overlay pattern as other CRMs: ingest the package, return structured analysis, map into the Pipedrive deal you already run.
Moves: Deal notes, custom fields, and document links you map
Stays: Pipedrive pipeline and activity workflow
Integrations
Overlay Salesforce, Dynamics, Leasepath, and your LOS.
Kaaj is an underwriting overlay. It prepares the credit file and writes structured KYB, bank analysis, fraud signals, and memos into Salesforce, Dynamics, Leasepath, HubSpot, LTi Aspire, and the CRM or LOS you already run. Those systems stay the record. You choose the handoff: API, webhook, button, or email.
Systems
Connect Kaaj to the tools you already use
Filter by CRM, origination, intake, or API. Salesforce, Dynamics, Leasepath, HubSpot, and LTi Aspire have a dedicated page for what writes back and what stays in your system of record. Custom stacks use the API docs.
CRM
5How it connects
Salesforce
Write KYB, bank analysis, fraud signals, and the memo into the Salesforce records you already use. Salesforce stays the system of record.
Moves: Structured fields, evidence links, memo, review status
Stays: Opportunity pipeline, funding, and origination objects you already run
Salesforce overlay →How it connects
HubSpot
Keep HubSpot automations. Ingest from email or the deal record, then write analysis back without a second CRM.
Moves: Deal fields, attachments or links, credit-ready outputs
Stays: Pipeline stages, sequences, and HubSpot ownership of the relationship
HubSpot overlay →How it connects
Microsoft Dynamics
Layer underwriting on Dynamics without replacing lease origination. Leasepath shops keep Dynamics as the CRM spine.
Moves: Extracted credit fields and source-linked findings
Stays: Dynamics as CRM of record; quoting, documents, and funding if Leasepath owns them
Dynamics overlay →Zoho
Write bank-statement and KYB outputs into Zoho after analysis. Field list is the map you agree at implementation, not a fixed Zoho app.
Moves: Named fields and files you choose to sync
Stays: Zoho as the lender-facing CRM
LOS and origination
5How it connects
Leasepath
Kaaj is the package-to-memo overlay beside Leasepath. Leasepath stays the Dynamics equipment-finance LOS. Not a replacement.
Moves: Credit file, memo, exceptions, evidence into the deal record
Stays: CRM, quoting, documents, funding, and the lease book on Leasepath
Leasepath overlay →How it connects
LTi Aspire
Intake can start in Salesforce. Extracted credit data writes into Aspire without stuffing the full package into Salesforce.
Moves: Credit fields and decision artifacts into Aspire
Stays: Aspire as origination and lifecycle; files can stay in Kaaj or SharePoint
Aspire overlay →Guide
Uptiq
Kaaj can overlay Uptiq the same way it overlays any origination workflow. Category fit (who owns origination vs the credit file) belongs on the compare hub, not as a dual-run architecture claim.
Moves: Package analysis and memo outputs you map
Stays: Uptiq’s origination role, if that is the system you keep
See platform comparisons →Mortgage Automator
Same overlay: Kaaj works the credit file and writes structured output into the origination system you keep, including Mortgage Automator when that is the record.
Moves: Underwriting outputs you map
Stays: Origination, closing, and servicing on Mortgage Automator
Guide
Solifi
Source-led discovery guide for a possible Kaaj layer beside Solifi. It does not claim a certified Solifi connector.
Moves: Only what a later field contract allows
Stays: Solifi as the secured-finance operating platform until a live handoff is scoped
Read coexistence guide →Intake
2OneDrive
Ingest deal files from OneDrive, SharePoint, Google Drive, or Dropbox. Storage is intake, not the system of record.
Moves: Approved files into Kaaj for analysis
Stays: The lender’s drive as the file store if that is policy
Shared inboxes and forwards. Deduplicate against CRM-triggered deals so the same package does not run twice.
Moves: Attachments and message context into the package
Stays: Your mail system; analysis credits can wait for a button if you want
API and auth
3Docs
REST API
Full REST path for custom LOS, CRM, or internal underwriting tools. You choose identifiers (EIN, deal ID, email token) to join systems.
Moves: Package in; JSON findings, exceptions, and memo fields out
Stays: Your origination schema and unique keys
Open API docs →Docs
Webhooks
Async completion notices when analysis finishes. Prefer this when a CRM API times out around two minutes.
Moves: Status and payload to a URL you control
Stays: Retry, auth header, and mapping on your side
Open API docs →SSO / SAML
Enterprise sign-on for credit and ops seats. Separate from the data handoff into CRM or LOS.
Moves: Identity assertions for Kaaj access
Stays: Your IdP as the source of user truth
Handoff
However you want to connect
There is no single required connector. Pick the trigger your ops team will actually run, then map fields into objects you already own. Endpoints, auth, and payloads are in the API documentation.
REST API
Push a package in and pull structured findings, exceptions, and memo fields out. You own the mapping into your objects.
Webhook
Kaaj posts JSON when analysis finishes. Your team maps the payload. Useful when Salesforce times out on a long synchronous call.
Button or manual trigger
Credit or ops fires analysis on the files they choose, so credits do not run on every inbound email or portal upload.
Email and file drop
Ingest from a shared inbox, OneDrive, SharePoint, Google Drive, or Dropbox, then write the result back to the system of record.
What moves
Structured KYB, bank and MCA findings, fraud signals, exceptions, memo fields, and evidence links — mapped onto the records you designate.
What stays
The CRM or LOS as system of record. Pipeline, quoting, documents, funding, and bureau pulls you already run. Human credit authority.
FAQ
Direct answers
Connect the overlay
Bring the CRM or LOS you already run
We will map the trigger and the field list onto your objects. No rip-and-replace.
Book a working session →