I recently read that describing your pricing as a fraction of costs saved by the product, makes it easy for customers to understand and accept it.
Well, then here we go:
Quick sidenote that Testmap for Jira's main target customers are big corporates with lot's of applications to maintain, lot's of business processes to handle and a bunch of projects (maintaining or enhancing of their software landscape) to deliver throughout the year.
Pricing model
Testmap for Jira is a cloud add-on for Jira Software. As such, a company pays for the same amount of users as it has licences for the underlying Jira Software.
Let's take a rather average sized company with 500 Jira users. This is what the math would look like:
Calculation
Take an average daily rate of 1000€ for a testmanager. If you happen to be one yourself ask yourself these questions (or if you are not, then ask a testmanager from your company or someone else you know with expertise):
Well, I will go out on a limb are and say that every testmanager (or his or her sidekick) will spend way more time over a course of a whole year for handling these tasks than just the roughly 9 days needed, to make up for the yearly investment (9 days * 1000€ daily rate = 9.000€).
Yet you can do all of these tasks with the help of Testmap for Jira in literally under 10 minutes.
So even if using Testmap for Jira would only help with the aforementioned jobs (which is far away from what it really offers), this would already be financially beneficial. For ONE project! Think about how many projects your company does throughout the year and multiply it with this factor.