Absolutely. "Not for free" is exactly the right stance here.
Look, I've been on both sides of this table. When you've spent six months onboarding a client, building their workflows, integrating their CRM, training their team - that's not a passive asset. That's active relationship management, support, and opportunity cost. The moment the contract lapses, you're still holding the keys to their operational setup. If they want to keep using that infrastructure, continuation pricing isn't "unfair" - it's honest about the ongoing value you're providing.
I usually frame it this way: the monthly retainer during the contract covered the heavy lifting. post-contract, the pricing reflects the reduced but real ongoing commitment: data hygiene, minor tweaks, access to your expertise when something breaks. If they don't see the value in that, they're free to migrate. But migrating costs them time and risk.
LTV-to-CAC math only works if you protect the L part. Letting continuation slide for free kills your unit economics. stick to your pricing. if the client pushes back, offer a clear breakdown of what they're paying for post-contract (e.g., "x hours/month of ad hoc support, priority escalation, quarterly health checks"). if they still baulk, it's a sign they never valued the relationship beyond the initial project. that's fine - you've got better clients to serve