{"id":3230,"date":"2026-11-19T12:16:48","date_gmt":"2026-11-19T10:16:48","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3230"},"modified":"2026-11-19T12:17:01","modified_gmt":"2026-11-19T10:17:01","slug":"what-belongs-in-a-website-maintenance-retainer","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/what-belongs-in-a-website-maintenance-retainer\/","title":{"rendered":"What Belongs in a Website Maintenance Retainer?"},"content":{"rendered":"<p>\u201cSmall website updates included\u201d sounds like a convenient service promise until a customer asks for a new booking flow in a two-line email. Decide what work your ongoing service covers before using message length as a measure of effort.<\/p>\n<h2>Start with the work, not the package name<\/h2>\n<p>Consider a fictional freelance maintainer designing a service for a small museum website. The museum regularly changes visitor information, occasionally adjusts page layouts and is considering a new membership enquiry process. Calling all three \u201cupdates\u201d hides very different preparation and review needs.<\/p>\n<p>Collect a handful of representative requests from the kind of work you can actually support. If you use real examples in planning, remove private customer material. Describe each intended result in ordinary language. This is preparation for your service and pricing decisions, not a legal contract template or a statement about what an existing agreement requires.<\/p>\n<h2>Example one: a confirmed text correction<\/h2>\n<p>The museum supplies replacement opening hours for one named page. Before treating the request as routine, establish the source wording, affected locations and desired publication timing. Check whether the same information appears elsewhere within the agreed scope. A seemingly simple correction can involve a decision about consistency, not just typing.<\/p>\n<p>Your worksheet could classify this as a routine content edit when the wording is supplied and approved, the affected locations are known and the work uses an existing content structure. Record the check you would include afterwards: inspect the intended pages and report the published result. Define how an unclear or disputed replacement is handled before it reaches the editing queue.<\/p>\n<h2>Example two: changing the presentation<\/h2>\n<p>The museum asks to move the visitor-information panel above a gallery. The intended outcome may be reasonable, but the work now includes a layout decision. Which views need checking? What happens to the surrounding content? Does the client need to choose between two treatments before implementation?<\/p>\n<p>You might include a bounded class of adjustments to an existing layout, or you might assess them separately. Either approach needs examples. Avoid a rule such as \u201canything taking five minutes\u201d unless you can explain who estimates it, what the estimate includes and how uncertainty is resolved. The visible edit can be shorter than its preparation and verification.<\/p>\n<h2>Example three: adding a new function<\/h2>\n<p>A request to collect membership enquiries introduces another set of questions. What information is collected, who receives it, what response is shown and which process handles the enquiry afterwards? Those questions must be answered before you can sensibly describe the implementation work. Do not promise capabilities from an unspecified tool simply because the client calls it a form.<\/p>\n<p>Mark this example as a separate scoping conversation in the proposed service. Identify the information required for that conversation and how the client will receive an estimate or proposal. Keeping an enquiry outside the routine queue does not mean dismissing it; it means giving it a route appropriate to the decision involved.<\/p>\n<h2>Add the boundaries that affect daily delivery<\/h2>\n<p>For each request class, record the inputs, implementation work, included checks, decision owner and completion message. Then ask how the service deals with work volume, incomplete requests, urgent changes and dependencies on other people. If you offer different service levels, explain their actual operational differences rather than filling the page with vague priority labels.<\/p>\n<p>Include your own preparation and checking when considering price and capacity. A request may require little editing but significant investigation. Do not invent a universal allowance or rate from these examples. Use your experience, supported tasks and available capacity to prepare an offer you can maintain, and obtain appropriate review of the terms you eventually use.<\/p>\n<h2>Try the description against a new request<\/h2>\n<p>Before presenting the service, give someone a fourth example: \u201cPlease add a seasonal visitor notice with a different enquiry route.\u201d Ask them to identify what is included, what needs clarification and what would trigger a separate scope decision. If the answer depends on your unspoken interpretation of \u201csmall\u201d, revise the service description. The useful result is a clearer preparation worksheet, not a promise that every future request will fit a neat category.<\/p>\n<p>Write down the requested outcome before deciding whether it fits the retainer. A site-specific request record can then support a clear conversation about included work and a separate quote.<\/p>\n<p>When a request appears to repeat earlier work, compare <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/did-the-client-ask-again-or-did-the-website-change-again\/\">the original request, completion and new observation<\/a>. To define the checks behind completion, use <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/\">the distinction between implemented, checked and accepted work<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Build a service worksheet from actual kinds of requests, including the information, checks and approvals each needs. A short message can still describe substantial work.<\/p>\n","protected":false},"author":1,"featured_media":3267,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[19],"tags":[],"class_list":["post-3230","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-small-business-life"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-02-02.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3230"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3230\/revisions"}],"predecessor-version":[{"id":3345,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3230\/revisions\/3345"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3267"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}