Reading an agency proposal: the line items that actually predict trouble

A proposal is a sales document first and a scope document second, and the two goals pull in opposite directions. The sections written to close the deal are usually polished. The sections that actually protect you once work starts, revision limits, change-order pricing, what counts as a deliverable, get far less attention. Reading a proposal for what it doesn't say is a better filter than reading it for what it does.

"Unlimited revisions" is the line that should slow you down, not reassure you. Unlimited revisions on what, exactly, and until when? Agencies that offer this usually mean unlimited revisions within the originally agreed scope, and any client-requested change outside that scope becomes a new, separately billed request. That's reasonable, but it should be written down as a rule, not implied by a friendly-sounding word on page one.

Ask what happens the first time you request something outside scope: is there a pre-agreed hourly rate, a standard minimum charge, a requirement that changes be approved in writing before work starts? A proposal that answers this upfront is telling you the agency has been burned by scope creep before and built a process around it. A proposal that's silent on it is telling you the answer will be improvised, usually under time pressure, which rarely favors the client.

"Homepage design" can mean a single desktop mockup or a fully responsive, interaction-annotated design ready to hand to a developer. Ask for the specific artifact you'll receive at each milestone, in the format you'll receive it, and how many rounds of feedback that specific artifact gets before it's considered final. Vague deliverable language is the single most common source of disputes we see between clients and their previous agencies.

A 50/50 split, half up front and half on completion, gives an agency little incentive to hit interim milestones on time, since they're paid the same either way. Milestone-based payments tied to specific, checkable deliverables (wireframes approved, design approved, staging site live) give both sides a shared, dated record of progress and make it much easier to spot a project drifting off schedule before it's too late to fix cheaply.

Don't just ask for a reference. Ask the reference one specific question: did the project finish on the originally quoted budget and timeline, and if not, why not? Most references will say yes to "were you happy with the work," because most agencies do produce a good final product eventually. Far fewer will say yes to the budget-and-timeline question, and the honest answer to that one tells you far more about what to expect.

Push for a second, harder question if the reference call is going well: what would you have asked for differently at the start, knowing what you know now? Most people are reluctant to volunteer criticism of a vendor they're still working with, but a direct question about their own hindsight tends to get an honest answer, since it's framed as their own learning rather than a complaint about the agency.

The gap between what a proposal implies and what it actually means usually surfaces in the first two weeks of a project, not before. A line like "weekly check-ins" can mean a scheduled thirty-minute call with an agenda and a written follow-up, or it can mean an informal message whenever someone remembers. Both technically satisfy the sentence in the proposal, and only one of them actually keeps a project on track.

Ask, before signing, what the first two weeks look like specifically: who you'll talk to, on what cadence, and what you'll have in hand at the end of week one. An agency that can answer in concrete detail, a kickoff call on a named day, a shared project board live by day three, a first draft by day ten, is describing a process it has actually run before. An agency that answers in generalities is describing an aspiration.

Most proposals list roles rather than names: a project manager, a designer, a developer. That's normal for a document written before staffing is finalized, but it's worth asking directly who will actually be assigned before work starts, and whether that person has capacity right now or is currently finishing another client's project. An agency stretched thin will sometimes staff a new engagement provisionally and reassign later, which shows up to the client as an unexplained slowdown in week three with no clear cause.

Ask for the actual names and a rough percentage of that person's time dedicated to your account. The answer won't always be perfect, capacity genuinely shifts week to week, but an agency willing to give a specific, checkable answer is telling you something different than one that deflects to "our team will handle it" without naming who that team actually is.

Every project hits at least one moment of disagreement, a missed date, a design direction the client dislikes, a technical limitation nobody anticipated. A proposal that never mentions how disagreements get resolved is telling you that question hasn't been thought through, and you'll be negotiating a resolution process for the first time exactly when tempers are already short, which is the worst possible moment to be inventing a process from scratch.

We look for proposals, ours included, that name a specific escalation path: who raises a concern, who it goes to, and what the timeline for a resolution looks like. It doesn't need to be elaborate, a single paragraph naming a point of contact and a response window is enough, but its presence signals an agency that has actually run into friction before and built something in response, rather than one that's simply never had a project go sideways yet.

Almost no proposal addresses what happens if the client wants to end the engagement early, whether for cause or simply a change in business direction. Ask directly: what do you receive if you terminate the contract partway through, source files, a partial refund, documentation of what's been built so far? An agency with a clear, fair answer to this question is one confident enough in its own work to let a client walk away with something usable, which is itself a meaningful signal.