WEB DESIGN & DEVELOPMENT / A PRACTICAL ANSWER
What should a web design proposal include?
The short answer
A web design proposal should make the promised result, included work, responsibilities and exclusions understandable. It should explain how the supplier will approach your problem and what will be working at handover. A visually polished presentation is less useful if it leaves content, integrations, verification or ownership undefined.
What to agree
Look for a page or journey inventory, content responsibilities, design deliverables, development scope and acceptance checks. Clarify whether forms are connected to a real delivery system, whether existing URLs are reviewed and whether training or documentation is included.
How to decide
Read the assumptions alongside the price. Establish review rounds, third-party subscriptions, change approval and post-launch support. If a supplier cannot yet confirm an integration, the proposal can include an investigation stage with a defined output rather than burying the uncertainty.
ILLUSTRATIVE EXAMPLE / NOT A CLIENT RESULT
Make it concrete.
Two proposals may both promise a contact page. One may include validation, delivery testing and error states; another may assume your team supplies the form service. Comparing those outputs is more meaningful than comparing the page count.
Before you commission
- Ask what will be demonstrated before acceptance.
- Check who supplies and enters content.
- Separate one-time fees from ongoing commitments.
A plain-text worksheet. Downloading does not send us your details.
FROM THE QUESTION TO THE WORK
A useful next step.
Bring the decision, the existing situation and the information you have. We can help define a scope before you commit to a wider project.
Explore the relevant service