Kaaj raises $3.8M in seed funding to power the future of small business lending 🎉Read more

Salesforce overlay

Kaaj sits on Salesforce. It does not replace your LOS.

Yes. Kaaj is an underwriting overlay on Salesforce: the package comes in from email, portal, button, or API; Kaaj prepares KYB, bank and MCA analysis, fraud signals, and a source-linked memo; structured output writes into the Salesforce objects you already use. Salesforce and the LOS stay the system of record. You choose the trigger so analysis credits only fire on files you intend.

Map this overlay →All integrations

What moves

Into Salesforce

Credit outputsStructured KYB, spreading, exceptions, fraud signals, and memo fields you map.
EvidenceLinks or selected files so an underwriter can open the source without a second filing step.
StatusReview state so ops can see analysis finished without living in a sidecar-only tab.

What stays

Still your system of record

System of recordOpportunity, account, and origination objects you already run. Kaaj does not become the LOS.
Bureau pullsExisting Equifax, Experian, or PayNet paths can stay in Salesforce. Kaaj is not an FCRA takeover.
Documents (optional)Full packages can stay in Kaaj, SharePoint, or OneDrive if you do not want hundreds of Salesforce attachments.

Handoff

However you want to connect

Button, webhook, API, or email. Use a manual button when you do not want every inbound file to spend a credit. Use a webhook when Salesforce would time out on a long synchronous call. Map results into existing objects; a sidecar tab alone is not the default. 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

  1. 01

    Name Salesforce as CRM of record and name the LOS if it is separate (Aspire, Leasepath, nCino, or other).

  2. 02

    Pick the trigger: button, webhook, API, or email. Separate buttons for KYB, bank statements, and invoices if you want feature-level spend control.

  3. 03

    Stand up a sandbox and a least-privilege integration user. Partial sandbox is enough to start UAT; full-copy is a lender choice.

  4. 04

    Agree the unique deal key so Salesforce and email cannot double-create the same application.

  5. 05

    Run 5–10 production-like packages in sandbox before go-live.

FAQ

Salesforce overlay questions

Can AI underwriting sit on top of Salesforce without replacing our loan origination system?

Yes. That is the architecture. Salesforce and the LOS remain the record. Kaaj overlays package intake, completeness, KYB, bank and MCA analysis, fraud review, memo, and writeback.

Can extracted financials and KYB write into existing Salesforce objects, not only a sidecar tab?

Yes. The field map is yours. Kaaj returns structured outputs; your team maps them onto the objects and permission sets credit and funding already use.

Can we use a button instead of an automatic webhook?

Yes. A manual Salesforce button is a supported trigger so analysis only runs on files you choose. Webhooks and APIs are available when you want completion posted back asynchronously.

How do we stop duplicate applications when Salesforce and email both trigger the same deal?

Agree one unique identifier (deal ID, EIN plus application, or a subject token) and treat one channel as the creator. The other channel attaches to that record instead of opening a second application.

Should we wait to integrate until after we migrate from Dynamics, Aspire, or TurboLease to Salesforce?

No. Overlay the system you run today. Kaaj does not require a Salesforce migration to start. If you later move CRM, the same overlay pattern maps to the new objects.

What Salesforce objects and permission sets does the integration user need?

A least-privilege integration user that can read the intake objects and write the mapped output fields. Exact objects depend on your org. Confirm in sandbox with credit and funding before production.

How long does Salesforce onboarding take?

Public materials describe a focused overlay pilot in days, and the homepage states live in two weeks for a scoped workflow. Sandbox, field map, and security review set the actual calendar. It is not a guaranteed SLA for every org.

Continue

Related pages

All Kaaj integrations →Named CRM, LOS, intake, and API overlays. You choose the handoff method.Kaaj vs. Northteq →Northteq Aurora is a Salesforce-native equipment-finance LOS. Kaaj is the overlay beside it.Kaaj + Microsoft Dynamics →Same overlay on Dynamics when Salesforce is not the CRM.Kaaj + LTi Aspire →Salesforce intake with writeback into Aspire, without storing the package in Salesforce.Data security →SOC 2 Type II public posture and trust-center path for security review.Kaaj product →Package intake through memo, with human review before the handoff.