Current Situation

1. Inflated Opportunity Size on Public / Open Instances:

• • evaluationOpportunitySize currently calculates the opportunity based on the total registered user count of the host product (e.g., an open Jira instance showing 46,000+ public/community users).

• • It does not distinguish between actual paid/billable active seats and non-billable registered users, skewing conversion forecasting.

1. Lack of Host Licensing Context & Concessions:

• • The vendor License API and reporting exports return generic details such as parentProductName and parentProductEdition (e.g., Standard), but omit whether the host holds a Community, Open-Source, Non-Profit, Academic, or discounted status.

• • Partners lack the contextual data required to evaluate why a user count is high or qualify leads appropriately.

---

Suggested Solution

1. Surface Billable / Paid Active Users:

• • Introduce a dedicated field (e.g., billableUserCount or hostPaidSeats) in the vendor license API response and report exports that reflects the host instance’s actual billable user tier.

• • Alternatively, update evaluationOpportunitySize calculation logic to exclude non-billable and public user accounts.

1. Enrich Host License Metadata (withDataInsights payload):

• • Expose host-level classification and discount attributes, such as:

• • • hostLicenseCategory: e.g., COMMERCIAL, COMMUNITY, OPEN_SOURCE, NON_PROFIT, ACADEMIC, GOVERNMENT

• • • hostDiscountType / hostProgram: Indicators specifying if the host instance is on a specialized concession or discount tier.