SolutionsCase studiesInsightsCompanyClient login

Case studies

Evidence, filterable.

6 completed engagements, reported the way we report to clients — stat first, method shown, constraints included. No logos; the category runs on NDAs, and the numbers don't need them.

System
Marketplace
Revenue band

Showing 6 of 6 cases · constraints included in all 6

The system — installed over 90 days

2 systems, 1 drawn interlock.

01Profit & Pricing — weeks 1–4Fee audit + unit economics current. The margin floor first, so every later decision had a true denominator.
02Demand & Inventory — weeks 3–10Daily forecast per SKU, reorder points with supplier variance, human approval gate, automated POs.
03Ad re-weighting — weeks 8–12Bids re-anchored to margin per SKU, stock-gated by the demand system. No new ad platform — new arithmetic.
SALES VELOCITY+ LEAD-TIME VARIANCEMARGIN PER SKUPROFIT ENGINE · WK 1–4FORECASTDAILY · PER SKUREORDER ≤21DRULE-TRIGGEREDHUMAN APPROVALOWNER: FORECASTING LEADPO ISSUEDAUTOMATEDBID CEILINGADS ANSWER TO MARGINSTOCK GATESCORECARDFORECAST VS ACTUAL · MONTHLY

The result — 2 quarters, reported monthly

Reported with the misses on the chart.

Contribution margin+0%Q1 → Q3 · settlement data
Stockout days/quarter31 → 0Q3 vs onboarding
Air freight share of COGS11% → 0%Q3 vs onboarding
Forecast accuracy0%Q2 · published · launches excluded
Forecast vs actual — contribution margin by month
ActualForecast — dashed, always

The misses are on the chart. Months 2 and 4 came in under forecast — they're why the Q2 accuracy number means something.

Source: client scorecard · SP-API settlement data · Jan–Jun 2026

Forecast versus actual contribution margin over six months. Actual tracked forecast closely, with months two and four coming in under forecast — marked as misses.

Constraints — what didn't work
  1. The hero SKU stayed capacity-limited through Q3 — supplier MOQ, not forecast. Margin gains came from the other 41 SKUs.
  2. 1 price step was reversed after 11 days — elasticity said no. The reversal is in the log, and in this report.
  3. New launches ran manual all 6 months. No history, no autopilot — the 2 launched SKUs are excluded from the accuracy number.
"First partner that told us what wouldn't work — then proved what would."

COO — the operator in this case

Method — numbers from client scorecards and SP-API settlement data · periods as labeled · exclusions stated above

The next case study could be your account.

The audit is where every one of these started — 14 days, read-only, and the report is yours to keep.