A project inquiry often happens before a buyer has a complete brief. A form can help them explain the situation, but it can also become another task they postpone. Begin with the information needed for the first conversation and make the rest easier to discuss later.
Ask about the intended outcome
Give someone room to describe what they want to change or build. A service selector can provide a starting point, but it should not be the only way to explain the project. Include a sensible option for people who are unsure which label fits their needs.
Separate useful context from unnecessary effort
Consider what the team actually needs before responding. Timing, starting point, and a short description may be more useful than a long specification at this stage. If you ask about a constraint, explain it clearly and allow uncertainty when a firm answer is not yet available.
Keep the interaction predictable
Use visible labels, understandable errors, and a clear way to move between steps. Preserve entered information when someone reviews a previous answer. A short form can still feel difficult if the person cannot tell what will happen after the next button.
Describe the finish accurately
Tell the person what happened and what they should expect next. A connected inquiry form and a preview that only prepares a brief need different confirmation messages. Keep the wording aligned with the real behaviour so the visitor knows whether any further action is required.
