What a design request form should ask
Designers who take work from strangers end up asking the same things:
- The client's name, business, contact details and billing details.
- What they need: the type of project and the deliverables, such as a logo, a menu or a set of social posts.
- Who it is for, what it should achieve and who they compete with.
- References: brands or designs they like, and what they dislike.
- Existing assets: logo files, fonts, colors, copy and photos, uploaded with the form.
- The deadline, the budget range and who has the final say.
Keep it to what you need to quote. A client who is asked twenty questions before getting a price tends to leave, and the rest can come in the kickoff.
Ask for references, not adjectives
"Modern" and "clean" mean something different to every client. Ask for two or three examples they like, with a line on what they like about each, and one they would not want. A reference image tells you more than a paragraph of adjectives, and it gives you something to point back to when the first draft is judged.
Write down what is in scope
Most scope creep starts with a deliverable that was never written down. List what the price covers, such as the logo in two formats, and what it does not, such as extra sizes or a second concept. Agree the extras as a change to the order, with a new price, instead of absorbing them one message at a time.
Deposits, and when the final files go out
Designers commonly ask for around a third to a half of the price before starting, and many hold the final files until the balance is paid. Say both on the quote, along with the late-payment rule, so nobody learns them after the work is done. Terms differ by place, so check yours locally.
Keep a clear line between invoiced and paid. Mark a payment as received when you have seen the money in your account, not when the client says they sent it.
Count revision rounds
Say how many rounds of changes the price includes, commonly two or three, and what counts as one. A color tweak and a new direction are not the same amount of work, so many designers count only the second as a new round. Charge extra rounds at a rate you stated up front.
Get a yes or a list of changes
"Looks good" in a chat is not an approval, and feedback scattered across email, chats and file comments leaves everyone unsure which version is current. Send each draft with a clear question: approve, or send back with changes. Keep the answer on the project it belongs to, and name each version so there is only one current one.
When an inbox stops being a project list
An inbox works for two or three projects. It strains when requests arrive by message, email and referral, when you cannot say which drafts are waiting on a client, or when a payment is chased from memory. At that point the form, the list of projects and a page where clients check their own project are worth having in one place.