The cost-estimate badge · ZopDev University

Outcome

By the end of this lesson, you will be able to read the cost-estimate badge, interpret the single-figure estimate and its per-target breakdown, and justify event cost vs revenue impact.


Prerequisites	M2.9.L1 - L4
Time	9 minutes

1. Concept

Before you commit to an event, you are told what it will cost.

The number is a single figure, not a range: the hourly cost difference times the event duration. It comes with a flag when any rate is a fallback, and a breakdown showing which part of the scale-up accounts for what.

THE ESTIMATE TELLS YOU:
  Total additional cost for the event
  Per-target breakdown
  Whether any rate is a fallback (the Estimated badge)
  ROI framing vs business value

The estimate is the basis for the commit decision.

What the estimate covers

EVENT: Black Friday 2026 (24 hours)
SCOPE: 3 production ASGs

COST ESTIMATE:
  Event window cost (24h, event start to end): $4,800
  Total additional cost for event:        $4,800
  (Per-hour delta × event duration. The detail page total
   covers the event window only; the wizard's preview tiles
   also count the pre-scale and cooldown hours)

  Baseline cost continues normally:        $X,XXX (unchanged)

  Per-target breakdown:
    asg-checkout (10 → 40 instances, 24h): $2,880
    asg-api (20 → 60 instances, 24h):      $1,680
    asg-search (5 → 30 instances, 24h):    $240

Estimated badge: shown

The transparency lets the customer make informed decisions.

Why “estimated”

Three sources of estimation uncertainty:

1. ACTUAL PEAK DURATION UNKNOWN
   Event might be exactly 24h, or might extend by hours
   Marketing/business may make last-minute adjustments

2. CLOUD RATES CAN CHANGE
   Pricing API gives current rates
   Spot prices fluctuate
   On-demand can change rarely (but possible)

3. PER-INSTANCE COST VARIES
   RI coverage affects effective per-instance cost
   Savings plans cover variable share
   Sustained-use discounts kick in at certain durations

THE ESTIMATE USES current rates and defined duration
ACTUAL COST may vary

The uncertainty is reasonable; the estimate is best-effort given the inputs.

No range: plan your own margin

COST ESTIMATE: $4,800

WHAT IT IS:
  One figure: (event $/hr - current $/hr) × event hours
  No lower or upper bound
  No confidence percentage

WHAT IT IS NOT:
  A guarantee: the event can run long, rates can move,
  discounts can cover more or less than expected

YOUR MARGIN, ON TOP:
  Estimated badge shown (a fallback rate was used):
    plan a wider margin; provider averages can be far off
    for very small or very large instance types
  No badge (every rate from live pricing):
    a smaller margin for overrun and rate changes

The estimate gives you a figure. The margin is your call, and it belongs in the budget you present.

Reading the breakdown

PER-TARGET BREAKDOWN:
─────────────────────────────────────────────────────────────────
asg-checkout
  Current:  10 × $4/hr = $40/hr
  Event:    40 × $4/hr × 24h = $3,840
  Additional: $3,840 - ($40 × 24) = $2,880
  Note: assumes $4/hr rate per instance

asg-api
  Current:  20 × $1.75/hr = $35/hr
  Event:    60 × $1.75/hr × 24h = $2,520
  Additional: $2,520 - ($35 × 24) = $1,680

asg-search
  Current:  5 × $0.40/hr = $2/hr
  Event:    30 × $0.40/hr × 24h = $288
  Additional: $288 - ($2 × 24) = $240

TOTAL ADDITIONAL: $2,880 + $1,680 + $240 = $4,800

The breakdown shows where the estimated cost lands. Helps identify the biggest contributors.

What the badge means

NO BADGE:
  Every rate came from live pricing data
  Rows and totals agree

isEstimated = YES when any of these is true:
  A compute rate did not come from live pricing
  (the bundled rate table or a provider average was used,
   even when the table had a match)
  A database rate fell back to a default
  The breakdown rows and the totals drift apart

NOT A HISTORY FLAG:
  The badge has nothing to do with how many times
  the event has run; a repeat event shows it again
  if its rates still come from fallback pricing

The badge tells you where the rates came from. Treat a flagged figure as best-effort.

Updating the estimate

Estimates update if:

EVENT CONFIG CHANGES:
  Capacity multiplier adjusted
  Duration changes
  Scope added/removed

PRICING DATA UPDATES:
  Weekly sync of pricing_cache
  Spot rates change
  RI coverage adjustments

CUSTOMER triggers re-estimate:
  Manual refresh
  After config changes
  Before final commit

The customer can re-estimate at any time via the wizard.

Cost vs benefit framing

Event Readiness costs are typically much less than the customer experience benefit:

EVENT: Black Friday
ESTIMATED EVENT READINESS COST: $4,800
EXPECTED ADDITIONAL REVENUE: $250,000+
  (Based on smooth performance maintaining conversion)

ROI: 50x

THE ESTIMATE IS SMALL relative to the value of avoiding
lost sales from latency spikes

This framing helps justify the cost to Finance.

Avoiding under-justification

COMMON MISTAKE: present only the cost
  "Event Readiness will cost $4,800. Approve?"
  Finance: "$4,800 is a lot for a one-time scheduling thing."
  Decision delayed; may not approve

BETTER: present cost + value
  "$4,800 cost; projected $250K revenue impact from smooth event"
  "50x ROI"
  "Without this: estimated $25K loss from latency-driven bounces"
  Decision is clear

DOCUMENTATION:
  Save the ROI calculation
  Save the comparison post-event
  Build a track record for future events

The cost without context is hard to approve. With value framing, easy decision.

Post-event reconciliation

AFTER EVENT, reconcile estimate vs actual:

ESTIMATED COST: $4,800
YOUR PLANNED MARGIN: +15% ($5,520)
ACTUAL COST: $4,920 (from Cost Reports for the event window)
WITHIN YOUR MARGIN: yes

ACCURACY: estimate was within 3% of actual

OVER MULTIPLE EVENTS:
  Keep your own record of estimate vs actual
  Use it to set the margin for the next event
  ZopNight does not adjust the estimate from past events

Reconciliation is your learning loop, kept in your own records.

2. Demo

A team’s first event estimate review:

EVENT: Marketing campaign Nov 30 (24 hours)

ZopNight shows in wizard:

  EVENT WINDOW (24 hours; pre-scale and post-event
  windows are not costed):
    asg-marketing-api:    25 → 60 instances = $2,160
    asg-search:           10 → 25 instances = $360
    asg-notification:      5 → 15 instances = $180
    TOTAL EVENT WINDOW:   $2,700

  GRAND TOTAL:            ~$2,700

  Estimated badge: shown (one rate is a provider average)
  Team adds a 20% margin: plans for ~$3,240

CUSTOMER REASONING:
  Compare to estimated impact:

  ESTIMATED REVENUE IMPACT FROM AVOIDING LATENCY SPIKES:
  ~$45,000 (conservative: based on marketing's projected conversions
   without latency-related dropoff)

  ROI: $45K / $2.7K = ~17x

  Plus: brand experience preserved
  Plus: customer trust maintained

DECISION: approve Event Readiness for $2.7K to capture $45K opportunity

POST-EVENT (Dec 1):
  Actual cost: $2,780 (close to estimate)
  Actual revenue impact: $52K (above projection)
  ROI confirmed: ~19x

  Lessons:
    Estimate accurate within 5%
    Capacity adequate for actual peak
    No issues during event

  For next event: margin can come down, based on this record

The math makes the case clearly.

3. Hands-on (5 min)

Read a cost estimate:

□ STEP 1: Open Event Readiness; pick an event
  Event: __________
  Cost estimate: $_____
  Estimated badge shown? yes / no
  Margin you will add: ___%

□ STEP 2: Per-target breakdown
  Target 1: __________   Cost: $_____
  Target 2: __________   Cost: $_____
  Target 3: __________   Cost: $_____

□ STEP 3: Estimate vs revenue impact
  Expected revenue if successful: $_____
  Expected loss if latency spikes: $_____
  ROI: _____x

□ STEP 4: Decision
  □ Approve (ROI strong)
  □ Reject (ROI weak; investigate options)
  □ Adjust capacity (cost too high; reduce multiplier)

□ STEP 5: Post-event commit
  When to reconcile: __________
  Owner: __________

A 10-minute exercise builds the cost-justification muscle.

4. Knowledge check

Q1

The cost-estimate badge isEstimated = YES indicates:

A. Best-effort cost estimate
B. A guaranteed maximum cost for the event
C. Always wrong
D. That the event has already been billed

Show answer

Correct: A. At least one rate came from fallback pricing rather than live data (or rows and totals drifted), so the figure is best-effort, not a guarantee.

Q2

A 7-day event shows an estimate of $12,000 and no range. How should the team plan the budget?

A. Treat $12,000 as a guaranteed ceiling for the event
B. Add their own margin, since the figure is a point estimate
C. Wait for ZopNight to publish the upper and lower bounds
D. Divide by seven, since the estimate covers one day only

Show answer

Correct: B. The estimate is the hourly cost difference times the event duration: one figure with no confidence band. Plan your own margin on top, wider if the Estimated badge shows.

Q3

A team’s Event Readiness ROI calculation: $5K estimate vs $80K expected revenue impact. The ROI:

A. Approve
B. Reject
C. Marginal; the estimate is too uncertain
D. 16x ROI is strong

Show answer

Correct: D. $80K / $5K is 16x: worth approving. Document the math for future events.

5. Apply

Cost estimate appears in the Event Readiness wizard and on the event’s detail page. Breakdown by target. A single figure, with an Estimated badge when any rate fell back to an average.

For your team: always present cost + value to Finance, not just cost. ROI math is the easy approval path.

Module quiz

Complete M2.9 → 10-question module quiz.

Outcome

1. Concept

What the estimate covers

Why “estimated”

No range: plan your own margin

Reading the breakdown

What the badge means

Updating the estimate

Cost vs benefit framing

Avoiding under-justification

Post-event reconciliation

2. Demo

3. Hands-on (5 min)

4. Knowledge check

Q1

Q2

Q3

5. Apply

Module quiz

Related lessons

Start with the bill.