Let's see what a typical meta is for:
- ...Writing Stack Exchange users to communicate with each other about Writing Stack Exchange (asking questions about how the websites work, or about policies and community decisions)
- ...Writing Stack Exchange users to communicate with Stack Overflow the company (posting bugs, suggesting improvements, or proposing new features), and
- ...Stack Overflow the company to communicate with the community (soliciting feedback on new ideas or features, or discussing policies that affect the whole network)
So unless it's something that is directly related to the website (e.g. if Word would have a plugin which converts a Word document to markdown which is directly pasteable into a Stack Exchange post), it's off-topic.
to have a place to incubate ideas and feedback.
This sounds rather broad for a single Q&A, too.
Of course, if you can demonstrate how your product solves a question on the main site, and you include affiliation, it's fine to post about it. This happens frequently on Software Recommendations, and also from time to time on the programming sites with libraries being 'promoted' by their authors. If done on the right question and it's genuinely a good solution, it's a win-win situation for all.
Otherwise, consider writing a paragraph about it in your profile, together with a 'read more' link.