# Kevin Rao, Head of Product at Stackfield Commerce — read of demand-forecasting-api, 2026-05-30

> 9 years bouncing between product and ops at e-commerce enablement companies. Currently running forecasting and replenishment tooling for a 40-person Series A that serves Shopify Plus brands. Coach my daughter's U10 soccer team Saturday mornings, which means I have exactly zero patience for anything that wastes my Friday prep time.

## How I got here

Searched "demand forecasting API shopify webhook" because we're evaluating whether to build our own signal-aggregation layer or buy something off the shelf. Third result was this page. We have a standing meeting Tuesday to decide. I had 8 minutes on my lunch break.

## What I clicked first

The spec table. I skipped the hero entirely and went straight to "Signal aggregation" because that's the actual problem I'm trying to solve. "Collect demand signals from web traffic, sales pipeline, customer support, social mentions, and supply-side constraints. Synthesize into unified forecast." That line is doing real work. It named the exact constellation of data sources I've been manually stitching together in a Looker dashboard that nobody trusts.

Then I read the hero: "Predict what customers want before they know." I wrote that off. Sounds like a slogan from someone who's read too many Shopify partner newsletters.

## Where I paused

The adoptability block. Specifically: "Honest disclosure: we don't have live customers on this idea yet." I stopped and reread the whole page from the top because I had fundamentally misunderstood what this was. I came here looking for an API to call. This is not that. This is someone selling me the idea of building this API. The "$5 to unlock the dossier" pricing and "Adopt the build" framing only clicked after I'd read the page twice. That's a significant orientation failure. I spent two of my eight minutes confused about what product I was even looking at.

## What I distrusted

The Fermi math is published with real specificity ("$-30,886 Year-1 take-home") and yet there's zero methodology visible. I get that the number is meant to be honest and sobering, but without knowing what assumptions went into it I can't tell if it's rigorous pessimism or just vibes dressed up in a formula. "1 in 8 meaningful-success odds" is the same problem. Where does that ratio come from? How is "meaningful success" defined? It reads like a confidence signal that's actually a confidence trick.

Also: "buyer clarity: 10/10" as a self-scored axis, on a page that took me two full reads to understand what was being sold. That score is either wrong or measuring something very different from what I'd call buyer clarity.

## What would convince me

I'd want to see one builder who went through this process and shipped something real. Not a revenue number, not a testimonial blurb. A URL. A working product I can inspect. Specifically: someone who bought the $99 build pack, actually launched a demand forecasting API, and has even a handful of paying customers. That would reframe the whole page from "startup content studio" to "accelerator with a track record."

## What I'd ask in an email reply

1. The spec table says "REST + webhook API" and lists Shopify, Stripe, PagerDuty as integrations. Is there an actual API in the $99 build pack, or is it scaffolding and a schema that I still have to build?
2. Has anyone actually purchased the adopt tier and launched? Can you point me to a live product built from this dossier?
3. The signal aggregation spec is interesting to me specifically. What's the assumed architecture for pulling in customer support data? Ticketing system webhooks, or something else?

## Verdict: on-the-fence

The transparency is genuinely unusual and I respect it, but I arrived here looking for a product to use and found a product to build. Those are different shopping trips. If I were in "should I start a forecasting API company" mode instead of "what can I plug into our stack" mode, I'd probably have replied already.

---
*Memo by skeptic persona, generated 2026-05-30. Studio breaks own self-grading loop.*