The premise
Most financial products have a very clear role at the moment of purchase. You choose what to buy, you pay, the transaction appears in your account. Then the bank goes quiet.
Everything interesting that happens next belongs to somebody else. Shipping, delivery, returns, price changes, gifts, reorders, offers, customer service — individually these look like small utility moments, too mundane for a financial institution to care about. Together they’re a far richer picture of a customer’s commercial life than a list of merchants and amounts will ever be.
So the question I chased was what a bank could become if it stayed useful after checkout.
What Shopify was actually building
I started somewhere adjacent, with Shopify’s drift from infrastructure company serving merchants into a company with a direct relationship with consumers. Laid out in order, the moves are more interesting than any of them is alone. In 2013, Shopify Payments pulled payment processing into its own ecosystem. In 2017, its experimental group shipped Arrive, a retailer-agnostic package tracking app — their first direct consumer touchpoint after checkout. In 2020, Shop folded Arrive’s post-purchase utility together with Shop Pay’s accelerated checkout into a broader consumer shopping product.
The features aren’t the story. The sequence is. Shopify found a high-frequency, high-intent moment in the shopping journey and used it to widen its relationship with customers. Tracking gave people a reason to come back; the visits created opportunities for discovery; discovery created opportunities for another purchase; and every interaction generated context that improved the next one.
Tracking wasn’t the product
Traditional commerce models treat the purchase as the destination. Customers don’t. They keep interacting with a purchase long after checkout, and they keep asking the same small questions: did it ship, where is it, when does it arrive, did the price drop, can I return it, should I reorder it, was this supposed to be a gift?
Shopify reported that Shop users checked an order an average of 8.02 times between checkout and delivery. That number reframed the whole thing for me. The gap between buying something and receiving it isn’t dead air — it’s eight voluntary visits, from someone who has just demonstrated intent, at a moment when they actively want to hear from you.
Tracking wasn’t the product. It was the wedge.
From spend data to shopping context
Financial institutions already know a great deal about where customers spend and how much. They know remarkably little about what happened around the purchase. A post-purchase layer could add the missing dimensions: the merchant, the actual product, the timing of arrival, the intent behind it — gift, replacement, recurring buy — and the lifecycle afterward, whether it shipped, returned, discounted, or got reordered.
That context makes products the institution already runs measurably more useful, which is where the real opportunity sits:
Use post-purchase utility to build a richer understanding of the customer’s commercial life — and use that understanding to make the rest of the ecosystem more relevant.
The organization already had most of the pieces: shopping capabilities, transaction intelligence, notifications, merchant partnerships, and technology that could already identify purchase-related information. So rather than inventing a business from scratch, I looked at how a post-purchase product could connect what existed. Read as a chain — purchase, tracking, delivery, savings, recommendations, reorder — each moment makes the next product more useful. A delivered item can trigger price protection or replenishment. Purchase and delivery context makes a digital assistant situationally aware instead of generically chatty. Notifications stop being transaction alerts and start being news about your things. Knowing an item is a gift opens up reminders and delivery coordination. Retail partnerships get something concrete to integrate with.
None of that value lives in package tracking. It lives in the connections.
Buying the wedge instead of building it
The entry question was how to get into the space fast enough to learn anything. Building a tracking platform from zero means carrier integrations, years of edge cases, and arriving late anyway — so I looked at acquisition instead: start with a proven utility that already has customers, carrier integrations, and mature tracking; rebrand and scale it behind the reach and trust of a large consumer financial brand; then connect it outward to shopping, payments, notifications, financial intelligence, and partnerships.
The hypothesis was that acquisition compresses years of infrastructure work into a position inside a customer behavior that is already growing. As with everything else here, buying wasn’t the strategy — it was a test of whether the strategy could arrive in time to matter.
Concepts as probes
Strategy goes abstract fast, so I used product concepts to find out what the ecosystem would actually feel like. They were never meant as finished UI. They were probes: all packages in one place regardless of merchant or carrier; a price drop on something recently bought surfacing the savings right next to the order; a purchase that looks like a gift offering contextual actions before it lands; an assistant that knows an order shipped, arrived, or needs attention rather than treating it as a static line item; deliveries and gift-giving moments appearing where someone already manages their time; a merchant partner extending the experience straight from checkout into support.
Each one exists to answer a question the strategy couldn’t answer on its own: if we had this layer of customer context, what could the rest of the ecosystem become?
Why it could work
Four advantages, and only one of them is about the app. Economies of scale: existing infrastructure plus acquired technology lowers the cost of operating another consumer product. Economies of scope: more touchpoints mean more chances to introduce a relevant product without paying again for the customer’s attention. Ecosystem synergies: post-purchase context improves products that already exist, instead of trapping the value inside a standalone app. Speed: acquisition delivers customers, infrastructure, domain expertise, and carrier support on day one.
The goal was never another app. It was a new source of leverage across a portfolio that already existed.
Why it might not
The weaknesses are structural, not fixable with better design. Vertically integrated competitors — Shopify, Amazon, Apple, Google — hold stronger positions in the commerce stack because they control merchants, marketplaces, operating systems, or checkout itself. Fragile integrations: email parsing and third-party account connections buy broad coverage at the cost of reliability, which is exactly the wrong trade for a product whose entire promise is “we’ll tell you where your thing is.” Strong incumbents already have the consumer adoption.
And then trust, which I’d argue outranks the rest. A richer understanding of what people buy only creates value if they understand what’s being used and why.
More customer context is only an advantage when the value exchange is obvious to the customer.
Any honest version of this strategy has to treat transparency, permission, and customer control as product requirements, not implementation details. A bank that knows what’s in your boxes has to be visibly better for you than one that doesn’t.
What stuck with me
I started with a small utility — package tracking — and ended with a post-purchase intelligence layer connecting commerce, financial services, customer context, and everyday usefulness. The reframing was the output.
It also left me with a sequence I keep reusing: study an adjacent business rather than an adjacent interface; find the mechanism actually producing its advantage; ask whether that mechanism transfers to your ecosystem; make the hypothesis tangible through concepts; then go looking for the structural reasons it fails. Worth remembering that the most interesting opportunities often start with something that looks too mundane to matter. This one started with a package notification.
The concept probes are more fun to walk through than to read about. Schedule a conversation.