If you've ever tried to package a ComfyUI workflow for a client or a paying subscriber, you've probably hit this: it works perfectly on your machine, and then breaks the second someone else opens it.

The culprit is almost always the same — undocumented custom node dependencies.

Here's the fast way to catch it before a buyer does:

1. Open your workflow in a completely clean ComfyUI install (no custom nodes installed).

2. Every "missing node" error you see is a dependency you forgot to document.

3. Write down the exact repo + version for each one.

4. Re-test load order — some custom node packs silently conflict with others depending on install order.

This single audit step is the difference between a workflow that gets refund requests and one that gets 5-star reviews.

If you're building out a library of workflows to sell (whether as one-time products or a recurring Vault-style subscription), export-readiness is the foundation everything else — pricing, packaging, retention — is built on.

Curious what other AI artists here are building. What's the most complex workflow you've packaged for someone else?