Claude Design Client Intake Form Solo Practitioner

Claude Design for solo practitioner client intake is the cleanest first build I'd recommend to any solo or two-attorney practice testing the tool. Anthropic shipped Claude Design on April 17, 2026, and the math for solos is the simplest in the legal-ops landscape: a $20/month Claude Pro subscription replaces three or four overlapping SaaS tools and gives you a branded, mobile-responsive intake form you actually own. The traditional path is renting Clio Grow at $99/month, Lawmatics at $200+/month, or jamming Typeform/Calendly/HoneyBook into a Frankenstein workflow. The build path with Claude Design is one prompt for the form, one for the calendar, one for the conflict question — total time under two hours. This walks through how I'd build it, what fields actually matter for a solo practice, and where the form is good enough versus where you still want a real intake platform. Pricing pulled from the Anthropic pricing page.

What a solo practitioner's intake form actually needs

Solos overbuy intake software. The job is small: capture enough information to (1) decide whether to take a consultation, (2) run a conflicts check, (3) schedule the consult if it's a fit, and (4) start the engagement-letter process. That's it.

The fields that actually matter for a single intake form:

- Contact basics, name, email, phone, how they found you. - Matter type, short list (5-10 options) tied to your practice areas. Don't make it a freeform text field. - Counterparty information, the other party's name and any related entities you're aware of. This is the conflicts trigger. - One-paragraph problem statement, what they're dealing with, in their words. Caps at 500-1,000 characters. - Urgency, three options (this week / this month / no rush), not a freeform date. - Current representation, are they currently represented or have they been on this matter? - Consent + disclaimers, explicit checkbox for "I understand submitting this form does not create an attorney-client relationship."

Everything else (budget questions, document uploads, calendar embed) is an optional second step, not the first form. The first form's job is to get enough information to decide and route. A 12-field form converts measurably better than a 25-field form across most legal verticals.

This spec fits in a single Claude Design prompt. The Claude Design for legal operations 2026 anchor covers the broader pattern of right-sized internal builds.

The actual prompt sequence

Open Claude Design on Claude Pro ($20/month per the pricing page, solos don't need higher tiers). First prompt:

*"Build a client intake form for a solo law practice. Single-page, mobile-first. Sections: contact basics (name, email, phone, referral source), matter type (dropdown with 6 practice areas, I'll list them), counterparty information (name + related entities textarea), one-paragraph problem statement (500-character cap), urgency (3 radio buttons: this week / this month / no rush), current representation (yes/no), consent checkbox with attorney-client disclaimer. Submit button."*

Attach your existing site or brand guideline. Claude Design extracts colors, typography, spacing as defaults. Iterate until the form looks like your practice, usually two or three rounds, ten minutes total.

Second prompt: *"Add a confirmation screen after submit. Thank-you message, expected response time (within X business hours), what happens next, link back to homepage."*

Third prompt: *"Add a privacy/disclaimer footer. Link to privacy policy, link to terms, line saying 'Submitting this form does not create an attorney-client relationship.'"*

For most solos, this prototype is shippable as-is. If you want it deployed on your own domain with form submissions hitting your email or a database, hand off to Claude Code: *"Deploy this form at intake.[mydomain].com. Send submissions to [my email] and store them in a [Supabase / Airtable / Google Sheets, pick one] table for follow-up tracking."*

Claude Code handles the deployment and form-handler wiring. For solos, deployment costs $0-$20/month on services like Vercel or Netlify. Total tooling cost: $20/month for Claude Pro plus optional hosting. The how to use Claude Design in Claude Code legal workflow covers the deployment handoff in detail.

When this beats Clio Grow, Lawmatics, or HoneyBook — and when it doesn't

Where the build wins for solos:

- Cost. Claude Pro is $20/month flat. Clio Grow standalone is around $99/month, Lawmatics ranges from $200-$400/month, HoneyBook is $39-$79/month plus payment processing fees. Over a year, the build saves $200-$4,500 depending on which platform you'd otherwise pick. Across multiple builds (intake, scheduling, basic CRM), the savings compound. - Customization. A platform's intake form is what the platform allows you to configure. A built form is exactly what you want. For solos with specific intake patterns (contingency-fee personal injury asking different questions than estate-planning intake), this matters. - Branding. Your form lives at your domain, in your brand. No "Powered by HoneyBook" or generic SaaS chrome. - Data ownership. Submissions land in your database. No vendor sitting between you and your client data.

Where the platform still wins:

- Built-in conflicts integration. Clio Grow's integration with Clio Manage's conflicts module is real value if you already run Clio. A built form doesn't auto-check conflicts, you do, manually or via Claude. - Built-in calendar + payments. If you want a single tool for intake → consultation booking → retainer payment, HoneyBook or Lawmatics handles that flow turnkey. A built form requires you to wire in Cal.com / Calendly / Stripe yourself, which Claude Code can do, but it's not free incremental work. - Pipeline tracking. A platform's CRM views (lead → consultation → retained → matter open) come built-in. A built form lands submissions in a database; the pipeline tracking you build separately or layer in another tool. - Compliance certifications. SOC 2, HIPAA, etc., platforms publish these. A self-built form is as compliant as your hosting setup.

My take: for solos handling 10-30 intakes per month with clear practice areas, the build wins on cost and customization. For solos handling 50+ intakes per month who want pipeline tracking, payment processing, and conflicts integration in one tool, a platform like Clio Grow probably still wins. The is Claude Design good for non-designer legal teams covers the broader fit question.

Privacy, security, and the attorney-client disclaimer

Three things solos typically get wrong on self-built intake forms:

One, the attorney-client disclaimer. Submitting an intake form does not create an attorney-client relationship. Most state bar rules and ethics opinions are clear on this, but the form itself needs to say it explicitly. Put the disclaimer near the submit button in plain English, and have the user check a box acknowledging it. Don't bury it in a privacy policy footer. This protects you on the unsolicited-information side: a prospective client sharing case details on your form before you've cleared conflicts and accepted the engagement creates a duty-of-confidentiality issue if you don't have explicit terms in place.

Two, the data-handling story. Where do submissions go? If they land in a Google Sheet or your inbox, that's defensible for low-volume practice but it's also discoverable. For matter-related information, store submissions in a database with proper access controls and a retention policy. Claude Code can wire submissions to a Supabase or Postgres table with role-based access without much extra effort.

Three, the model-deployment surface. If your form uses Claude in any backend logic (auto-categorization, drafting first response, etc.), use Claude Team or higher per the Anthropic pricing page. Anthropic does not train on Team, Enterprise, or API inputs. Consumer Claude does not carry the same commitments. United States v. Heppner (SDNY, February 17, 2026) ruled that consumer Claude communications are not protected by attorney-client privilege or work-product doctrine — see the Heppner explainer for the deployment-surface implications. For an intake form that's just collecting information without AI in the loop, Pro is fine. For anything that processes submissions through AI, step up to Team.

The second-order read: most solo practices will run this form on Claude Pro with manual review of every submission, not AI auto-routing. That's the right deployment surface for the volume.

The Bottom Line: The verdict: for solos handling 10-30 intakes per month, a Claude Design-built intake form on a $20/month Claude Pro subscription beats Clio Grow, Lawmatics, and HoneyBook on cost and customization. The form ships in under two hours, lives at your domain, and stores submissions in a database you own. Where the build loses is integrated pipeline + payments + conflicts — if you need those in one tool, a platform like Clio Grow still wins. Don't skip the explicit attorney-client disclaimer near the submit button.