P
AI for Automotive F&I Manager

Build a Persistent F&I Knowledge Base with Claude Projects

For F&I Managers

Tools: Claude Pro (Projects feature) | Time to build: 1–1.5 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for basic questions — see Level 3 guide: "Use Claude for Objection-Handling Practice and Roleplay"

What This Builds

A Claude Project is like hiring an assistant who has already read every document you give them and remembers it across every conversation. Unlike a regular AI chat that forgets everything when you close the tab, a Project retains your uploaded documents and custom instructions permanently.

For an F&I manager, this means: upload your lender cheat sheet, product brochures, common objection scripts, and key compliance notes once — and then ask natural questions against that knowledge base every day without re-uploading anything. "Which lender should I try for this deal?" will pull from your actual lender lineup, not generic advice.

Prerequisites

  • Claude Pro subscription ($20/month at claude.ai)
  • Your F&I materials ready to upload: lender list/tiers, product descriptions, compliance notes
  • 1–1.5 hours to set up (ongoing use takes 30 seconds per question)

The Concept

A Project is like having a dedicated coworker who has read your entire F&I playbook. You set it up once — upload your documents, write a brief set of instructions — and every conversation you start within that Project begins with that context already loaded.

Without a Project: every time you ask Claude a question, you start from zero and explain your situation from scratch.

With a Project: you open it and ask "I have a 640 FICO buyer with $35K financed — which lender?" and Claude already knows your lender lineup, typical terms, and what you care about in deal structure.

Build It Step by Step

Part 1: Create the Project

  1. Go to claude.ai and sign in (Pro required)
  2. Look for "Projects" in the left sidebar (may be labeled "Projects" or show a folder icon)
  3. Click "New Project"
  4. Name it something clear: "F&I Deal Desk" or "Finance Office"
  5. You'll see a Project chat page with a sidebar for instructions and files

What you should see: A project workspace with a chat area on the right and a sidebar on the left for "Project Instructions" and "Knowledge."

Troubleshooting: If you don't see "Projects" in the sidebar, your Claude plan may not include it. Check your subscription at claude.ai/account — Projects requires Claude Pro.

Part 2: Write Your Project Instructions

The Project Instructions are a permanent set of directions that Claude reads before every conversation in this Project. This is how you make the AI "know" your role and respond the way you want.

Click "Edit Project Instructions" and paste the following (customize the bracketed sections):

Copy and paste this
You are an AI assistant for an automotive F&I Manager at [Your Dealership Name], a franchised [OEM Brand] dealership. Your purpose is to help with day-to-day F&I work during live deal situations.

ROLE CONTEXT:
- I handle all financing and aftermarket product sales (VSC, GAP, tire/wheel, paint protection)
- I use [RouteOne / DealerTrack] for lender submissions
- My DMS is [CDK / Reynolds / other]
- I see approximately [X] deals per month

HOW TO RESPOND:
- Keep answers under 100 words unless I ask for more
- When I describe a customer profile, give me the 2 most actionable recommendations first
- For compliance questions, give me the plain-language answer and then flag if I should verify with a compliance officer
- Use F&I terminology naturally (FICO, LTV, PVR, reserve, stips, funding, etc.)
- If I paste a lender bulletin or product description, summarize the changes that affect deal submission

REMEMBER:
- I'm often in the middle of a deal when I ask questions. Short, direct answers are better than comprehensive ones.
- Never recommend illegal practices or advise me to misrepresent terms to customers.

Customize the bracketed items with your real dealership info.

What you should see: The instruction text appears in the sidebar and is saved automatically.

Part 3: Upload Your Knowledge Documents

This is what makes the Project valuable. Upload the documents you actually use. You don't need polished PDFs — a rough text file of your lender notes works fine.

Document 1: Your Lender Cheat Sheet Create a text document with your lender lineup. For each lender, include:

  • Lender name
  • General credit tier they serve (prime, near-prime, subprime)
  • Min FICO (approximate)
  • Max LTV they'll approve
  • Max term offered
  • Any notable quirks (e.g., "Ally caps reserve at 2% on used vehicles")

Save it as a .txt or .docx file. In the Project sidebar, click "Add files" and upload it.

Document 2: Your Product Lineup Create a document describing each product you sell:

  • Product name as you present it
  • Coverage summary in 2-3 sentences
  • Common objections customers raise
  • Your strongest response angle for each objection

Document 3: Key Compliance Notes A reference document covering:

  • Your state's specific disclosure requirements
  • OFAC screening process at your store
  • Adverse action notice timing requirements
  • Any recent FTC or CFPB guidance your compliance officer flagged

You don't need to be comprehensive — start with the information you wish you had instant access to.

What you should see: Your uploaded documents appear listed in the Project sidebar. Claude now has access to them in every conversation.

Part 4: Test Your Knowledge Base

Start a conversation in the Project and test it with real scenarios:

Test 1 — Lender guidance: "Customer profile: 660 FICO, $32,000 financed, 72 months, 2022 Silverado. Which lenders should I try?"

Expected output: Claude references your lender cheat sheet and names specific lenders from your lineup with a brief reason for each recommendation.

Test 2 — Product pitch: "Customer just said they don't need a VSC because they're handy and fix things themselves. Give me two response options."

Expected output: Claude draws on your objection scripts (if uploaded) and gives you two natural responses.

Test 3 — Compliance quick-check: "Quick question: do I need to pull OFAC on a customer who is a co-applicant only?"

Expected output: Claude answers in plain language and notes whether to verify with your compliance officer.

What good output looks like: Answers that reference your actual documents — your lender names, your product names, your specific compliance notes — rather than generic information about the automotive industry.

Troubleshooting:

  • Claude doesn't seem to reference my documents: Make sure files uploaded successfully (they should appear in the sidebar). Try asking explicitly: "Based on my lender cheat sheet, which lenders serve 640-680 FICO buyers?"
  • Answers are too long: Add to your instructions: "Always keep answers under 75 words. I'm often between customers."
  • Claude gives outdated information: The uploaded documents are the source of truth for your dealership-specific info. Update them when your lender lineup or products change.

Real Example: A Live Deal Consultation

Setup: You've uploaded your lender cheat sheet, product descriptions, and compliance notes. It's a Tuesday afternoon and you're in the middle of a deal.

The deal: Customer is 52 years old, has a 700 FICO, is financing $44,000 on a new F-150 for 60 months. They've already said "I always pay cash for repairs" when you mentioned the VSC.

What you type in the Project: "52-year-old buyer, 700 FICO, $44K on new F-150, 60 months. Already said 'I always pay cash for repairs.' Which product should I lead with and what's the VSC angle for that objection?"

What Claude returns (drawing from your uploaded docs): "Lead with GAP — 60-month term on a new truck has significant early-period depreciation exposure, and 700 FICO suggests a standard lender without built-in GAP coverage. For VSC: this buyer's 'I pay cash' mindset actually supports the pitch — frame the VSC as keeping cash in their pocket when something does fail, rather than paying $2,000-$4,000 out of pocket at the shop. Ford PowertrainCare or equivalent is the credibility anchor."

The answer draws on your uploaded product descriptions and your objection scripts. Total time: 15 seconds.

What to Do When It Breaks

  • Files suddenly not appearing → Re-upload them. Occasionally Claude Projects loses file references. This is rare but can happen after system updates.
  • Claude giving wrong lender information → Update your lender cheat sheet document and re-upload. The document, not Claude's general training, should be the authority on your specific lineup.
  • Project chat suddenly acting like a regular Claude chat (no document knowledge) → Make sure you opened the conversation within the Project, not in a regular Claude chat. Projects are accessed via the left sidebar folder icon.
  • Hitting message limits → Claude Pro has a higher limit than free, but very long conversations can hit caps. Start a new conversation within the same Project — your documents and instructions are still there.

Variations

  • Simpler version: Use the free Claude tier without Projects, but paste your lender cheat sheet at the start of each conversation. It's more work but tests whether the underlying approach is useful before committing to Pro.
  • Extended version: Add a fourth document — your monthly deal log export from the DMS — and ask Claude to analyze patterns each month. Combine with the Level 3 Lender Rate Negotiation Analysis guide.

What to Do Next

  • This week: Create the Project, write instructions, upload your lender cheat sheet as the first document
  • This month: Add your product descriptions and compliance notes; refine the instructions based on how it responds
  • Advanced: Connect your Otter.ai training call transcripts by uploading them to the Project — your knowledge base grows every time you learn something new

Advanced guide for F&I Manager professionals. Claude Projects requires Claude Pro ($20/month). The Projects feature is available at claude.ai — interface location may change but the core functionality is stable.