Contracts and CMS
Permalink
I was wondering if anyone includes any specific clauses regarding client use of CMS. Do you have a clause for support under payment in the event an admin breaks or toys with settings in the backend that they simply "had to have access" to, and than needs your help ?
Anyone have any examples of what they throw in the mix ? I would like to avoid calls saying "I changed something I am not sure what it was but now this isnt working as it should" and than not having any clear clauses excluding support without payment for client actions after delivery, but at the same time word it so that I don't lose client confidence in the project.
I googled this like crazy to gain insight, but theres virtually nothing coming up specific to cms.
Anyone have any examples of what they throw in the mix ? I would like to avoid calls saying "I changed something I am not sure what it was but now this isnt working as it should" and than not having any clear clauses excluding support without payment for client actions after delivery, but at the same time word it so that I don't lose client confidence in the project.
I googled this like crazy to gain insight, but theres virtually nothing coming up specific to cms.
What I am using now is a contract, and attached project overview/outline containing all specifics like sitemap, image placements, design etc, while the contract covers all legal, and leans on on the overview.
The contract itself has been heavily plagarized from a few differnt things I have picked up on the net all made for public use, and is attached. Theres a typo I have to fix, but I am just going through it now rewording a few things.
The problem I see is the client breaks something, and then I am bound to fix it as they can easily say "it wasnt me" point the finger, and sic the lawyers to intimidate me into free support. I am trying to avoid that at all costs.
*I added additional clauses covering laptop views, cms aftercare. court cost liabilty in the event of breach which are enforceable in most countries, and streamlined it to make the owner of company personally responsible for adherance to the contract.
Will put the project overview into a psd template soonish in case anyone wants to use this, and hopefully I can find a lawyer that needs some web work to review it all.
The contract itself has been heavily plagarized from a few differnt things I have picked up on the net all made for public use, and is attached. Theres a typo I have to fix, but I am just going through it now rewording a few things.
The problem I see is the client breaks something, and then I am bound to fix it as they can easily say "it wasnt me" point the finger, and sic the lawyers to intimidate me into free support. I am trying to avoid that at all costs.
*I added additional clauses covering laptop views, cms aftercare. court cost liabilty in the event of breach which are enforceable in most countries, and streamlined it to make the owner of company personally responsible for adherance to the contract.
Will put the project overview into a psd template soonish in case anyone wants to use this, and hopefully I can find a lawyer that needs some web work to review it all.
Now that's a damn handy document Ekko.
It covers off a lot of stuff really nicely.
As growthcurve said everyone is different but I would also charge a customer hourly rate to fix any problems they may have caused.
It covers off a lot of stuff really nicely.
As growthcurve said everyone is different but I would also charge a customer hourly rate to fix any problems they may have caused.
With us, support (not just you fix their broken stuff but also you
help them figure out how to not break it in the first place) is
generally ponied together with some warranty that it'll do what it
says for a specific amount of time. ie 30 days included support in
SOW. Anything additional is hourly.
just to be clear, when you look at things like Aquia support or
Wordpress VIP - that's what they're selling. You're worried about how
to most effectively give it away for free. ;)
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
help them figure out how to not break it in the first place) is
generally ponied together with some warranty that it'll do what it
says for a specific amount of time. ie 30 days included support in
SOW. Anything additional is hourly.
just to be clear, when you look at things like Aquia support or
Wordpress VIP - that's what they're selling. You're worried about how
to most effectively give it away for free. ;)
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
That definitely works, 30 days support seems very fair. I usually do a small series of private link youtube videos specific for the site, so that all is covered, and I shouldn't face problems, and I haven't had any issues yet, but I am starting to go after larger fish and I am trying to cover all the bases. The warranty deal absoloutely helps inspire the confidence I was looking for.
Thanks
Thanks
Normally, I simply charge my normal hourly rate for any additional work. I think, ultimately, it's really up to the designer / developer to approach the client with this.
Of course, most freelancers run their businesses differently, so finding a universal solution is rather difficult.
In most cases, I just write up a custom contract, depending on what the client is looking for. For me, that's the easiest way to go.