A recurring fee needs a job description

Some work doesn’t end at launch: a CRM whose automations need watching, reports that need to be read, campaigns that need tuning. When we propose a monthly fee, it should name what continues. Which systems we monitor, what we fix, how quickly we respond, what we improve, and what sits outside the arrangement.

A monthly charge that covers little more than hosting and a vague promise of support isn’t that. If we can’t describe the continuing work plainly, it doesn’t belong in the proposal.

The same goes for terms. A client should be able to see what they’ll pay in total, how long it runs, how to end it and what they own afterward. We’d rather put that in the first proposal than have it found later in a contract.