a Sagan program · currently in private beta

Fifty "where is my order?" tickets a day. Three percent silently late — you hear about it last.

A customer emails asking where their order is. Support opens Shopify. The order is split between two fulfillment partners. They log into one portal. Then the other. Pull the tracking number. Paste it back into the ticket. Eight to twelve minutes per lookup, fifty times a day, on your dime. An AI agent watches every order and emails the customer before they ask.
tickets / day
50
order-status tickets, steady state
hrs / day
8+
support time in portals
orders silently late
~3%/mo
no alert, no email, no flag
order placed · partner routed · tracking pulled · delay detected · customer emailed · shipping log updated · order placed · partner routed · tracking pulled · delay detected · customer emailed · shipping log updated ·  order placed · partner routed · tracking pulled · delay detected · customer emailed · shipping log updated · order placed · partner routed · tracking pulled · delay detected · customer emailed · shipping log updated · 
the problem

Your fulfillment
is split. Your
visibility isn't.

An order leaves Shopify and routes to one of three partners based on the SKU. Each partner has its own portal, its own tracking feed, its own cadence. There is no combined view. Support builds one by hand, ticket by ticket, on the clock you pay for.

The tickets that reach support are the loud ones. The silent ones — the 3% that stalled at a partner warehouse or sat at the carrier hub for 48 hours — never get flagged. Those are the customers you lose.

01
Eight minutes per ticket

"Where is my order?" hits the inbox. Shopify → partner A, B, or C → tracking URL → paste back. Fifty tickets a day is a full shift spent before real work starts.

02
Silent delays go unflagged

Your dashboard shows shipped. The carrier shows label created. Three days later the customer writes in angry. The delayed cohort only surfaces as complaints.

03
Delayed cohort churns at 2–3x

Customers who wait 48+ hours past their expected delivery churn two to three times faster than baseline. You see it in LTV months later — never in time to intervene.

the math, if you want to look

$65K a year in CX burn.
$144K more walking out
through churn.

TICKETS / DAY
50
HRS / DAY ON ORDER TICKETS
8+
$ / YR CX BURN
$65K
$ / YR CHURN LEAK
$144K

50 tickets/day × 10 min × $30/hr loaded support cost = roughly $65K/year burned on order-status lookups. On churn: assume $120 AOV and $400 LTV. At 40K orders/year, 3% silently late = 1,200 delayed customers; at 2.5x baseline churn on that cohort you lose an incremental ~360 customers × $400 LTV = $144K/year in LTV walking out the door. That is the price of reactive ops — paid twice, in support wages and in the repeat buyers you never get back.

how it works

Your stack, already in place —
one agent watching the gaps.

step 01
Order lands

A Shopify webhook fires. The agent reads the SKU, figures out which fulfillment partner the order was routed to, and opens a watch.

step 02
Tracking is pulled

The agent polls the partner portals and your carrier tracking API. The status ladder writes back to the order record.

step 03
Delay is detected

When an order stalls past its expected shipping window, the agent flags it against the SLA for that partner and that carrier lane.

step 04
Email fires first

Your email flow tool sends the real status, the revised ETA, and the tracking link — before the ticket opens. The customer hears it from you, not from a silent dashboard.

agent · shipment monitor
order #48211 · shopify webhook received · SKU routed to fulfillment partner B
·· polling partner portal · label created 04-15 · no scan since
·· cross-checking carrier tracking feed · carrier idle 51h at origin hub
·· SLA breach · expected pickup 04-16, now 04-18
·· drafting customer notice · revised ETA 04-22
email flow triggered · customer emailed before ticket opens
agent: order resolved silently · support inbox untouched_
honest qualification

Is this for you?

built for you if
  • You run a $5–20M DTC brand on Shopify
  • Fulfillment is split across two or more partners (3PLs, warehouses, or brand-run)
  • An email flow tool already handles your lifecycle sends
  • "Where is my order?" tickets dominate your CX queue
  • You want the email to fire before the ticket, not after
not for you if
  • You ship from a single 3PL with native tracking webhooks
  • Your partners already push delay notifications to your customers
  • You sell B2B and buyers don't care about delivery-day precision
  • Your order volume makes these tickets a rounding error
pricing

Straightforward.
No retainer.

to build
$500
One-time. Scoped, built, and deployed in about two weeks.
then
usage-based
You pay when the agent runs. No seats, no subscription floor.

Full rate card and terms live on the program site → shipyourweekendproject.com

waitlist · private beta

Stop finding out — first
from the customer.

$65K/year in ticket-handling burn and $144K/year in churn you can't see. Email fires before the ticket opens, not after. A small cohort of DTC brands is onboarding this quarter.

Get the build