Skip to content
dvnt.io

Resources · glossary

Custom software

Software written for a specific company and its process, instead of bought off the shelf. You pay for the fit, and for the fact that nobody can change the rules or the pricing overnight.

Also called
  • custom software
  • bespoke software
  • custom software development
  • tailor-made software
  1. 01

    When off-the-shelf isn't enough

    When the process is your company's advantage rather than its burden. Then adapting to someone else's tool means giving that advantage away. In other cases a ready-made product usually wins on price and time.

  2. 02

    What you buy besides the code

    The rights to it, the documentation and a real ability to change supplier. These three decide whether in two years you have a system or a hostage situation, and they are settled in the contract, not after the fact.

  3. 03

    Where the risk lies

    In maintenance. A custom system has no community, no tutorials and no ready-made plugins; every change needs someone who knows it. The budget for development after launch is part of the decision, not a footnote.

  4. 04

    How to reduce the bill

    Start with the smallest version that genuinely takes the load off one process, and expand it based on usage. A full scope written down before the start almost always includes features nobody opens later.

In practice

Related terms

  • Build vs buyThe decision between building your own solution and buying a ready-made one. It is settled on costs over time and on whether the process is the company's advantage or just a necessity.
  • MVP (minimum viable product)The smallest version of a product that genuinely solves a user's problem and lets you check whether anyone will use it. Not a prototype, and not a version stripped of quality.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.