Home / Our Blog

Archive for the ‘Site Planning’ Category

Why You Don’t Want to Pay Your Web Developer for Updating your Website

Saturday, January 23rd, 2010 by Andrew Kucheriavy

Most companies prefer to update their own websites using built-in Content Management Systems. However, once in a while, we meet customers who are resilient to this idea and prefer a web developer handling it for them. To explain why it isn’t the best idea, I have decided to put together this list of Five Reasons you Don’t want your web developer doing this work for you:

cms-value1) Higher Cost & No Savings
We have estimated that the cost of having a web developer updating a website over the course of its lifespan can add up to 2-3 times the cost of integrating a Content Management System (CMS) and having the website updated internally.  In some cases, this cost becomes a contributing factor to why websites become stagnant and don’t get updated for years (terrible for search engines and company image).

2) You Are Not in Control
If you can’t update critical information on your own website, you are not in control of your own website. What if your web developer goes out of business or you can’t get a hold of them?  How you are going to publish that special promotion, correct a typo, or update important contact information?  Having the ability to control content on the website is of utmost importance for any business.

3) Delays & Low Priorities
The truth is that web developers don’t like maintaining and updating websites. It is hardly profitable and tedious work that always gets pushed to the end of the task list.   Resulting from this, customers can wait for the longest time to get their website updated. With a Content Management System built into the site, you can update your own website from the comfort of your office and on your own timetable.

4) Missing out on Long Term Benefits
Having a Content Management System on your website also has long term benefits: Since the content is kept separate from the design, the site can be easily redesigned without any change to the actual content.  With the content stored in the database, web developers can easily integrate the existing content into a newly designed web site.  This allows for a site to be upgraded more frequently in order to keep up with the latest trends and technologies. 

5) Wrong Perceptions
Despite what some think, having  a Content Management System on your website doesn’t cost much, it  is not difficult to use (if you can read this blog or use Microsoft Word, you will be to update content using CMS), and doesn’t take up much of your time.  It is secure and easy to use and for all the reasons above is the best tool your business website can have.

Five Questions to Ask Your Web Developer BEFORE Starting Your Project

Wednesday, January 20th, 2010 by Ilya Bernshteyn

You’re looking for a web project that meets your requirements, so make sure to do your due diligence and ask questions before diving in. This will help both parties get on the same page.

1) Your competition uses a particular Content Management System, what would they say it does better? After all, you are looking for the company that will best suit your needs.

2) How much time will this really take to get done? Often times schedules change as requirements get fleshed out and to arrive at an exact schedule, a development team needs to spec out the project.

3) How will my project be supported? There may be a ticket system, forum, 800 number, dedicated individual or even someone overseas as infamously pioneered by some big computer manufacturers. This is important since your websites will be a new piece of software to you and you will have questions.

4) How do you document the project? Projects are often planned in phases depending on complexity. A proposal starts the project and a technical specification gets into the details so that developers know what to do.

5) What’s the cost for the project? Here, on a project of moderate complexity, you actually don’t want an exact answer since the team you introduced the project to must get into the technical details, think through features, research APIs if that are being used, etc. and get their heads around the amount of work involved.

This list isn’t all encompassing, but should provide you with some common sense things to think about on your next web 2.0 development project.