Sell Automations on SchemaBounce

You build automations for clients. SchemaBounce hosts them, connects them to the buyer's tools, meters usage, bills the buyer and tracks versions. You set the price and keep 85% of each sale before payment fees (dec-013).

Builders sell on builders.schemabounce.com. These pages explain every step, in the order you meet it.

Not enabled yet

• Execution certification is not enabled. Every listing shows the Verified badge. The Certified badge appears when the platform turns certification on.
• Payouts are not enabled. Sales accrue in your Seller Hub balance. The monthly payout job is off until it is proven live. No payout date is promised here.

The path from your work to a sale

Step	What you do	Read
1	Check the fees and decide if the model fits	Earnings and fees
2	Register a publisher handle	Become a builder
3	Paste an n8n export and read the import report	Bring your n8n work
4	Choose a listing type and a price	Listing types and pricing
5	Decide what buyers can read	Open and sealed listings
6	Earn a trust badge	Certification and trust badges
7	Answer buyer requests with a proposal	Requests and proposals
8	Ship new versions to subscribers	Managed updates
9	Connect Stripe and get paid	Payouts, refunds and disputes
10	Work inside a client workspace the client controls	Clients, handover and support

The rules every builder agrees to are on one page: Builder rules.

What a builder is

A builder is a person or company that sells automations to businesses. SchemaBounce has two kinds of customer: businesses that use the platform, and builders that sell to them (dec-015). An agency or consultant who serves clients does so as a builder. There is no reseller or wholesale program.

You keep your tools and your client relationship (dec-016). The marketplace is where an automation becomes a priced, versioned, hosted product. n8n is the first deep import format. You do not have to rebuild your work or stop using n8n.

What the platform does for you

• Hosts and runs every deployed agent, workflow and domain.
• Connects the automation to the buyer's own accounts. The buyer enters their credentials, never you.
• Meters usage and bills the buyer.
• Freezes every published version and distributes updates as buyer-approved offers.
• Collects payment through Stripe and splits it.

What you do

• Build and maintain the playbook. Your name is on it.
• Write the listing and set the price.
• Answer your subscribers' questions about what the automation does.

Two ways to sell

• Listings. A buyer finds your bot, skill, workflow or domain template and buys it. See Listing types and pricing.
• Buyer requests. A business posts what it wants automated. You respond with a plan and a price. See Requests and proposals.

Services around a listing have their own pages: selling outcomes and maintenance subscriptions. To operate customer workspaces from your own MCP client, see Hosted MCP.