Process
What do I need to give my developer before they start?
Content, brand assets, access, and decisions. Specifically: the copy for every page, photographs, your logo in a vector format, access to the domain and hosting, a list of integrations by product name, and a single named person who can approve things.
The checklist
- Copy for every page, or a written agreement on who is writing it and by when
- Photographs of your actual work, at full resolution
- Logo files in vector format, plus your brand colours as hex values
- Domain registrar and hosting access, or confirmation of who holds them
- A list of integrations — payment gateway, CRM, accounting, email — by name
- Your legal details: trading name, registered address, VAT number if applicable
- One named decision-maker who can approve without a committee
Why the decision-maker matters most
A build waiting three days for feedback because it needs four people to agree costs more time than any technical problem will. Naming one person who can say yes is the cheapest schedule protection available.
What you should get in return
A written scope, a staging URL you can open at any time, a payment schedule tied to visible milestones, and confirmation in writing that ownership transfers on final payment.
The longer version
This answer is deliberately short. If you want the full treatment, Writing a website brief that gets you comparable quotes covers it in about 3 minutes — free, ungated, written from client work.
Who answered this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. These answers come from those projects rather than from a content brief. More about how I work, or ask me something directly.