The great thing about WordPress (perhaps its most impressive accomplishment), is that it makes web development so easy that non-developers can set up their own websites with little fuss. One-click installs, a plethora of themes to suit any style, thousands of plugins to extend functionality – before you know it, web developers could be out of a job…or could they?
To the contrary; at some point, customizing WordPress or its plugins is going to come with its coding challenges because, let’s face it, there’s always going to be a unique situation where someone needs their website to do something a WordPress plugin author would never imagine.
Or maybe it just got too hard for a business owner who, after trying to save money by making their own site, figured out they’re better off spending their time where it makes them more money, not where it boggles their mind. Fair enough. I feel the same about accounting.
Then there are the cases of the web developer who went MIA in the middle of a website mission, and the business owner now needs someone to pick up the project and keep it moving along.
In all three scenarios described above, when a client comes to a new web developer to take over, they are probably going to use the term “simple” to explain what they need done. It most likely will be far from that. The web developer needs to realize they’re not only picking up the pieces and carrying on as per ‘the usual,’ they’re also likely going to be cleaning up someone else’s mess…or figuring out how they made the mess to begin with. That takes time, which costs money, which is not worth the risk if you’re not covered with a good agreement beforehand.
Have a Strong Web Developer Agreement, Even for the Small Stuff
If you’re willing to help out a desperate new client who comes to you for their “simple” site fixes, good on you. But be careful. You will need to outline a few things very clearly to them:
A) They must have a backup system in place – no arguments about it! The backup system must be automating daily backups and you will need easy access to the backups in case you need to do a site restore. Recommend they set their site up on ManageWP (or offer to set them up on your account) or use BackupBuddy or VaultPress, all of which are tailor made for WordPress. Make sure you don’t collect login info to anything they own until they confirm their site is being backed up! You do not want anyone to be able to point fingers at you if anything goes wrong, just because you had access, even if it wasn’t you who did the deed. It’s not worth the pocket change to take on a job without this requirement.
B) You don’t know what you are going to find under the hood, and they might not like to hear about what you do find. Make it clear that it always takes longer to make changes to another developer’s code and that the estimate could change if you find ‘problem programming’ that is going to affect your work, within good reason. I am not talking about some tacky CSS or HTML tables that aren’t a web developer’s dream but will still let the site survive (everyone has to learn somewhere. Simply correct them and steer them in the right direction, don’t alarm them about stuff like this). I am talking about things that are just plain wrong (such as insecure code, errors, site slow-down issues, etc.), and things that will prevent you from being able to help them out. Let them know it will cost extra to find and fix the mess.
Once I had a client who said, “I want to be able to make updates to my WordPress site but I can’t see where our past developer put our content.” Turns out, the web developer hard coded a bunch of content into PHP files (including the address, can you believe it?) instead of properly using the WordPress dashboard to allow the client to make content changes themselves. (“Why use WordPress at all?” is the question I would have had for the former developer). This was a case where ‘under the hood’ was not going to cut it at all for what the client wanted. The client needed a newly built site as far as the back end was concerned. So that’s what we did, and he was happy to pay for it.
C) It might not be worth the ROI to patch things up when what they need is a new website. Imagine trying to fix and patch up an old broken car where the repairs will cost so much that it’s not worth the investment anymore. This is why car insurance companies would rather pay for write offs, and websites are the same. If they are poorly built, hugely outdated, and just not getting the client anywhere without expensive “Frankenstein” development (you know what I mean, add a block here, link to something there, put some content on a sub domain….), then seriously, it’s time to blow it up and start from scratch. It will be a better long-term investment and, knowing WordPress well enough, combined with a top tier designer, you can build it to last more than two or three years.
Some Final Words About Playing It Safe When Taking on “Patch Up” Web Development Work
When you quote on a job like this, be sure to quote by the hour, not by the project since, as we’ve described above, even YOU don’t know how long it’s going to take you.
You don’t want to be held up to an expectation that will take you twice or three times as long to complete than you anticipated. Keep in mind that if you are in the scenario where the client came to you after trying to save money by attempting to make their own website, they will be on a budget, and may not have realistic expectations or values when it comes to hiring a professional. They may think it’s easier to do than it really is (thanks to the advent of dummy-proof website builders like Wix and Weebly).
Also, get very, very clear with the client what it is they are going to require of you. Don’t settle for instructions like, “just a few colour changes here and there” as a job description. It is pertinent to make it very clear WHAT is going to require a colour change. If you are not clear, this again will cause budget problems because the client will be imagining one thing, while you are imagining another, and the two ideas of what’s to be done can collide. The colour change example is just an example. Usually a client will ask you for something vague that you will later find out will take some serious hacking that, you either can’t do, or don’t want to do or, more likely, they can’t pay for.