Product Requirements Documentation - Pricing and Packaging

Target release	Sep 30, 2025
Epic	Type /Jira to add Jira epics and issues
Document status	DRAFT
Document owner	@Douglas Erickson (Deactivated)
Designer	@David Walters
Tech lead	@Dave Martin
QA

Objective

https://docs.google.com/spreadsheets/d/1Rq8xMLvyxEWpbp6hehkt4p_rxiGvr803MCsIrONoK6U/edit?usp=sharing

The primary goal is to define and enforce which product capabilities are available in each pricing tier (including add-ons), connect this to billing, and introduce in-app paths for customers to upgrade.

Core Concepts & System Requirements

Company Product Tier: A system concept will be created to map customers to a specific product tier: Core, Fleet, or Enterprise.
Product Features: A system concept will be created to map features to specific tiers.
Features not included in a tier may be available as an "add-on."
Billing Integration: The new tier and feature concepts must be integrated with the existing billing logic to ensure customers only have access to what they have paid for.

Tiered Feature Distribution

Operations

Core Customers: Do not have access to Basic Shipment Optimization.
Core Customer Add-Ons: Can optionally purchase Route & Distribution, Advanced Shipment Optimization, and SMS Messaging.
Fleet Customer Add-Ons: Can optionally purchase Advanced Shipment Optimization (Itinerary Planning)
Enterprise Customers: Receive all Operations features.

Client Portal

Core Customers: Do not have access to Route & Distribution, Route & Distribution Driver Tracking, White Labeling, a placeholder for an Embedded Chat Widget, and a Personalized URL.
Fleet Customer Add-Ons: Can optionally purchase a Personalized URL.
Enterprise Customers: Receive all Client Portal features.

Driver App

Core Customers: Do not have access to Routed & Distribution, Depot Scanning, Bulk Receive Scanning, and Over Short & Damaged Tracking.
Fleet & Enterprise Customers: Receive all Driver App features.

In-App Upsell Strategy

Phase 1: All features unavailable to a user's tier will be hidden in the specified applications.
Phase 2 (Scope Only):
- Unavailable features will be made visible in Operations but clearly marked with "Fleet" or "Enterprise" tags.
- An in-app marketplace will be created for Admins to add Add-On features and integrations.
- An in-app subscription management experience will be created for Billing Admins to upgrade tiers and add users/drivers.

Success metrics

Goal	Metric
Commercial
Operational
Product Analytics

Assumptions

Tiered access assumes the software will cater to the needs of the courier by offering varying levels of features.
Offering various price points allows access to companies that may require budget flexibility
Offers scalability and options to the customer.

Milestones

2025

2026

Lane 1

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Jan

Feb

Mar

Apr

May

Pricing & Packaging (Phase 1)

Requirements

Requirement	User Story	Importance	Notes
Entitlements Service (Core Creation) Creating the foundational concepts of tiers, features, and add-ons within the system's architecture	As a Developer, I need to create the "Company Product Tier" concept in the system's data model and business logic so that each customer account can be assigned to a specific tier (Core, Fleet, or Enterprise).	HIGH	This may already exist in some degree with the implementation of Professional and Enterprise Licensing
	As a Developer, I need to create the "Product Features" concept in the system, which can be mapped to one or more product tiers, so that we can define which features belong to which tier.
	As a Developer, I need to extend the data model to support à la carte "add-ons," ensuring a feature can be enabled for a customer independently of their base product tier.
	As a Developer, I need to build the core enforcement logic in the codebase and APIs that checks a customer's tier and add-ons to grant or deny access to a specific feature, so that entitlements are enforced system-wide.
Tier Matrix (Rule Implementation) Translating the defined feature matrix into enforceable rules within the newly created Entitlements Service.	As a Developer, I need to implement the specific entitlement rules for the Operations portal, ensuring Core customers are blocked from "Basic Shipment Optimization" as defined in the product requirements.	HIGH
	As a Developer, I need to implement the specific entitlement rules for the Client Portal, ensuring Core customers are blocked from features like "Route & Distribution," "White Labeling," and "Personalized URL".	HIGH
	As a Developer, I need to implement the specific entitlement rules for the Driver App, ensuring Core customers are blocked from features like "Routed & Distribution," "Depot Scanning," and "Bulk Receive Scanning".
	As a Developer, I need to implement the rules ensuring Fleet and Enterprise customers receive all Driver App features as specified in the requirements.
Config & Billing (Integration) Creating the critical link between the Entitlements Service and the financial/billing system.	As a Developer, I need to create a robust integration layer that connects our new Entitlements Service with the current billing system so that features a customer receives are always in sync with what they are paying for.
UI/UX (Frontend Implementation) Work for the front-end team to consume the Entitlements Service and display the correct state to the user.	As a Front-End Developer, I need to integrate with the Entitlements Service to conditionally hide UI components for features that are unavailable to a user's tier, fulfilling the Phase 1 requirement to not degrade the user experience.	HIGH
Phase 2 (Scope Only)
Config & Billing	As a Developer, I need to build the backend functionality for an in-app marketplace where a Billing Admin can select and purchase add-on features, which must successfully trigger the billing system and update the customer's entitlements upon completion.	HIGH
	As a Developer, I need to build the backend functionality for in-app subscription management that allows a Billing Admin to upgrade their company's tier, which must handle the change in the billing system and update the customer's "Company Product Tier" in our system.
UI/UX	As a Front-End Developer, I need to build UI components that fetch entitlement data and display "Fleet" or "Enterprise" tags next to unavailable features, creating the awareness required for the Phase 2 upsell path.
	As a Front-End Developer, I need to build the UI for the in-app marketplace, including the card layout for add-ons, based on the UX prototype and designs.
	As a Front-End Developer, I need to develop the inline upgrade "nudges" (tooltips and modals) that appear when a user interacts with a feature they are not entitled to.
Analytics & Launch	As a Product Manager, I need to build analytics events to track user interactions with gated features and upgrade nudges so that we can measure the commercial success of this project.
	As a Product Manager, I need to create new internal and customer-facing documentation that details the features and limitations of each new product tier.
	As a Product Manager, I must design and document a "Migration Playbook" that defines the technical and communication steps for transitioning existing customers to the new tier structure.

User interaction and design

Placeholder: UX will produce a prototype showing:

Tier‑based navigation states (visible, grayed‑out, hidden).
Inline upgrade nudges (tooltip + modal).
Marketplace card layout for à‑la‑carte add-ons.

Target date for clickable Figma: June 27.

Open Questions

Question	Answer	Date Answered
Edge Cases
Onboarding
Security
Timeline
Marketplace Alignment

Out of Scope

Changing individual price points.
Implementing discount logic, promotions, or reseller contracts.
Re-platforming the legacy billing system (the project will only integrate with it).
Feature redesigns that are not related to feature gating.