Workflow Store Licensing: Personal, Commercial, Resale
TL;DRWhat each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase.
TL;DR: What each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase.
Table of contents
- License tiers and price multipliers
- Deployment docs and dependency lists
- Changelogs and update access
- R2 signed download links after purchase
Why this matters now
The AI freelance market is splitting in two. Contract counts for generative AI and creative production are growing sharply, while the average value per contract is falling and entry-level project volume has contracted. Meanwhile, AI-augmented professional services and complex orchestration work are growing in both contract count and revenue. The dividing line is no longer whether you can use a model — it is whether you can turn a model output into something a business can actually ship.
All figures in this guide are based on the platform's historical transaction sample as of 2026-11. Prices in CNY are stored internally as integer cents; USD amounts are converted using an exchange-rate snapshot locked when the order is created.
1. License tiers and price multipliers
Start by writing down what "done" means. What each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase. In practice, the teams that finish fastest are the ones that define an observable check for each step before any generation begins: an input specification, an expected artefact, and a person who signs off on it. For license tiers and price multipliers, capture the three most common failure modes and turn each into a checkable acceptance item.
A useful discipline is to keep three artefacts for every engagement: the original brief and its structured decomposition, intermediate versions with their parameters and prompts, and the final delivery with its acceptance record. The platform automates the first and last of these. Its brief builder turns a plain-language request into tasks, deliverables, a budget range, a timeline and skill tags; its delivery pre-check compares the submitted work against the original requirements and produces a 0–100 alignment score with a line-by-line breakdown. Scores below 70 trigger a suggestion to supplement the delivery, but never block submission.
Buyers benefit because they can verify rather than trust. Sellers benefit because a documented acceptance trail makes disputes short and evidence-based. Funds stay in escrow until acceptance, with a 72-hour auto-accept window to prevent indefinite holds.
2. Deployment docs and dependency lists
Start by writing down what "done" means. What each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase. In practice, the teams that finish fastest are the ones that define an observable check for each step before any generation begins: an input specification, an expected artefact, and a person who signs off on it. For deployment docs and dependency lists, capture the three most common failure modes and turn each into a checkable acceptance item.
A useful discipline is to keep three artefacts for every engagement: the original brief and its structured decomposition, intermediate versions with their parameters and prompts, and the final delivery with its acceptance record. The platform automates the first and last of these. Its brief builder turns a plain-language request into tasks, deliverables, a budget range, a timeline and skill tags; its delivery pre-check compares the submitted work against the original requirements and produces a 0–100 alignment score with a line-by-line breakdown. Scores below 70 trigger a suggestion to supplement the delivery, but never block submission.
Buyers benefit because they can verify rather than trust. Sellers benefit because a documented acceptance trail makes disputes short and evidence-based. Funds stay in escrow until acceptance, with a 72-hour auto-accept window to prevent indefinite holds.
3. Changelogs and update access
Start by writing down what "done" means. What each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase. In practice, the teams that finish fastest are the ones that define an observable check for each step before any generation begins: an input specification, an expected artefact, and a person who signs off on it. For changelogs and update access, capture the three most common failure modes and turn each into a checkable acceptance item.
A useful discipline is to keep three artefacts for every engagement: the original brief and its structured decomposition, intermediate versions with their parameters and prompts, and the final delivery with its acceptance record. The platform automates the first and last of these. Its brief builder turns a plain-language request into tasks, deliverables, a budget range, a timeline and skill tags; its delivery pre-check compares the submitted work against the original requirements and produces a 0–100 alignment score with a line-by-line breakdown. Scores below 70 trigger a suggestion to supplement the delivery, but never block submission.
Buyers benefit because they can verify rather than trust. Sellers benefit because a documented acceptance trail makes disputes short and evidence-based. Funds stay in escrow until acceptance, with a 72-hour auto-accept window to prevent indefinite holds.
4. R2 signed download links after purchase
Start by writing down what "done" means. What each license tier allows, what to put in the deployment docs, and how to version a workflow product after purchase. In practice, the teams that finish fastest are the ones that define an observable check for each step before any generation begins: an input specification, an expected artefact, and a person who signs off on it. For r2 signed download links after purchase, capture the three most common failure modes and turn each into a checkable acceptance item.
A useful discipline is to keep three artefacts for every engagement: the original brief and its structured decomposition, intermediate versions with their parameters and prompts, and the final delivery with its acceptance record. The platform automates the first and last of these. Its brief builder turns a plain-language request into tasks, deliverables, a budget range, a timeline and skill tags; its delivery pre-check compares the submitted work against the original requirements and produces a 0–100 alignment score with a line-by-line breakdown. Scores below 70 trigger a suggestion to supplement the delivery, but never block submission.
Buyers benefit because they can verify rather than trust. Sellers benefit because a documented acceptance trail makes disputes short and evidence-based. Funds stay in escrow until acceptance, with a 72-hour auto-accept window to prevent indefinite holds.
Practical checklist
- Define the business outcome before selecting a tool
- Break the request into three to seven verifiable tasks, each with a deliverable
- Offer three tiers so the buyer has a clear upgrade path
- Agree on acceptance criteria and explicit exclusions before work starts
- Keep every change inside the order thread
- Deliver source files, licence terms and handover documentation
Frequently asked questions
Can I start without a portfolio?
Yes. Begin with a narrowly scoped order, use escrow and the pre-check report as your trust signal, then raise prices after three to five documented cases.
How are commissions calculated?
Gig orders are charged 10%, projects 8% and workflow products 15%, plus a 1% withdrawal fee covering payment-channel costs. All are deducted at settlement.
How do currency fluctuations affect settlement?
They do not. The exchange rate is locked at order creation and stored on the order; settlement and withdrawals are accounted in integer CNY cents.
Related reading
Risk notice: the platform provides matching and fund escrow only; it makes no promise about delivery quality or earnings. Price ranges are based on historical transaction samples and are indicative only.
FAQ
Can I start without a portfolio?
Yes. Begin with a narrowly scoped order and use escrow plus the pre-check report as your trust signal.
How are commissions calculated?
Gig 10%, project 8%, workflow 15%, plus a 1% withdrawal fee at settlement.
How is currency risk handled?
The exchange rate is locked at order creation; settlement uses integer CNY cents.
Risk notice: the platform provides matching and fund escrow only; it makes no promise about delivery quality or earnings. Based on platform transaction samples, as of 2026-11。