Automated Underwriting

Main Issue

Bank statements were processed manually, downloaded from DocuSign, uploaded to MoneyThumb, and entered into Pipedrive. This slowed underwriting and required dedicated staff time.

Main Goals

  • Eliminate manual processing
  • Automate underwriting analysis
  • Automatically update the CRM

How These Goals Were Achieved

  • Automated intake directly from DocuSign
  • Implemented an AI step in Zapier to clean and normalize bank statement URLs
  • Sent structured data via webhook to Make only when three bank statements are present
  • Integrated MoneyThumb API for automated underwriting analysis
  • Automatically uploaded underwriting results and reports into Pipedrive to the correct deal

Automated Workflow

1. Client Submission

  • A client completes a DocuSign form.
  • The submission includes client information and three bank statements.

2. Zapier / AIĀ 

  • When the DocuSign is completed, Zapier triggers.
  • Zapier creates a new deal and person in Pipedrive.
  • An AI step in Zapier normalizes and cleans the bank statement URL strings.
  • Zapier then sends a structured webhook (with the cleaned URLs and deal ID) to Make.com only if the person uploaded three bank statements.
svg+xml;charset=utf

3. Processing in Make + MoneyThumb

  • Make receives the webhook with the three bank statements and deal ID.
  • The three bank statements are sent to MoneyThumb via API.
  • MoneyThumb analyzes them and returns an Excel underwriting report.
svg+xml;charset=utf

4. Automatic CRM Update

  • Make receives the Excel output.
  • The underwriting Excel report is uploaded directly into Pipedrive to the correct deal.
svg+xml;charset=utf
svg+xml;charset=utf