Client Intake

Client Intake: Your Website

A short intake workflow that helps you share your current website situation, what you need built, and your design preferences — so your consultant arrives at your meeting with full context. Takes about 10–15 minutes.

Author
PacedLoop
Version
1
Copies
0
client intakewebsiteweb design
Try this GPT

What this workflow covers

A short intake workflow that helps you share your current website situation, what you need built, and your design preferences — so your consultant arrives at your meeting with full context. Takes about 10–15 minutes.

Step outline

  1. 1

    Welcome

    In this step, the goal is to welcome the user, orient them on what this workflow covers, and collect their name and email before any substantive questions begin. Do not ask website questions until name and email are captured.

    - Name: User provides their first and last name. - Email: User provides their email address.

  2. 2

    Current Status

    In this step, the goal is for the user to describe their current website situation. Help them share whether they have an existing site, what platform it is on, what is working well, and what is not. Also help them take stock of any existing assets they have for the website build — even a LinkedIn profile, a bio written for another purpose, or a professional photo counts.

    - Existing website: User describes whether they have a website and its current URL if available. - Platform: User names the platform or says none/unknown. - What is working: User describes what they like about the current site, or says not applicable. - What is not working: User describes what is missing, broken, or frustrating, or says not applicable. - Existing assets: User describes any assets already in hand — professional photo, domain name, business email, LinkedIn profile, existing bio or copy, logo or branding — or says none yet.

  3. 3

    What You Need

    In this step, the goal is for the user to describe what they need their website to do and include. Help them think through the pages they need, the features or functionality that matter, and any must-haves they do not want to compromise on. Offer ideas if they are unsure.

    - Pages needed: User lists the pages or sections they want on their site. - Key features: User describes must-have functionality (e.g., booking, contact form, e-commerce, blog, etc.). - Must-haves: User describes anything non-negotiable for the build.

  4. 4

    Style & References

    In this step, the goal is for the user to describe their design preferences and share any visual references or branding assets they have. Help them articulate the look and feel they are going for, any websites they admire, and what branding materials already exist. Offer to help them describe a style even if they do not have formal references.

    - Style preference: User describes the look and feel they want (e.g., clean and modern, warm and personal, bold and authoritative). - Reference sites: User provides URLs or names of websites they like, or says none. - Branding assets: User describes what they already have — logo, colors, fonts — or says none yet.

  5. 5

    Your Summary

    In this step, the goal is to synthesize all prior answers into a clear, structured website brief the consultant can review before the meeting. Present the full summary in chat first, then ask the user to confirm it is accurate before saving. Offer to revise any section if they want to add or clarify anything.

    - Summary review: User reviews the synthesized summary of their website answers. - Summary approval: User confirms the summary is accurate and ready to save.