Simple, single-location operations with basic needs:
- Cafes & Coffee shops - Simple menu, minimal inventory tracking
- Takeaway & Fast casual - Limited recipes, high-volume simple items
- Delis & Sandwich shops - Basic ingredient management
- Small restaurants (1-7 employees) - Owner-operated, simple workflows
- Beverage-focused businesses - Juice bars, smoothie shops, simple drink menus
- Manual operations - Limited need for integrations or advanced features
- Trial users - Testing the platform, not yet committed to complex workflows
Characteristics: Basic recipe management, manual invoice entry, single admin user, infrequent stocktakes, simple menu with few ingredients per item.
Complex, multi-faceted operations requiring advanced management:
- Multi-location chains (2+ venues) - Centralized management needs
- Full-service restaurants - Complex menus, extensive wine/cocktail programs
- Catering companies - Variable menu planning, event-based operations
- Food production facilities - Large-scale prep, complex supply chains
- Central kitchens - Multi-location supply and recipe standardization
- Large teams (8+ employees) - Multiple user roles, workflow coordination
- Restaurant groups - Shared operations across multiple brands
- Integration-heavy operations - POS systems, accounting software, automated workflows
Characteristics: Regular stocktakes (weekly+), complex recipes with many ingredients, multiple active users, automated integrations, sophisticated inventory management, dish-heavy menus requiring precise costing.
Key Differentiator
Pro tier restaurants have operational complexity that requires advanced features like multi-user collaboration, automated integrations, frequent inventory management, and sophisticated recipe costing - while Essentials tier restaurants need basic functionality for simpler, single-person operations.
📋 Filters & Analysis Tools
Adjust these thresholds to experiment with different tier classification criteria. Changes will re-classify all restaurants.
Pro Tier Indicators
High transaction volume indicates complex operations
Higher revenue suggests larger, more complex operations
More users indicates team collaboration and workflow complexity
Extensive recipe library suggests complex menu management needs
Complexity Scoring
Combined operational complexity score (recipes + suppliers + users)
Formula:
Complexity = Recipes + Suppliers + Active Users
Shows how many restaurants are classified as Essentials vs Pro based on operational complexity indicators.
- Single venue with 1-7 employees
- Venue types: Cafe (2), Takeaway (3), or Deli (6)
- Has
isLimitedTrial = true
- Multi-location (2+ venues)
- Single venue with 8+ employees
- Complex venue types (Restaurant, Chain, Food Production, Catering) with 4+ employees
- Central kitchen or HQ location
- Has POS or accounting integrations
main_restaurant table fields: numberOfVenues, numberOfEmployeesCategory, venueType, isLimitedTrial, isCentralKitchen, isHq, posIntegration, accountingSoftwareIntegration
Compares average feature usage between Essentials and Pro tiers - each feature shows side-by-side comparison of average counts.
For each tier, we calculate the average count of each feature across all restaurants in that tier.
Features Tracked:Recipes: Count of active recipes ( recipeCountfromanalytics_dimensionrecipe)Suppliers: Count of active suppliers ( supplierCountfromanalytics_dimensionsupplier)Procedures: Count of active procedures ( procedureCountfromanalytics_dimensionprocedure)Preps: Count of active prep items ( prepCountfromanalytics_dimensionprep)Menu Items: Count of POS items ( menuItemCountfromanalytics_dimensionpositem)
isDeleted = false filter
Compares average number of active users, monthly invoices, and sales transactions between tiers to validate if Pro restaurants are more active.
Average values for each activity metric across restaurants in each tier.
Metrics:Avg Active Users: Average number of unique users per restaurant ( activeUsers30dfromanalytics_dimensionrestaurantuser)Avg Monthly Invoices: Average invoice count in last 30 days ( invoiceCount30dfromanalytics_factinvoice)Avg Monthly Sales: Average sales transactions in last 30 days ( salesCount30dfromanalytics_factsales)
Data Source: Fact tables joined with dimension tables, filtered by date range and
isDeleted = false
Shows the percentage of restaurants in each tier that have paid subscriptions, helping validate if tier classification predicts willingness to pay.
(Paid Restaurants / Total Restaurants) × 100 for each tier
Paid Restaurants: Restaurants where hasPaidSubscription = trueTotal Restaurants: All restaurants in the tier (including trials, free, and paid)
Data Source:
main_restaurant.hasPaidSubscription field
Identifies potential misclassifications by highlighting restaurants with operational complexity that doesn't match their assigned tier.
Identifies potential misclassifications based on actual usage patterns.
- High recipe count (>50): Suggests complex menu management
- Many suppliers (>20): Indicates complex purchasing needs
- Large team (>10 users): Shows organizational complexity
- High invoice volume (>100/month): Indicates high transaction volume
- Low recipe count (<10): Limited menu complexity
- Few suppliers (<5): Simple purchasing
- Small team (≤1 user): Minimal collaboration needs
- Low invoice volume (<10/month): Light transaction activity
Specific restaurants that may be misclassified - either complex operations in Essentials tier or simple operations in Pro tier.
Lists specific restaurants that may be misclassified for manual review.
Selection Criteria:Complex Essentials Essentials-tier restaurants with complexity score >100 OR invoice count >100/monthSimple Pro Pro-tier restaurants with complexity score <10 AND invoice count <10/month
recipeCount + supplierCount + activeUsers30d
- "Consider Pro tier" for complex operations currently in Essentials
- "Consider Essentials tier" for simple operations currently in Pro