PilotX for Shopify brands running Klaviyo

Claim the revenue between your store and your sends. PilotX is the layer between.

Your Shopify store records what every customer did. Your flows send on a fixed rule. Nothing in between works out the right move for one person, so the revenue in that gap goes unclaimed. PilotX connects natively to Shopify, decides per customer, and sends it.

See the revenue in the gap Audit your revenue leaks free

Live in about 30 minutes. Measured against a control group you set.

Store · decision · sendWorked exampleLive

Store knowsAva has bought the Amber twice, and keeps browsing.

PilotX decides the move

To Ava L.Two Amber candles in, browsing againEmail

LUMENSlow evenings, lit well

Cedar & Smoke

Your next evening, Ava.

You have burned through the Amber twice. Cedar & Smoke is its darker turn for the colder months, and it ships free with your next order.

Add Cedar & Smoke

Chosen from what she actually buys

Sent through your sender

Sends out7:40pm via your Klaviyo, deliverability kept.

Your store knows. Your sends reach. The call in between is the revenue that slips through, and the layer PilotX closes.

Measured against a control group you set42,318 customers, each one joined up

Illustrative worked example · fictional brand, not a measured PilotX result

The gap between them is where the money leaks.

Two halves that never meet per customer. PilotX is the decision that joins them, one move for each person.

Your store knows

What they bought, what they keep browsing, and how long since they last ordered.

The gap today

Nothing decides the right move for each person, so everyone gets the same campaign, or nothing at all.

Your sends go out

Email, SMS and push reach them, but only as good as the call behind them.

PilotX closes it: it reads Shopify natively, decides the move for each customer, then sends it itself or through the tools you already run.

Signals in, decisions out

Wired to everything on either side.

Every signal your store and stack record flows in, PilotX makes one call for each customer, and it goes out across email, SMS, push, WhatsApp, in-app, ads, Pulse and support.

Signals inWhat PilotX reads

Your best signal sourceOrders, catalogue, browsing and customers, read per shopper

and the rest of your stack

PilotX decidesOne call per customer

Channels outWhere PilotX acts

Your channel outWritten native to the channel, checked on brand, and it can send through the tools you already run

and the rest of your stack

And across your ops. PilotX coordinates and escalates through the rest

Connect it, way one

Drop in the SDK

Add PilotX to your website or app with one snippet. PilotX becomes the stack, and reaches anything else you run through MCP.

Anything else, through MCP

Connect it, way two

Plug into what you run

Already have your store, sender and warehouse wired up? Connect them in a click. Nothing to migrate, nothing rebuilt.

PilotX does both, whichever suits your team. Live in about 30 minutes.

The modelled return

Up to 50%more revenue, about 3x a broadcast

$10of extra sales for every $1 you pay

Joining the store to the sends, per customer, is modelled to add up to 50% more revenue, about three times the 15% either tool reaches alone. PilotX is paid 10% of the extra, capped at $2,500 a month. Every result is measured against a control group you set.

Model your returnModelled, and measured against a control group you set. Never a guarantee.

Free, on your exact stack

See the revenue sitting between your store and your sends.

Give us your Shopify store. We map the revenue slipping between what each customer did and what they get sent, and show how deciding the right move for every customer, one by one, closes it. Free, before we ever speak.