You are a typical IT services company.

Ever noticed how near-identical the website of any standard small-to-medium sized IT services company is? They all say the same thing in different words.

Here are a few stereotypical statements:

• We have a well defined SDLC/Agile methodology: No, you do not. What you have is the following:
• Incomplete requirement specs
• Templated design documents
• Superficial project plans
• Inexperienced coders
• Missed milestones
• Artificial deadlines
• We are quality-oriented: No, you are not. Continuing from the above, what you have is:
• A QA team that tests everything manually and whose test cycles are counted in weeks.
• Delays in QA release builds from development team.
• Increasing pressures on QA teams to compromise on their testing to meet above-mentioned artificial deadlines
• fights between engr and QA teams about deadlines and definition of bugs.
• We use industry standard best practices: No you don't. You either:
• do not have a single document that actually outlines what that "best practice" is.
• If you do, it is a vague document created by someone is response to a past crisis.
• It is lying on a backup file server and nobody has actually ever read it after it was created.
• Our engineers are the best: No they are not. You have 1 or 2 "HR executives" who work their butts off coordinating with recruitment agencies that flood you with unsuitable resumes and setting up interviews with overworked senior developers who have their own deadlines to meet.  Your engineers are whoever you could hire in the one-month "ramp-up" period that you wrangled out of your customer.
• We are customer-oriented: No you are not. You have a process that requires at least weekly conference calls with customers because your team is incapable of coming up with the right solutions on their own and want customer validation every step of the way.
• We are low cost: - no, you are not. You have a top heavy team with non-billable mid-level management layer that contributes the most to your project costing. You try to make it justifiable by explaining that they are a shared cost across multiple projects. In times of crisis, this same team will gather in a meeting room and cast accusatory looks at the poor innocent coffee machine lying in the corner.

Are you really different from the rest?