This is Part 2 of a 3-part series on hiring and managing a web development agency. Part 1 covers how to choose the right agency. Part 3 covers how to tell if the agency is doing its job after you sign.
Part 1 was about selecting the right agency to evaluate. Part 2 is about the document that turns that sales conversation into an actual commitment. Proposals are where vague assumptions become future disputes if you do not read them carefully.
Read Scope Before Price
The price line is the easiest number to compare and usually the least useful one in isolation. The same number can represent a very different deliverable depending on what is included, excluded, or left vague.
Before evaluating cost, confirm that the proposal is specific about:
- Page count or page types
- Required functionality
- Integrations
- Content responsibilities
- Testing expectations
- Launch support
If the scope is weak, the price is not really comparable to anything else.
Confirm the Hidden Work Is Accounted For
A proposal can look complete while quietly excluding the tasks that make the site usable in practice. Areas worth checking directly:
- Copywriting or content migration
- Photography or media handling
- CRM, booking, e-commerce, or other integrations
- Browser and mobile testing
- Basic SEO setup
- Training after launch
If a required item is missing, it does not become free later. It usually becomes a change order.
Understand Revisions and Change Orders
“Two rounds of revisions” sounds clear until each side defines revision differently. Ask:
- What counts as a revision
- What triggers a change order
- Whether out-of-scope work requires written approval
- What rate or pricing method applies when scope expands
The goal is not to prevent all change. It is to prevent surprise billing and surprise resentment.
The Timeline Assumptions
A proposal timeline is only meaningful if the assumptions behind it are visible. Look for clarity around:
- Who is responsible for delays caused by missing client feedback
- What happens if agency-side milestones slip
- Whether dates are tied to approvals and deliverables
- Whether the project can stall or be re-queued if it goes inactive
Without those terms, the timeline is often more of a sales signal than an operating plan.
Read Ownership, Access, and Hosting Terms Carefully
The proposal or contract should make clear:
- What you own after final payment
- How credentials are delivered
- Who controls the domain and hosting account
- What happens if you later move the site elsewhere
This is one of the most important sections in the document because it determines whether the relationship can end cleanly if needed.
Tie Payments to Verifiable Deliverables
Balanced payment structures usually connect each payment to something you can actually review:
- Initial deposit
- Design or build milestone
- Launch or final delivery
The exact percentages vary. What matters is that payment triggers are tied to real progress, not just elapsed calendar time.
Clarify Post-Launch Support
Many projects reveal edge cases only after launch. The proposal should say:
- Whether bug fixes are included after launch
- How long that support window lasts
- What happens after the initial support period ends
That clarity matters because the days immediately after launch are often the most operationally active.
Part 3 covers the next phase: once the agency is engaged, what should be happening without prompting, and what questions tell you whether the relationship is healthy.
Previous: Part 1: How to Choose the Right Agency Next: Part 3: How to Know If They Are Doing Their Job
Related reading: Hiring and Managing a Web Development Agency, Part 1: How to Choose the Right Agency, Hiring and Managing a Web Development Agency, Part 3: How to Know If They Are Doing Their Job, and How to Hand Off Your Website to a Professional Without Losing Control of Your Business.