Why do you only hear from your web vendor at renewal time?
Attention follows contract structure. On a locked annual agreement, the economically important moment is the renewal, so that's where the vendor's attention concentrates: quiet for ten months, then responsive and full of plans in the weeks before you re-sign. It's not a character flaw; it's what the incentive rewards. The audit below takes twenty minutes with your own inbox, and the auto-renewal clause it sends you to read has a deadline in it that matters more than the renewal date itself.
What it usually means
The renewal-time surge tells you the vendor can be attentive; they're choosing when it pays. That's worth knowing when you evaluate the relationship, because the service level you experience in renewal month is the ceiling, and the other ten months are the floor. You're buying the floor.
The innocent version exists: some vendors run genuinely quiet-but-solid operations, doing the maintenance, hitting the tickets, and simply not performing their attentiveness. The contact audit below distinguishes quiet competence from absence, because quiet competence still leaves a trail: shipped work, flagged issues, the occasional unprompted note. Absence leaves only the renewal cluster.
Long lock-ins are routinely justified as continuity or amortized setup, and sometimes that's real. But a term also caps your ability to walk, and the vendor knows your practical alternative to renewing is a migration whose difficulty they control. The quieter the year, the more the term is doing the retention work the service should be doing, which is the pattern vendor lock-in names.
What it costs while it stays this way
The immediate cost is the service gap between what renewal month proves possible and what the other ten months deliver; weeks-long turnaround on small changes is the usual shape of the floor. You have seen the ceiling; you're paying for it and receiving the floor, and the difference compounds across everything else on this site's list: unflagged issues, unproposed improvements, a site drifting behind the business.
The sharper cost hides in the paperwork. Most annual service agreements auto-renew, and most auto-renewal clauses carry a notice window: cancel in writing 30, 60, or 90 days before the term ends, or the contract renews for another full year on its own. Miss the window by a day and the decision has been made for you. Vendors don't hide this clause, but they rarely calendar it for you either, and the renewal-time charm offensive lands, not coincidentally, after the window has usually closed.
Renewal is also when pricing moves. An increase presented three weeks before expiry, with the site, the hosting, and sometimes the domain in the vendor's hands, isn't a negotiation; it's a toll booth. The audit and the calendar entry below are what convert it back into a negotiation.
How to confirm it yourself
- Chart a year of vendor-initiated contact. Search your inbox for the vendor's domain, filter to messages they started, and list the dates. One glance settles it: if the dots pile up in the sixty days before renewal and thin out everywhere else, the pattern is confirmed. Automated reports count separately; classify them in the next step.
- Classify what each contact was. Mark each vendor-initiated message: finding or recommendation, shipped work, routine automated report, upsell, renewal. A year where the only non-renewal contact is automated reporting is a year of absence with good tooling.
- Find the auto-renewal clause and its notice window. Pull the agreement and search for renew. Read for three things: whether it auto-renews, for how long, and how many days before expiry written notice is required to stop it. Put that notice deadline, not the renewal date, in your calendar now, with a reminder a month earlier.
- Plot what the price has done at each renewal. List the fee at signing and at each renewal since. Increases clustered at renewal, without corresponding scope changes, tell you how the vendor prices your switching costs.
- Note what the renewal pitch contains. If plans, audits, and enthusiasm appear in the renewal conversation that you haven't seen since the last one, ask the obvious question: why do these arrive on this schedule? The honest answers are informative, and so are the other kind.
What the vendor's answers actually mean
Raise the quiet year and the replies fall into familiar shapes. Each is a position, not a fact, and each tells you what the engagement has actually been.
“We like to give clients space unless something needs attention.”
Space is what absence is called at renewal. A working site still produces findings; a vendor watching it has some. Ask for the last three things they noticed and the dates they raised them.
“You didn't submit many requests this year.”
The model stated plainly: their activity waits on yours. On a maintenance contract that may be fair; on anything priced as ongoing service, it means the quiet months contained nothing.
“The increase reflects rising costs on our side.”
Possibly true, and unanswerable as stated. The reply that converts it back into a negotiation: compared to what month-to-month would cost, and with what transfers if we decline?
“We have big plans for your site next year.”
The renewal-month version of attention. The test isn't the plans; it's whether anything resembling them appeared in the preceding ten months, and your contact chart already answered that.
What actually fixes it
The structural fix is aligning the vendor's incentive with your experience: shorter terms, month-to-month after an initial period, or an engagement where continuing is earned by the work rather than owed by the contract. Vendors confident in their service accept these terms, and the amount of resistance to shorter terms is a fair measure of how much the lock-in was carrying. If replacing the arrangement is on the table, how to choose a B2B web design agency covers what to ask before you sign the next one.
Inside an existing term, put the attention expectation in writing: a defined cadence of reviews whose agenda is vendor-side findings, closer to a standing website audit than a status call. It converts vague dissatisfaction into something checkable, and it builds the record you will want at the actual renewal decision. The sibling symptom on project work, having to spec everything yourself, is worth reading alongside; the two usually travel together.
And regardless of what you decide about the vendor: calendar the notice window today, and start any evaluation ninety days before it closes, not at the renewal date. The window, not the renewal, is the real decision point, and evaluating with the window still open is what keeps every option, including staying, an actual choice.
The message to send, ninety days out
Send this well before the notice window closes. It's not a cancellation; it's what makes the renewal a decision instead of a default.
Hi [name],
Our renewal is coming up on [date], and we want to make the decision properly rather than by default. Three things would help, by [date, at least two weeks before the notice deadline]:
A short summary of the year: what shipped, what you flagged, and what you would change next year. Current pricing for renewal as-is, and for a month-to-month arrangement. And confirmation of what transfers to us, domain, hosting, site files, analytics, if we were to go a different direction.
Nothing here is a decision; we just want real numbers and a real record in front of us when we make one.
Common questions
Are annual contracts for website work normal?
Common, yes, especially bundled with hosting and maintenance. Necessary, mostly no. Genuine ongoing work has a rhythm that benefits from commitment, but plenty of capable vendors work month to month after an initial project precisely because it keeps them accountable. Normal isn't the same as in your interest, and the bundling is often what makes leaving feel impossible.
What is an auto-renewal notice window and why does it matter more than the renewal date?
It's the period, commonly 30 to 90 days before the term ends, during which you must give written notice to prevent automatic renewal. Miss it and the contract typically renews for a full additional term regardless of what you decide afterward. It matters more than the renewal date because it's the last moment the decision is actually yours; everything after it's commentary.
What questions should I ask before renewing?
Three: what did you proactively bring us this year, with dates; what would month-to-month cost instead; and what specifically transfers to us if we leave. The third is the quiet test. If leaving means losing the domain, the hosting, or the analytics history, the renewal isn't really a choice, and that's worth knowing while the notice window is still open.
The vendor is competent, just silent. Is that enough?
It can be, if what you're paying for is maintenance and the price reflects that. The audit separates the cases: silent competence leaves shipped work and flagged issues in the trail; silence leaves only reports and renewals. Decide based on the trail, then make sure the fee matches which service you're actually receiving.