HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Finance and data

Private Credit Surveillance Engine

For private credit funds and direct lenders: 11 Claude prompts that monitor covenants, recalculate the borrowing base, read amendment redlines, and draft the LP note, on documents that never leave your own tenant, so a covenant drift is caught before quarter end, not after.

Free — runs in your own ClaudeMedium setup · 4 steps11 ready-to-run prompts
Set it up free — takes 3 minutes ↓Or have us wire it in →
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. 1

    Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. 2

    Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first — it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/moodys-surveillance-kill#the-vault . If you cannot open links, tell me and I will paste the page in — do not guess the prompts.

I want to set this up properly so Claude runs surveillance on my private credit book on real documents, not a one-off chat. Walk me through it step by step, do not skip anything. Treat me like a credit professional at a fund who has never built a Claude Project and does not write code. Define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is a private Claude Project where the credit agreements, compliance certificates, and borrower financials live so every prompt reads from one place.

## The setup — a private Claude Project
Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a Team or Enterprise plan so my deal data stays in my tenant and is excluded from training. Pin **Claude Opus 5**. Nothing to install.
2. **Make the workspace.** In Claude, create a new **Project** named for the facility or the fund. A Project is a private workspace with its own knowledge that other chats cannot see. My credit documents stay in my own tenant; consultance never sees them.
3. **Load the credit file.** Drop the credit agreement, the latest compliance certificate, the borrowing base certificate, the borrower financial statements, and any amendments into the Project knowledge. PDF is fine.
4. **Run the vault.** Run prompt 01, the onboarding router, pick the facility and where the data lives. Then run 02 onward: covenant check, borrowing base, amendment redlines, the portfolio roll up, the LP note, the financial spread, the watchlist call, the timeliness signal, the living memo, and the surveillance playbook.
5. **Keep the judgment.** Every prompt outputs for a credit professional to review. Nothing here contacts a borrower or moves money. A named human owns every call.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, covenant, headroom, borrowing base, advance rate, eligibility, add back, leverage, coverage, watchlist, redline.
- Do NOT tell me a step is "not possible." If I cannot find the Project button, it is in the left sidebar of claude.ai.
- Never paste data I am not allowed to share into a public chat. Use a Project with my tenant controls. The whole point is the documents never leave my environment.
- This monitors the book and flags drift early. It does not replace credit judgment or the IC. Not legal, tax, or investment advice.

First message: ask me "Which facility do you want to set up first, and do you have its credit agreement plus the latest compliance certificate ready to upload? Or do you want to start with a portfolio wide covenant roll up across the book?" Then start step 1.
Step 2 · run it on your data

Step 1 set it up. These 11 prompts do the work.

the vault

The 11 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 11 prompts, numbered, in order · nothing left out.
You are my private credit surveillance engine. Ask me one question at a time to set up: which facility or facilities am I monitoring, where does the data live (uploaded to this Project, pasted, or a connector my firm approved), which documents do I have (credit agreement, compliance cert, borrowing base cert, financials, amendments), and am I monitoring one name or rolling up the whole book. Once I answer, confirm the scope back as a checklist and tell me which of the prompts that follow apply. Do not start analysis until I confirm.
Here is the credit agreement and the latest compliance certificate for this facility. Extract every financial covenant with its exact definition and threshold. Calculate each one from the certificate. For each, output covenant, limit, actual, headroom, and status. Flag anything within 15 percent of its limit as drifting, and show the math so I can check it. Do not accept the borrower's own calculated compliance without re deriving it.
Here is the borrowing base certificate and the eligibility criteria from the credit agreement, plus the prior period certificate I am pasting below. Recalculate availability: eligible receivables after the concentration and aging exclusions, apply the advance rate, subtract reserves, compare to the commitment. Show every exclusion you applied and flag any collateral that moved from eligible to ineligible since the prior cert.
Here is the original credit agreement section and the proposed amendment redline. Tell me in plain terms what changed, whether each change is borrower favorable or lender favorable, which covenants or definitions it touches, and any new carve out or basket that widens what the borrower can do. Flag anything that weakens our position or our ability to monitor.
Here are the latest covenant results for all facilities in the portfolio, pasted as a table. Rank every facility by tightest headroom. Group any facilities sharing a sector, a sponsor, or a covenant type that are all drifting in the same direction. Tell me where I have correlated risk building across the book, not just one name. Give me the three names to look at first and why.
Using the covenant results, borrowing base changes, and any amendments this quarter, draft the LP surveillance note: portfolio health summary, facilities on watch with the specific reason, any breaches and the remedy status, and material changes since last quarter. Institutional tone, specific numbers, no filler. Mark anything you cannot support from the data as needing my input.
Here are the borrower financial statements for the last two periods. Spread them into a standard credit template: revenue, EBITDA, adjusted EBITDA with the add backs identified, leverage, coverage, and free cash flow. Flag any add back that looks aggressive or new versus the prior period, and any line that moved more than 20 percent without an obvious reason.
Here are my watchlist criteria and this facility's current metrics: leverage, coverage, headroom trend, and payment history. Apply the criteria mechanically and tell me whether this name should be on the watchlist, at what level, and which specific trigger it hit. If it is close but not over, tell me exactly what would tip it.
Here is the reporting and payment history for this borrower over the last 12 months: due dates and actual dates for compliance certs, financials, and interest payments. Find any trend toward lateness, any pattern of just barely on time, and flag it. Early lateness is often the first soft signal of stress. Give me a punctuality trend, not just a count.
Here is the original credit memo and the changes since: amendments, covenant results, and financial updates. Produce a current state memo that carries forward the original thesis, marks what has changed, and states whether the original investment case still holds. Flag any change that contradicts the thesis we underwrote.
Interview me about how we monitor this book, one question at a time. Build the surveillance playbook: every facility, what gets checked, on what trigger, from which document, and the escalation path when something drifts. Output it so a credit analyst who has never seen the book could run monitoring next month.

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit

Rent it forever, or own it once.

For private credit funds and direct lenders: 11 Claude prompts that monitor covenants, recalculate the borrowing base, read amendment redlines, and draft the LP note, on documents that never leave your own tenant, so a covenant drift is caught before quarter end, not after.

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

The vault runs surveillance on documents you load by hand. Consultance wires it into production inside your own environment: fund administration and data room feeds connected so covenants and borrowing bases recalculate the moment a cert lands, alerts routed to the right credit officer, an audit trail your LPs accept, and portfolio wide roll up across every facility. Reply "wire it" for a 30-minute slot.

Book a build call →
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. This is the lender's own surveillance and monitoring support, not a credit rating and not independent valuation. It does not replace credit judgment or the investment committee. A named human owns every call. Your data stays in your own Claude tenant, we never see it. Not legal, tax, or investment advice.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Finance and data

Free Portfolio Quant Research Desk

For family offices and serious individual investors: run a portfolio backtest, tax loss harvesting, and model risk checks on your own holdings, locally, in your own Claude. Replaces the $250k quant seat you would otherwise hire.

Setup guide →
Finance and data

Private Equity Deal Sourcing Playbook

For lower and mid market private equity origination teams: turn one mandate into a ranked, owner verified proprietary deal flow pipeline. Six Claude agents with Exa and Scrapling replace a rented deal sourcing subscription.

Setup guide →
Finance and data

Free Jira Alternative for Deal Teams

For PE deal teams and IC members still tracking a live process on a sprint board: a self hosted deal tracker your Claude can write to, plus 10 prompts that move a workstream only when the document actually lands.

Setup guide →
Get the free kitBook a call

manual now, installed when you're ready

What you have

The free version above. It runs this read on a file you paste in, in your own Claude. Yours to keep.

What we install

The same read, wired into your private credit stack, running the second a report lands. Nothing to upload, no new login.

See the installed version

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is Private Credit Surveillance Engine?

Private Credit Surveillance Engine is a finance and data build in the consultance.ai AI Build Library. For private credit funds and direct lenders: 11 Claude prompts that monitor covenants, recalculate the borrowing base, read amendment redlines, and draft the LP note, on documents that never leave your own tenant, so a covenant drift is caught before quarter end, not after. It fits Private credit funds, direct lenders, PE credit teams, and family offices with a private debt sleeve who pay for surveillance software plus an analyst and still find out about a covenant slip too late. Setup difficulty is Medium, with 4 plain-English steps.

What does Private Credit Surveillance Engine do?

For private credit funds and direct lenders: 11 Claude prompts that monitor covenants, recalculate the borrowing base, read amendment redlines, and draft the LP note, on documents that never leave your own tenant, so a covenant drift is caught before quarter end, not after.

Who is Private Credit Surveillance Engine for?

It fits Private credit funds, direct lenders, PE credit teams, and family offices with a private debt sleeve who pay for surveillance software plus an analyst and still find out about a covenant slip too late.

How hard is Private Credit Surveillance Engine to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 11 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The vault runs surveillance on documents you load by hand. Consultance wires it into production inside your own environment: fund administration and data room feeds connected so covenants and borrowing bases recalculate the moment a cert lands, alerts routed to the right credit officer, an audit trail your LPs accept, and portfolio wide roll up across every facility. Reply "wire it" for a 30-minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. This is the lender's own surveillance and monitoring support, not a credit rating and not independent valuation. It does not replace credit judgment or the investment committee. A named human owns every call. Your data stays in your own Claude tenant, we never see it. Not legal, tax, or investment advice.

Want this built into your workflow?

Private Credit Surveillance Engine is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book your free AI audit