iMarketplace

What an iMarketplace Is Not: Four Common Misconceptions

Understanding what an iMarketplace is not helps separate a proposed platform model from familiar products carrying new terminology.

An iMarketplace is not a conventional marketplace with a fashionable name, a chatbot attached to its search bar, an aggregator of external offers or a super-app collecting as many functions as possible. As we define it here, it is a platform organised around what a person intends to accomplish, with artificial intelligence native to its architecture and several related areas of everyday life connected in one experience.

The term is not yet an industry standard. It describes a category WEVONE is proposing and documenting publicly, so its meaning should be judged by clear structural criteria rather than by the presence of the letter “i” or an AI feature.

These distinctions matter because many existing platforms already have excellent search tools, large audiences, trusted transaction systems and strong specialist communities. An iMarketplace does not invalidate those strengths. It represents a different approach to how needs are expressed, interpreted and connected.

Not a rebranding of the marketplace

A traditional marketplace generally arranges supply into categories. A user selects fashion, furniture, property, services or vehicles, enters keywords and applies filters. This model is familiar, efficient and particularly effective when the user knows what the item is called and where it belongs.

Calling the same catalogue an iMarketplace would not alter its underlying logic. The difference described in Marketplace vs iMarketplace begins before the interface: does the platform expect a category and query, or can it interpret an intention stated in ordinary language?

Consider someone who says: “I need a suitcase for a three-day trip, no more than five kilometres away, and I may only need it for the weekend.” This is not merely a search for the keyword suitcase. It includes size, distance, duration and openness to buying or renting. An intent-led system should identify those elements, ask about anything important that remains unclear and search across suitable forms of supply.

The distinction can be summarised as follows:

| Misunderstanding | What it adds | What an iMarketplace requires | |---|---|---| | Rebranding | New terminology or visual identity | Architecture centred on intentions | | Chatbot layer | A conversational input box | Dialogue connected to discovery and action | | Aggregation | Results gathered from multiple sources | Native relationships across several universes | | Super-app expansion | Many functions in one application | Relevant needs connected around a user journey |

This does not mean categories disappear. Categories can remain useful for browsing, moderation, reporting and inventory management. The change is that users are not forced to translate every need into the platform’s taxonomy. Understanding intent instead of keywords explains why “what I want to achieve” can carry more useful context than a short search phrase.

Not a chatbot attached to a catalogue

Conversation must affect the result

A chatbot can answer support questions, suggest search terms or redirect users to existing pages. Those functions may be valuable, but they do not by themselves create a conversational marketplace.

In an iMarketplace, dialogue is part of the transaction journey. If a person asks for “a driver to the airport early on Monday”, the system might need to clarify the collection point, number of passengers, luggage and required arrival time. The answers should change which offers are considered and how they are ranked. They should not simply produce a link to a transport category.

That distinction is explored in Conversational Search: How It Actually Works. The conversation needs access to structured listings, availability, location, permissions and other relevant platform information. It must also communicate uncertainty rather than pretending to understand details that were never supplied.

AI must be architectural, not decorative

An AI marketplace may use artificial intelligence for several purposes: interpreting natural language, assisting with listings, detecting inappropriate content, recommending relevant options and connecting needs across universes. The defining issue is not how many AI tools appear on screen, but whether they were considered when the platform’s data, workflows and interactions were designed.

This is the difference between native AI and added AI. Added AI can substantially improve an established product, and established platforms have the advantage of extensive inventories, user habits and mature transaction tooling. Native AI starts from a different design premise: conversation and interpretation are expected from the beginning rather than fitted around a catalogue built for keyword search.

An AI assistant marketplace must still provide controls. Users should be able to review assumptions, adjust location, reject recommendations and understand whether they are dealing with a seller, service provider, landlord or driver. Conversation should reduce effort, not conceal important distinctions.

Not an aggregator

An aggregator brings offers or information from several sources into one place. It can save time, expand choice and make comparison easier. Travel search, price comparison and listings portals demonstrate the practical value of this model.

An iMarketplace is not defined by collecting external results. Its multi-universe structure means that goods, services, housing, mobility, missions, events, animals and skills can exist as related forms of supply inside a coherent platform experience. Identity, location, trust mechanisms and conversational context can therefore carry from one part of a journey to another, subject to appropriate consent and safeguards.

Suppose somebody is planning a weekend away. They may need a short rental, transport, pet care and perhaps a local event. An aggregator could display links from four providers. A multi-universe platform instead treats these as parts of one intention and may help the user address them in sequence. The principle behind why universes work better together is connection, not simply collection.

The same applies to moving house. Finding a flat might lead to a need for a driver, parcel delivery, gardening help or a second-hand bike for the new commute. A genuine connection between universes should arise from that context. It should not be a generic attempt to cross-sell unrelated offers.

Not a super-app for its own sake

A super-app usually describes a broad digital environment containing many services. Such products can offer convenience, habitual use and a single point of access. Their success often depends on scale, infrastructure and a strong existing relationship with users.

An iMarketplace may also contain several kinds of activity, but breadth is not its purpose. The test is whether different universes help fulfil connected intentions. Adding restaurant bookings, banking, messaging or entertainment merely to increase the number of functions would not make a platform an iMarketplace.

For example, a person who wants to sell second-hand clothes may also need listing assistance, local collection or parcel delivery. Those activities form a plausible journey. A person seeking a private tutor might later need a quiet room or transport, but the platform should make that connection only when it is relevant. Multi-Universe: What It Changes for Users examines how breadth can reduce repeated searches without turning every possible service into a mandatory bundle.

The objective is coherence:

  • one intention can involve several forms of supply;
  • context can be retained where the user permits it;
  • the assistant can ask clarifying questions across universes;
  • each universe keeps the information and safeguards appropriate to it;
  • recommendations are based on relevance rather than breadth alone.

What positively defines an iMarketplace

Avoiding the four misconceptions leaves five defining properties.

It begins with intention

The user can describe a desired outcome in ordinary language: “find near me a second-hand bike suitable for a short commute” or “I need gardening help on Saturday and a way to remove the cuttings”. The platform works out the likely objects, services, constraints and relationships involved.

It uses native artificial intelligence

AI is part of discovery, interaction and platform operations from the outset. This can include natural-language interpretation, listing support, moderation and contextual recommendations. Human judgement and explicit user controls remain necessary.

It is conversational

The system can ask a useful follow-up question. This is more than presenting a long form one field at a time; the dialogue should resolve ambiguity and improve the available choices. The wider implications are covered in The AI-Assisted User Experience.

It is multi-universe

Different areas of everyday exchange can exist in one environment. A second-hand bike, a private tutor, a weekend rental, gardening help and pet care are not forced into one undifferentiated category, but they can be connected when an intention crosses boundaries.

It supports a journey rather than an isolated query

A move, weekend or event commonly creates several needs. The iMarketplace model aims to recognise that relationship, while allowing the user to address only the parts they choose.

These properties correspond to Intelligence, Intention, Interaction and Individualisation, with multi-universe connection providing the environment in which they operate. They are described together in The Four I of the iMarketplace.

WEVONE as an early illustration

WEVONE is one concrete illustration of this proposed category, not evidence that the category has already become established. As of August 2026, it is a young platform, public since 2026, with a few hundred registered members. It is far smaller than Vinted, Leboncoin, eBay or Facebook Marketplace, whose scale, liquidity, established habits and specialist tooling remain significant advantages.

Available today, WEVONE brings several universes into one app: Tutus for second-hand goods and fashion, Nest for housing and space rental, Mission for services and local gigs, Events, and Pilote for transport and parcel delivery. More universes are planned.

Its built-in AI, Mia, supports conversational natural-language search, including a request such as “a black T-shirt with an eagle on it”. It also assists with listing creation through photo analysis and title and price suggestions, moderates listings and photos, and provides cross-universe recommendations. Local discovery is map-based and filtered by the area currently being viewed.

WEVONE describes participation as “Earn from every action”: buy, sell, rent, book and earn. Income is never guaranteed; it depends on factors including demand, location, condition and pricing. The platform’s present size also means that availability may be limited in some places or universes.

Conclusion

An iMarketplace is best understood by its architecture and behaviour, not its branding. It is not a renamed catalogue, a chatbot over filters, an aggregator of disconnected providers or a super-app pursuing breadth for its own sake.

It is a category we are proposing for platforms designed around intentions, native AI, useful conversation, individual context and connected universes. Whether this model becomes widely adopted remains an open question. Its practical value will depend on relevance, trust, supply, transparency and whether it genuinely makes everyday journeys easier.

FAQ

Is iMarketplace an established technology term?

No. It is not yet an industry standard term. WEVONE is proposing and publicly defining the category around a specific set of structural characteristics.

Does any marketplace with AI become an iMarketplace?

No. AI can improve a conventional marketplace without changing its category-led architecture. An iMarketplace requires intent-led, conversational and multi-universe design, with AI native to the platform.

Can an iMarketplace still use categories and filters?

Yes. Categories and filters remain useful. The difference is that users can begin with an ordinary-language intention rather than having to identify the correct category first.

Is an iMarketplace the same as a super-app?

No. Both may cover several activities, but an iMarketplace connects universes to fulfil related intentions. Accumulating unrelated features is not its objective.

Is an iMarketplace an aggregator?

Not by definition. An aggregator gathers results from different sources. An iMarketplace is designed to support relationships and journeys across native universes in one platform architecture.

Does WEVONE already provide every proposed universe?

No. Goods and fashion, housing and spaces, services and gigs, events, transport and parcel delivery are available today. Additional universes are planned, and availability varies according to local supply.

Further reading

  • What Is an iMarketplace? — a concise introduction to the proposed category.
  • Catalogue or Conversation? — how two different discovery models shape the user journey.
  • Specialist Platforms vs Multi-Universe Platforms — the strengths and trade-offs of focused and broader platform designs.
  • What an iMarketplace Owes Its Users — the responsibilities accompanying AI-assisted discovery and connected services.