What to ask before a monthly retainer adds a new tool to your site

Wait, what exactly am I agreeing to right now

A designer on a maintenance retainer mentions, almost in passing, that they can add online booking or a payment link to your site. It sounds simple, like it's already covered by what you're paying monthly. Before agreeing, there's a question worth asking out loud instead of nodding along: what actually changes, and who owns what gets created?

A retainer covering routine maintenance and a retainer that's quietly grown to include new tools are not the same agreement, even when the invoice looks identical.

Updating a plugin, fixing a broken link, swapping a photo, that's maintenance. Adding a booking system, a payment processor, or an email marketing tool is a different category of work entirely. It creates a new account, a new login, and often a new monthly cost sitting outside the retainer.

Ask directly which category the proposed addition falls into. If it creates an account you didn't have before, it's an addition, not maintenance, and it deserves its own conversation before it happens.

This distinction matters even when the person proposing it isn't trying to hide anything. A designer thinking in terms of "helping you out" can genuinely not realize they're describing a new piece of infrastructure, not a small fix.

A short pause before agreeing costs nothing. "Let me think about that and get back to you" is a complete, reasonable answer to any proposal that adds a new tool.

Who actually owns the account the tool creates

Every new tool needs an account somewhere, under your business email or under the agency's. This matters more than it sounds like it should. An account under the agency's login means you don't hold the admin access if the relationship ever ends.

Ask for the account to be created under your own email from the start, with you holding the login credentials, even if the agency manages it day to day.

Write the login down somewhere safe the moment the account exists, not months later when you actually need it. An account you technically own but can't get into is not really yours.

Ask this question the same way for every future tool, not just the first one. It's easy to get the account ownership right on the first addition and then let the habit slip on the next.

Whether the new tool connects to your existing customer list first

A new booking or payment tool often keeps its own separate list of names and contact details, disconnected from whatever system already holds your customer records. Add it without checking, and you end up with two lists that never talk to each other.

Ask whether the new tool syncs with what you already have, or whether it's building a second, disconnected pile of the same information. This exact problem gets its own full treatment in why a booking tool and a payment link split your customer list in two.

Ask the question before the tool is set up, not after names have already started collecting in two separate places. Untangling two lists later takes far more effort than checking this once up front.

What happens to the tool if you cancel the retainer

If the retainer ends, does the tool keep running under your own account, or does access disappear with the agency relationship? This should be answered before the tool goes live, not discovered the week you try to switch providers.

A tool tied entirely to the agency's own accounts and logins is a tool you don't actually control. Ask the question early enough that the answer can still shape how it gets set up in the first place.

Get a plain answer, not a reassurance. "It'll be fine" is not the same thing as knowing exactly what continues working and what stops the day the retainer ends.

Ask what it would take to move the tool to your own account if you ever needed to. A clear, specific answer is a good sign. A shrug is worth paying attention to.

Getting the addition scoped in writing

A verbal "sure, we can add that" is not a scope. Get the specific tool named, the account ownership stated, and any cost written into an actual proposal or email before work starts.

This protects both sides. A written scope means nobody's guessing later about what was actually agreed to, and it gives you something to point back to if the tool doesn't work the way it was described.

A single confirming email is enough. It doesn't need to be a formal contract, just something in writing that both sides can refer back to.

Ask for the scope before you say yes in the meeting, not after. Once work has already started, a written scope becomes a formality instead of the thing that actually shaped the decision.

None of this needs to feel adversarial. A designer who's actually acting in good faith will put the same answers in writing without hesitating, and that willingness tells you something on its own.

How this differs from a general maintenance retainer

A general maintenance retainer keeps an existing site working. Adding a new tool is closer to a small project happening inside that relationship, with its own scope and its own ownership questions.

Website tools in general are part of what a small business website actually has to do. This is the moment where the list of tools attached to your site starts growing, rather than just being kept up and running.

Understanding what a normal maintenance retainer covers on its own, separate from feature additions, is worth reading through who actually takes care of a website after launch. And if the pricing itself feels unclear, what actually drives the cost of a website explains the models a retainer like this sits inside.

More from the blog

All posts