Skip to content
Morris Standard Talk to Ian

Website design questionnaire

Build the brief before we build the website.

Use this questionnaire to give Morris Standard the business context, customer priorities, content, functionality, AI opportunities, visibility and practical constraints behind the project. You do not need to know every answer before you begin.

Begin the questionnaire ↓Talk to Ian →
BusinessPurpose firstCustomersClear journeysAIOnly where usefulScopePractical constraints
The project briefSeven connected chapters
01—07
  1. 01
    BusinessContext, offer and reason for the project
  2. 02
    CustomersAudience, decisions and useful outcomes
  3. 03
    WebsiteCurrent site, brand, content and direction
  4. 04
    FunctionFeatures, commerce and integrations
  5. 05
    AI & automationUseful roles, boundaries and human control
  6. 06
    VisibilitySearch, location and marketing
  7. 07
    ScopeBudget, timing, approvals and constraints
Unknown is a valid answer.Leave genuinely undecided points open rather than inventing certainty.

Before you begin

A useful brief explains the business before it lists the pages.

There is no score to chase. The purpose is to make the first design and technical decisions better informed.

01Use real examples.

Current frustrations, customer questions and day-to-day work are more useful than polished marketing language.

02Leave unknowns open.

You do not need to choose the platform, technology or final feature set before the requirements are understood.

03Think in outcomes.

Explain what customers and staff should be able to do more easily when the project is working properly.

04AI is optional.

If AI has a useful job, define it. If it does not solve a real problem, there is no need to force it into the project.

01 — Business: Start with the commercial context.
Which best describes the project?
02 — Customers: Define the people and the decisions.
03 — Website: Keep what works. Change what does not.
04 — Function: Describe the jobs the website must do.
Known features or capabilities
05 — AI & automation: Decide whether AI has a useful job.
Would you like AI considered as part of the website or wider workflow?
What could AI usefully help with?Select any that sound relevant. “Not sure” is a useful answer if you want advice.
How much human review should AI outputs or actions have?
06 — Visibility: Connect the website to how customers find you.
Current or planned marketing channels
07 — Scope: Put the practical constraints on the table.

Need more time?Save the answers you have so far and return later. The draft is stored privately in WordPress and a secure link is emailed to the address entered above; the link stays valid for 30 days from your latest save, after which the unfinished draft is deleted automatically.

Ready to send?You can still discuss or change the scope after this. The questionnaire is a starting brief, not a fixed specification.

What happens next

The answers become a working brief — not an automatic quote.

Business context, customer needs, functionality, AI choices and practical constraints are considered together before a solution is proposed.

  1. 01Ian reviews the context

    The brief is read as a connected business problem rather than a list of requested pages.

  2. 02Unknowns stay visible

    Anything that still needs evidence, access or a conversation is identified rather than guessed.

  3. 03The next step is agreed

    That may be a proposal, a review, a narrower discovery task or a direct conversation before scope is fixed.

A practical next step

Prefer to talk it through instead?

A questionnaire is useful when you want to organise the detail in writing. If the project is still difficult to define, a direct conversation may be the better first step.

Direct with IanClear scopePractical recommendationNo unnecessary layers
Talk to Ian →Start a project →