What to prepare before requesting a website proposal

A solid website quote starts with a clear problem and scope. These decisions will help you request comparable proposals.

“We need a new website” is a starting point, but it isn’t enough for two studios to prepare comparable proposals. Without knowing what your business needs, each provider will have to make their own assumptions about pages, content, features, and responsibilities.

You don’t need to arrive with a detailed technical specification. It is helpful, however, to explain what you want to achieve, what already exists, and what decisions are still pending. A good initial conversation helps clarify the scope and uncover missing information before finalizing a quote.

Table of Contents

Explain what problem the website needs to solve

Start with your business and the people you want to serve. A website may need to present your services better, make inquiries easier, bring together a catalog, or replace a site that no longer reflects what the company does. Those situations require different decisions.

Describe what a visitor should be able to do and what questions they should resolve before reaching out. If you already have a website, point out what works and what doesn’t: it could be hard-to-find information, outdated content, or a form that doesn’t fit the way your team works.

It’s helpful to share the questions you get during sales conversations. You don’t need to turn every single one into a page: they help clarify what information is missing and what should take priority in the site structure.

Gather what exists before defining what's new

A review of your current website helps identify content and features worth keeping. Include important pages, articles, forms, documents, languages, and connected tools. If there are URLs that clients use or share, the redesign needs to take them into account.

It is also helpful to take inventory of copy, photos, visual identity, and project materials. Distinguish what is ready to publish from what needs review or still has to be produced. A proposal that includes copywriting or photo selection involves different work than one that receives all approved materials.

When showcasing client work, confirm what information and images you can use. That decision affects the available content and how the portfolio will be presented.

Identify features and how they will be managed

A feature isn’t just a visual element. A form needs a recipient and a response process. A booking system requires defining availability, notifications, and who handles changes. A private area or an online store adds decisions about access, content, and ongoing operations.

Describe what should happen when someone uses the feature, even if you don’t know the right tool for it. For example, instead of asking for a specific integration without context, explain what information needs to move from one system to another and who will use it. The studio can then evaluate options and clarify what needs confirmation.

Separate what is essential for launch from what could be added later. Working in phases can make sense if the first delivery solves a complete need and future evolution is planned; postponing an essential decision without defining its impact can lead to rework.

Check accounts, access, and responsibilities

Domain, hosting, email, and analytics tools may be managed by different people or providers. You don’t need to send passwords when requesting a proposal, but you should identify who controls each account and whether access will be available when the project requires it.

In a redesign, ask how existing pages will be protected, what will happen to their URLs, and how the launch will be coordinated. If email shares infrastructure with the website, it’s important for the team to know about that dependency before planning a migration.

Within your company, designate who will provide information, who will verify facts, and who will gather feedback. A project with multiple stakeholders moves forward more smoothly when there is a clear way to make decisions and resolve disagreements.

How to compare proposals without looking only at the bottom line

Two proposals can have different totals because they cover different work. Review what each one includes: structure, design, copy, page count, languages, revisions, migration, testing, and launch. If a feature is described broadly, ask them to explain what it will do and what is out of scope.

Ask about ongoing costs as well. Hosting, maintenance, licenses, third-party tools, and recurring content might be billed separately or included with specific conditions. What matters is understanding what you will pay and who will handle each part once the site is live.

A proposal should explain timeline dependencies: what material it needs, when it will be reviewed, and how scope changes are handled. A short turnaround is not comparable to another if one assumes content is already prepared and the other includes producing it.

Our guide to website costs breaks down the line items and factors that can change an investment. Use it alongside concrete proposals, not as a substitute for a written scope.

What to share in the initial conversation

To get started, it is usually enough to explain what your business does, who you want to reach, what problem the website needs to solve, and what material you have available. If you have an existing site, share its URL and point out the pages or features you consider important. Add a target date if it is tied to a real need, and explain what decisions or materials are still pending.

If you have a budget range, sharing it can help evaluate alternatives. If you don’t have one yet, ask the studio to explain what scope they propose and what options would be left out. A helpful proposal should help you decide, not require you to know all the answers in advance.

At Capricorn Nexus, we can review the scope of your website project. Tell us what your business needs and what exists today; with that information, we can ask the right follow-up questions and assess a proposal tailored to the work.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top