Skip to content
Sale Day Readiness // Sale Simulation

Know your break point before your customers find it

We simulate your sale at full gas, so the real one stays sticky until sell-out.

A load test of the full purchase path, sized to your own sale. You are not paying for a load test. You are paying to not lose a sale day. Fixed fee, sized to your sale.

Sale Simulation · Telemetry
Sale Simulation · Telemetry Baseline 800, Target 2,500, Break point 3,400 concurrent shoppers. Sold out 3,000. SOLD OUT 3,000 BASELINE 800 TARGET 2,500 BREAK POINT 3,400 CONCURRENT SHOPPERS P95 MS
Example curve. Your report carries your own figures. Sold out is the finish line, not a crash.
Two tiers

Audit first, then simulate

Tier 01

Sale Readiness Audit

The first step
Length: One week

The low-cost first engagement. Built to tell you whether you need a full simulation and what to fix first either way.

  • Architecture review: what you own versus what lives inside a vendor platform
  • A light synthetic test of the purchase path
  • A prioritized risk list, in plain terms
Pricing: Fixed fee
Tier 02

Sale Simulation

The main product
Length: Sized to your sale

A load test of the full purchase path at three points: baseline, target, and break point. Then a readiness report, a fix list in three buckets, and one re-test after fixes.

  • Three-point curve across the full purchase path
  • Readiness report with the break point named
  • Fix list in three buckets: Fixed by us, For your dev team, Take to your vendor
  • One re-test after fixes
Pricing: Fixed fee by concurrency band
Concurrency bands

Priced against the sale, never the hours

  • Up to 500
  • Up to 2,500
  • Up to 10,000
  • Custom
The three-point curve

Baseline, target, break point, sold out

Baseline
What the last big sale peaked at

150 or 4,000, whatever it was. We start where you actually were, with your own traffic and order figures.

Target
What the next sale should hold

The number the next sale is planned around. We run the full purchase path there and report p95 latency and error rate at every step.

Break point
The first thing that fails

We ramp past target until something gives, and we name it: the step, the system, and the figure. That number goes in the report.

Sold out
The finish line

The report runs from first click to the sold-out mark. Sold out is the end state on every chart, not a crash, and it has to land before the break point.

What gets tested

The full purchase path

Third parties in scope, tested with notice
  1. [01] Browse

    Menu and product pages under the surge, including cached versus live inventory counts

  2. [02] Cart

    Add, update and remove at volume, with the inventory hold behind each line

  3. [03] Checkout

    The full checkout flow, age and ID gates, address and pickup selection

  4. [04] Inventory holds and reservations

    Reservation timing, release, and the race between two shoppers and the last unit

  5. [05] Oversell protection

    The count that stops the sale at zero, under load, with carts racing

  6. [06] Queue or waiting room

    How the queue admits shoppers, what it shows them, and what happens when it fails

  7. [07] POS sync

    Orders landing in Dutchie, Treez, Blaze or Flowhub while the floor sells the same stock

  8. [08] Payment

    Authorization and capture in test mode, timeouts, and the retry path

  9. [09] SMS and notification bursts

    The blast that starts the sale and the confirmations that follow it

  10. [010] Internal systems on 4/20 and holidays

    Online orders and in-store volume landing together, so the POS and the back office hold too

Tested with notice

Third-party providers (Dutchie, Weedmaps, payment, SMS) are in scope. You tell the vendor the window, with the notice template we supply, so nobody gets rate-limited mid-test and the vendor sees the same figures you do.

Scope of fixes

We test everything, we fix what you own

Every finding lands in one of three buckets
Fixed by us

What you own and we can change: storefront code, checkout and inventory-hold logic, POS sync, caching, test coverage.

For your dev team

What you own and your team should change, documented with the failing step, the figures, and the fix we would make.

Take to your vendor

What lives inside Dutchie, Weedmaps, your payment or SMS provider. Written so you can hand it over as a ticket.

What the brand provides

What we need from you

  • Staging, or an agreed production window
  • Hosting and deploy access
  • Payment in test mode
  • Inventory holds that will not poison real stock
  • Vendor notice (template supplied)
  • Last big sale’s traffic and order figures
Add-on and Sale Day Ops

Runbook, failover, and the room

Sale-day runbook and failover plan

Add-on
  • Manual mode
  • Backup data path
  • Waiting room
  • The vendor-down switch

Sale Day Ops

Per event

The studio in the room on sale day: pre-launch go/no-go checklist across storefront, POS, payments, inventory holds and notifications; live monitoring and a war-room channel for the sale window; runbook and failover ready; post-sale report with what held, what did not, figures, and the fix list.

The founder

Brendan’s experience

Brendan Connelly, founder of Sticky Peaks
Brendan Connelly // Founder

Sticky Peaks is run by Brendan Connelly. The figures below are his record, stated as experience.

Sample report

See what the readiness report looks like, with example figures.

See a sample report
The first step // Sale Readiness Audit

What happened on your last drop?

Everyone has an answer, and the answer is where we start. The Sale Readiness Audit takes one week: an architecture review, a light synthetic test, and a prioritized risk list. Fixed fee, sized to your sale.