Proposals
AuraScore 81/100

Distributed System Resiliency and Scalability Pitch Brief

Build an executive technical pitch brief for high-throughput distributed system redesign proposals.

Use this template to author pre-sales pitch briefs for high-concurrency cloud architecture deals. It empowers systems architects to articulate fault tolerance, concurrency gains, and infrastructure value.

Template

Role: Lead Distributed Systems Architect preparing commercial architecture redesign proposal briefs.

Context

  • Enterprise Client: {{customer_organization}}
  • Throughput and Concurrency Goals: {{throughput_target}}
  • Current Failure Modes and Bottlenecks: {{current_failure_modes}}
  • Cloud and Infrastructure Ecosystem: {{cloud_provider}}
  • Service Level Agreements: {{slas_required}}
  • Target Proposal Timeline: {{timeline_weeks}}

Task

Author a high-impact technical pitch brief detailing a distributed systems architecture overhaul for {{customer_organization}}, demonstrating how the proposed design resolves {{current_failure_modes}} while meeting {{throughput_target}}.

Method

  1. Analyze current systemic failure modes described in {{current_failure_modes}} across compute, storage, and networking layers.
  2. Define the target distributed architecture leveraging native capabilities of {{cloud_provider}}.
  3. Formulate high-concurrency design patterns (e.g., event sourcing, CQRS, backpressure handling) to achieve {{throughput_target}}.
  4. Map fault-isolation boundaries and automated failover mechanics to safeguard {{slas_required}}.
  5. Structure phased delivery milestones achievable within {{timeline_weeks}}.
  6. Detail risk mitigation strategies for live data migration without incurring downtime.
  7. Define key financial and compute efficiency optimizations inherent in the new design.

Constraints

  • MUST explicitly address every failure mode listed in {{current_failure_modes}}.
  • MUST utilize service nomenclature native to {{cloud_provider}}.
  • MUST NOT recommend single points of failure in any tier of the proposed topology.
  • Keep architecture specifications practical and scoped to {{timeline_weeks}}.

Output format

  • Executive Architecture Summary (under 120 words)
  • Target Topology & Component Specifications (4 structured bullet points)
  • Resiliency & High-Availability Model (numbered list of 3 mechanisms)
  • SLA & Performance Benchmarking Plan (table: Metric, Target, Validation Strategy)
  • Phased Implementation Roadmap (timeline mapping for {{timeline_weeks}})

Self-review

  • Does the proposed topology natively support {{throughput_target}}?
  • Are the infrastructure components strictly accurate for {{cloud_provider}}?
  • Is the SLA verification plan capable of validating {{slas_required}}?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-proposals
software-engineering-debugging
proposals
distributed-systems
system-architecture