Team Project · Team Lead

Rufus-Amelia 2.0

A two-part design audit of Amazon, ending in a proposal that turns consumer intent into verified demand before anything is manufactured.

My role
Team Lead, Data Analysis, Service Framework
Team
Five, Industrial & Graphic Design
Year
2026 / Mar, 2 weeks
Type
Design Management, Strategic Audit
Overview
Two audits, one argument

Audit I maps what Amazon actually is, a commerce layer, a cloud layer, and a content layer that reinforce each other. Audit II takes the failure that survey exposed and proposes a fix: connect the buyer-side AI to the seller-side AI so demand is verified before production starts.

I led the team and took the data analysis and the service framework myself. The reason the two audits belong on one page is that the second only makes sense if you accept the first: Amazon's problem is not that it moves too slowly, it is that its speed is built on manufacturing things nobody has committed to buying.

Snapshot

Rufus reads intent, Amelia runs the seller side, and today neither one tells the other anything. The proposal closes that loop.

Problem Definition

Convenience is the product, and the cost of it is paid upstream. Goods are made speculatively, shipped fast, and returned at scale, with no demand validation anywhere before the purchase.

What Audit I found
The intelligence gap

Rufus and Amelia both sit inside a system where Amazon is the platform, the competitor, and the beneficiary at once. Their data circulates independently rather than in a shared loop.

This is the finding the whole proposal turns on. Amazon is using AI to capture value that third parties once created on its platform, and in doing so it undermines the network effects and participant incentives that made the platform valuable to begin with.

Discovery

Amazon is not simply an online retailer. Its architecture spans commerce, cloud, and content, and each layer shapes behaviour at a systemic level rather than a product level.

Three layers, one ecosystem
What each layer is actually optimising for

I read each service against the UN Sustainable Development Goals, because that is what forces the trade-off into view instead of letting the growth story stand alone.

Rufus, the buyer-side AI

In beta since February 2024, Rufus converts vague shopping intent into a ranked list, a confident decision, and a resolved post-purchase experience.

Amelia, the seller-side AI

A persistent intelligence layer across every page of Seller Central, built on Amazon Bedrock with retrieval so it pulls seller-specific data in real time.

Amelia already connects to FBA, Seller Central, Rufus, and Q, and the stated direction is autonomous action on inventory, pricing, and account operations by 2030. The connection it does not have is the one that matters.

Strategy
Synchronising consumer intent with operational intelligence

How can we convert strong demand signals into commercial opportunities before the product even exists? That is the question the proposal answers, with a real-time feedback loop between the buyer-side and seller-side AI.

Three mechanisms
Future Fulfillment

Rufus generates virtual product thumbnails from intent signals, users reserve future concepts, and Amelia converts those reservations into verified demand for suppliers, all before production begins.

This breaks the founding assumption of e-commerce, which is that the product already exists. Here the demand is generated and validated first, and production follows it.

How it gets measured

Three tiers, ordered so that an upstream failure invalidates everything below it rather than hiding inside an aggregate.

Who benefits

The model redistributes value across three groups. Customers move from choosing among what exists to co-creating what gets made, sellers stop gambling on forecasts and produce against confirmed orders, and logistics partners plan against real volume rather than projected volume. The benefit shifts away from reactive retail intermediaries, which is also the reason it would be politically hard inside the company.

Conclusion
Beyond prediction, toward prospective commerce

Prediction guesses what people will buy from a catalogue that already exists. Prospective commerce asks them to commit first, and treats that commitment as the trigger for making anything at all.

What I take from leading this is that an audit is only useful if it names the mechanism, not the symptom. Waste, returns, and emissions all read as separate problems until you notice they share one cause, which is that nothing in the system verifies demand before production. Once the team saw that, the proposal wrote itself.

What the model does not yet answer