Erika L Walker-Arnold wrote:
>Yeah, it's all back-ed up, etc. that's not an issue at all.
>
>It's someone with enough knowledge of the web industry basically
>"inheriting" the business and keeping it running.
>By the time all is said and done there could be over 400 sites running
>on 3 different servers that just need support and possibly further
>services.
>
>I really like the hosting company solution, as we're pretty tight with
>them. they know CF, they already manage and have access to the servers.
>Probably find a few point people to handle the clients and get
>agreements drawn up.
>
>Does that sound pretty feasible?

Yes. The most important part is probably documentation. The person that inherits everything needs to know exactly what the recurring tasks are and has to have a full list of contacts, deadlines etc.

If you can draft up a nice contract with your hosting company or a buddy, I bet some of your customers will even want to pay for this sort of insurance.

>Whatever we do, it also needs to have a bit of cascading to it, meaning
>we can let someone "inherit" the business, but what if something happens
>to them just days later? How many levels would you take care of and/or
>arrange?

I would expect one level to be enough.

>We take all this pretty seriously and I have no intention of
>letting anyone "hang out to dry" because that would be horrible. Well, I
>think so anyway...

Weird as it may seem, a detailed procedure for switching to another hosting provider, whether before or after your own business has ceased to function, can be a very good way to attract customers. It has to include stuff like the right to receive a copy of the site, a copy of the database, configuration files etc.
You should not hand it to them without explanation (that looks very weird), but taking care of exit strategies in a contract is a much overlooked part of business.

Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to