What happens to your content when you move to a headless CMS
Thinking about migrating to a headless CMS? Here's what actually happens to your content during the move, and how to prepare for it.
The quality of your brief determines the quality of your quotes.
A good brief doesn't need to have every answer. But it should be honest about what you know and where you need help. Things worth including:
What you do, who your customers are, and what makes you different. Don't assume the agency knows your industry.
What's working, what isn't, and any analytics you can share (traffic, bounce rate, conversion rate). If you don't have analytics, say so.
Do you have copy ready, or will it need to be written? Do you have photography, or will stock images or a shoot be needed? Content is one of the biggest variables in project cost, and most briefs don't mention it.
Do you need a specific CMS? Integrations with a CRM, booking system, or payment gateway? E-commerce functionality? These have a significant impact on cost and timeline.
Even a range helps. Saying "we're working with $15–25k" lets agencies scope a solution that fits rather than guessing what you can afford.
When do you need this live, and is there a hard deadline (like a product launch or event)?
For more detail on how a good web project runs from start to finish, see our project delivery guide.
Once you've sent your brief to a few agencies, you'll get proposals back. Here's how to compare them meaningfully:
A good proposal responds to what you asked for. A generic one has been copy-pasted from their last pitch.
An agency that comes back with clarifying questions before quoting is a good sign. It means they're trying to understand the problem rather than just pricing a task list.
You should be able to see exactly what's included and what isn't. If the proposal is vague about scope, the final invoice will be too.
A quote without a timeline is just a number. You need to know when things will happen and when you'll be involved.