Where are we today?
SuppliFlex is pre-revenue. We are three founders, Sarah Wehkamp, Sandy Uzcátegui and me, working between New York and Casablanca. We are building a real-time supply chain operations platform for US product brands that sell direct to consumers and wholesale: one system of record for inventory, orders, purchasing, fulfillment and accounting sync.
In October 2026 we rebuilt the platform from scratch. On Friday 30 October, at 12:00 CT, we open a public sandbox. Production beta follows on Friday 13 November, and general availability on Monday 23 November.
The usual order for a company like ours is different. You find a few customers, run private pilots, collect logos and quotes, and only then let the public near the product. We are doing it the other way around, and I want to explain why.
Why let people in before we ask for anything?
The people we build for run operations at brands doing somewhere between $500K and $50M a year. They have heard a lot of promises about inventory that finally ties out and syncs that finally work. Most of those promises arrive in a slide deck, followed by a request for a call, a contract and a migration.
We think the order should be reversed. Before we ask an operator for their time, their data or their money, they should be able to open the product and decide for themselves whether it is worth any of those. If SuppliFlex does not hold up on a Tuesday afternoon when nobody from our team is watching, no sales process should be able to talk them past that.
So the sandbox asks for almost nothing. A workspace takes under a minute. There is no card and no setup. It lasts 30 days and can be extended, you can invite teammates, and you can reset it whenever you want to start over.
Why does a demo you run yourself beat one we narrate?
A narrated demo shows the path the presenter chose. It moves at the presenter's pace, skips the screens that are not ready, and ends before anything awkward happens. That is not dishonest, but it is not evidence either.
The sandbox is the real product on seeded data, not a recorded tour or a mock-up. You choose one of three seed packs, each with 18 months of history: apparel DTC and wholesale with two warehouses, a 3PL, B2B price lists and open POs; food and beverage with lots, expiry, FEFO picking and supplier lead-time drift; or consumer electronics with serials, returns and RMAs, marketplace spikes and carrier tracking.
The data does not sit still. A simulator we host emits Shopify, Amazon, QuickBooks and carrier events every few minutes, so orders arrive, stock moves and syncs happen while you work. A time machine jumps to the end of the day or the end of the month, so you can see what a close looks like without waiting four weeks.
You decide where to click. If you want to see what happens when demand spikes on one channel, or when a supplier starts missing delivery windows, you can go looking for it. That is a better test of whether the product fits your operation than anything I could narrate.
How do we stay honest about what is not finished?
A sandbox opened two weeks before production beta will have gaps, and pretending otherwise would undo the whole point. So anything that is not in production yet is flagged "coming to production" inside the product, on the screen where you would expect to find it.
The flags do two jobs. They tell you exactly where the line between today and the roadmap sits, so you are not left guessing which parts you could rely on. And they hold us to dates. Production beta on 13 November brings real connectors, the migration wizard, CSV import, billing, the public API v1 and the TypeScript SDK. General availability on 23 November completes order to cash and procure to pay, with GL sync, period close, sales tax, multi-currency, the custom report builder, scheduled exports, SSO and SCIM, and published prices. Every flag should disappear on one of those days or on a date we tell you.
What do we ask in return?
Two things.
First, feedback. Tell us what you expected to find and could not, what took too long, and what would stop you from running your business on it. A pre-revenue team can still change direction quickly, and the sandbox is where we want to learn what to change.
Second, for a small number of brands, a deeper commitment. Our pilot program has room for ten US design partners doing $2M to $15M a year, with 50 to 5,000 SKUs, selling on Shopify or Amazon, keeping their books in QuickBooks or Xero, and running one to twenty stock locations. Design partners go live from 13 November, with migration done alongside a founder, a call every two weeks through January, a parallel run on real orders, and a case study at the end. That is a real ask of an operations team's time, which is why we want people to see the product before they agree to it.
And nothing done in the sandbox is thrown away. Sandboxes convert in place to paid workspaces, with the data kept.
What can you do next?
From Friday 30 October at 12:00 CT, you can open a sandbox and pick the seed pack closest to your business. From 13 November, a guided trial lets you connect Shopify, Amazon or QuickBooks read-only and see your own catalog and orders.
If you would rather go through it with one of us, book a demo, and bring the questions the sandbox raised. If your brand fits the profile above and you want to shape what we build next, join the pilot program.
We would rather earn your attention with the product than ask for it with a pitch. The sandbox is how we try to do that.