What’s a Product?
A product groups everything related to a single service:- The metrics you track
- The pricing plans available
- Customer subscriptions
- Usage data and analytics
Creating Products
Products require minimal configuration:- Name - Customer-facing display name (e.g., “Neural Network Training”, “Cloud Analytics”)
- Description - Brief explanation shown during checkout
- Metadata - Optional key-value pairs for internal tracking
When to Create Products
Create separate products when you have:- Distinct services with different metrics
- Independent pricing strategies
- Separate customer bases
- Different billing cycles or payment terms
Examples
Single Product Strategy A machine learning platform might have one product:- Product: “ML Training Platform”
- Metrics: GPU hours, model storage, inference requests
- Plans: Researcher, Startup, Enterprise
-
Product 1: “Data Warehouse”
- Metrics: Storage TB, compute hours, queries
- Plans: Developer, Business, Enterprise
-
Product 2: “Stream Processing”
- Metrics: Events processed, throughput GB
- Plans: Basic, Professional, Scale
-
Product 3: “ML Pipeline”
- Metrics: Training jobs, model deployments, predictions
- Plans: Starter, Growth, Custom
Best Practices
Keep it simple. Don’t over-segment. One product can support multiple plans and customer types. Think customer-first. Products should align with how customers think about your services. Plan for growth. Structure products to accommodate future features without major refactoring.Analytics
Paygentic provides product-level analytics:- Revenue breakdown
- Usage patterns
- Customer distribution
- Growth metrics
Next Steps
With products defined, you’ll need to:- Add billable metrics to track usage
- Create plans for different customer segments
- Set prices for each metric