Website Development Quotes: Define Pages, Design and CMS Scope
Published:
Last Updated:
Authors: Shusaku Yosa
A website quote becomes useful when the work behind it is clear. A five-page corporate site built from approved copy is a different assignment from a five-page site that needs positioning, content planning and a new design direction. Page count is a starting point, not a complete specification.
This guide helps teams preparing a landing page, corporate website or service site compare scope before comparing totals. It does not set a universal market price. The aim is to describe what must be built, who supplies the inputs and who will run the site after launch.
Describe the visitor's task before choosing pages
Write down the main visitor, the question they need answered and the action they should be able to complete. A corporate site may need to establish credibility before a visitor contacts the company. A service page may need to explain suitability and limitations before a request for information.
For a redesign, name the practical difficulty. “The website feels dated” leaves many possible solutions. “Mobile visitors cannot find the service conditions and inquiry link” gives the team a task to investigate. Separate changes to visual style from changes to navigation, content and functionality.
Five conditions that change the work
Condition | What to specify |
|---|---|
Site type | Landing page, corporate site, service site or a more complex application |
Page inventory | Required pages, later additions and existing content to retain |
Design variation | Shared layouts versus pages requiring their own design |
CMS and functions | What staff must edit and whether membership, booking or integrations are needed |
Languages | Which pages need another language and who supplies the translation |
Create a page inventory with a proposed address, purpose, available copy and layout group. Ten pages using a common structure do not create the same design work as ten unrelated layouts. Likewise, reducing page count may not reduce complexity if the remaining pages contain custom interactions or a complicated inquiry flow.
List deliverables and exclusions separately
Ask which stages the proposal covers: information structure, page design, implementation, display checks and launch. If your staff will edit the site, discuss access, instructions and handover files. If outside support will continue, define the kinds of updates and the period covered.
Do not assume that copywriting, photography, translation, hosting, paid software, content migration or analytics implementation are included. A site move may also need a plan for old addresses and launch sequencing. The SEO cost and scope guide explains how to separate search improvement work from website production.
Make usability checks concrete. For an inquiry form, identify labels, instructions, error feedback and keyboard use as review topics. W3C's forms tutorial provides useful reference material. Agree on the pages and methods to be checked; a design review alone is not evidence that every accessibility requirement has been met.
Keep business decisions inside the company
Your team usually knows which product statements are accurate, which information is confidential and who can approve publication. External support can help organize that knowledge into a structure, design and implementation. Distinguish final copy from a folder of reference documents: turning source material into approved page copy is additional work.
Nominate one person to collect feedback. Agree when structure, visual design and pre-launch content will be approved. A new requirement introduced after implementation can affect several stages at once. Ask how corrections to the agreed work differ from a change in requirements, and record how changes will be assessed.
Three examples of different project boundaries
A landing page with approved materials
The company provides the message, copy and usable images. The request focuses on page production and implementation. Confirm the inquiry form, display checks and launch responsibilities. Advertising distribution and writing the underlying campaign message should be listed separately if they are also required.
A corporate site planned from the beginning
Several departments hold different documents and nobody has agreed on a page structure. The brief includes organizing information and deciding what belongs in the first release. If staff will publish news, specify the CMS editing workflow and ownership. This is an illustrative scope, not a fixed delivery package or timetable.
A service site with booking or membership
The work extends beyond ordinary page production. Describe account access, booking rules, existing systems and the information passed between them. A standard website estimate should not be treated as the total for an undefined application. Explain the workflow and request a separate assessment of the functional requirements.
What Ficilcom's current estimator asks
The website development estimator asks for the engagement scope, site type, total pages, additional custom design, CMS or extra functions, and pages in additional languages. E-commerce and membership, booking or external-system integration are marked for an individual quote. Additional-language pages assume supplied translation; translation work is separate.
The result is a preliminary estimate based on Ficilcom's stated conditions, not a market average or a binding project quote. Add migration requirements, unusual functions and ongoing responsibilities when discussing the project. Include the required delivery and review languages in your brief, and confirm them before agreeing on the work.
A brief that helps providers compare the same work
- Identify the primary visitor and desired action.
- List required pages and separate later additions.
- State which copy, images, logos and translations are ready.
- Describe the CMS owner, required functions and current systems.
- Give the preferred launch date and the business reason behind it.
- Name the approver and the owner after launch.
When comparing proposals, put missing items beside the total instead of judging by the total alone. Ask whether each provider has assumed the same materials, page structure and approval process. A clear exclusion is more useful than a vague promise that everything is covered.
Frequently asked questions
Can we ask for help before the page count is final?
Yes, start with the information that must be available at launch. Use the same provisional inventory for each proposal and ask which decisions must be resolved before a firm quote can be prepared.
What if we only need design?
Agree on file formats, shared components, important states and handover to the implementation team. See the UI/UX scope guide when the main task is improving a user journey.
Does production include future maintenance?
Do not assume it does. Content updates, technical incidents and hosting administration are distinct responsibilities. Specify the period and tasks in any continuing engagement.
Compare a defined scope
Once your inventory and materials are clear, use the website estimator to explore the relevant conditions. Check the assumptions and exclusions, then include unresolved functions and launch constraints in your inquiry.
