This resource belongs to the guide for bankers introducing a client opportunity. It applies when the company being introduced is itself a lender, such as a specialty finance company or an equipment lessor with its own credit team.
The packet template: seven blocks, each answerable in conversation
Each block has a purpose. Together they let SourceX judge whether a review is worth scheduling without anyone moving a record.
| Block | Fields to record | Why SourceX needs it |
|---|---|---|
| 1. Sponsor and scope | Lender type, loan products in scope, sponsor's role | Shows who can authorize a licensing discussion and what the records cover |
| 2. Systems | CRM, document store, servicing system, any spreadsheet used for tracking | Shows where each step of the trail lives |
| 3. Record types | Condition, checklist item, evidence file, approval history, servicing status | Shows which steps are captured as records at all |
| 4. Volume and range | Years retrievable per system; approximate conditions per year | Shows depth, without a sample |
| 5. Join keys | Identifier used in each system and since when | Shows whether a condition can be followed end to end |
| 6. Owners | Admin owner per system; who reviews conditions | Shows who would answer SourceX's questions |
| 7. Unknowns and constraints | Open questions; borrower agreement and privacy notice exist (yes or no) | Keeps the packet honest and flags rights questions for review |
Block 7 records only that borrower agreements and privacy notices exist. Whether any record may be licensed is a rights and privacy question SourceX reviews with the lender, not something a partner judges.
Sample packet from a fictional equipment lender (Illustrative)
A fictional 340-person equipment finance company, filled in during a 40-minute call with its head of credit administration and its CRM admin. Every value is invented.
| Block | Field | Entry |
|---|---|---|
| 1 | Lender type and products | Equipment loans and leases to mid-size manufacturers and contractors |
| 1 | Sponsor | Chief credit officer, with the CFO informed |
| 2 | CRM | Salesforce Financial Services Cloud since 2019 |
| 2 | Document store | Box, one folder per loan, since 2017 |
| 2 | Servicing | Loan servicing platform since 2014, condition and tickler records |
| 2 | Side tracking | Closer spreadsheet for post-closing conditions, 2014 to 2019 |
| 3 | Record types | Approval conditions, document checklist items with approval history, evidence files with versions, servicing condition status |
| 4 | Years retrievable | CRM 2019 onward; Box 2017 onward; servicing 2014 onward |
| 4 | Volume | About 2,500 conditions a year; roughly 60% post-closing |
| 5 | Join key in CRM | Account and loan application on each checklist item |
| 5 | Join key in Box | Loan number in folder name since 2018; borrower name before |
| 5 | Join key in servicing | Loan number |
| 5 | Related-entity links | Account relationships recorded for guarantors since 2021 |
| 6 | Owners | CRM admin; records manager for Box; servicing manager |
| 6 | Condition reviewers | Credit analysts and closers |
| 7 | Box version limit | Unknown; records manager to confirm the plan setting |
| 7 | Approval history export | Unknown until the CRM admin checks |
| 7 | Rebooked deals | Unknown whether checklist items move when a deal changes entity |
| 7 | Borrower agreements and privacy notice | Exist; terms not reviewed |
Read it as a reviewer would. The strongest years are 2019 onward, when all three systems exist and Box folders use loan numbers. 2014 to 2018 depends on a closer spreadsheet. The open questions are specific enough for SourceX to ask the right person.
Fields that never go in the packet
The packet's value depends on what it leaves out. If a field below comes up in conversation, do not write it down.
| Never record | Record instead |
|---|---|
| Borrower names, guarantor names or entity details | "Account relationships recorded since 2021" |
| Loan numbers, amounts or rates | "About 2,500 conditions a year" |
| Any document, screenshot or redacted sample | Record types and the system that holds them |
| Rejection reasons for a particular condition | "Rejection notes kept in approval history" |
| Logins, API tokens or export files | The admin owner's role |
| Personal contact details beyond a business email | The owner's title |
Why three fields matter more than the rest
Join key in CRM. Salesforce's documentation says a checklist item created from an opportunity is associated with that opportunity's account and loan application, and later changes to the opportunity's account or loan application do not update those associations automatically. So "account and loan application" is the honest entry, and "what happens on rebooking" belongs in the unknowns until someone checks.
Approval history. Salesforce's document tracking runs uploaded files through an approval process, and customers upload new versions of rejected documents. If the lender used that feature, the rejection and its reason can survive. Record whether it was used and since when, not what any rejection said.
Box version limit. Box keeps a plan-dependent number of prior versions (for example 50 on Business plans, 100 on Enterprise, unlimited on Enterprise Plus), and admins can adjust it within those limits. That setting decides whether a first, rejected submission still sits beside the accepted one. The records manager can read it from the admin console; nobody needs to open a file.
Collecting the packet in one call
Ask the sponsor to bring the CRM admin and the records manager. Go block by block and read each field as a question. Where a number is uncertain, write a range and mark it as an estimate. Where nobody knows, write "unknown" and the name of the role who would. Close by reading the unknowns back so the lender can correct them.
For per-system starting points, the Salesforce inventory template covers CRM fields, and the Outlook inventory template helps where conditions are chased by email. The companion pages go deeper: the record-chain guide traces one condition through each key, the completeness checklist scores the gaps, and the missing-context comparison shows what a single export gets wrong.
Before introducing, confirm the basics: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. For the covenant side of cures, see equity cure rights; for how a review of records is framed, see what a data audit is.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
When the lender's sponsor has filled in the packet and wants to talk, register as a partner, check who qualifies and read the program terms before you send the introduction.