What is Direct COTS Software Purchase?
Going through an integrator adds a markup and can even shake quality — a story about buying straight from the maker.
The integrator buys the press machine and adds its own margin.The client doesn't know the maker's actual price.
The integrator sometimes even swaps in a cheaper model quietly.The integrator's chase for margin can even lower the machine's quality.
Direct COTS purchase = the client contracts straight with the maker.The integrator only installs and connects it, and sets no price.
Side by side, bundled and separate procurement clearly differ on margin and price.Transparent pricing and no product swaps are the main payoff of separate procurement.
Direct purchase still leaves contract work to manage.Prices turn transparent and quality holds, but the purchase and install contracts each need tracking.
Direct COTS purchase = having the client contract straight with the maker for commercial software, while the integrator handles only installation and integration — a public-sector IT procurement practice.
In public IT projects, when a system integrator (SI) bundles in the purchase of commercial off-the-shelf software, hidden markups and budget-driven downgrades to cheaper products can creep in. To prevent this, public projects above a set size have the client contract and buy COTS software directly from its maker or supplier, barring exceptions such as when integration isn't feasible, while the SI handles only installation, integration, and customization. This aims to keep pricing transparent and pay software its fair value.
When grown-ups say it
- Direct COTS Purchase
- The client contracting straight with the maker. The core of separate procurement.
- Split/Separate Procurement
- Splitting purchase and installation into separate contracts. The procurement structure that makes direct purchase possible.
- COTS
- Commercial software that already exists off the shelf. What direct-purchase rules apply to.
- System Integrator (SI)
- The company that assembles the pieces into a whole. Handles only installation and integration after direct purchase.
- Fair Value Payment
- Paying software its proper price without discounting it away. One of the goals behind the direct-purchase rule.
- Scope Change
- Requirements changing partway through the contract. Still a risk to manage even under split procurement.
- Subcontract Management
- Overseeing work a contractor passes on to another company. Public software projects cap subcontracting by law.
- Conditions of Good Software
- Buying it directly doesn't automatically guarantee quality. Quality is ultimately judged by these conditions. → what makes a good book