An example prompt for a marketplace

Build a marketplace where local potters sell handmade ceramics. It needs: seller onboarding and kyc, listings and media, search, filters and discovery, orders and the escrow state machine, payments, platform fee and payouts and buyer-seller messaging. Rule that must always hold: every status change goes through transitionOrder using UPDATE ... WHERE status = from in one transaction with an order_events insert; side effects are enqueued as jobs. Leave out for now: no custom KYC or identity-document storage and no learned ranking, ML fraud scoring or multi-currency presentment in phase 1.

Replace the first sentence with your own idea. The list of needs stays useful whatever the niche, because it comes from what a marketplace has to do.

• Build a freelance marketplace for translators and their clients. Start with seller onboarding and kyc and listings and media, and add search, filters and discovery once those work.
• Build a rental marketplace for camera gear between neighbours. People should be able to A single, auditable order lifecycle from payment to release, with deadlines.

Forge AI picks a reference architecture from how you describe the app. These phrases point to a marketplace: marketplace, two-sided marketplace, buyers and sellers, sellers and buyers, etsy, airbnb, fiverr and upwork.

• A single order state machine with compare-and-set transitions.
• Postgres full-text and btree search with precomputed ranking.

This is a reference design for the category, not a promise that every item is generated today. Built-ins such as email, background jobs, file uploads and search are coming soon, so anything here that needs them is something you add yourself for now.

• Dedicated search engine (OpenSearch/Typesense) with geo and learned ranking: Postgres FTS and btree filters are enough and keep the stack small.
• Read replicas for search and storefront reads: primary handles phase-1 load.
• Dedicated websocket tier for messaging and presence: SSE over LISTEN/NOTIFY covers open threads.
• Multi-currency presentment and cross-border payouts: single currency per listing ships first.

How detailed should a prompt for a marketplace be?

Name the users, the main objects, one rule that must always hold and one thing to leave out. The plan fills in the rest, and you can change it before generation.

Which words tell Forge64 this is a marketplace?

Phrases such as marketplace, two-sided marketplace, buyers and sellers and sellers and buyers point to this category.

Can I change the app after the first build?

Yes. Describe the change in plain English and Forge AI edits the app; the quality gate checks the code again.

• How to build a marketplace
• Marketplace architecture
• Marketplace security checklist
• Marketplace scaling checklist
• Often combined: SaaS dashboard
• Often combined: online store
• All app types