Getting started / Planning notes
Start with a useful brief, not a shopping list.
A few questions to connect a website or systems project to the change you actually need.
Name the change first
Before choosing features, describe what should become easier. It might be understanding your offer, reaching the right person, or keeping track of an enquiry. A concrete problem gives the conversation a useful starting point.
Separate what exists from what is assumed
List the website, content and processes already in place. Then list the unknowns: permissions, missing assets, ownership or timing. An honest unknown is more useful than an assumption hidden inside the scope.
Define the next decision
A first conversation does not need to solve the whole project. It should help identify the next question, the evidence needed and who can answer it. That makes the following proposal more deliberate.
A planning note, not a personalised recommendation. Use the assessment to explain your starting point for human review.
Explore the assessment