What GameStop Taught Me About Building a Revenue System Before the Tools Existed

Before customer data platforms had a name — before every SaaS vendor promised a "unified customer view" out of the box — a version of that system was running at GameStop.

I know because I helped build it by hand.

The tools we have today did not exist. What we had was a massive loyalty program, a content engine, and a team that understood one thing clearly: if you can tie every customer interaction to a persistent profile, you can build something powerful on top of it. We did not call it a revenue system. But that is exactly what it was.

The assets we started with

GameStop had three things most companies would envy:

1. PowerUp Rewards — a loyalty program with over 65 million members generating transaction-level data across every store and online purchase
2. Game Informer — the largest gaming publication in the world, with millions of subscribers consuming content every month
3. Owned channels — email, in-store, web, and direct mail reaching the most engaged gaming audience on the planet

The raw material was there. The challenge was connecting it.

Building the unified customer table

There was no CDP to install. No pre-built data model to configure. We built the unified customer table ourselves — stitching together loyalty transactions, content engagement, channel interactions, and purchase history into a single view of each member.

This was painstaking work. Manual data integration, custom ETL processes, and constant reconciliation across systems that were never designed to talk to each other. But when it worked, we had something rare: a persistent customer profile enriched with event-level data across every touchpoint.

That foundation made everything else possible.

What we got right

The audience was the product. We did not sell impressions in the abstract. We sold access to specific segments of the loyalty database — new console owners, lapsed members, high-frequency buyers, genre enthusiasts. The targeting was built on actual purchase behavior, not surveys or modeled data.

Content drove engagement between purchases. Game Informer was not just a magazine. It was an engagement platform that kept the audience connected in the months between buying a console or a new title. That ongoing relationship created value that went far beyond individual transactions.

Measurement was closed-loop. Because we owned the loyalty data and the point of sale, we could answer the question that matters: did the customer who saw a campaign actually buy? We could answer with transactional data, not click proxies. That closed-loop measurement — connecting spend to outcomes — is still the foundation of any real revenue system.

What we got wrong

Every campaign started from scratch. We had the data, but not the feedback loops. The insights from one activation did not automatically inform the next. There was no system learning from every interaction and improving over time. Each campaign was a standalone project that required rebuilding audience segments, coordinating across teams, and manually pulling performance data after the fact.

No AI layer. The patterns were in the data. We could see them in retrospect. But we had no way to surface them in real time or use them to predict what a customer would do next. Every decision was backward-looking.

The system depended on heroes, not process. The people who understood the data and the business were the system. When they moved on, institutional knowledge walked out the door. There was no operating framework that kept the machine running independent of any individual.

This is the gap between having data and having a revenue system. Data is an asset. A revenue system is data plus process plus feedback loops plus a way to turn insights into action without starting over every week.

Intuition vs. evidence

At the time, our intuition told us we were ahead of the curve. And in some ways we were — most retailers had not even started thinking about their loyalty data as a strategic asset.

But the evidence, looking back, is clear: we were doing revenue operations without a revenue system. We had the inputs but not the architecture. We had the signals but not the playbook to act on them consistently.

The difference between what we built at GameStop and what teams can build today is not the data. Most mid-market companies already have more customer data than they can use. The difference is the connective tissue: the operating cadence, the feedback loops, and the AI layer that turns a pile of customer events into a system that gets smarter every week.

Bridge to today

Everything I learned building that unified customer table by hand shaped the Gain Method. The four stages — Connect, Discover, Design, Operationalize — exist because I watched what happens when you skip any one of them.

• Connect without Discover gives you a data warehouse nobody queries
• Discover without Design gives you insights nobody acts on
• Design without Operationalize gives you a brilliant pilot that dies after the first quarter

At GameStop, we nailed Connect and parts of Discover. We stumbled on Design (no repeatable playbook) and never reached Operationalize (no feedback loops, no AI layer, no weekly operating rhythm).

Next 30 days

If you are sitting on customer data and wondering whether you are closer to a revenue system or a data warehouse, here is how to find out:

1. Audit your customer table. Can you tie a single customer's interactions across marketing, sales, and service into one profile? If not, start there. You do not need a CDP. You need a plan.
2. Map your feedback loops. Pick your last three campaigns or outbound motions. Did the results from campaign one change how you ran campaign two? If the answer is no, you have a data asset but not a system.
3. Identify your "hero dependencies." Who on your team is the system? What happens to your revenue operations if they leave? Write down the three decisions that only that person can make, and start documenting the logic behind them.
4. Run one closed-loop test. Pick a single segment, run a targeted action, measure the outcome against a holdout, and document what you learned. Do this in one week, not one quarter.
5. Establish a weekly signal review. Block 30 minutes every Monday to review what the data told you last week and what you will do differently this week. This is the seed of an operating cadence.

The tools are better now than anything we had at GameStop. The gap for most teams is not technology — it is the system that tells you what to do with the technology every week. That is what Journey Gain helps teams build.