PlateMates social dining concept + published MVP, brand direction, UX, and sourc
salesby My Team
FREEPlateMates — as-is MVP / concept package
Working sale copy and inventory. This is a truthful as-is listing draft, not an owner-ratified valuation, offer, warranty, or commitment to transfer any asset. Confirm ownership, authority to sell, and transferability of every asset before publishing or accepting an offer.
Marketplace listing title
PlateMates social dining concept + published React MVP, brand direction, UX, and source package (as-is)
Marketplace listing description
PlateMates is an early-stage social-dining concept and published, interactive MVP. The product direction is dish-first discovery: diners browse dishes, save a shareable “plates to try” tasting list, and could eventually find compatible nearby diners to share multiple dishes at one table.
The package is offered as-is for a buyer who wants a starting point rather than a functioning operating business. It includes a polished diner-facing website/MVP, its source and implementation structure, the PlateMates brand direction, and the documented product/UX concept. The buyer would take responsibility for validating rights, rebuilding production capabilities, adding real data and integrations, and operating the service.
The public site currently uses clearly labeled mock/sample restaurant and dish data. It is a concept preview, not evidence of live inventory, revenue, demand, partnerships, bookings, or traction. All third-party image, data, menu, API, hosting, domain, and other rights must be verified before commercial use or transfer; no third-party right is represented as transferable unless separately confirmed in writing.
Included in the package (subject to rights and transferability verification)
Published MVP/site: PlateMates public site at https://40603094c98e82e9449eeacda7e516a2.ctonew.app, including the landing page, concept explanation, sample-dish discovery, cuisine filters, tasting-list tray, and interest/early-access flows.
Source code and implementation: The current TanStack Start / React + Vite + Tailwind application in /home/team/shared/site, including route and component structure, TypeScript types, build configuration, publishing scripts, and implementation documentation (SITE.md).
Brand direction: PlateMates name and the existing visual direction as represented in the MVP (warm cream palette, espresso ink, tomato accent, gold highlight, food/social-dining positioning, typography choices, logo treatment, and messaging). Trademark, domain, copyright, and other ownership/transfer rights are not assumed and require diligence.
UX/design assets: The implemented responsive diner journey and interaction patterns, including hero and concept sections, “how it works,” sample-dish cards, cuisine filtering, tasting-list tray, join modal, operator/licensing section, FAQ, accessibility-oriented labels/focus behavior, and responsive styling.
Sample content structure: TypeScript data model and illustrative records for eight dishes across Japanese, Mexican, Italian, and Indian cuisines, with restaurant name, dish name, price, description, tag, rating, image path, and alt text fields. These records are explicitly demo content, not verified restaurant/menu data.
Licensing / buyer-facing section: Existing on-site copy describing potential operator/platform use and a possible starting package. It is informational positioning only: there are no established license terms, exclusivity terms, standard fees, or signed licensee arrangements included.
Implementation notes: The site’s current limitations and future-build direction, including the need for a backend, real content and rights, matching, bookings, payments, moderation/safety, privacy, and integrations.
Static visual assets currently in the package: public/images/hero.webp and eight dish images (dish-ramen.webp, dish-pizza.webp, dish-tacos.webp, dish-butter-chicken.webp, dish-sushi.webp, dish-gnocchi.webp, dish-tostada.webp, and dish-biryani.webp), subject to verification of their source and commercial-use rights.
Not included or not yet available
No verified revenue, profit, financial statements, paying customers, customer database, usage analytics, or validated traction.
No restaurant partnerships, signed operators, licensees, reservations, bookings, table availability, or live restaurant relationships.
No live diner matching, messaging, accounts, profiles, community moderation, or production social features.
No live Google Maps, Yelp, restaurant-menu, discovery, reservation, or other external API integration.
No server-side lead database or connected CRM. The interest, tasting-list, and licensing interactions are browser/client-side demonstrations; submitted values are stored locally in the user’s browser only and are not delivered to the seller.
No connected Stripe account, payment processing, subscriptions, checkout, or other monetization system.
No verified transferable rights to third-party photography, imagery, restaurant names, dish/menu data, ratings, APIs, domains, fonts, hosting accounts, or other third-party material unless separately confirmed.
No representation that the domain, brand registrations, source materials, or every image/content item is owned by or assignable by the seller. These are diligence items.
No continuing development, marketing, integration work, legal advice, operating service, support commitment, or outcome guarantee unless separately agreed and funded.
Honest current status and technical limitations
The MVP is published and interactive, but it is a concept/demo surface, not a production marketplace or operating business.
The site is a TanStack Start application using React, TypeScript, Vite, and Tailwind. It has a single / route and client-side UI state for filtering and list interactions.
The eight dish records and restaurant names are illustrative sample/mock content. Prices and ratings are not current or verified. The public site labels the content as sample and states that it is not live listings, real-time data, real bookings, or real people.
The tasting list can be added to, removed from, cleared, and persisted in localStorage on the user’s device. It is not a shared account-backed list or server record.
The early-access/join form performs browser-only validation and local storage. It does not transmit an email or create a lead for the seller. The licensing inquiry form has the same browser-only limitation.
The repository contains a database helper that expects DATABASE_URL, but no connected database-backed feature is present in the current MVP. A buyer must independently provision and secure infrastructure.
There is no authentication, authorization, server-side persistence, API layer for live listings, matching algorithm, booking workflow, payment flow, admin tooling, analytics setup, or production data operations.
The current public hosting URL and domain arrangement should be treated as deployment details to verify, not as a promise of permanent hosting or automatic domain transfer.
Buyer fit
Potentially relevant buyers include:
Restaurant groups seeking a dish-led discovery and group-dining concept for their own portfolio.
Hospitality operators looking for a social dining / guest-engagement starting point.
Food-discovery, reservation, or restaurant software platforms that want a shareable tasting-list UX layer.
Entrepreneurs who want a polished concept/MVP foundation to validate, rebuild, and operate.
This list describes possible fit, not buyer interest, demand, or a guaranteed commercial outcome.
Buyer responsibilities and future costs
The buyer assumes responsibility for all post-sale validation, development, and operation, including:
Confirming chain of title and rights for the brand, domain, source, design, fonts, photography, data, names, and any other included material; replacing anything that cannot be used.
Building and paying for hosting, domain renewal, email, database, authentication, monitoring, analytics, backups, security, development, API usage, maps/data licenses, payment processing, and other infrastructure.
Securing restaurant/operator agreements and lawful, current menu, venue, pricing, image, ratings, location, and availability data.
Designing, implementing, testing, and maintaining matching, accounts, messaging, bookings, payments, notifications, admin tools, and server-side lead capture if desired.
Handling privacy, consent, data retention, accessibility, consumer disclosures, terms, safety, moderation, liability, insurance, tax, payment, and other legal/regulatory requirements in each market.
Funding product development, QA, content operations, customer support, sales, marketing, partnerships, and any integration work. No future effort or spend is included by default.