Buyers say what matters.
A budget, a destination and a few must-haves. No email is needed to search. Sharing aggregate demand is optional.
BUYER-LED COMMERCE / A MRPRIME EXPERIMENT
What if brands shared demand,
instead of buying the same attention?
Tell us what you need. Explore real merchant offers. Keep a record of what was requested, checked and bought.
Free for buyers. You choose the merchant and approve payment there.
A request is a signal.
A checkout is a step.
An order needs evidence.
Actual pilot figures.
Test activity excluded.
Read the definitions →
THE LOOP
The first cohort is designed for complementary home and coffee brands. Participation begins with a small, measurable experiment.
A budget, a destination and a few must-haves. No email is needed to search. Sharing aggregate demand is optional.
A participating brand contributes a useful link from an existing customer touchpoint. The buyer discovers relevant products across merchants.
Requests, merchant checks and order confirmations stay separate. Brands can measure what their contribution generated.
THE MRPRIME BET
We’re testing whether an agency can earn its place by organising buyer demand and shared distribution. The first proof will be observed purchases, not a claim that the network already works.
Read the research and the risks ↗FOUNDING COHORT
We’re looking for UK-first home and coffee brands with a working direct store, products that complement each other, and a traffic source they can contribute.
Explore the brand pilot ↗Product order follows catalogue relevance. Payment to MrPrime does not buy a recommendation.
Brands receive aggregate evidence. Buyers keep their private request and choose where to transact.
Results will include misses and limitations. Any public case study needs the participating brand’s agreement.
FOR BUYERS
Start a buying request. Compare merchant offers, check an exact option, then choose whether to continue.
Loading this browser’s requests…
MERCHANT CATALOGUE
Prices are for the shown item, before final shipping and tax. Currency is shown as returned. Search order is supplied by the catalogue; it is not a paid placement.
That’s useful evidence too. Record what stopped the purchase.
FOR BRANDS / FOUNDING COHORT
Help build a route to buyers who say what they need. Contribute distribution. Learn which needs your catalogue can fulfil.
See the actual pilot numbers →PROPOSED 30-DAY PROOF PILOT
Draft commercial terms for review. No payment or contract is created by applying. No automatic renewal.
No sales guarantee. No assumed Shop commission. Customers buy directly from the merchant. Ongoing agency work is a separate proposal based on the evidence.
UK-first home and coffee brands selling on Amazon with a working Shopify direct store. Complementary products, stock to fulfil, and enough owned traffic to run a useful test.
A post-purchase page, editorial guide or other permissioned touchpoint. We don’t ask for a customer-list export.
Checkout, payment, fulfilment, returns and customer service remain with the merchant.
The initial cohort is a proposal. No brands have been named as participants without their agreement.
PUBLIC EVIDENCE DESK
The figures below come from stored records. Test activity is excluded. Small groups stay private.
Reading the ledger…
A distinct browser cookie or authenticated agent identity with a consented request. This is not a verified unique person.
A stated product need and item budget. Optional aggregate consent must be on. Requests expire after 90 days.
A merchant checkout created after the buyer’s instruction. It is not payment, an order or a sale.
The provider returned completed status and an order reference for the same checkout, with exactly the reviewed item and quantity. Refunds, cancellations and off-platform orders may be missing.
A controlled merchant-data comparison and return adjustment are needed before claiming lift or charging on profit. Individual receipts are private. Groups with fewer than five contributing sessions are suppressed.
CHECK THE RECORD
Download your own JSON receipt from a buying request. This checker recalculates each event’s checksum locally in your browser. The file is not uploaded.
A checksum detects an edited file when compared with its recorded digest. It is not an independent signature: the database operator could rewrite both.
Search, option checks, checkout handoff, private receipts, consent controls and applications are functional product paths. The network effect, customer acquisition cost and sales lift remain pilot hypotheses.
MRPRIME / THE MID-2027 AGENCY THESIS
Research cut-off: 13 November 2026. Three business models, one chosen experiment, and the evidence that could kill it.
My choice is Demand Commons: make MrPrime the organiser of a buyer-led distribution network. Brands contribute a route to buyers; buyers declare a need; the network records the journey to a merchant-confirmed order. Sell the ability to create and fulfil demand, with operating expertise behind it.
We found close predecessors in reverse marketplaces, collaborative commerce and agent transaction testing. The distinctive proposal is their commercial combination inside an Amazon-focused agency. Search cannot prove that nobody has built it. A six-month advantage and survival through 2027 are targets to earn, not facts we can certify.
Amazon’s Seller Assistant announcement describes persistent business context, connected workflows and access through Amazon Quick and Claude. That attacks the value of charging merely to interpret dashboards or operate Seller Central. Availability varies by geography and release stage. Amazon, 23 September 2026.
Amazon Ads Agent extends automation into campaign work across formats. Independently, Profasee already markets coordinated AI employees for pricing, advertising and inventory, including a shadow-mode evaluation. Seller Labs has offered Amazon advertising tools through MCP since earlier in 2026. A dashboard with an agent attached is weak differentiation. Amazon Ads, 29 September · Profasee · Seller Labs release history.
Inference for June 2027: routine execution, answers and basic audits face further price pressure. That does not mean every workflow becomes reliable or every agency disappears. It means MrPrime should anchor its fee in an asset the client cannot get merely by switching models: distribution relationships, observed demand and accountable commercial decisions.
| Model | Lead hook | What the client buys | Why it might survive / why it might fail |
|---|---|---|---|
| 01 · Demand Commons Chosen | Before proof: “Bring one route to buyers. See which requests your products can fulfil.” After evidence: “Here are the buying needs your range leaves unanswered.” | A distribution experiment, opportunity analysis and a managed route from buyer need to merchant checkout. | Consented relationships and useful traffic take time to reproduce. The cold start, shared-traffic incentives and weak conversion could kill it. |
| 02 · Agent transaction assurance | “Give your commerce agent a budget in a test environment. We’ll show where its promise, checkout and outcome diverge.” | Independent adversarial tests, operating limits and incident evidence for teams delegating revenue-critical actions. | Accountability persists after automation. Existing agent checkout testing and payment protections make the territory crowded; liability cannot be solved with a dashboard. |
| 03 · The agency you can leave | “In 30 days, own your operating system, permissions, history and handover. Keep it when you fire us.” | Portable operations, documented decision rules and a clean transfer between in-house staff, agents and service providers. | Ownership and continuity matter, but software vendors already offer agency replacement and portable data. It is a good service promise, a weaker news story. |
Assurance remains a useful ingredient in the chosen product: it stops a prepared checkout being sold as a purchase. Portability remains a service principle: each buyer can export the record. Neither needs to become a separate product or a claim of insurance.
| Primary-source release | Actual opening | How this build uses it |
|---|---|---|
| 13 October 2026 Shop MCP | A single integration exposes cross-merchant product discovery and checkout preparation to an independent app or agent. | Live anonymous catalogue queries, exact product-option checks, checkout creation and buyer-triggered status reads. Payment stays with the merchant. |
| 16 October 2026 UCP buyer consent | Participating cart/checkout integrations can negotiate store-specific privacy and marketing choices. | The current product keeps its aggregate consent separate and hands merchant consent to the merchant checkout. It does not claim to implement this protocol extension yet. |
| 4 November 2026 Amazon Shop Direct workspace | Eligible merchants can submit direct-store selection for discovery in Amazon’s US shopping experience. | Strategic signal that distribution boundaries are changing. It is not used as a UK acquisition channel in this build, and listing eligibility is not assumed. |
| 11 November 2026 Merchant knowledge API change | Shopify is moving merchant questions toward UCP ask_business; the older policies-and-FAQs tool is scheduled for retirement. | The product asks the merchant about requirements and policies using the current tool. Returned answers are labelled merchant statements, not verified product facts. |
The meaningful October opening is lower integration friction. It is not exclusive technology. Any competitor can access it; MrPrime’s proposed head start comes from using it to form a working cohort and accumulate credible evidence before the idea becomes standard agency packaging.
| Existing offer | What it already covers | Boundary of our differentiation |
|---|---|---|
| iwant | Structured buyer wants, supplier offers and agent protocols. | We cannot claim to invent demand-side commerce or reverse marketplaces. |
| Shopify Collective | Collaborative selling, product imports, inventory syncing and supplier fulfilment. | We are testing a buyer-request and distribution-sharing model; we do not import stock or act as a reseller. Cross-brand commerce itself is established. |
| VerityScore Prova: advertised prior art; endpoint unavailable at final check | Published tests of Shop MCP product discovery, plus an advertised agent-checkout testing product whose live operation was not verified. | We cannot claim a first AI shopping laboratory. Our assurance work serves a demand experiment. |
| NVIDIA agentic commerce | Merchant-side agent commerce patterns and protocol integration. | “An agent that sells products” is not the disruption. |
| Epinium · DataDoe | Agency-replacement positioning, in-house operation and multi-client data access. | Seller-owned operations and portable data are not untouched territory. |
The bounded novelty claim: our reviewed sources did not establish an identical deployed offering combining a contributing-brand distribution cohort, buyer-controlled request records, merchant-confirmed checkout outcomes and an agency sales process centred on those results. That is a differentiation hypothesis, not proof of absence. Several competitors could assemble the same pieces.
Start with six complementary roles, not six lookalike sellers: coffee, drinkware, brewing equipment, kitchen storage, table linen and home fragrance are candidate roles. These are proposed categories, not signed partners. Qualify UK-first Amazon brands with working direct stores, stock, useful margins and a permissioned traffic source.
The first acquisition offer is a concrete experiment: contribute one customer touchpoint for 30 days; learn what people request, what does not match and which journeys become orders. The application captures product fit and potential traffic. An optional link opens MrPrime’s existing enquiry form, “Speak with Robert Prime”, to support the sales conversation. A separate agreement defines scope before an operator activates a contribution link.
The first cohort should get a research-partner offer with clearly capped delivery effort. Do not sell £1,500 pilots to small brands simply because a form exists. A paid pilot becomes defensible when projected traffic, contribution margin and the measurement plan justify it. The working site shows the draft £1,500 offer for review, with no charge or automatic renewal.
Once evidence exists, the stronger lead hook is category-specific: a short, permissioned “unfilled demand” release showing what buyers asked for, the principal failure reasons and observed purchase outcomes. A brand that recognises a fulfilment opportunity can apply from that evidence. Those buyers have not been promised to it; buyer choice remains independent.
The agency expansion: a pilot exposes concrete constraints — assortment, product information, stock, delivery economics or conversion. MrPrime can offer implementation against that evidence. The ongoing fee must justify work and measurable value; it should not be sold as an exclusive right to consumers or a payment for higher rankings.
A lower-value basket exposes the commercial risk. Assume 25,000 eligible sessions, a 4% request rate, an 8% observed-order rate, and that half those orders are incremental. At £35 net order value, £24.50 expected variable cost and 5% of net revenue refunded, the £1,500 fee is not covered. These are assumptions, not measured performance.
Expected contribution is £8.75 per incremental order; 172 incremental orders cover the fee. Amounts exclude VAT. Other pilot costs are assumed zero. The owner workspace includes an editable model with refunds, incremental share and additional costs. Reject or redesign pilots whose economics do not support the fee.
The owner report separates requests a partner contributes from orders received by its mapped merchant store. Authorised merchant reports can add refunds and costs after the exact order reference matches. Changes to the provider’s order reference, currency or total make earlier reports stale. These reported amounts still require a credible comparison before anyone claims incremental profit.
At 5,000 eligible sessions with the same conversion, refund and incremental-share assumptions, there are 16 modelled observed orders and 8 incremental orders. Their £70 expected contribution leaves £1,430 of the pilot fee uncovered. Traffic volume, basket economics and the ability to measure incremental value all belong in qualification.
For MrPrime, six £1,500 pilots produce £9,000 revenue. A planning assumption of ten delivery hours per brand at £60 loaded hourly cost consumes £3,600; a further £900 allowance for technology and shared operations leaves £4,500 before sales cost and general overhead. None of those costs is measured yet. Shop commissions are zero in the model; promoted placements are not assumed available. Track actual hours and provider costs before pricing renewal. Shop developer documentation.
The product implements buyer-request creation, live catalogue search, selected-option checks, merchant questions, explicit checkout preparation, merchant handoff, manual status refresh, a private event receipt and local checksum verification. It includes consent withdrawal, data deletion, group suppression, a brand application funnel and an owner pipeline with contribution-link generation. It also exposes bounded MCP tools. Private agent journeys require a configured, authenticated client; a public URL alone grants no access.
The public founding pilot accepts genuine buyer requests and applications. Explicit test journeys are labelled and excluded from public statistics. The earlier private environment remains separate. A completed checkout status without an order reference does not count as an order. A merchant quote is not converted silently into another currency. The service never calls payment completion.
These functions can prove a technical journey. They cannot prove willingness to contribute traffic, qualified lead generation, retained clients, commercial lift or newsworthiness. The evidence desk must remain at its actual counts until genuine participation produces new records. The source and release checks are part of the delivery, not a substitute for market validation.
| Window | Required evidence | Decision |
|---|---|---|
| Before launch | Named consenting brands; one owned placement each; recorded catalogue and delivery eligibility; agreed data handling; written scope; baseline traffic and margin data. | Do not announce an operating network until these exist. Never use a current client’s name as implied participation. |
| First 30 days | Target 6 contributing brands, 1,000 genuine consented requests across the cohort, and at least 50 provider-confirmed orders. These are pilot gates, not claims or statistical-significance thresholds. | Check buyer usefulness, traffic quality and evidence coverage. Stop or change the proposition if distribution commitments do not materialise. |
| Days 31–60 | Merchant-agreed holdout or matched comparison, returns-adjusted contribution, support effort, and paid continuation decisions. | Publish measured outcomes with denominators and uncertainty. Avoid causal language if the comparison is weak. |
| By February 2027 | At least 3 brands choose a paid continuation, with scope and contribution economics that make sense for both parties. | Scale that category or stop charging for an unproven demand promise. A software demo is not this gate. |
| By June 2027 | Repeat participation, reliable merchant data, sustainable delivery hours, buyer satisfaction and a second category that can stand on its own. | The intended advantage is a working network with evidence. If only the interface survives, the strategy has failed. |
For the merchant-data comparison, define eligible visitors, assignment, success event, exclusions and return window before seeing results. Randomise where the merchant’s implementation permits it; otherwise disclose the weaker design. Provider order references alone cannot identify all cross-device, delayed or off-platform purchases. The current app records observable journeys; it does not claim a deployed incrementality experiment or full order lifecycle reconciliation.
What should an Amazon agency sell when Amazon can do the work?
We’re testing an answer at MrPrime: organise demand. Demand Commons lets buyers state a need, explore merchant offers and keep a receipt of the journey. We’re inviting a small group of complementary home and coffee brands to contribute a route to buyers. We’ll publish what works, what fails and what remains unproven. If you have a direct store and a customer touchpoint worth testing, apply to the founding cohort.
“MrPrime tested a shared-demand model with [consenting brands] over [dates]. From [eligible sessions], buyers created [requests]; [provider-confirmed orders] were observed. [Return-adjusted result and comparison design]. Here is the method, the misses and the limitations.”
Replace every bracket with reviewed evidence. If the pilot fails, the honest experiment and its released method may still be interesting. Neither outcome guarantees coverage.
Yes. The code and protocol access are not a durable moat. The bet is on relationships with brands, useful buyer experiences, repeated contributions and credible measurement. Platform ownership and distribution rules are continuing risks. Exportable receipts reduce lock-in but do not eliminate dependence on the catalogue and checkout provider.
Only if the placement serves a complementary need and the return justifies it. A post-purchase or editorial touchpoint is the initial candidate; do not put a competitor in an active purchase path. The pilot must measure cannibalisation and the cost of attention. Mutual benefit is unproved until brands see it.
It shares the distribution problem with affiliates. Its proposed distinction is buyer-declared needs, explicit participation, missing-demand evidence and a shared measurement discipline. There is no assumed affiliate commission in the build. If the service produces only outbound clicks and no useful learning or orders, the objection wins.
The web form is an entry point, not a proposed replacement for a general assistant. The tool interface can let an assistant create and inspect a buyer-authorised request. The distribution comes from useful contexts in participating brands’ journeys. Without that context and a better outcome, buyers have little reason to return.
The implemented technical journey goes from request and application capture to checkout handoff and evidence inspection. Payment remains a deliberate merchant action. The commercial journey still requires people to agree, contribute traffic and buy. Those actions cannot be fabricated or guaranteed by completing the software.
Research combined current primary-source announcements, vendor product pages, protocol documentation, an exhaustive external research pass and direct calls to the public Shop endpoint. A live catalogue test and exact-option read succeeded on 13 November. The initial UK/GBP query also returned other currencies, reinforcing the need to preserve source values. Advertised competitor features were treated as prior-art signals, not independently proven performance. A later release or undiscovered private product may change the novelty assessment.
The product makes no claim of official Amazon or Shopify endorsement. It does not claim that public catalogue access supplies a ready-made audience. The practical recommendation is to launch a bounded research cohort, earn a result, and make that result the lead magnet.
PRIVACY & YOUR DATA
Product-specific notice · 13 November 2026 · founding pilot
Demand Commons is operated by MrPrime. You can search without providing an email address. Sharing your request in group statistics is optional.
A buying request contains the product description, must-haves, category, country, item budget, time, any participating-brand referral and your aggregate-sharing choice. A necessary first-party cookie identifies this browser so it can open its own requests. Authenticated agent requests use a separate, site-scoped identity.
The receipt records catalogue checks, selected offers, merchant answers and checkout status. We retain a hash of a returned order reference, not your card, shipping address or order contents from the final payment page. Do not enter sensitive personal information in a product request.
Product search terms, coarse delivery country and currency are sent to Shopify’s Shop catalogue. If you ask a merchant a question, your must-haves are included in that question. Preparing checkout sends the exact selected item, quantity one, country and currency. It does not send a name, email, full address or payment information.
The merchant’s website handles payment and its own privacy choices. You should read its policy before giving it personal details. This product’s optional group-statistics consent does not opt you into merchant marketing or replace consent choices at checkout. Shopify’s privacy policy.
The site and its structured records run on MrPrime’s managed Hostinger server. Encrypted HTTPS carries requests; owner access is restricted. Checked daily database backups are retained for seven days on the server. Images and brand fonts may load from Shopify’s image CDN and MrPrime. Their servers receive the network information needed to deliver those resources.
The public evidence desk shows aggregate, consented, non-test activity. Groups with fewer than five distinct contributing browser or agent sessions are suppressed. This threshold reduces disclosure risk; it is not a guarantee of anonymity. Brands do not receive buyer contact lists or access to your individual receipt.
MrPrime’s authorised owner can operate the database and application desk. Receipts are private to the browser or agent identity that created them. Export files contain your request text, so treat them as private if you choose to share them.
The application form records your name, work email, brand, store domain, category, optional Amazon link, traffic estimate and proposed contribution. Permission to respond is required to submit. It is separate from marketing consent; no marketing subscription is created. The owner can review, export and progress applications through the pilot sales process. An application, pipeline status or contribution link is not a signed contract.
The owner can match an agreed partner to its merchant store and compare requests contributed with orders received. This private operational report includes requests whose public aggregate-sharing option is off; it is not shared with other brands. An authorised merchant report may add order status, net revenue, refunds, variable costs and return-window closure. The exact merchant order reference is compared transiently with the provider reference’s hash; raw order and source-file references are not retained. Corrections create numbered revisions. These records follow their buying request’s 90-day retention and deletion controls.
Buying requests become inaccessible after 90 days. Expired requests, related receipts and inactive offer records are removed by the next hourly cleanup triggered by site traffic, or an owner cleanup. Catalogue prices expire after 10 minutes and are rechecked before a new option is approved. Brand applications expire after 90 days unless an activated partnership requires continued recordkeeping. We do not promise immediate deletion from platform backups.
The controls below apply to this browser’s records. Clearing the browser cookie removes your self-service access. For an agent-created request, an activated partnership or a record you can no longer access, contact MrPrime with its reference. Contact MrPrime · Main privacy policy.
Merchant catalogue data and answers can be wrong or incomplete. Product requirements, delivery, final totals, returns and eligibility must be reviewed with the merchant. Provider-confirmed status is not independent verification of fulfilment, net revenue or incremental profit. Demand Commons does not complete payments and is not the merchant of record.
MRPRIME OWNER ACCESS
Sign in to review applications, contribution partners and merchant reports.
OWNER WORKSPACE
Applications, contribution links and the evidence behind the next sales conversation.
Checking owner access…
Test leads are clearly labelled. Export only genuine, consented applications to your sales system. A pipeline label does not create a contract.
Confirm product fit, traffic contribution, merchant consent and the measurement plan on a fit call. Send a separate written pilot agreement through MrPrime’s existing sales process. Only then mark “contracted” and create its contribution link.