You may want to consider a many to many relationship instead. This would be a new custom entity to hold all your possible technology/software products (a master list for lookup purposes). Then you create the many to many relationship between an account and the lookup list. In this manner you can have any number of relationships between the two. This offers more flexibility than a multi-select option-set as you can always add more software products to the master list and those then become immediately available for use in the many to many relationship. We use this concept for many similar situations and in doing so we prevent the situation where a sys admin has to update an option-set – they can simply add a new record to the custom entity and that makes it available for selection on the account record in the related list.
If you've found this thread useful, dive deeper into User Group community content by role