Before anyone can sign in to Microsoft 365, they need their own user account. An account on its own isn't enough, though: until it has a license, the person can't use Outlook, Teams, SharePoint or Power Apps. The Microsoft 365 admin center creates the account and assigns the license in one short wizard. You'll use it here.
The last part turns the Lead Qualifier into something you can change without fear. You test the whole API, every failure from Part 6 included, with a fake that stands in for Claude, so the tests run in a fraction of a second and never cost a cent. Then you add a quality gate and a README, release version 1.0.0, and look back at everything you built.
Every service that depends on another service will one day see it fail. In this part the Lead Qualifier learns to fail well. Every problem with Claude becomes a clear HTTP response the caller can act on, slow requests stop at a timeout, and every lead writes one log line with its cost. That line says nothing about the customer.
Claude now reports the facts about every inquiry. In this part your own code turns those facts into a decision: a lead score from 0 to 100, a priority, and the reason behind every single point. The rules fit on one screen, a salesperson can read them, and a tricky sender cannot talk their way to the top of the list.
This is the part where the Lead Qualifier starts thinking. You write the instructions Claude follows, send each inquiry to Claude with the official Python SDK, and get back a validated LeadAnalysis every time. By the end, a real sales inquiry goes in through your API and comes back as clean, structured JSON in about five seconds.
Before you ask Claude to qualify a lead, decide exactly what a qualified lead looks like. In this part you design that shape as Pydantic models. Claude will be forced to follow it, your code will rely on it and your CRM will receive it. Then you lock it in with tests that run in under a second and never cost a cent.
Before the agent can read a single inquiry, it needs a proper home. In this part you build the project the way production teams do: one command creates it, every package version is locked, your Claude API key is loaded safely from a file Git never sees, and a running FastAPI app answers its first request.
Most businesses still sort their incoming inquiries by hand. Someone reads every contact-form message and email, decides who is a real buyer, and types a reply. This series builds an AI agent that does the first pass in a few seconds: it reads an inquiry, pulls out the key details, scores it, drafts a reply, and hands everything back as clean JSON a CRM can use.
Every app that talks to Claude, from a ten-line script to a full AI agent, needs an API key. Getting one takes about two minutes in the Claude Console. This guide shows every screen, explains each setting, and covers what most guides skip: storing the key safely, paying for usage and replacing a key later.
You do not need a terminal to get code from GitHub onto your computer. Visual Studio 2026 clones a repository in a few clicks, either from the URL GitHub gives you or straight from your GitHub account, and this guide walks through both routes screen by screen.
