Creating a service
Package your skills into a fixed-scope, pre-priced offering clients can order without negotiating.
A service is a fixed scope at a fixed price with a stated delivery time. Clients order it directly — no proposal, no negotiation. That is its value to them, and its discipline for you: everything ambiguous has to be decided before publication rather than argued about afterwards.
What separates a service that sells
- A title that names the outcome, not the technology. "Automate your invoice approvals in n8n" sells; "n8n workflow development" does not.
- An explicit inclusion list — and an explicit exclusion list. The exclusions are what prevent the argument at the end.
- Honest delivery times. A missed date costs more reputation than a longer promise ever cost you in orders.
- Real examples: screenshots, an anonymised workflow, a short before/after.
- A revision count you can live with. This number decides how the end of every order feels.
Scope that holds
- "Includes: 1 trigger, up to 5 actions, error alerting to Slack."
- "Not included: building the Slack app, data migration."
- "2 revision rounds within 14 days of delivery."
- Named prerequisites the client must supply.
Scope that leaks
- "Full automation setup."
- No exclusions at all.
- "Unlimited revisions."
- No mention of what you need from the client.
Review before it goes live
Every service passes an automated policy check and may be reviewed by a person before it appears publicly. You can save a draft, preview it, and keep editing while it is in review. Listings are held or rejected for contact details, off-platform links, or claims that cannot be true.
Skills come from the approved list
Service and profile skills are chosen from the platform’s approved skill set rather than typed freely. It keeps discovery filters meaningful — a free-text skill nobody searches for helps no one find you.
A minimum engagement value may apply. Price at or above it, or your service cannot be ordered.
34 articles · Ask a question