Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are migrating everything off our core server shortly but we need outside expert help. We know what we want to do but we are nervous about the execution so we want to hire a reputable consultancy.

I want to contact a few consultancies to get quotes to do the implementation. But even this is unfamiliar territory. I am thinking of asking the consultancies for estimates for implementation times, costs, rollback plans, return to operation times and willingness to execute some the project remotely. I think there may be three to four days work spread over three to four weeks. Would this qualify as an sla? What information should we be asking for? What should we be looking out for in the replies and what should we be insisting on?


locked by HopelessN00b Jan 22 '15 at 6:07

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as not constructive by John Gardeniers, womble, Iain Nov 16 '12 at 20:20

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 0 down vote accepted

What you're looking for here is not an SLA, as an SLA is typically for ongoing support of a service, rather than an exceptional change to that service (as you're describing).

You may want to read up on the RFP process as it's used in IT consultancy/service procurement just as much as any other field:

As well as surrounding information on the responding parties that allows you to make informed decisions about whether they're a suitably capable and professional organisation, you should also get details in the RFPs about the proposed approach to the work to be performed.

All of this together should provide enough of a basis for you to select the best provider and method to meet your needs.


You've actually got a fairly decent set of things to ask for already. The fact that you're even thinking about asking about rollback plans and such suggests you're thinking a lot more about this than the average customer -- which puts you in a good place.

The trick is in evaluating the responses -- they'll all promise the world, and the more incompetent the staff, the more slick the tender response. It's tough, and ultimately a lot of it comes down to your "feel" for the person or people involved -- not a particularly good or scientific basis, but I'm yet to find someone who isn't in IT who can see through the bullshit (and to find someone who can see through the bullshit, you've got to... see through the bullshit. It's a circular problem).


One helpful thing to evaluate responses -- ask for references, CVs of people who will be assigned for the job, experience they have with similar projects.

This may be hard on companies who want to enter the market (how to get the first reference?), but it reduces your risk (lower chance they will be learning too much on your project).


Not the answer you're looking for? Browse other questions tagged or ask your own question.