Call it the third-oldest profession. Consultants have been with us since the days of cave paintings, and over that time they've learned a few tricks to extract money from their clients.
IT consultants are among the most slippery of the bunch. Among their favorite tricks: Using "scope change" to line their pockets, claiming expertise they do not actually possess, promising you their superstars and then sending in the rookies, purposely delaying decisions and sowing confusion as they rack up billable hours, and collecting kickbacks from other service providers. The worst ones may even hold your company's intellectual property or systems hostage until you pay up.
[ Also on InfoWorld.com: Learn how to avoid IT's biggest money wasters -- and how to assemble your crackerjack A-Team for IT special ops. | Get sage advice on IT careers and management from Bob Lewis in InfoWorld's Advice Line newsletter. ]
Not all consultants are like this, of course. We talked to several upstanding members of the profession about the worst tricks their ethically challenged colleagues try to pull and how IT can avoid becoming snared by them.
Of course, the client side often shares the blame, says Steven A. Lowe, CEO of Innovator LLC, a consulting and custom software development firm. Most consultant-client conflict stems from a lack of honest communication.
"The client expects the consultant to magically solve all of their problems without further input beyond the initial consultation session," Lowe says. "The consultant expects the client to tell them everything relevant, and fails to ask the appropriate and serious/hard questions. I call this the 'fairy godmother' problem, as each side expects the other to magically know when and how to rescue the other."
Here some of some of the worst tricks to watch out for. Don't say you haven't been warned.
This trick is as old as the hills. Consulting firms deliberately underbid to win your business, hoping to make it up via additional fees due to scope change and "customization." By the time the real bill surfaces, you'll be so invested in the project and/or the firm that it will seem cheaper to simply pay it and move on.
One reason is that if a service provider offers a realistic cost estimate, it will likely lose out to other firms that lowball it, says Steve Bogner, managing partner for Insight Consulting Partners.
"Most consulting firms know at the time they place their bid that the scope is too small for the results the clients want," he says. "But if they put in a bid to cover an expanded scope, they will lose."
Even if the consulting firm's bid hits all the key parts of your RFP (request for proposal), there's still plenty of flexibility when they drill down to how your requirements will be implemented, says Mike Meikle, CEO of the Hawkthorne Group, a boutique management and technology consulting firm.
"Since these requirements are all at a high level and subject to drastic change, firms use this knowledge as leverage for far higher fees -- usually $200 an hour or more," he adds.
The fix: Build some flexibility into your RFP, says Meikle.
"There should be an amount of leeway in the requirements/scope to avoid the 'out of scope' clause being used and additional charges from being incurred," he says. "How flexible the vendor is with this process should factor heavily in whether you select them to do the work."
You thought you hired the New York Yankees. But when it comes time to actually do the work, you get the Scranton Yankees.
One of the classic dirty tricks big services firms pull is to bring their best and brightest to the sales meetings to close the deal, then send in newbies fresh out of school to do the actual work, says Diana Kelley, a partner with research and consulting firm SecurityCurve. Worse, they may still charge you premium rates for staffers with minimal experience.
"Staffing with less experienced employees is fine as long as the customer knows what they're getting and aren't being charged senior staff rates for junior staffers," Kelley says, "Unfortunately, that's not always the case; some companies staff with low experience but bill at high."
A similar technique is also used when responding to RFPs, says Meikle.
"Consulting firms will pack their responses with all their top consultants' résumés," he says. "Then, when they win the assignment and sign the contract with the client, none of those top people are actually involved in the contract. Sometimes the résumés themselves are of consultants who either no longer work for the firm or who have never actually been an employee."
The fix: Be sure to meet the key team members who will be handling your project and ensure that they match up to the résumés that were provided, says Meikle. Also, stipulate in the contract that these are the people the vendor promised to provide.
"If they do not deliver these resources, add either a penalty or a means to acquire a resource with a comparable skill set," he says. "Normally, just requesting to meet the proposed team will disqualify some vendors due to their inability to present them to you."
It's true that Rome wasn't built in a day -- but it would have taken even longer if the workers had been paid by the hour. The longer things take, the more consultants make, which is why allowing indecisiveness to fester is a key tactic used to string out projects, says Patrick Gray, president of Prevoyance Group, a business strategy consulting company.
"When you have a large consulting team that helps manage an IT project, they can sabotage budgets and burn cash simply by enabling indecisiveness and allowing low-level analysts to accept any and all scope changes," he says. "Billable hours tick by unchecked as the consulting team dutifully schedules endless meetings and stands idly by as a three-day decision drags into a multimonth debate."
The fix: Stay on top on the management, scope, and scheduling of your IT projects, says Gray.
"While most consulting companies really do want you to succeed, there is always an inherent conflict in the relationship," he says. "As your project drags on and your revenue goes down, the consulting company's revenue goes up. You are always going to do the best job protecting your interests, so don't outsource that task."
You hire an outside firm to write some custom software, develop a website, or manage your infrastructure. Months later you decide to go with a different provider and discover you don't actually own the source code, the domain name, or the passwords to your network -- your services firm does. Sometimes the only solution is to pay the ransom or threaten to sue.
"I rescued a client recently from another company that was hosting servers for them containing their financial and personnel files, Exchange database, intranet -- the works," says Jeff Pagano, owner of cloud IT services firm Iconic Consulting. "This rotten apple was not happy about being dumped and was holding the client's data hostage until his demands were met. We had to get the client's lawyers involved before the consultant agreed to release the data, and then it was in a proprietary format. We ended up eating the cost of getting this data restored and into our data center."
Howard Sherman, founder of tech support and Web design firm RoyalGeeks.com, says the "we own you" strategy is the single worst tactic pulled by consulting scoundrels. He cites the experience of one RoyalGeeks client that was left high and dry by a former Web developer who was "cruel to the point of pure evil."
"The client had to register a whole new domain name and seek new Web hosting services because access to his own website and domain name was rendered impossible," he says. "Even worse, the contract stated that the entire site design -- including the databases driving the back end -- remained the developer's intellectual property. The business didn't legally own its own website. We had to push the reset button and redo everything from scratch."
The fix: First, carefully screen the consulting firm to make sure you're not hiring a scoundrel, says Sherman. Then make sure that ownership of any intellectual property or domains created by the consultant is clearly spelled out in the contract and demand copies of all documentation, including log-ins and licensing information.
Is your consultant strongly recommending a product or service from a third party? They may be getting a cut of any deal or incentives on the back end -- a nice second or third income on top of what you're already paying.
"Always make sure that you know how the consultant is getting paid so you understand their incentives," says Jeffrey Bolden, managing partner for Blue Lotus SIDC. "A consultant can be making money via billable hours as well as making commissions on products or bringing in other vendors. We avoid that conflict of interest by providing our clients with hardware or software at our cost, and bill just for the time of the engagement."
For example, a consulting firm may recommend an outsourced solution that will save your company money, but not nearly as much as if you contracted with the outsourcer directly, says Chris Smith, partner at strategy consulting firm ARRYVE. The consultants pocket the difference, and the client is never the wiser.
"The reality is that many big IT consulting firms are getting 100 to 300 percent margins on the outsourced resources they are providing," he says. "Sure, the client is getting cost savings, but this is probably one of the bigger areas where IT consulting firms are extracting money out of their clients."
The fix: Since you're unlikely to find out how big a cut your consulting firm is getting from the outsourcer, says Smith, your best bet is to ask for competitive bids, then negotiate a better price with the firm you want to go with.
You need a shovel, they'll sell you an earth mover. Want to manage your contacts? They'll convince you an enterprise-level turnkey CRM system is the way to go. Why? Because nobody makes money selling shovels and contact managers.
"My personal 'favorite' dirty trick is IT consultants who sell the client on a complex customized solution that takes months of time to implement when the latest out-of-the-box product would cover 80 percent of the functionality and 110 percent of what the client actually needs," says Mark Mueller-Eberstein, CEO of Adgetec, a consulting, coaching, and mentoring company. "With the current speed of technical innovation, most 'customized' solutions are outdated the time they are implemented anyway."
Eberstein points to a large international bank that hired consultants to create a content creation workflow for its country reports. The consultants said it would take six months to build an automated system. Using Microsoft SharePoint, the bank developed and rolled out its own system in two days.
Because many IT shops are paid by the applications and licenses they sell, their goal is to activate as many applications as possible, says Chris Stephenson, co-founder of ARRYVE.
"In a recent RFP meeting for our client, I asked the consultant's IT sales rep if we could automatically send quotes to clients from a central email," says Stephenson. "His response was to highlight a more expensive application in the CRM software that allowed chatter with clients, centralized all communications into one portal, used Twitter (really), and did a whole bunch of other great things. When he finished, I repeated my questions, and after a pause, he said, 'No, it is unable to do that'."
The fix: Be wary if the sales team is pitching great applications rather than focusing on your business requirements, says Stephenson. The applications often cost more than the feature you're requesting and sometimes miss the business problem completely.
No matter what problem you have, the consultant knows the solution. And if they don't know the solution, they'll pretend they do anyway. Faux expertise has brought down more than a few IT projects, usually after megabucks have been spent.
One of the worst dirty tricks is when consultants take on projects they're unqualified to handle, says Innovator LLC's Steven Lowe. Unfortunately this is often exacerbated by clients that assign committees of people with no understanding of the problem to oversee the consultant.
"When this situation occurs by accident, I call it the 'empty suit' problem," says Lowe. "When it occurs on purpose, I call it the 'vampire' problem. When the consultant is an empty suit, success cannot be delivered. Instead, the consultant attempts to prolong the project until the budget and participants are exhausted, or the consultant magically acquires the necessary expertise. If the consultant goes into the commitment knowing that success is impossible, the empty suit problem becomes the vampire problem."
But having empty suits on the client side can cause projects to grind to a halt due to the inability to make the right decisions, adds Lowe.
"Huge sums of money can be wasted before the project is killed," he says. "When both sides are empty suits, the project can go on so long that it drains the life out of the company."
The fix: Drive a stake into it. Create a reasonable but short deadline for a definitive action, result, or concrete plan to limit the damage and see where you stand, says Lowe.
"A measurable result by a specific date can be used as a stake in the ground to provide an anchor for the project," he says. "This anchor can serve as a short-term target or goal, a feasibility test for a proposed solution, a competency test of those involved, a visible measure of progress, and a deterrent to 'analysis paralysis'."
And if you don't?
"A committee with no incentive or deadline to act and little technical qualification may be quite content to bleed money to vampires until the original issue either goes away on its own or becomes someone else's problem."
- Dirty vendor tricks
- IT turf wars: The most common feuds in tech
- IT personality types: 8 profiles in geekdom
- A-Teams of IT: How to build your crack strike force
- Jackass IT: Stunts, idiocy, and hero hacks
- True IT confessions
- Stupid user tricks 5: IT's weakest link
- The dirt locker: Dirty duty on the front lines of IT
- Bridging the IT generation gap
- IT's biggest money wasters
- Quick and easy IT productivity wins
- The 7 deadly sins of IT management
- 20 more IT mistakes to avoid
- 16 ways IT can do less with less
- Seven things IT should be doing (but isn't)
- 5 reasons IT pros should be paranoid