back-of-envelope

Estimate system capacity and latency for design problems.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill back-of-envelope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: back-of-envelope
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/performance/back-of-envelope
Command: npx skills add https://github.com/hung-phan/system-skills --skill back-of-envelope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill empowers you to make informed design decisions by providing rough but accurate estimations of system capacity and latency. It helps you avoid costly mistakes and over-engineering.

Core Features & Use Cases

  • Capacity Estimation: Quickly size new services by predicting their resource requirements (CPU, memory, bandwidth).
  • Latency Analysis: Estimate the time taken for operations at different layers of the system.
  • Use Case: When considering a new database design, use this Skill to estimate whether a single or multiple database instances will be needed based on expected load and data volume.

Quick Start

Use the /system-review review command to estimate the capacity for a new payment processing service with expected high traffic.

Frequently Asked Questions about back-of-envelope

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate system capacity for a new service without precise measurements?

Back-of-Envelope (BOTE) capacity estimation provides order-of-magnitude predictions for CPU, memory, and bandwidth requirements. It sizes new services by assessing resource needs against expected load and data volume without requiring precise measurements, preventing costly over-engineering.

How do I analyze latency across different layers of a system design?

Back-of-Envelope latency analysis estimates operation times across different system layers to identify potential bottlenecks. It provides rough but accurate latency projections for initial sizing and feasibility studies, helping you assess design limitations before committing to an architecture.

When do I need back-of-envelope calculations for resource planning?

You need back-of-envelope calculations for resource planning during initial sizing, feasibility studies, and design reviews. This technique helps determine if a high-traffic service requires single or multiple database instances by predicting resource needs and avoiding over-engineering.

How do I size database instances for expected traffic and data volume?

To size database instances for expected traffic, use BOTE techniques to calculate order-of-magnitude resource requirements. This assesses expected load and data volume to determine if a single or multiple database instances are needed, guiding your database design decisions.

What are the limitations of using rough estimates for system design reviews?

The limitation of using rough estimates is that they provide order-of-magnitude approximations rather than precise measurements. While suitable for initial feasibility studies and sizing, they should not replace detailed benchmarks when assessing exact resource limits or complex system bottlenecks.