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.
19.5%Verified fulfillment rate, converting speculative production into pre-sold assets by removing the stakeholder gamble.
85.4%Intelligence yield, with Amazon acting as the intelligence hub that turns behavioural signals into a B2B product.
ZeroWaste supply-chain target, synchronising the manufacturing start point with confirmed demand rather than forecast probability.
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
One-click overconsumptionThe frictionless purchase loop is also an unverified demand loop. Products are manufactured on a forecast, shipped, and returned, and nothing in the flow checks whether the demand was real.
Packaging waste and carbonHyper-fast delivery means excess packaging and freight emissions. The model has no way to manage the risk of physical production without verified demand, so waste is created before anyone buys anything.
Always-on engagementContent and commerce are tuned for watch time and purchase frequency. The same machine that drives engagement drives the carbon output per customer per year.
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.
Rufus riskOptimising for purchase intent erodes the browse-and-discover behaviour responsible for roughly 20 percent of e-commerce sales. Optimising for conversion can cannibalise discovery.
Amelia riskAmelia risks becoming a tool that lets Amazon replace sellers rather than one that empowers them. Once sellers read it that way, migration off the platform accelerates.
No confirmed integrationThe two launched as separate tools with no confirmed data path between them, which means buyer demand signals are not circulated back to the sellers who would act on them.
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
E-CommerceB2C marketplace, third-party seller services, fulfillment logistics, and advertising, with 62 percent of unit sales coming from third-party sellers. 37.6 percent of the US e-commerce market.
AWSMore than 200 fully managed services and a four to five year head start on Azure and Google, holding 30 percent of global cloud infrastructure. Over 90 percent of the Fortune 100 use AWS partner solutions.
Prime Video315 million global users in 2025, differentiated by the Prime bundle, Amazon devices, and e-commerce data integration rather than by catalogue alone.
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.
E-CommerceThe core value is not speed, it is the elimination of friction, from one-click checkout to predictive restocking. That creates income across a wide seller and delivery ecosystem, and it structurally incentivises overconsumption and non-circular returns at the same time.
AWSThe core value is stability rather than storage or compute. It expands scalable infrastructure to governments, enterprises, and startups, while near-monopoly dynamics and complex pricing reinforce digital inequality, and the data centres carry a heavy energy and water load.
Prime VideoIt is not competing for attention, it is capturing loyalty. Bundled with membership, anchored by live sports, and monetised through shoppable advertising, which is genuine innovation in content and commerce convergence and an engagement design that optimises for watch time rather than well-being.
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.
DiscoveryParses intent, classifies categories, generates clarifying questions, and renders a ranked product list. Reduces browse-stage drop-off and improves category entry conversion.
DecisionExtracts specs, aligns features, and synthesises reviews into a comparison. Shortens comparison time and lifts detail-page dwell and conversion.
Post-purchaseResolves delivery status, returns and exchanges, and product usage without menu navigation. Reduces support ticket volume and return rate.
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.
AnalyticsAccelerates data-driven decisions and catches anomalies early, with demand forecasting across all seller tiers.
OptimizationLifts listing search rank, strengthens price competitiveness, and improves advertising return on ad spend.
OperationsPrevents stock-outs and overstock, shortens support response, and removes account suspension risk through proactive compliance monitoring.
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
Intent aggregationFragmented future concepts from Rufus interactions are synthesised into unified demand nodes for manufacturers, turning unstructured behavioural signals into structured commercial intelligence.
Privacy-first data siloUsers consent to demand aggregation without exposing individual identity to external manufacturers, so suppliers receive high-fidelity intent without receiving people.
Real-time predictive loopA reservation immediately updates a production dashboard. Amelia converts Rufus intent signals into inventory and pricing decisions as they happen.
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.
1,250KRaw intent signals at the discovery stage, captured across the ecosystem as unstructured behaviour.
74.2%Engagement velocity at the interaction stage, where virtual prototyping moves a user from wanting something to verifying it.
19.5%Verified fulfillment at conversion, locking in demand through future-queue commitments and then producing against it.
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.
Intent signalThe feasibility and accuracy of the virtual products suggested. This is the upstream layer that determines whether any downstream number means anything.
Efficiency signalFulfillment performance from the moment a seller accepts a reservation through production and delivery. This is the layer the user actually feels.
Value signalThe quality of the demand data supplied to sellers and manufacturers. Because it is sold as a B2B product, it carries service-level accountability.
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
Empirical validationThe work rests on high-level strategic estimation without diverse real-world use cases. It assumes behavioural intent translates reliably into purchase commitment, and that assumption is untested.
AI autonomy governanceThe gap between predicted intent and actual commitment needs a transparent governance framework. Closing it by assumption is exactly the failure the audit criticises elsewhere.
Post-fulfillment transparencyFor customised or niche products, standardised after-sales guidelines are hard to design. The model has to account for what happens when a demand-validated product still disappoints.