The Marketplace: buy, sell & install proven systems
The Marketplace turns Mass into a two-sided economy. Creators list funnels, templates, emails, and whole multi-asset systems; buyers browse, check out, and install them straight into their own account as an editable remix. Every listing is reviewed before it goes live, every creator has a profile that can be verified and featured, and the same publish pipeline feeds both the public marketplace and the onboarding template library.
16 min read · The complete marketplace guide
What the marketplace is
A catalog of installable assets, from a single template to a complete system.
The marketplace is where finished work gets shared and sold. A listing points at a backing asset — a funnel, a template, an email, or a composite "system/app" made of several components — and carries everything a buyer needs to evaluate it: a title, short and long descriptions, a thumbnail and preview images, tags and industries, a category, pricing, and a license. Buyers find listings through search and category browsing, sorted by trending and other signals.
Listings come in two shapes. A simple listing wraps one backing artifact. A composite listing (a system or app) is defined by its components — each pointing at an aspect and an optional source artifact, carrying the blueprint used to rebuild it on install — so an entire multi-page, multi-asset system can be packaged and sold as one product.
- Many content types — funnels, templates, emails, and composite system/app bundles can all be listed.
- Rich listing record — title, descriptions, thumbnail, preview images, tags, industries, category, pricing, and license.
- Composite bundles — a system/app listing is defined by component rows, each carrying the blueprint used to rebuild it.
- Discoverable — search and category browsing surface only published, non-deleted listings, sorted by trending and more.
Becoming a creator
A creator profile is the identity behind every listing — and it can be verified and featured.
To sell, you first register a creator profile: a display name (turned into a unique slug), a bio, avatar and banner, website and social links, and a payout email. The profile is the owning identity for every listing you publish — listings reference a creator, so the profile must exist before anything goes live. A user can hold one creator profile, and the system find-or-creates one automatically when an admin publishes on a user's behalf.
Admins curate the creator side of the market. A creator can be verified (a trust badge buyers see on listings), featured (surfaced more prominently), or suspended (removed from sale), and can carry badges and internal admin notes. Verification and featuring are how quality rises to the top without hiding the long tail.
- One profile per user — display name → unique slug, bio, avatar, banner, links, and a payout email for revenue.
- Owns every listing — listings reference the creator, so the profile is created before anything is published.
- Verified & featured — admins can verify (trust badge), feature (more prominence), or suspend a creator.
- Auto-provisioned — admin-published systems find-or-create the owning creator so a listing always has a valid owner.
Listing & the approval workflow
Every new listing is created pending and goes live only after review.
Creating a listing captures the category and content type, the backing content (or the components for a composite), the marketing copy and media, the pricing type and price, the license, tags, industries, and visibility. New listings are always created with a pending status — they require approval — so nothing reaches buyers without a review. For composite listings, the component rows that define what's inside are persisted alongside the listing.
An admin then reviews and publishes. Only published, non-deleted listings appear in search and on the public surfaces; pending and removed listings stay out of the catalog. That review gate is what keeps the marketplace's quality and safety bar consistent as the catalog grows.
- Pending by default — every new listing starts pending — it can't be bought until an admin publishes it.
- Captured at creation — category, content type, backing content/components, copy, media, pricing, license, tags, visibility.
- Components persisted — composite listings save their component rows so the bundle's contents are programmed in.
- Published-only surfaces — search and public pages show only published, non-deleted listings.
Pricing & licenses
Free, paid, freemium, or subscription — with a license that sets usage rights.
A listing's pricing type is one of free, paid, freemium, or subscription, with a price (and an optional compare-at price for showing a discount) in USD. Free listings install immediately at checkout with no payment step; paid listings route through Stripe checkout before the asset is granted. Pricing is set by the creator at listing time and can be edited on their own listings.
Each listing also carries a license type (standard by default, with extended options) that defines what a buyer may do with the installed asset. The license travels with the listing so the terms are explicit at the point of purchase, not buried in a separate agreement.
- Four pricing types — free, paid, freemium, and subscription, priced in USD with an optional compare-at price.
- Free installs instantly — free purchases skip payment and land in the buyer's account immediately.
- Paid via Stripe — paid listings route through a Stripe checkout before the asset is granted.
- License attached — a standard (or extended) license sets usage rights and travels with the listing.
Checkout & install-by-remix
Buy through a cart, then the asset lands in your account as an editable copy.
Buying runs through a cart. You add listings, then check out: if everything is free, the assets are added to your account immediately and you're sent to your purchases; if anything is paid, you're redirected to Stripe and the grant completes when payment confirms. Purchases are recorded so an installed asset stays available in your library.
Install isn't a read-only copy — it's a remix. The blueprint a listing carries is rebuilt into your own account as new, editable resources: a funnel becomes your funnel, a system rebuilds its pages and assets under your tenant. You start from proven structure and immediately make it yours — change the audience, offer, brand, and copy — rather than staring at a blank canvas.
- Cart checkout — add multiple listings and check out once; free carts complete instantly, paid carts route to Stripe.
- Recorded purchases — every install is recorded so the asset stays in your purchases/library.
- Installs as a remix — the listing's blueprint is rebuilt into your account as new, editable resources.
- Yours to change — start from converting structure and swap audience, offer, brand, and copy to fit your business.
The blueprint publish pipeline
How an ingested site or system becomes a listing the whole platform can reuse.
Behind composite listings is the blueprint engine. An admin ingests a site, email, or bundle into a derived blueprint that carries the original markup as its source. Publishing persists that blueprint — either as a marketplace system listing (with its component rows and steps) or as a reusable template — so the same work appears in both the public marketplace and the AI-onboarding Template Library, where a non-admin user can remix it.
Because the published row embeds the full derived blueprint and a synthesized page structure, the marketplace card, the onboarding "page structure" grounding, and the remix pipeline all agree on what the asset is. One publish action lights up discovery, onboarding, and install from a single source of truth.
- Ingest → blueprint — a site, email, or bundle is ingested into a derived blueprint that keeps the original markup as its source.
- Publish once, appear twice — publishing surfaces the asset in both the public marketplace and the onboarding Template Library.
- Self-consistent — the embedded blueprint and synthesized page structure keep the card, grounding, and remix in agreement.
- Components & steps — system listings persist component rows and listing steps so the bundle rebuilds faithfully on install.
The public showcase & agency surfaces
The same catalog renders MASS-branded publicly and agency-branded on a white-label domain.
Listings are presented through a host-aware showcase. On the public Mass surface, visitors see MASS branding and only publicly-approved (or global) listings. On an agency's surface — reached through their white-label custom domain or subdomain, or a path-based agency link — the showcase resolves to that agency's tenant and brand, and shows all of that tenant's published listings because they own the surface.
This means a creator or agency can run their own branded marketplace storefront without a separate build: the catalog, checkout, and install all work the same, but the branding and the visible set of listings follow whoever owns the domain the visitor arrived on.
- Host-aware context — the showcase resolves branding and the visible listing set from the request's domain.
- Public surface — MASS-branded, showing publicly-approved and global listings only.
- Agency surface — a white-label domain/subdomain resolves to the agency's brand and shows all their published listings.
- No separate build — the same catalog, checkout, and install power both the public market and each agency storefront.