LTi Aspire overlay

Salesforce can take the package. Aspire keeps the book.

Kaaj overlays LTi Aspire. Intake may start in Salesforce, email, or a portal. Kaaj completes KYB, document and bank work, and the memo, then writes extracted credit data into Aspire. The full document set does not have to live in Salesforce. Aspire stays the equipment-finance origination and lifecycle system. Kaaj does not replace Aspire. You choose the handoff.

Map this overlay →All integrations

What moves

Into LTi Aspire

Credit data into Aspire	Mapped fields and decision artifacts after analysis, not a retyped spreadsheet.
Evidence links	Pointers to the package in Kaaj or SharePoint when Salesforce should not hold the files.

What stays

Still your system of record

Aspire	Origination, asset, and lifecycle records Aspire already owns.
Salesforce (if used)	Can remain the intake CRM without becoming the document warehouse.

Handoff

However you want to connect

A common pattern is Salesforce or email in, Kaaj analysis, Aspire writeback, files in Kaaj or SharePoint. Button, webhook, or API — whichever your ops team will actually run. API docs.

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.

Implementation

Scope the field map before go-live

01
Name Aspire as origination of record.
02
If Salesforce is intake-only, do not store the full package there.
03
Map the unique application ID across Salesforce, Kaaj, and Aspire.
04
UAT writeback on a non-production Aspire company first.

FAQ

LTi Aspire overlay questions

Can extracted credit data write back into Aspire after Salesforce intake without storing documents in Salesforce?

Yes. That is a supported overlay pattern: Salesforce or email for intake, Kaaj for the credit file, Aspire for the origination record, files in Kaaj or SharePoint.

Does Kaaj replace LTi Aspire?

No. Aspire is full-lifecycle equipment-finance software. Kaaj is the package overlay beside it. Score replacement questions on Kaaj vs. LTi.

Do we need to finish a Salesforce migration before Aspire writeback?

No. Overlay the stack you run. If intake is already in Aspire or email, skip Salesforce as a requirement.

Continue