Hey everyone! I'm curious about how you guys manage splitting plugin costs with your clients, especially with tools like Crocoblocks, KadenceWP, or Elementor that have multi-license subscriptions. Do you include these costs in your maintenance packages, or charge clients their share upfront with the overall build cost? Additionally, how do you deal with clients who might push back or refuse to go along with subscription models, which seem to be pretty common nowadays? I'd love to hear your thoughts!
5 Answers
Honestly, I don’t really get involved with plugins. I just focus on writing code and deploying. Sounds like a headache, but I feel for you!
Clients have two options: they can opt for my monthly maintenance package where everything is included, or if they choose not to, they need to pay upfront and handle the maintenance themselves. This actually becomes a point of contention for many, which is why I tend to use fewer paid plugins.
I usually cover recurring costs within my monthly maintenance fees without breaking down each individual charge. I just let clients know that all their server and maintenance expenses are bundled into one monthly payment, which gives me the flexibility to adjust my maintenance charges based on the actual workload.
I usually factor plugin costs into monthly maintenance contracts. If I can find bulk discounts, clients are more likely to stick around since they feel like they’re saving money compared to buying individual licenses.
I recommend the plugins they need and have clients create the accounts for licenses. This way, I don't have to deal with transferring accounts if they decide to leave. It's less hassle for everyone involved since clients end up owning their licenses outright.
Totally agree! We stick to a standard set of plugins with unlimited developer licenses when possible. We charge a general maintenance fee that covers the yearly license costs without itemizing everything for the client.