first, it uses "PM" in the title, but note that upbase is a
project management tool, not a product one. project management tooling could be viewed as a subset of product, but in other ways, project management is a related, but separate discipline.
second, if your product management processes deliver no value to your colleagues, then you may need to work on that, perhaps more as an organization than an individual pm. the product management process and tooling should absolutely deliver value to developers, designers, and other individual contributors. most pertinently, tracking velocity is for the team first and foremost, and secondarily for others. it's like keeping score in basketball--it's how the team knows how it's doing.
third, it may be big and "enterprisey", but jira is just fine for product/project management. when folks complain about jira, ~99% of the time, it's a complaint about the process and people involved, but turned toward the tool because it's hard to criticize the offending party directly.
i do agree that product management tooling is secondary to sales, marketing, finance, accounting, etc., and so must interface with those other systems for "truth" rather than being a system of record.