Kapan Mereka Membutuhkan Bantuan dalam Negosiasi Kontrak TI dan Perangkat Lunak?
Feeling overwhelmed with the fine lines about data ownership and overages? Not sure how bad the software agreements will fire back once you go-live? Don’t understand how to compute the total cost of ownership for complex pricing models such as consumption-based pricing? KANO IT and Software Contract Negotiation services are designed to help companies when they struggle with these challenges.
Tidak Ada Pengalaman dalam Pengadaan Perangkat Lunak Perusahaan yang Kompleks
Pertama kali membeli perangkat lunak perusahaan? Bingung dengan istilah perangkat lunak perusahaan seperti modul, hak akses, dan korelasinya dengan perizinan? Takut vendor akan mengambil tindakan dan kemudian mendapatkan tagihan yang besar? Perusahaan mencari bantuan dari KANO ketika mereka tidak memiliki pengalaman dalam pengadaan perangkat lunak perusahaan yang rumit dan persyaratannya yang berbelit-belit.
No Experience Understanding How Architectural Decisions Drive Software Costs
No experience with enterprise architecture? Relatively new to estimating how complex interactions of systems might drive the pricing? Limited experience understanding why queue or EDI may drive your pricing? Companies seek help from KANO when they don’t have experience understanding how architectural decisions drive software costs.
Limited Experience In Understanding Financial Risks Embedded In Software Contracts
Not sure if you fully understand the software contracts? Not sure about the financial risks embedded in the software contracts and how they might fire back in the future? Companies seek help from KANO when they need help understanding financial risks embedded in software contracts.
No Experience With Complex Pricing Models Such As Transaction-Based Pricing
Not sure how consumption-based pricing works? Confused about how your business transactions might drive the price of your technical transactions? Overwhelmed with technical terms such as API-based pricing and connectors? Companies seek help from KANO when they don’t have experience with complex pricing models such as transaction- and consumption-based.
Limited Experience With Add-On Risks
Not sure how vendor conflict could result in substantial charges? Confused about how add-on pricing could end up being more than the core software? Relatively new to add-ons and their impact on pricing? Companies seek help from KANO when they might not understand how add-ons work and how they impact pricing.
Limited Exposure In Understanding Different Licensing Models
Not sure how to estimate the costs for on-prem vs. cloud? Not sure how entity-based, user-based, and consumption-based pricing compare? Not sure how the user access might drive licensing? Companies seek help from KANO when they have limited experience with different software licensing models.
Metode Kami
Our Methodology For IT And Software Contract Negotiation
The process starts with an assessment of the current architecture and licensing agreement in place. By comparing ElevatIQ’s proprietary database, each line item is compared for potential discounts and financial risks. The review process also redlines the contract items and identifies any financial risks. Then through a series of negotiations with software vendors, an appropriate plan is built to get the maximum discount from the software vendors.
Step 1: Contract And Architecture Review
This phase takes a deep dive into the software contract and architecture. As well as identifying potential issues embedded in the software contract. Through a series of meetings with the customer and vendors, a plan is laid out for the discount or missing pieces that could increase the costs substantially later on.
Step 2: Negotiation
This negotiation phase works with software vendors as they revise the contract. A comparison, along with ROI and TCO analysis, is provided for each option. As well as briefing the team with different options.
Step 3: Award Of The Contract
This phase is the final negotiation phase, where a series of demonstrations may be required to ensure that there are no more red flags with the finalized vendor and contract. Once satisfied, the contract is awarded to the final vendor.
Indonesian