Output preview required
Every product must show the output structure or sample result so buyers can judge fit before checkout.
Nexus Product Standards
Every marketplace product should help buyers understand the outcome, setup path, support expectation, and responsibilities before they pay.
What every product must make clear.
Nexus is not a vague template directory. Products need visible outputs, setup requirements, ownership, and technical readiness.
Demo data labeled
Demo profiles, screenshots, or seeded examples must be clearly labeled internally and never presented as real customer results.
Required inputs listed
Buyers should see the websites, tools, files, accounts, or data needed to run the automation.
Setup path visible
Products must explain whether setup is self-serve, guided, custom request, or not supported.
Technical review before launch
Hosted workflow products must pass import, credential, and runtime checks before approval.
Support expectations defined
Developers and Nexus operators must describe what support covers and what becomes new scope.
Buyer responsibilities visible
Buyers own correct access, valid credentials, accurate input data, and truthful business context.
Maintenance signals shown
Products should show last tested, last updated, and maintained-by details when available.
No hidden checkout path
Paid products should show base price, guided install fee when enabled, and setup choice before checkout.
See something unclear on a product?
Ask Nexus before checkout. The right product should be understandable before setup starts.