diff --git a/documentation/docs/install-pmm/plan-pmm-installation/hardware_and_system.md b/documentation/docs/install-pmm/plan-pmm-installation/hardware_and_system.md
index 33d50356682..a0ac76ce8e9 100644
--- a/documentation/docs/install-pmm/plan-pmm-installation/hardware_and_system.md
+++ b/documentation/docs/install-pmm/plan-pmm-installation/hardware_and_system.md
@@ -6,7 +6,7 @@ For guidance on selecting the best deployment method based on these requirements
 ## PMM Server resource requirements
 Resource requirements scale with the number of nodes and services monitored. Here are our recommendations for different deployment scales:
 
-=== "Typical deployment (1-30 nodes)"
+=== "Typical (1-30 nodes)"
 
     This is the most common deployment scenario, suitable for small to medium-sized environments:
 
@@ -37,6 +37,11 @@ Resource requirements scale with the number of nodes and services monitored. Her
     - **Storage**: 500+ GB
     - **Example workloads**: Large enterprises, mission-critical database fleets
 
+=== "Extra Large (500+ nodes)"
+
+    Get free database assistance or contact our experts for personalized support.   
+    [Get help from Percona](../../get-help.md)
+
 ### Optimize ClickHouse for limited memory
 
 If you experience ClickHouse memory issues (such as "memory limit exceeded" errors), you can switch to a low-memory configuration optimized for constrained environments. See [ClickHouse memory issues](../../troubleshoot/qan_issues.md#clickhouse-memory-issues-in-low-memory-environments) for details.