IBM Support & Services Negotiation

Negotiating IBM Service Credits: A Strategic Guide to Maximizing Value

Negotiating IBM Service Credits

Negotiating IBM Service Credits

IBM software deals are known for their complexity and high costs. Beyond the software licenses, IBM and its partners offer a range of services from consulting to training that can significantly impact your success with the product.

Service credits are a negotiating tool savvy buyers use to extract more value from a deal without simply asking for a deeper discount. Read our comprehensive guide, IBM Support & Services Negotiation: Cutting Costs on Support, Cloud, and On-Prem.

These credits serve as pre-paid vouchers for IBM services or training that would otherwise incur additional costs.

By securing service credits during negotiations, you can offset implementation costs, accelerate user adoption, and improve ROI on the IBM investment.

However, it’s essential to approach these negotiations strategically and with a healthy skepticism. IBM’s sales teams may not volunteer service credits upfront, and when they do, the credits often come with limitations.

In the sections below, we explore the landscape of IBM services available, explain how service credits work, identify prime opportunities to negotiate them, and outline the key risks to be aware of.

Finally, we share proven tactics and recommendations to help you confidently negotiate IBM service credits and secure a better overall deal.

IBM Services and Training: What’s Available

IBM is not just a software vendor – it’s also a global services provider. Understanding the types of services IBM offers will help you know what to ask for in your negotiation.

Key categories include:

  • IBM Consulting / Global Services: IBM’s consulting arm (formerly IBM Global Services) provides a broad range of professional services. These include strategy consulting, technical architecture design, software implementation, system integration, and project management. In the context of a software purchase, IBM Consulting can assist with deploying the product, configuring it to meet your needs, or providing business process consulting to ensure you derive maximum value from the software. Their expertise is deep, but their rates are premium – often several hundred dollars per hour. This means any consulting days or hours included as service credits can represent significant value (and cost savings) if you plan to use IBM’s experts for deployment.
  • Product-Specific Services: Many IBM products come with specialized “Expert Labs” or product-specific services. These are teams focused on a particular IBM software (for example, IBM WebSphere Lab Services or IBM Data & AI Expert Labs). They offer targeted assistance, such as health checks, performance tuning, custom coding, or best-practice setups tailored to that product. When negotiating a software deal, you can ask for credits to use these expert services. For instance, if you’re buying an IBM Cloud Pak or a security software package, IBM might provide a certain number of hours for its product specialists to help implement it. These services ensure you can hit the ground running with the new software and often are shorter engagements compared to full consulting projects.
  • Partner-Delivered Services: IBM has an extensive ecosystem of certified partners and resellers. These business partners often provide implementation and support services for IBM products, sometimes at a lower cost or with more regional presence. In negotiations, IBM might agree to fund partner services as part of the deal. For example, instead of IBM’s own consultants, a local IBM partner could deliver the deployment using service credits from IBM. The result for you is similar – you get expert help without extra cost – but a partner on IBM’s behalf does the work. It’s important to ensure the partner is qualified and that IBM coordinates the arrangement. Partner-delivered service credits can be useful if IBM’s own team is booked up or if a partner has specialized knowledge of your industry.
  • IBM Training Programs: Beyond hands-on consulting, IBM offers formal training and education for its products and solutions. This includes instructor-led courses (virtual or on-site), online self-paced learning subscriptions, and certification programs. Training ensures your team can effectively use and manage the IBM software. As part of a deal, you can negotiate training vouchers or credits that allow your staff to attend IBM training courses at no additional charge. IBM Training vouchers might cover, for example, a week-long admin course for two employees, or a certain number of online class hours. Including training is a double win: it saves you money and boosts user proficiency, which in turn helps you realize the value of the software sooner.
  • Typical Cost of Services: IBM services are high-value but come at a high cost if purchased separately. Consulting engagements can easily run into the thousands of dollars per day per consultant. Similarly, a week-long IBM training class for one person may cost several thousand dollars. Knowing this, service credits worth even 5–10% of the software deal value can translate to a substantial amount of consulting hours or training seats. For example, an additional $50,000 in service credits might equate to roughly 20-30 days of IBM consulting time (depending on rates) or multiple enrollments in training courses. Being aware of service pricing helps you gauge how many credits to request. It also reminds you that IBM has a considerable margin in services, giving you $50k of consulting, which likely costs IBM much less than a $50k discount off software license revenue. This is why IBM might prefer to add services over further reducing the price, and why you should seize that opportunity.

Read about IBM third-party support, Third-Party Support for IBM Software: Can You Cut Costs (and Is It Worth It)?.

How Service Credits Work

Service credits can be a fantastic bargaining chip, but they come with their own structure and fine print. It’s crucial to understand how they operate so you can maximize their use and avoid surprises.

Here’s how IBM service credits typically work:

  • Structured as Hours or Vouchers: IBM service credits often come quantified either as a set number of hours/days or as specific vouchers. In an offer, IBM might state, “40 hours of consulting services included” or provide vouchers equivalent to a specific service (for example, one voucher = one day of an expert’s time or one training class enrollment). In some cases, credits may be denominated in currency value (e.g., “$30,000 worth of IBM services”). However, even value-based credits will internally translate to a certain scope of work or time. Always clarify the unit: is it 40 hours of a consultant’s time? Is it a “pack” of services, such as a health check engagement? Knowing this helps you plan their use and ensures IBM delivers the equivalent expertise or work hours you expect.
  • Scope of Use: Service credits usually have defined usage scopes. They are typically intended for use with services related to the products you are purchasing. For instance, if you buy IBM Security software and get service credits, IBM expects you to use them on security software deployment, configuration, or related training – not on an unrelated IBM project. Some credits are broad (e.g., can be applied to any services from IBM’s software group), while others are narrow (only for a particular product’s lab services or only for training courses). During negotiation, ask for flexibility in how you can apply the credits. The more freedom you have to choose the type of service, the more valuable the credits. Also, verify whether the credits can be used for on-site consulting, remote assistance, or only for predefined service packages. Understanding the scope ahead of time prevents a situation where you attempt to use the credit for a needed task, only to be told it’s out of scope.
  • Expiration Terms: “Use it or lose it” is a common condition with service credits. IBM will set an expiration date by which the credits must be consumed – often aligning with the annual cycle or contract term. For example, credits might expire 12 months after the deal is signed, or by the end of the next calendar year. Expiration is a risk for you (we’ll discuss later), but it’s also a motivator to plan services early. When negotiating, aim to secure the longest possible validity for the credits (e.g., 18-24 months instead of 12) to provide your team with more scheduling flexibility. Mark the expiry date on your calendar and make sure everyone internally knows about it. IBM certainly won’t remind you when your free services are about to lapse.
  • No Cash Value / Non-Transferable: IBM service credits are not redeemable for cash or other discounts. This is usually explicitly stated in the contract. If you don’t use them, you can’t ask IBM for a refund or apply the unused value towards license costs or support renewals. Additionally, service credits are generally non-transferable outside your organization. They are provided to you (the customer) as part of your purchase – you can’t sell them or give them to another company. In many cases, even within a large company, the credits might be tied to a specific project or business unit. Ensure the right internal team can utilize them. Also, check if IBM restricts transferring credits to a partner. For example, if you prefer a certified partner to do the work, does IBM allow the credit to cover that partner’s fees? Typically,
    IBM would handle the arrangement if so, but it’s worth asking. Bottom line: treat service credits as a one-time, use-it-here-only bonus, not a currency.
  • Operational Details: To actually use your service credits, you’ll need to coordinate with IBM’s services organization (or the partner designated). This usually means scheduling the services in advance. Don’t assume you can call IBM a week before the credits expire and immediately get a consultant on site – lead time is important. Engage your IBM account team or the services project manager early to plan out when and how to utilize the credits. Ensure there’s a clear process for redemption, such as a special code in the contract or a clause stating that IBM services will invoice those hours against an internal budget, rather than billing you directly. Clarify who can authorize the use of the credits on your side (you don’t want confusion if a department tries to use them without procurement’s knowledge). Also verify if there are any additional costs when using the credits. Often, the credits cover labor for consulting or training fees, but expenses such as travel costs for on-site work or certification exam fees (in the case of training) may be separate. Knowing these details will help you avoid any “surprise” charges – you want the included services to truly be free. Finally, track usage of the credits internally: keep a record of how many hours or vouchers have been used and how many remain, so you utilize them fully before they expire.

Negotiation Opportunities

Not every buying scenario is equal when it comes to asking for service credits. There are certain moments and deal situations where IBM is more inclined to agree to these extras. Being aware of these opportunities can give you leverage to negotiate more effectively:

  • Large Deals and Enterprise License Agreements (ELAs): In big-ticket deals – such as enterprise license agreements covering multiple products or a large, multi-year software purchase – IBM has more at stake and greater flexibility. When you’re committing a significant spend, IBM is keen to ensure the deal goes through and that you can successfully deploy what you’re buying. This is the prime time to request service credits. In fact, IBM often proactively includes some services in large proposals (e.g., a “customer success manager” or a few weeks of an expert’s time) to sweeten the offer. Don’t settle for the token amount. In an ELA negotiation, for example, you might push for an annual pool of service hours each year of the term, ensuring continuous support. Large enterprises can also negotiate for custom workshops or even co-development efforts with IBM as part of a strategic partnership – these are essentially specialized service credits. The bigger the deal, the more you should aim to get a proportionate amount of services bundled in.
  • End-of-Quarter or End-of-Year Pressure: Timing Can Be Your Ally. IBM sales teams face quarterly and annual targets. As the end of a quarter (especially Q4) looms, the urgency to close deals increases dramatically. At these times, even if your deal is small to mid-sized, the representative might be under quota pressure. If you’ve hit a limit on discount or if pricing is largely agreed but you haven’t signed yet, that’s an opportunity to ask for “just one more thing” – like some service credits – to seal the deal. Often, adding extra value through services doesn’t require the same executive approvals as offering a substantial discount on the software. It may come out of a different budget or be seen as a concession that maintains the software’s price integrity while still making the customer happy. For example, in late December, you might say: “We’re very close, but our management would be more comfortable signing if IBM could include, say, 100 hours of consulting to help us implement.” Chances are, the rep, eager to book the deal, will work to make it happen. Just be sure to have that commitment in writing (quote/contract) before you sign.
  • When Discount Limits Are Reached: Every vendor, including IBM, has internal guidelines on how far they can discount a product. You might reach a point in negotiation where the sales team says, “We’re at our floor price” or “We can’t discount further without higher approvals.” Whether or not that’s true, it’s a signal that pushing more on price alone may yield diminishing returns. At this stage, shifting the conversation to service credits can break the logjam. Perhaps IBM can’t drop the price by an extra 5% without obtaining CFO approval, but they might be able to include $20,000 worth of services with far less bureaucratic hurdles. To IBM, that $20k in services might only cost them the internal cost of consultants (and they may have bench resources available), whereas a $20k discount is a direct revenue hit. So if you sense you’ve hit a discount wall, pivot: “Alright, if we can’t go lower on price, how about including some training and deployment support to make this a complete solution for us?” Often, you’ll find the door opens to negotiate services at that point.
  • New Product or Strategic Sale: If your purchase involves a new IBM product or a solution area that IBM is actively promoting, you have leverage to obtain extras. IBM places strategic importance on certain offerings (for example, AI and analytics, cloud services, or new acquisitions they’re promoting). For these, IBM is hungry for successful deployments and reference customers. They know that if you succeed with the new product, you’ll speak positively about it and likely expand usage. IBM might even have special programs or funding to support these sales (sometimes called “adoption funds” or similar). Use this to your advantage: express that you want to adopt the new tech but need help. For example, “We’re excited about being an early adopter of Product X, but we’ll need some hands-on assistance from IBM to get it running right.” This sets the stage for IBM to offer service credits for initial setup or architecture guidance.
    In some cases, IBM will include a few weeks of an expert’s time for new products by default – but if they don’t, definitely ask. Also, suppose the product is new to the market. In that case, IBM might have a smaller pool of knowledgeable consultants externally, so negotiating access to their internal experts (developers or lab specialists) via service credits can be incredibly valuable.
  • Competitive Situations: When IBM knows they are in a competitive battle for your business, it will pull out more stops. If you’re evaluating IBM versus other vendors (Oracle, Microsoft, SAP, or a SaaS alternative, for instance), make it clear to IBM that the overall value of the deal will decide the winner – not just the license price. Competitors might offer free implementation or training as part of their proposal. You can use that: “We like IBM’s solution, but Vendor Y is offering to include the first phase of implementation at no extra cost. This makes their total proposal more attractive.” Whether or not Vendor Y truly did, IBM will feel pressure not to lose value. In response, IBM can match or beat that by including its own service credits. Even if there’s no competitor explicitly offering it, you can hint that “others have offered us incentives like training – can IBM do something similar?” In competitive scenarios, the key is to make IBM believe that the inclusion of services could be the deciding factor. This often unlocks additional concessions, as the IBM team will justify internally that these credits are necessary to win the deal. Just be prepared to show commitment if they meet your ask – don’t bluff about competition unless you’re ready to move if IBM says no.

Risks & Pitfalls

Service credits can certainly add value, but buyers need to be clear-eyed about their limitations. If not managed well, these “free” services can lead to disappointment or underutilization.

Here are the main risks and pitfalls to watch out for:

  • Expiration = Use It or Lose It: The most common pitfall is simply not using the credits before they expire. It’s easy for organizations to become caught up in the rush of a new software deployment and then become preoccupied with other priorities. Months go by, and before you know it, that generous “100 hours of consulting” included in your deal has only 10 hours left unused – and a looming expiration next month. Once expired, those credits are no longer available. IBM isn’t obligated to extend them (unless you negotiate an exception, which can be difficult after the fact). This is literally lost value. To avoid this, treat service credits like perishable goods: plan their use from day one. Identify projects or needs for which those hours will be allocated, if it’s training vouchers, schedule employees for classes right away. If it’s consulting time, get the SOW (Statement of Work) drafted with IBM services as soon as the main contract is signed. A proactive approach ensures the credits don’t quietly expire unused.
  • Limited Scope – Not All Services Qualify: A nasty surprise can be discovering that the service credits won’t cover the particular help you need. Perhaps you assumed your credits could be used for on-site hands-on keyboard implementation, but find out they’re only valid for remote advisory support. Or you try to use training credits for a specialized advanced course, and learn that it only applies to standard introductory courses. IBM may restrict credits to certain service categories or specific teams. For instance, credits might be good for “IBM Expert Labs for Cloud Pak deployments” but not for general consulting on integrating with non-IBM systems. Always double-check the fine print on what’s included. If something critical is excluded, negotiate upfront to broaden the scope or have that particular service included separately. Also, be mindful that partner-delivered services might not accept IBM’s credits unless there’s an arrangement – if you prefer a particular third-party, clarify if the credits can fund their work or not. The more specific you can be on intended use cases for the credits in the negotiation phase, the less risk of a mismatch later.
  • Quality and Availability of Experts: Not all service engagements are equal. Ideally, when you use your credits, IBM will send its A-team to assist you. However, there’s a possibility that “free” services may not get top priority in scheduling or staffing. For example, if the region’s star architect is fully booked with paying client projects, your included consulting hours might be fulfilled by a more junior resource or delayed until someone becomes available. Additionally, if you wait too long to redeem credits, you may encounter availability issues (e.g., “all our trainers are busy during Q4, the next workshop slot is in 3 months”). This can diminish the value of the credits – what good is “free” help if it arrives too late or with less expertise than you needed? To mitigate this, involve the services team early and emphasize the critical nature of the engagement. Sometimes you can even name the desired consultant in the contract or SOW if you know someone great. If the quality of support matters, state this during negotiations: for example, request that a senior architect be allocated for at least X hours. While IBM won’t promise specific people in the sales contract, raising the concern sets an expectation. Also, consider using credits sooner rather than later, when IBM’s motivation to make you happy (early in the customer lifecycle) is highest.
  • Non-Refundable, No Substitution: Service credits are typically one-way offerings – once agreed, you can’t later swap them out. Let’s say you negotiated $30k in training vouchers, but later realize you needed consulting hours more – IBM is unlikely to convert those training vouchers into consulting days for you midstream. The same goes for if you only use part of the credits; you can’t apply the remainder to something else, like support fees. This means you should carefully match the type and amount of credits to your actual needs during the negotiation. It’s wise to err on the side of the services you’re most certain to use. If you know you’ll use consulting but aren’t sure about training, push for more consulting hours and fewer training vouchers (or vice versa). Once the contract is signed, you have what you have. Another substitution issue arises if circumstances change – for example, you negotiated on-site consulting, but then all work goes remote; those credits might technically be for on-site only. Getting IBM to adjust them later is not guaranteed. Thus, build in flexibility if possible (e.g., wording like “credits can be used for on-site or remote services, as needed”). And remember, no refunds – if you negotiate way more credits than you can realistically use, you’re leaving money on the table.
  • Hidden Costs: “Free” services aren’t always completely free. One common hidden cost is travel expenses. IBM might include 10 days of consulting, but in the fine print, travel and living expenses for those consultants are billable to you. If they need to fly people in or have them on-site, that could add thousands of dollars that you didn’t budget for. Negotiate travel cost responsibility upfront – ideally, get IBM to cover it or at least set a cap (or opt for remote delivery where feasible). Another hidden cost can be the environment setup or prerequisites. For example, IBM will conduct a workshop using your credits, but you need to provide the necessary sandbox environment, data, or other resources. If you don’t have those ready, you might need to spend money to prepare for the “free” service. Additionally, consider the opportunity cost: if you use IBM’s credits, IBM might subtly steer you towards using more of their products or services down the line (a form of upselling). While not a direct cost, it’s a strategic consideration. Lastly, if the included services don’t cover everything, you might end up paying for additional days beyond the credit. IBM will happily continue the work on a time-and-materials basis once you’re out of credits. Always clarify what happens if the scope requires more effort than the credits cover – will IBM stop at the limit, or continue and bill you? Avoid being surprised by an overage.
  • Dependency on IBM (or Partner): Using IBM’s own services can create a degree of dependency. This is a subtle risk: by relying on IBM consultants for implementation or support, you may not develop as much internal capability with the product. Later, you could find yourself reliant on IBM (or the partner) for ongoing changes or optimizations, which, of course, would be at additional cost. It’s not to say you shouldn’t use the help – just be mindful to involve your team in the process and use the opportunity to learn, rather than simply handing off all the work. Additionally, IBM’s approach to solving problems will naturally involve IBM tools and methods, which could shape your environment in a way that favors staying with IBM’s ecosystem. If you’re okay with that, fine, but if your strategy is to stay flexible, ensure the services work includes knowledge transfer to your team and is done in a standard way that you can maintain. Lastly, an obvious point: if the deal includes partner services credits, you become dependent on that partner’s availability and quality. Ensure you vet the partner or have the option to choose a different one if necessary. In summary, use the free services wisely – treat them as enablement for your team, not a crutch that leaves you tied to IBM for every tweak.

Negotiation Tactics That Work

Securing service credits from IBM requires effective negotiation techniques.

Here are some tactics, refined from real-world deal experiences, that can increase your chances of getting what you want:

  • Ask Early and Clearly: Don’t treat service credits as an afterthought or a “nice-to-have” tossed in at the end. The earlier you signal your interest in including services, the more seriously IBM will take your request. For example, when you provide initial requirements or an RFP to IBM, explicitly state that you expect proposals to include a services component or training credits. By making it part of the baseline expectation, you frame the deal as more than just a license sale. IBM reps are trained to listen for key deal requirements – if from the start, one of yours is “this solution must come with deployment assistance”, they will factor that in. Additionally, being clear means quantifying it: don’t just say “some services,” but rather specify “we are looking for at least 3 weeks of on-site consulting support in the package.” Clarity gives the rep something concrete to ask their management for approval on. Remember, if you wait until the final contract review to bring up service credits, IBM may claim budgets are exhausted or it’s too late to change the deal. Early asks can be baked into the deal structure more smoothly.
  • Leverage the Adoption Angle: IBM wants your implementation to succeed – especially if the sale is strategic or could lead to more licenses in the future. Use this fact as a bargaining chip. Frame service credits not as a concession on price, but as a mutually beneficial investment in success. For example: “IBM, we want to ensure we roll out your software company-wide and get full adoption. To achieve this, we’ll need expert assistance in the initial phases. Including services in this deal will help ensure we become a long-term success story for you and potentially a reference account.” By positioning it this way, you appeal to the IBM rep’s desire to see the project succeed (and thereby buy more later or look good to their bosses). It’s a relatively low-cost give for IBM if they believe it secures a happy customer. This approach can soften resistance – you’re not just asking for freebies, you’re aligning interests. In some cases, IBM even has internal programs (like “client success funds” or similar) that sales can tap specifically to boost customer adoption. If you hint that, without proper services, your project might stumble, IBM has an incentive to ensure you get that help.
  • Tie It to the Deal Closure: Simply put, make service credits a condition of saying “yes.” This is a classic negotiation move: when the deal is almost there but you have one sticking point left, use your willingness to sign as leverage. For instance, tell the rep or sales manager: “We’re ready to sign this week if you can include X amount of services at no extra charge.” The key is timing and credibility – you should indeed be prepared to sign if they meet the condition. This tactic is most effective near the end of negotiations, when IBM has invested a significant amount of time and is eager to finalize the deal. They’ll weigh the cost of those extra services against the risk of delay or losing the deal and often find a way to justify it. When using this tactic, be specific and firm. “We need 50 hours of training included to move forward – it’s the final approval item on our side.” Also, obtain a written agreement as soon as possible (even an email) once they confirm, to avoid any “I didn’t say that” scenarios. Salespeople sometimes test if you’re bluffing, so be ready to hold your ground. If they push back, you can reiterate how small an ask it is relative to the deal size, or remind them that you’re choosing IBM partially because you expect better support like this.
  • Benchmark and Bluff (if needed): Information is power in negotiations. If you have colleagues or industry peers who have done deals with IBM, find out what they got. Perhaps another company got “200 hours of lab services” included in a similar deal – use that as a benchmark. You can bring it up by saying, “In our industry, we know of other clients who received significant service assistance in their IBM agreements; we expect the same level of commitment to our success.” You don’t have to reveal names or details – and IBM will rarely confirm or deny what others received – but it signals that you are an informed buyer. If you lack real benchmarks, a little bluff can be employed carefully: for example, implying that a competing vendor’s proposal includes services, or that you have alternative quotes. Be cautious with bluffing – it should never be outright false about something that is easily verifiable. However, saying “We have a comprehensive offer on the table from Competitor X that includes training and migration help” can push IBM to match. Sometimes, even mentioning Gartner or consulting advice, such as “our consultants advise that we insist on services being included to ensure success,” adds weight. Essentially, you are creating an external justification for your request, which helps the IBM salesperson in getting approval internally (“the customer is asking this because their policy or a competitor offer demands it”). Just be prepared: IBM might ask what specifically the other offer includes – so have a plausible answer or pivot to emphasizing you simply expect IBM to provide equivalent value.
  • Get It in Writing (Contractual Clarity): Verbal promises or even email notes about service credits are meaningless if they don’t appear in the final contract or purchase order. IBM deals often consist of a main license agreement and maybe a separate statement of work or an order document for services. Ensure that the negotiated service credits are documented in one of these binding documents. It should detail the quantity and type of service credit, as well as any key terms (such as expiration date and scope). For example, if you negotiated “80 hours of IBM consulting services to be delivered within 12 months at no charge,” that exact phrase (or an official equivalent) must appear in the agreement. If it just says “IBM will provide implementation assistance,” that’s too vague and unenforceable. Also, avoid fuzzy wording like “IBM may provide up to 80 hours” – may is not will. Insist on firm commitments. It’s also a good idea to include a reference to which part of IBM (or which partner) will deliver the service, to avoid finger-pointing later. Don’t sign until the contract reflects every aspect of the service credit deal. If the contract is complex, work with your legal or procurement team to double-check that nothing got left out in the final edits. Many unfortunate buyers have signed, thinking they’d get something, only to find it was dropped in legal review or was in a side email, but not the contract. Protect yourself by treating service credits like any other line item you paid for – documented and enforceable.
  • Validate the Value of Credits: Sometimes IBM will dangle a large-sounding number of service hours or dollars, but you should sanity-check what you can actually do with those credits. 100 hours of general consulting is useful, but “100 hours of junior offshore support” might not be. Similarly, “$100,000 worth of training” sounds huge, but if each course costs an inflated $5k list price, is that 20 training seats? Do you even have 20 people who need training? In negotiation, don’t be immediately wowed by the face value IBM attaches to the credits – work out the real utility. Ask IBM for a menu of how the credits could be spent. For example, “what would 50 hours cover in terms of deliverables? How many days on-site is that?” If they say $50k of training, ask “how many students or classes does that typically equate to?” Ensure the credit amount aligns with your planned usage. Also, sometimes a smaller amount of the “right” kind of service is better than a larger amount of less useful service. For instance, 5 days of an expert architect on-site might drive more value than 15 days of a generic trainer. You could negotiate quality over quantity: “Instead of 10 generic vouchers, we want 5 days with your senior WebSphere specialist.” By validating value, you not only avoid overestimating what you got, but you also demonstrate to IBM that you’re knowledgeable, which can lead them to take your requests more seriously.
  • Confirm Services Team Commitment: A clever tactic is to loop in the IBM services team (or partner) during the negotiation process. While the sales rep focuses on closing the software sale, the actual delivery of services might be someone else’s responsibility. Have a meeting or call with the services delivery manager or the IBM Expert Labs team early on. In that discussion, talk about your needs and ensure they acknowledge what is being promised. You might ask, “Have you guys reserved capacity for these 3 weeks of consulting around our go-live?” or “Will the trainer be available in Q3 when we plan our workshop?” Getting affirmative answers – or at least raising the question – helps avoid a scenario where the sales team promises credits but the delivery team later says, “We’re overbooked.”Furthermore, involving them sometimes creates an internal champion for your cause. The services team often welcomes funded work (even if it’s “free” to you, it counts as utilization for them), so they might encourage the sales team to include sufficient scope. When you finalize the contract, you can even request that the specific services SOW be attached or completed concurrently. The ideal scenario: as you sign the software license, you also sign a brief SOW that says “IBM will perform X services, for Y days, starting roughly Z date, billed against the service credits at $0 since it’s prepaid
    .” That level of clarity locks everyone in. In summary, don’t accept service credits in a vacuum – get the delivery details ironed out and make sure IBM’s teams are on the same page to deliver what was promised.

Comparison: Standard Deal vs. Negotiated Deal with Service Credits

To illustrate the impact of negotiating service credits, the table below compares a typical software purchase from IBM with and without service credits included:

AspectStandard Software Deal (No Credits)Negotiated Deal (With Service Credits)
License DiscountStandard discount on software (e.g. 15-20% off list).Similar software discount (e.g. 15-20%), plus additional value in services. The software price isn’t lowered further, but extra services are bundled in.
Implementation ServicesNone included. Customer must self-implement or hire IBM/partners separately at additional cost.IBM (or an IBM partner) provides implementation assistance as part of the deal (e.g. a set number of consulting hours/days at no charge). This accelerates deployment and reduces out-of-pocket implementation costs.
TrainingNot included by default. Any user or admin training would require a separate purchase of courses or training subscriptions.Training vouchers/credits included. For example, your team gets to attend IBM training courses or workshops without extra fees. This improves user proficiency and is a direct cost saving on enablement.
Support & AdoptionStandard product support only (helpdesk for issues and updates via Support contract). No proactive guidance beyond what you pay for.Enhanced adoption support. The included consulting can be used for best-practices guidance, environment tuning, or even a post-deployment health check. This hands-on support improves time-to-value and software usage success.
Total Offer ValueSoftware licenses + basic support. Any services are extra, so total value equals what you pay.Software licenses + support + services bundle. The buyer gains additional value (often 5-15% of deal value in services) at the same price, effectively getting more for the money. ROI is higher if credits are utilized fully.
Cost CertaintyLower upfront cost on software, but unknown services cost later (could be significant if you need help). Budgeting for full project implementation is harder, as services are a variable expense.Upfront cost includes needed services, providing cost certainty for the project. Fewer surprise expenses pop up during deployment. The business case is stronger when implementation and training are accounted for in the deal.
RisksRisk of under-utilization of the software if the customer skims on hiring experts (due to cost) or faces delays (lack of skills). No expiration concerns, since nothing extra is included.Use-it-or-lose-it risk: service credits must be used by expiry or they’re forfeited. Also need to ensure availability of IBM resources. However, if managed, the risks are mitigated by upfront planning. The overall risk of project failure is lower due to expert involvement, but the buyer must actively manage the credits.

Key Takeaway: A negotiated deal with service credits transforms the transaction from a pure product sale into a more solution-oriented package.

The customer ends up with the software and the help to use it effectively, for roughly the same financial outlay.

In contrast, a standard deal might appear cheaper at first glance, but often leads to higher costs later for consulting and training, or worse, a failed implementation if those services are not procured. Thus, savvy buyers lean towards deals that include service credits to ensure successful outcomes.

Read about IBM Premium support, IBM Premium Support: Getting Enhanced Support Without Excess Cost

FAQs

  • Will IBM include deployment services with software purchases? – It’s not standard practice, but it’s negotiable. IBM typically sells deployment services separately; however, for large or strategic software deals, you can request a certain amount of implementation assistance to be included in the purchase.
  • Can unused service credits be refunded or converted to a discount? – No. Unused service credits expire worthless. They can’t be cashed out or applied as a price discount later. This is why planning their use is crucial – you either use them within the term or lose them.
  • Can IBM training vouchers be used globally or only within a specific region? – IBM training vouchers are generally usable across IBM’s global training network for your company’s employees. They aren’t transferable to other companies. Some vouchers may be region-specific due to local training partners, so it’s wise to verify any geographic restrictions when you receive them.
  • Are service credits negotiable during renewals, or only for new purchases? – You can negotiate them in both, but it’s more common with new purchases or major expansions. During renewals or extensions, you have less leverage, but if the renewal is significant (or if you hint at exploring alternatives), IBM may agree to include some service credits to secure the renewal. Always ask – the worst they can say is no.

5 Actionable Recommendations for Buyers

Finally, here are five actionable tips for anyone negotiating an IBM software deal, to ensure you maximize value through service credits and beyond:

  1. Make Services Part of the Deal Strategy: Before you even engage IBM, decide what kind of services (implementation help, training, etc.) you’ll likely need and treat them as must-haves in the negotiation. Communicate this early to IBM so they factor it in.
  2. Time Your Negotiation for Leverage: Align your deal discussions with IBM’s quarter-end or year-end when possible. IBM is more likely to include extras, such as service credits, when it is under pressure to close deals and meet targets.
  3. Insist on Contractual Clarity: Ensure that every promise – especially service credits, their scope, and expiration dates – is clearly outlined in the contract. Do not rely on verbal assurances. If the contract language is vague or missing these items, push back and get it added before signing.
  4. Plan to Utilize Credits Immediately: Once you secure service credits, don’t put them on hold. Assign project owners to schedule the consulting or training. Treat the credits as project tasks with deadlines, so they are used fully and effectively.
  5. Learn and Build Independence: Use the IBM-provided services to train your team and document knowledge. The goal is to become self-sufficient after leveraging the credits. This way, you get the immediate benefit of IBM’s expertise while reducing long-term dependence on paid services.

By following these recommendations, you will approach IBM negotiations with a tactical mindset – extracting more value, avoiding common pitfalls, and setting your organization up for a successful implementation.

Negotiating service credits requires some extra effort, but the payoff in support and savings can be well worth it. Good luck with your IBM deal!

Read about our IBM Negotiation Service.

IBM Support Negotiation: How to Cut Support Costs on SaaS, Cloud & On-Prem

Do you want to know more about our IBM Negotiation Service?

Author
  • Fredrik Filipsson

    Fredrik Filipsson is the co-founder of Redress Compliance, a leading independent advisory firm specializing in Oracle, Microsoft, SAP, IBM, and Salesforce licensing. With over 20 years of experience in software licensing and contract negotiations, Fredrik has helped hundreds of organizations—including numerous Fortune 500 companies—optimize costs, avoid compliance risks, and secure favorable terms with major software vendors. Fredrik built his expertise over two decades working directly for IBM, SAP, and Oracle, where he gained in-depth knowledge of their licensing programs and sales practices. For the past 11 years, he has worked as a consultant, advising global enterprises on complex licensing challenges and large-scale contract negotiations.

    View all posts