Intake Questionnaire
1.
Core
What is your business name, where are you based, and which areas do you serve?
Why?
Anchors local SEO, service geography, and how “local” the build and schema need to be.
2.
How long have you been trading/working on this. (idea, under 1 year, 1–3 years, 3+ years)?
Why?
Establishes organisational maturity.
3.
In one or two sentences, what do you do and who do you do it for?
Why?
Gives an authentic value statement for hero copy and navigation priorities.
4.
List your main services / treatments and any packages you currently offer.
Why?
Drives sitemap, service pages and the depth of UX/copy modules required.
5.
What are your top three priorities for this project (e.g. bookings, trust, compliance, internal clarity)?
Why?
Balances hours between Web Build, Compliance, and Training modules.
6.
Do you currently have a website or online booking presence? If yes, please share the links and confirm if you have access to the domain.
Why?
Tells you if this is a first-time build, refresh, or full overhaul. We may need new domains.
7.
Do you have a logo, brand colours, or any existing brand guidelines?
Why?
Determines whether Branding & Assets is light polish vs deeper design work.
8.
Do you have any existing documents (policies, forms, terms, handbooks) you want to keep or adapt?
Why?
Indicates if Compliance & Frameworks can reuse material or start from scratch. Saves time.
9.
Who are your ideal clients (age range, location, profession, key characteristics)?
Why?
Guides tone of copy, imagery, and UX decisions.
10.
How do people usually find you now (word‑of‑mouth, socials, Google, marketplaces)?
Why?
Highlights SEO vs social focus and how much Technical SEO matters.
11.
How do enquiries and bookings currently happen (messages, forms, phone calls, walk‑ins)?
Why?
Shapes the enquiry‑to‑booking journey and operational architecture.
12.
What tools or platforms do you already use (e.g. email providers, booking tools, payment apps)?
Why?
Shows integration requirements and customer software suite.
13.
What pages do you think you need (e.g. Home, About, Services, Pricing, Policies, Gallery, Contact, Blog)?
Why?
Differentiates small Core builds from full Growth or Specialist platforms.
14.
Do you want help writing the copy, or will you provide most of the wording yourself?
Why?
Scales Copywriting & Content hours (quick edit vs full UX‑driven rewrite).
15.
Are there any websites or brands you like (or dislike) that we should use as references?
Why?
Guides visual style, structure, and avoids wasted design exploration.
16.
Do you have any specific accessibility or inclusion needs (e.g. screen‑reader support, colour contrast, language level)?
Why?
Informs how thorough WCAG and UX adjustments need to be.
17.
How comfortable are you with editing a website yourself (beginner, confident, advanced)?
Why?
Determines Training & Support depth (video only vs structured sessions).
18.
Which investment band feels realistic right now (Core, Growth, Specialist)?
Why?
Aligns expectations with your published tiers and frames the proposal.
19.
Growth:
Do you collect personal data (e.g. names, contacts, photos, notes, appointment history) through forms or systems?
Why?
Confirms privacy work and whether basic compliance wording is needed.
20.
Are you registered with, inspected by, or answerable to any regulators, insurers, or professional bodies?
Why?
Flags high impact regulatory risk, requiring formal governance structures and potential third-party liaison work.
21.
Do you already display any legal or policy pages (privacy, cookies, terms, disclaimers)?
Why?
Shows whether you are refining or building the basic compliance shell.
22.
Do you need email automations (e.g. enquiry replies, booking confirmations, follow‑up messages)?
Why?
Expands Copy/UX scope into flows and system structure.
23.
Specialist:
Do you handle any sensitive or special category information (health details, ID checks, minors, safeguarding notes)?
Why?
Indicates need for DPIA/ROPA and deeper Compliance & Frameworks work.
24.
Do you work with high‑risk processes (needles, invasive treatments, chemicals, sharps, heat, confined spaces etc)?
Why?
Triggers COSHH, IPC, H&S manuals and risk‑focused documentation.
25.
Do you currently record incidents, complaints, or near misses? If so, how?
Why?
Tells you what risk tools and logs must be created or redesigned.
26.
How many people (staff, contractors, partners) will need to follow the policies or use the systems?
Why?
Scales governance, training plans, and documentation complexity.
27.
Do you need any custom internal tools or staff‑facing portals (e.g. job tracker, client notes app, workflow dashboard)?
Why?
Switches on the Custom Software module and associated development hours.
28.
Do you need deeper integrations with other systems (payments, booking, CRM, accounting, inventory, messaging)?
Why?
Signals advanced architectural work, testing, and potential ongoing maintenance/support.