# Role
You are a Client Intake System Designer who builds questionnaires for service-based businesses that qualify leads, set expectations, and gather all information needed for project success.
# Task
Design a comprehensive client intake form for my [SERVICE_TYPE] business that qualifies prospects, prevents scope creep, and captures everything I need to deliver outstanding results.
# Instructions
**Your Service Details:**
- Service Offered: [YOUR_SERVICE_TYPE]
- Typical Project Duration: [TIMEFRAME]
- Average Project Value: [PRICE_RANGE]
- Biggest Past Project Failures: [WHAT_WENT_WRONG]
- Information You Always Wish You Had Earlier: [MISSING_INFO]
**Client Red Flags:**
[DESCRIBE_PROBLEM_CLIENT_PATTERNS]
Based on this information:
1. **Qualifying Questions Section**: Create 5-7 questions that help you identify whether this client is a good fit (budget awareness, timeline expectations, decision-making authority, previous experience with similar services)
2. **Project Scope Capture**: Design questions that force clients to articulate exactly what they want, preventing vague requests that lead to scope creep later
3. **Success Criteria Definition**: Add questions that make clients define what success looks like in measurable terms, creating shared accountability
4. **Resource and Access Needs**: List what you need from them (logins, files, brand assets, stakeholder availability) with clear deadlines for providing each item
5. **Expectation Alignment**: Include statements they must acknowledge about your process, communication style, revision limits, and timelines
6. **Red Flag Detection**: Embed questions whose answers reveal warning signs (unrealistic timelines, budget mismatch, micromanagement tendencies, unclear authority)
7. **Next Steps Clarity**: End with a clear explanation of what happens after they submit (review timeframe, proposal delivery, deposit requirements)
Format this as a fillable form I can implement using [GOOGLE_FORMS, TYPEFORM, AIRTABLE, or OTHER_TOOL]. Include guidance on which questions should be required versus optional.