Do You Need A Website Negotiator?

by Beth J. Bates on February 9, 2009 · 3 comments

I can only dream of being as cool as Shatner in the Priceline Negotiator commercials. But I do what I can…

Along with consulting on social media and marketing, I do a lot of technical web development work. My background is in custom software development and project management and over the years, I’ve worked on the prickly projects – by that I mean projects that include a special challenge.

One of these challenges that keeps popping up (and that I feel is the all-time most unprofessional issue ever) is dealing with a client’s website that’s being held hostage by another developer. Often this other “developer” has decided upon another calling, couldn’t make it in the web biz or wants to bleed the client dry by forcing them to pay for updates. It is one of the most deplorable situations in the web business and I can’t believe how often it happens. Most times clients are trusting and just want to give the guy the benefit of the doubt…until they can no longer get him on the phone and can’t get to their website.

If your website is fairly simple, a good developer can pull the site from a web browser and replicate it. This is by no means a “good” solution, but it will work as a last resort. Flash can be uncompressed and re-coded. Images can be recreated. But, this takes time and money that, technically, you’ve already put into your website.

Here are a few things to keep in mind when working with a new web developer. If your developer ever refuses to give you access to the items below, you may want to consider someone else.

  • Ask for login credentials to everyting. Here are the most important items to keep on file:
  • FTP Information for the server. This consists of a URL, user name and password. If the developer refuses to give you this information for their own server, suggest that he develop/host the live site on your own server. Hosting is cheap and sites can easily be moved from one server to another. If the developer is using his own development server, ask how you will be able to get this code if he is not available. Small shops are great to work with but can be problematic if only one person has access to the code.
  • Domain credentials. Sometimes development shops and ISPs will register your domain on your behalf. Be sure to either ask for the credentials so you have access to your domain, ensure that they add you as a contact on the account or move the domain to your own registrar. When the domain is up for renewal or you need to move servers, you’ll need this information.
  • Database information. If you are running any databases, ask for the DSN, database path,  user name and password. Also ask to receive a regular backup of the data if the developer is hosting the website. Your data is like gold and you want to ensure that you have access to it at all times.
  • Ask who you should contact if you can’t get in touch with your developer. Things happen. People get sick or are into accidents. You want to know who you should contact should your developer be unavailable.
  • Be proactive. Ask your developer for regular updates or weekly status reports. Be sure that you are “in the loop” as the project progresses. I suggest a weekly status call or email with larger projects. You’ll have an increased comfort level and your developer knows that he or she always has a set time for a discussion.

When your website is being held “hostage” or your developer has disappeared there is a feeling of helplessness. But, there are folks out there (like me) who have dealt with uncooperative developers, hostage websites and recovery efforts. So, before you pull your hair out, give a website negotiator a call. We’re here to help!

Share and Enjoy:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • email
  • FriendFeed
  • HelloTxt
  • LinkedIn
  • MySpace
  • Netvibes
  • Ping.fm
  • Reddit
  • RSS
  • StumbleUpon
  • Yahoo! Buzz

{ 3 comments… read them below or add one }

Tracey Holinka February 13, 2009 at 7:48 am

Beth great tips for those thinking about getting a website. I’ve run across websites being held hostage several times in my practice and had to wrangle them free. Often the other “developer” was not a professional but someone who just put up a shingle.

Beth J. Bates February 14, 2009 at 8:09 pm

Thanks for the great comment, Tracey. It’s sad that this situation happens as much as it does. As the client, you are vulnerable and many times don’t even know that you are being taken advantage. I’m all about being proactive and if someone doesn’t want to share information with me, it’s an immediate red flag.

Lori February 16, 2009 at 10:04 am

Most problems of this nature are easy to avoid. I design, build, and maintain web sites, and here’s the advice I give to all of my clients. NEVER let a web developer register your domain name for you. (Because then they technically own it.) You can go to register.com and do it yourself easily enough. NEVER let a web developer sign you up for or provide your web hosting account. Do it yourself. (See domain name advice.) If the web developer doesn’t work out, then all you have to do is find someone else and change the password to your accounts. At the very least, this will prevent your site from being “hijacked,” and a web developer with integrity should insist on it being this way. I always prefer that my clients sign up for their own domain name and web hosting accounts (though I guide them through the process as needed). Along with protecting my client’s interests, I avoid having their accounts on my credit card as well. It’s best for both parties.

Leave a Comment

Previous post:

Next post: