Pricing

Enterprise planning suites are six figures and take a year.

RetailPulse is a fraction of that, live within 48 hours of the box being plugged in, and implementation is quoted as a fixed number, because we know what it takes. The price does not go up because you grew.

The anchor

Live in 48 hours, not next winter.

Enterprise planning suites: $60,000–$180,000 a year, six to twelve months to go live, and a services line quoted on time and materials.

RetailPulse: a fraction of that, on an appliance in your building, rented, so there is nothing to spec and no capex paper. We quote implementation as a fixed number.

There is no rate card here, on purpose. The number depends on your estate, and we would rather show you the product on your own data first and talk about price at the end, as a relief rather than a pitch.

Enterprise suiteRetailPulse
Time to live6–12 months48 hours from plug-in
Annual cost$60k–$180kA fraction of that
ImplementationTime and materialsA fixed number
Runs onTheir cloudAn appliance in your building
HardwareNot their problemRented, sized for the job, ours to fix
When you growThe bill growsThe price is the price
Including next year

Add SKUs, add stores, add users. The price is the price.

Everyone else charges you more for succeeding, because their costs scale with your growth: per SKU, per warehouse, per user, per rand of inventory. Ours don't. It runs in your building.

That removes the most common source of mid-market renewal friction: the bill that crept up 40% because you opened four stores.

Founding customers

Three places. They fill. That is it.

"I'm taking three founding customers this year. They get the rate that reflects being first, direct access to me rather than a support queue, and real influence over what gets built next. I'm still choosing which module comes after ordering. In return I need to be able to say your name and show the numbers. That's the whole deal, and it's in writing."

Founding terms exist because I don't have a reference site yet. They end when I do.

A founding customer is in the conversation about what comes after ordering. The fourth customer inherits what the first three decided.

Rob · Founder, RetailPulse

The way in

You don't have to change anything to find out.

RetailPulse runs alongside what you already have, in your building, and tells you what it would have ordered. It doesn't touch your system. It doesn't place an order. For the first few weeks it just keeps a scorecard against your own decisions.

If it's wrong, the box goes back and you've lost a month. If it's right, you'll know in eight weeks, from your own data, not from my case study.

See it on your own data.

Twelve weeks, one category, anonymised by you. A ten-minute job, not a project. Send it Thursday and you'll have the findings the following Wednesday.

  1. 1 · The extract"Twelve weeks, one category, anonymised by you." A ten-minute job, not a project. No NDA drama, no IT ticket, nothing to approve.
  2. 2 · The findings"Here is what it found in your data." The engine has never met a real dataset it did not find something embarrassing in. Evidence about you, not persuasion.
  3. 3 · Run-alongside"Eight weeks. It doesn't touch anything." Zero operational risk; your own scorecard.
  4. 4 · Founding agreement"One of three places." By then you have your own proof, and the scarcity is real.
Send the extract

A personal reply within 24 hours, from Rob, not a sequence.