Use this buyer’s checklist to compare capabilities, scope, contracts, timelines, ownership, and post-launch responsibilities before you sign.
A portfolio can show visual range, but it does not explain how a company defines requirements, writes code, controls changes, or transfers ownership. Compare prospective partners using the same criteria and require important commitments in writing. The right choice depends on your business requirements, internal capacity, technical risk, and plans after launch.
Evaluation checklist
Discovery and strategy
Capability: translating business requirements into a buildable plan. Mechanism: stakeholder interviews, audience and conversion-path review, content inventory, functional requirements, and documented acceptance criteria.
Design validation
Capability: testing the direction before full production. Mechanism: wireframes, component concepts, or working prototypes that let stakeholders review hierarchy, interactions, and responsive behavior early.
Development architecture
Capability: selecting technology that fits the site’s operating needs. Mechanism: a documented stack, reusable components, content-management approach, integration plan, deployment process, and explanation of technical tradeoffs.
Accessibility and performance
Capability: building against defined quality standards. Mechanism: semantic markup, keyboard testing, contrast checks, responsive testing, performance budgets, and an agreed target such as WCAG 2.2 AA where applicable.
Communication and change control
Capability: keeping decisions, feedback, and costs traceable. Mechanism: named contacts, scheduled reviews, shared task tracking, approval gates, and a written process for estimating changes outside the approved scope.
Ownership and handoff
Capability: allowing your organization to operate or transfer the website. Mechanism: contract language covering intellectual property, source files, repositories, domains, hosting, credentials, documentation, training, and final deliverables.
Implementation path
011. Define the buying brief
List required page types, user actions, integrations, content needs, compliance constraints, launch dependencies, and internal approvers. Separate required capabilities from later-phase ideas so every company prices the same baseline.
022. Test the shortlist
Ask each company to explain its discovery process, design validation method, development stack, testing standards, and handoff procedure. Request relevant work examples, but evaluate the reasoning and responsibilities behind them rather than aesthetics alone.
033. Normalize the proposals
Compare deliverables, exclusions, revision structure, content responsibilities, launch tasks, and support—not only the total. Fixed-price proposals need a precise scope; open-ended projects need rate terms, reporting frequency, spending controls, and a change-approval process.
044. Review the contract
Confirm payment milestones, cancellation terms, intellectual-property transfer, third-party license obligations, source-file delivery, credential ownership, hosting responsibilities, change requests, and post-launch support. Payment should follow identifiable stages rather than ambiguous percentages of completion.
055. Set delivery gates
Establish approvals for strategy, prototype, design system, development, content entry, testing, and launch readiness. A typical custom marketing site may require about 6–12 weeks, while e-commerce or integration-heavy work may take 12–24 weeks or longer depending on content, feedback speed, and technical dependencies.
066. Plan launch and ownership
Document redirects, analytics, forms, backups, domain settings, deployment access, training, and rollback responsibility. Define whether the initial support period is 14–30 days or another stated term, what qualifies as a defect, and how later maintenance is authorized.
Tradeoffs and risks
Portfolio bias
Visual polish does not establish that a site met its business requirements, remained maintainable, or performed well. Ask what the company was responsible for, which constraints shaped the work, and how decisions were validated.
Unclear scope
Terms such as “custom design” or “SEO included” are too broad to price or enforce. A proposal should identify page types, templates, integrations, content responsibilities, technical SEO tasks, revision terms, and exclusions.
Proprietary lock-in
Some platforms restrict source-code access, hosting portability, or administrator control. Determine whether the site can move to another provider and whether you will receive the code, assets, data exports, and account credentials needed to operate it.
Missing quality standards
Accessibility and performance should not be implied. Require a stated accessibility target, browser and device coverage, testing methods, and a process for managing image weight, JavaScript, fonts, and third-party scripts.
Timeline compression
Short schedules usually require faster approvals, ready content, fewer dependencies, or a narrower first release. Confirm what happens when feedback, integrations, content, or stakeholder decisions arrive late.
Post-launch gaps
A site can launch without a clear owner for updates, monitoring, backups, security, or defect resolution. Define the included support window and separate ongoing maintenance responsibilities before final payment.
Detail questions
What should I ask before hiring a web design company?
Ask who performs strategy, design, development, testing, and project management; how feedback is handled; and what happens when scope changes. Also ask which platform will be used, who owns each account, what you receive at handoff, and who supports the site after launch.
What should a web design contract include?
The contract should specify deliverables, exclusions, schedule assumptions, payment milestones, revision terms, change-request procedures, and acceptance criteria. It should also address intellectual property, third-party licenses, source files, repository access, credentials, hosting, cancellation, launch support, and ongoing maintenance.
How much should a professionally built website cost?
As a planning range, a custom business marketing site may fall around $8,000–$25,000, while e-commerce, complex content systems, AI features, or custom integrations can move projects into the $20,000–$75,000-plus range. Page and component count, content readiness, design depth, data migration, integrations, accessibility requirements, and review cycles drive the final scope. Treat ranges as screening tools, not substitutes for a written proposal.
How many revisions should a proposal include?
Many fixed-scope projects define two or three review rounds at major stages, while custom project engagements may use continuous feedback within agreed boundaries. The important distinction is how a round is defined, when feedback is due, and how new requirements are estimated and approved.
Should I own the website source code and accounts?
For a custom build, the contract should state when ownership transfers and identify any licensed components that remain subject to third-party terms. Your organization should understand who controls the domain, hosting, analytics, code repository, content system, payment accounts, and other operational credentials.
How can I evaluate accessibility and performance claims?
Ask for named standards and testing procedures rather than general promises. Useful specifics include the WCAG target, keyboard and screen-reader checks, supported browsers, image and script controls, performance measurement tools, and responsibility for third-party services that can affect results.
Compare Your Requirements With a Defined Build Plan
High Desert Web Designs can review your scope, identify technical dependencies, and outline a fixed-price package or custom project path.