26
May 2010

To rent or to buy?

I recently had an enquiry from a potential client who were looking to have their site updated. By updated I mean alteration to their existing site and not a redesign (yet). The client does have the aspirations to one day spend time and money on their site as they recognised that 99% of their business is brought in through their existing web presence and understand it's a strong marketing tool.

In our various communications they have outlined their immediate requirements and went on to describe their hopes for the future and how they'd like their site to work for them one day. This immediately said to me that they have the right idea but will need guidance on how to acheive it so I set up a meeting.

Dead money.
So, in a quaint little pub in a nice little village we begin to talk over the requirements and it becomes all too apparent that their business is growing at a rate their current site can't keep up with. My suggestion was to map out what they would like the site to do (in a dream situation) and allow me to cost that out with them. The reason I chose to do this is that all too often people just don't know what web development should cost and only seem to imagine it costs nothing or way more than they can afford. My aim was to demonstrate to them that if they continue to spend money on frequently updating their site over the period of a few years that this was in effect 'dead money', as they would ultimately be doing a full overhaul at some point anyway.

My suggestion was to consider the idea of getting their ultimate goal costed, breaking that into a phased approach and seeing if this scenario was more beneficial and more affordable. This option would enable them to make the changes they want make when they want to make them (obviously through a CMS), thus giving them total control over their end product.

After reading a recent blog post by @robynslingsby about the pitfalls of shared ownership and the arguments for renting versus buying, this all got me thinking... There are some similarities to be drawn here. I am the property owner in this scenario and the prospective client is the buyer. Their choices are to either rent my services on an on going bases or alternatively they can take the leap and buy outright.

A moral argument.
In my mind I would consider it immoral of me to not make these suggestions to a client. To simply take their money to update their site now and then pitch a rebuild to them later on would be entirely unethical. Of course if they choose to take that option then it is there for them but at least they have made an educated decision and I can take the client on with a clear conscience.

My question is...
Which side of the fence should we sit, should we take the clients money and do what they asked without question or should we attempt to better educate the client in the hope they do the right thing for themselves whether you get the business or not?

 

May 26, 2010
SimianE said...
Personally, I'll always try and tell the client what I think's best for their business in the long run. If my clients do well, then I've done a good job... and also, most clients are unaware of how much can be achieved with a good web presence.
Having said that, a big rebuild takes time and money, and often clients have neither. Sometimes a simple update is what's needed immediately, with a view to more in the future. It's tough for me as a developer, to limit my vision of what I know I can achieve - but sometimes there just isn't the time to go full blown on a project.
I think the best you can do is, as you have, make the client aware of all the options available too them and let them make the choice. That honesty and openness will hold you in good stead with them as their business grows... A small update today... tomorrow, the world!
May 26, 2010
punkeyfunky said...
@afovea Wearing my vendor manager hat: present the client with the options, and let them decide. When I'm spending my money for my company, my goals aren't necessarily laid out to the vendor I'm working with. This might be because I'm choosing to withhold them, because there isn't yet a specific strategy, or that what I do know is confidential and can't be shared.

If I'm talking to a vendor it's because:
a) I want them to do a job (rather than do it in house)
b) I'm *asking* for their input, opinion and ideas (mostly within the criteria I specify)

I am looking for relatively simple (as much as possible!) answers:
- what are the options?
- how does each option work in the short/mid/long term?
- how much will each option cost?
- can I change my mind? if I do what is the impact?

When presented with the options I can make an informed choice.

Oh and for the record, you're what I'd consider a "vendor" :)

-Lee

May 26, 2010
Richard Leggett said...
I would agree, it's never in the client's or your best interest to take the money and simply do what they want. You wouldn't hire an architect and hand over detailed plans; that confuses who the expert is here. You'd let them know what your requirements are, some things you like and see what they can do to help realise it.

As SimianE points out, you won't be thanked for it when it crumbles and they get someone else to do the site next year.

Of course it depends on the project. If it's a campaign site, it only has a shelf life of a year or so, and so you can go wild. For a company's site, and in this particular case, I would strongly push the CMS option, Drupal for example.

This would allow them to choose to utilise your services in a big initial effort, creating the structure and methods for updating, and then allows them to choose cost options later, either updating simple copy and images themselves (for them this provides value, for you, no mundane maintenance time which could be spent getting new clients), or for bigger changes and additions they can get you in to do some heavy work. This is as you have already suggested.

The other important thing you point out is re-builds. After 3-5 years websites really start to show their age. They are more like company cars in this respect. The analogy of buying a car on higher-purchase fits quite well, there's money to be paid regularly, and after the term you buy a new one and start again.

One thing I would disagree with is that you aren't the property owner, they are. You're the architect and maintenance men, it's ultimately their responsibility to get the best people in to maintain the thing else broken windows will be introduced.