How to Build an AI Intake Form for Clients (And Why It Should Be Your First Build)
- An AI intake form is a short web form that collects what you need from a new client and processes it automatically - routing the data, generating a structured brief, and triggering a confirmation - without you doing anything manually.
- Building it yourself with Claude Code takes a few hours and gives you a live demo you can show prospects the same day. The form itself becomes the proof you know what you are doing.
- You can sell the same build to clients in any service business: coaches, consultants, agencies, local businesses. It is a fast first project that often opens the door to a bigger engagement.
What an AI Intake Form Actually Does
Most builders describe an intake form as a form that collects information. That is the boring version. The useful version collects information, processes it, and hands you something actionable - a structured project brief, a qualified lead score, a calendar link pre-loaded with context - before you have spoken to the person.
For your own agency, that means every new inquiry goes through the same filter. You stop spending 20 minutes on discovery calls that should have been disqualified in 90 seconds. For clients who hire you to build one, it means they stop receiving a wall of unstructured email and start getting clean, routed, actionable data from every new lead or customer.
The build is small enough to finish in a focused afternoon using Claude Code in the desktop app. It is also specific enough that you can demo it to a prospect immediately, because the form itself is the proof of skill. There is no portfolio piece more convincing than watching someone interact with something you built while they sit across from you.
The Four Parts of an Intake Form Worth Building
Not every intake form is worth the word AI in front of it. A static HTML form that emails you the results is just a form. The version that justifies a real fee has four moving parts.
| Part | What it does | Why it matters |
|---|---|---|
| The form | Collects structured answers to the right questions | Garbage in, garbage out - the questions determine whether you get a usable brief |
| The processor | Runs the answers through a prompt that generates a structured output | Turns raw text into a brief, a score, a set of next steps - something you can act on |
| The router | Sends the output somewhere useful: email, Notion, a CRM, a Slack channel | Closes the loop so nothing sits in a form response inbox nobody checks |
| The confirmation | Sends the person who filled it out a useful reply | Sets expectations, starts the relationship, and filters out people who put in junk answers |
The four parts of an AI intake form and what each one does
You can build all four of these with Claude Code. The form itself is a React component or a plain HTML page. The processor is a small server function that calls a Claude API endpoint. The router is a webhook or a direct integration. The confirmation is a triggered email. None of it requires a framework you have not used before.
How to Build It in the Claude Code Desktop App
Open Claude Code on the desktop, create a new project folder, and start with a description of what the form needs to do. Be specific about the inputs and the output format. A vague brief produces a form that works technically and fails practically.
- Tell Claude Code the purpose: a client intake form for a web design agency, a lead qualification form for a coaching business, a new customer onboarding form for a local service. Name the specific use case so the questions it suggests are relevant.
- Describe the output: you want a structured brief that includes the project type, timeline, budget range, the client's stated goal, and a one-paragraph summary. Putting this in the prompt means the processor knows what to produce.
- Ask for a simple backend: a Node or Python function that receives the form submission, calls the Claude API with the answers as input, and returns the processed output. The desktop app handles the API integration.
- Add routing: tell Claude Code where the output should go. If you use Notion, say so. If you want a Slack message, say so. The integration code is a few lines and Claude Code writes it.
- Build the confirmation email last: give it the processed output as context so the reply references what the person actually said, not a generic thank-you.
By the time you have gone through those five steps you have a working system. Run it locally, fill it in yourself, and verify the output looks like what you described. That is the demo you show the first prospect who asks what you can build.
What to Charge for This Build
The range for an intake form build is wide because the value delivered is wide. A basic form with email routing and a confirmation is a few hundred dollars. A form that integrates with a CRM, scores leads, generates a brief, routes by category, and triggers a calendar booking is a different conversation.
Frame the price against what it replaces. If a coaching client is spending two hours a week on discovery emails with leads who were never qualified, that is time they put a number on when you ask. The form that filters that down to 20 minutes of reviewing clean briefs has a value that has nothing to do with the hours you spent building it.
A clean starting point: quote the form as a standalone project in the range where you can deliver it confidently in under two days, then add an optional monthly fee for updates, API costs, and support. That structure is covered in more detail in [how to structure client payments with milestones](/blog/structure-client-payments-milestones). The monthly fee matters here because the Claude API has a cost per call that compounds as the form gets used.
Which Clients Buy This First
The clients who buy an intake form fastest are the ones who already feel the pain of unstructured inbound. Coaches and consultants who get rambling emails from leads. Agencies that receive project briefs by voicemail. Local service businesses that get inquiry calls during the hours they are too busy to answer properly.
- Coaches and consultants: they deal with unstructured client inquiries constantly and already pay for tools like Calendly and Typeform, so they understand the category.
- Marketing and design agencies: their own intake is usually a mess because they were too busy building client systems to build their own.
- Local service businesses: home services, bookkeepers, and other trades-adjacent businesses that get leads from Google but have no system for what happens next.
- Online course creators and community owners: they handle new student or member inquiries manually and the volume scales faster than their bandwidth does.
The outreach message for this build is short. Describe what you built for yourself, attach a screen recording of it processing a real submission, and ask if they have the same problem. You are not selling a concept. You are showing them a working system and asking if they want one.
Turning the Intake Form Into the First Step of a Bigger Engagement
The intake form is a strong first project because the handoff reveals what else the client needs. Once you have built it, you have visibility into their lead flow, their CRM or lack of one, their follow-up process, and the gaps in how they turn an inquiry into a paying customer.
That intelligence is worth more than the project fee. Use it to write a one-paragraph summary of what you found and what you would build next if they wanted to continue. Deliver it as part of the handoff, not as a pitch. The clients who have something worth building are easy to identify from inside the system you just shipped them.
This is the same principle behind the audit offer covered in [the audit offer - foot in the door](/blog/the-audit-offer-foot-in-the-door). A small, contained first deliverable that gives you legitimate access to the client's operations and a natural reason to describe what comes next.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What is an AI intake form?
An AI intake form is a web form that collects information from a client or lead, processes the answers using an AI model like Claude, and produces a structured output - a project brief, a lead score, a set of next steps - automatically. The difference between this and a regular form is the processing step: instead of forwarding raw answers to an inbox, the system turns those answers into something actionable before it reaches you.
How long does it take to build an AI intake form with Claude Code?
A basic version - form, processor, email routing, confirmation - takes a focused afternoon using Claude Code in the desktop app. A version with CRM integration, lead scoring, and category-based routing takes one to two full days. The time depends on how many integrations you need and how specific the output format has to be for your use case or your client's.
What does an AI intake form cost to run?
The Claude API cost for processing a typical intake form submission is small - a few cents per submission depending on the length of the answers and the complexity of the output you are generating. For most clients with moderate volume, the monthly API cost is well under the monthly fee you charge for maintenance and support. Pass it through at cost plus a margin rather than bundling it into a flat monthly estimate.
Can I sell an intake form build to a client who is not technical?
Yes, and non-technical clients are often the best buyers because they have no way to build it themselves and they feel the problem acutely. You do not need to explain how Claude processes the answers. You show them the form, show them what comes out the other side, and describe the hours that saves them. The technical explanation is optional - the before and after is the pitch.
Should I build the intake form in a no-code tool instead?
You can, but building it with Claude Code means you own the logic, the integrations are not locked to a specific platform's pricing, and the output format is exactly what you need it to be. No-code tools for forms charge monthly fees that compound, limit what you can do with the processed output, and are harder to customize when the client's requirements change after launch. A coded version also becomes a more defensible service: the client cannot replicate it by subscribing to the same tool.
Last reviewed September 7, 2026.
Co-founder of the Claude Code Profit Room. Went from shipping software to closing paying clients, and now teaches builders the selling half of the equation.
More from David Iya →
