Capvera File Grader
The AI push, done with Grok. Run a complete file — bank statements, processing statements, and the application — through the locked Capvera File Grader prompt to get a classification, a reasoned summary, and a client-ready PDF report before you make the build-or- fund call.
This is a reasoning aid, not the underwriting decision. The AI reads the documents and proposes a classification — Ready for Funding, Build Client, or No. You still own the call, and the senior advisor still closes it.
Set it up once
One project, one locked prompt
Do this a single time. After that, every file is just a matter of dropping the documents in and asking for the review.
Open Grok and create a project
Create a project named Capvera File Grader. Keeping it in its own project means the instructions stay loaded and every review comes back in the same format.
Open Grok AIAdd the File Grader prompt
Paste the full prompt below into the project instructions. Do not edit it — the classification rules, the strict document-only analysis, and the exact output structure are what make the reports comparable across files.
Leave the project open
You will come back to this same project for every client. No need to re-paste the prompt each time.
The prompt
Paste this in exactly
This is the locked prompt. Do not rewrite it, shorten it, or add to it — the classification thresholds inside it are the ones Capvera actually uses, and keeping it identical is what makes one file's report comparable to the next.
Capvera Client File Review Prompt
Capvera Client File Review Prompt
You are reviewing a full funding file for Capvera.
Study every uploaded document (bank statements, application, and anything else provided). Base every number and conclusion only on what is visible. Do not invent figures, fill gaps, or assume.
Capvera classifies every file as one of three outcomes:
Ready for Funding — Deposits are clean, consistent, and already tell a fundable story. Revenue is bankable and the file is not overstacked.
Build Client — One of the following is true:
- Real monthly revenue of $10,000 or more, but a meaningful portion comes through Zelle, Cash App, Venmo, cash, checks, or other non-bankable rails.
- Client is already depositing through bankable rails but is overstacked on existing loans/advances/positions.
No — Monthly true revenue is under $10,000 ($9,999 or below is never a Build), or the file does not currently support funding for any other clear reason.
Output a clean professional summary in this exact structure:
Client File Review
Business: [Name]
Reviewed: [Today's date]
Classification: Ready for Funding / Build Client / No
Summary
One short plain-language paragraph on what the file actually shows and the recommended next step.
Key Findings
Average monthly deposits / revenue:
Deposit consistency:
True business revenue (vs transfers/owner money/funder advances):
Negative days / NSFs:
Existing funder positions / stack:
Time in business:
Card Processing vs ACH
Card processing: [X]%
ACH / other bankable: [X]%
Off-rail (Zelle, Cash App, cash, checks, etc.): [X]%
Why This Call
2–4 short bullets explaining the classification in simple terms. If revenue is under $10k, state that clearly as the reason it is not a Build. If the client is already processing but overstacked, note that.
Recommended Path
Ready for Funding → best-fit Capvera program(s) and any notes.
Build Client → explain why (off-rail deposits and/or overstacked) and the recommended next step (payment rails cleanup/seasoning or stack reduction).
No → main reason(s), including if revenue is under $10k.
Notes
Any red flags, missing items, or strengths the team should know.
After the text summary, also generate a clean, professional PDF report using the Capvera logo. Place the logo centered at the top, with "Heroes Recovery Center" (or the actual business name) and "File Review" centered directly beneath it. Make the overall design spacious, modern, and easy to scan, with clear section headers and well-formatted tables for Key Findings and Card Processing vs ACH.
Keep the entire response concise, accurate, and usable by the Capvera team immediately.Running a file
One client per response
The whole loop, every file. The single most important rule is at the top — one client at a time, or the AI blends two businesses into one report.
Upload everything for ONE client
Bank statements, processing statements if they take cards, and the completed application — all attached in the same message. Do not start a second client in the same response.
One client per response
Let it produce the summary and the PDF
Grok returns the text review in the standard structure, then generates the branded PDF report with the Capvera logo, the business name, and the File Review heading.
Download the PDF report
Save the generated report to your machine. This is the document that goes into the client's file — the text reply is for you, the PDF is for the record.
Add it to Documents in Go High Level
Upload the PDF into the client's Documents tab in GHL, alongside the statements and the application. A report that only exists in the Grok chat is not in the file.
Open the Go High Level guideEvery client after the first
You do not re-paste the prompt. Stay in the same project, upload the new client's documents, and write “do it for this customer too”. The project instructions carry the full prompt forward on every run.
What good looks like
A finished File Review
This is the output from a practice file — logo centered at the top, business name and File Review beneath it, then the findings and the card-vs-ACH breakdown. Aim for a report that reads this cleanly.
Sample — Capvera File Review
Heroes Recovery Center
File Review · practice file
Open the PDFThe PDF is the deliverable. Grok writes the text review in the chat, then builds the branded report as a separate document — that document is what gets filed, not the chat reply.
Every report carries
- The Capvera logo centered at the top
- Business name and File Review beneath it
- The classification: Ready for Funding / Build Client / No
- Key Findings and Card Processing vs ACH as formatted tables
The AI proposes. You decide.
A “Ready for Funding” from Grok is a strong signal, not a green light — you have still read the statements yourself. If the AI and your own read of the file disagree, trust the one you can point at on the page and flag it to the senior advisor.