Custom software qualifies when the development work is technically new for the company and it is genuinely uncertain at the start whether the approach works. Think of an integration between warehouse system, ERP and carrier that does not exist yet, or a calculation model for planning or purchasing that is in no standard package.
What does not qualify: buying off-the-shelf software, setting up or configuring Exact, AFAS, SAP Business One, Dynamics or Odoo, switching on a standard connector, or building a standard website. A wholesaler that only sets up existing software does no research and development work. We say so, and no proposal follows.
RVO assesses three things: (1) the project involves a "new information technology principle", an approach that is new for the organisation, not necessarily for the market; (2) there is real technical uncertainty whether it works, so routine development does not count; and (3) the work consists of systematic development activities. A common mistake is describing the business problem instead of the technical one.