Enterprise Developer Platform Deployment Topology Surcharge Matrix
Design a commercial surcharge matrix for private cloud, air-gapped, and custom-governed engineering deployment environments.
Use this template when establishing commercial add-on pricing for enterprise software engineering platforms requiring non-standard deployment models, rigorous compliance controls, or dedicated infrastructure.
Role: Senior Commercial Deal Desk Manager specializing in enterprise infrastructure and developer platform agreements.
Context
- Supported deployment topologies: {{deployment_model_options}}
- Regulatory and compliance standards: {{compliance_framework_scope}}
- Support and maintenance SLA tier: {{support_response_tier}}
- Dedicated tenant infrastructure cost: {{tenant_isolation_overhead}}
- Baseline annual contract value: {{customer_contract_volume}}
- Custom CI/CD and pipeline integration scope: {{custom_integration_requirements}}
Task
Produce a comprehensive topology and support surcharge matrix to standardise enterprise contract add-ons for self-hosted, private cloud, and air-gapped developer infrastructure deployments.
Method
- Review {{deployment_model_options}} to categorize baseline shared SaaS, dedicated VPC, on-prem, and air-gapped environments.
- Quantify ongoing maintenance and release engineering overhead associated with each deployment model.
- Calculate compliance uplift fees necessary to support audit and certification requirements in {{compliance_framework_scope}}.
- Incorporate {{tenant_isolation_overhead}} into the baseline infrastructure cost model for isolated environments.
- Factor in {{support_response_tier}} commitments including 24/7 runbook support and dedicated escalation engineers.
- Structure fixed vs percentage-based pricing uplifts relative to {{customer_contract_volume}}.
- Build the final surcharge matrix detailing deployment tier, uplift formula, included features, and mandatory add-ons.
Constraints
- MUST define commercial uplifts as either a fixed dollar amount or an annual percentage uplift on {{customer_contract_volume}}.
- MUST specify minimum contract terms for isolated or on-prem topologies.
- MUST NOT provide air-gapped support options without pricing dedicated support engineering personnel.
- Limit matrix entries to standard commercial options without custom one-off legal terms.
Output format
- Section 1: Deployment Topology Architecture Summary
- Section 2: Enterprise Topology Surcharge Matrix (Markdown table with columns: Deployment Option, Base Uplift %, Minimum Floor ($), Compliance Features Included, Maintenance SLA, Setup Fee)
- Section 3: Margin Safeguards and Sales Governance Rules
Self-review
- Verify that every option in {{deployment_model_options}} has an explicit row in the matrix.
- Confirm that compliance overhead for {{compliance_framework_scope}} is covered by the baseline uplift.
- Ensure clear distinction between recurring annual uplifts and one-time setup fees.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.