The project type dropdown uses three phrases, not three categories

The contact form has a project type field with three options. A new website. An accessibility audit or fixes. Not sure yet, let us talk. The options are not database categories or internal labels. They are phrases a person would say in conversation. Each one starts with a lowercase article or pronoun and reads as a sentence fragment that completes the question what are you looking for. The first option covers defined build projects — a client who knows they need a website and wants to discuss scope. The second covers audit and remediation work — a client who has an existing site and needs accessibility compliance. The third covers everything else — a client who has a problem but does not know what the solution looks like yet. Three options span the full range of inbound enquiry intent without forcing the person to classify their own request. The third option matters most. A contact form without a catch-all option loses the visitors who do not see themselves in the predefined categories. They leave the page. The not sure yet option gives them permission to reach out without knowing exactly what they want. The phrase let us talk sets the expectation that the first step is a conversation, not a purchase. The project type appears in the notification email body as a labelled line so you can see what the person is looking for before you read their message. It does not appear in the subject line because the subject already carries the name and optional business name, and adding a third piece of information would push it past the point where most email clients truncate. Three options, three sentence fragments, one dropdown. The field does the intake triage before any human reads the message.