Design Brief

Project Introduction

This project is to design an in-app "Marketplace" section for the Operations app. The primary goal is to provide a self-service experience for our customers to discover, purchase, and activate additional features ("add-ons") and connect third-party services ("integrations").

Currently, our product is offered in three tiers: Core, Fleet, and Enterprise. Many features are only available in higher tiers or as paid additions. The process for a customer to add these features currently requires manual intervention from our sales or support teams. This new marketplace will streamline that process, allowing for instant provisioning of new functionality. This is expected to increase Annual Recurring Revenue (ARR) through upsells and improve customer satisfaction by making feature discovery and activation seamless.

The designer should refer to this spreadsheet for a comprehensive understanding of what features are available at each tier and which are considered add-ons.

Users and Needs

• Users: The target users are existing customers, specifically the administrators of their company's account. These are the individuals with the authority and need to manage their subscription, enable new workflows, and make purchasing decisions.

• User Needs & Goals:

  • Discoverability: Users need a centralized place to easily see all the features and integrations available to them that are not part of their current subscription plan.

  • Clarity: Users need to clearly understand the value proposition of each add-on/integration, what it does, and how it will benefit their business.

  • Transparent Pricing: Users need to understand the cost associated with an add-on, whether it's a one-time fee, a recurring charge, or if it requires a full subscription upgrade to a higher tier.

  • Self-Service: Users want to be able to activate (and potentially deactivate) services on their own, instantly, without having to contact a sales representative and wait.

  • Distinction: Users need to understand the difference between a native feature unlock (an "add-on") and connecting to a third-party service (an "integration"), as this may have implications for their workflow, data, and billing.

Tasks

The design should enable a user to perform the following primary tasks:

• Browse & Discover: Navigate to a dedicated "Marketplace" or "Add-ons" area within the application.

• Search & Filter: Search for specific add-ons and filter the view by relevant criteria. The design should explore filtering/sorting controls, considering categories (e.g., Finance, Customer Portal) and type ("Add-on" vs. "Integration").

• Evaluate Options: View a detailed page for each item that includes:

  • A clear description of the feature and its benefits.

  • Pricing information.

  • Any prerequisites (e.g., "Requires Fleet tier subscription").

  • Screenshots or short videos demonstrating the functionality.

• Activate Add-ons: For a straightforward add-on (e.g., SMS Messaging for a Core user), the user should be able to complete the purchase and activation flow entirely within the app.

• Initiate Upgrades: For features that require a higher subscription tier (e.g., Health Data Protection), the user should be clearly informed and guided to initiate the plan upgrade process.

• Manage Existing Services: View which add-ons and integrations are currently active on their account.

Timeline and Deliverables

This section should be completed in collaboration with the Project Manager and development team.

• Timeline:

  • Discovery & User Flow Diagrams: [Date]

  • Wireframes: June 28, 2025

  • High-Fidelity Mockups & Prototype: [Date]

• Key Deliverables:

  • User flow diagrams for discovery, purchase, and upgrade paths.

  • Wireframes detailing the layout of the marketplace and individual product pages.

    • Marketplace

  • High-fidelity, interactive prototypes for key user flows.

  • UI assets and specifications ready for development handoff.