Update License Key Logic to Implement Ops Tier Pricing While Maintaining Classic Licensing for XD

Date: July 7, 2025

Version: 0.2 (Discovery Phase)

Contributors: @Douglas Erickson (Deactivated)

The Problem & Our Current Understanding

For our business to launch its new strategic pricing tiers, we must update our licensing system which currently blocks this initiative. This is critical now because the inability to generate and validate licenses for new tiers is the sole blocker to a key company initiative aimed at driving revenue growth and better serving distinct market segments.

Evidence: This project directly enables a top-level company strategy. The cost of inaction is a 100% block on launching the new "Core," "Fleet," and "Enterprise" pricing plans, delaying projected revenue growth indefinitely.

Target Users & Context

Primary Persona Profile: Customer Manager / Supervisor at a client company. This user is responsible for the overall function and value of the software. They are not deeply technical but need to ensure that the license they purchase unlocks the features they were sold. They operate in a business environment where software downtime or incorrect feature access can disrupt daily operations and carries a real financial cost.

Jobs-to-be-Done (JTBD): When I purchase a new software tier and apply my license key to the Operations application, I want to immediately access all the features I've paid for, so that I can get the business value I was promised without delay or disruption.

• Current Pains & Impact:

  • Business Pain: The inability to launch new pricing tiers prevents the company from capturing new market segments and realizing revenue growth. (Impact: Blocks strategic company goals).

  • Sales Pain: Sales Representatives cannot sell the new, more profitable tiers because there is no mechanism to provision them. (Impact: Lost sales opportunities).

• Current Workarounds:

  • There are no workarounds. The inability to generate a valid license key is a hard stop, which makes this project business-critical.

• Secondary Stakeholders:

  • Internal Sales/Billing Team: Care about ease of generating and issuing the correct keys.

  • Internal Support Team: Care about understanding the new system to troubleshoot effectively.

  • Classic X Dispatch Users: Care that their existing application continues to work without any changes or disruption.

Key Objectives & Success Metrics (FY2025 Q3-Q4)

• Objective 1: Successfully enable the launch of the new pricing strategy.

  • KR1: The first 10 license keys for the new tiers are successfully generated and provisioned to customers by the launch date. (Leading)

  • KR2: < 5 critical support tickets related to incorrect license validation are reported in the first 30 days post-launch. (Lagging)

• Objective 2: Ensure a seamless and non-disruptive transition for all users.

  • KR1: Achieve 100% pass rate on the regression test suite confirming backward compatibility with the classic X Dispatch application. (Lagging)

  • KR2: Sales & Billing teams achieve a 95% score on a readiness assessment after training on the new license generation tool. (Leading)

Hypotheses & Assumptions

• Opportunity Hypothesis:

  • We believe that by updating our internal licensing infrastructure to support tiered plans, we can successfully enable the launch of our new pricing strategy. This will empower our Sales team to provision customers on the appropriate tiers, resulting in immediate revenue growth and better market alignment, without disrupting our existing classic user base.

• Key Risks & Assumptions:

  • Technical Risk: The new license key structure might have unforeseen conflicts with the classic X Dispatch application, causing instability.

    • Mitigation: Build a proof-of-concept and conduct rigorous regression testing against the classic application early in the development cycle.

  • Process Risk: The new internal process for generating keys could be confusing for Sales/Billing, leading to errors.

    • Mitigation: Conduct a workflow mapping workshop with Sales and provide clear documentation and training before rollout.

  • Dependency Risk: The timeline is dependent on the readiness of the go-to-market teams to launch the new pricing.

    • Mitigation: Hold regular cross-functional sync meetings with Marketing, Sales, and Product to ensure alignment on the launch date.

Discovery Partners & Interested Customers

As a backend-focused project, the primary discovery partners are internal. However, for beta testing the end-to-end process, we will engage with:

• CXT User Group Members: Key members who have expressed interest in new advanced features, making them ideal candidates for the "Enterprise" tier. (Status: To be contacted).

• New Sales-Led Customers: A small number of new customers in the final stages of closing a deal who are targeted for the new tiers. (Status: To be identified by Sales).

Validation Plan (Next 4-6 Weeks)

This plan covers the initial discovery and technical validation from July 8, 2025, to August 18, 2025.

• Key Questions to Answer:

  • What is the process for a customer moving from an existing tier to a new tier mid-cycle?

  • What is the defined error handling and support process if a license key fails to validate?

  • Do we need the ability to generate time-limited trial licenses for the new tiers?

  • Is the audit logging in our internal tool sufficient for troubleshooting and tracking?