The Verified Handover Protocol

What exactly must a seller deliver — and how the checklist works.

Every listing on clAIssified comes with a Handover Checklist specific to the tool type. The seller must complete every required item before your payment is released.

What is checked

The checklist depends on the type of tool sold:

Web App / SaaS

GitHub repository access, all environment variables and secrets, hosting access (Vercel/Netlify/AWS), database access, domain transfer, admin account creation, and a walkthrough call of at least 30 minutes.

Automation (Make / Zapier / n8n)

Exported workflow file, list of all connected accounts and credentials, step-by-step reconnection guide, and seller assistance with reconnecting to your accounts.

Chrome Extension

Chrome Web Store developer access transfer or ownership transfer, full source code, all API keys documented, and buyer confirmation that the extension works in their browser.

API Tool / Script

Source code (GitHub or ZIP), all dependencies documented, environment variables fully documented, deployment guide, and a confirmed test run in the buyer's environment.

Prompt Library

All prompts in the agreed format, usage guide, example outputs, and buyer confirmation of completeness.

Optional vs. required items

Some checklist items are marked "(if applicable)" — these only apply in certain situations, for example notifying existing users of a transfer. Required items must always be completed.

What happens after the checklist

Once all required items are complete, you receive a notification to confirm the handover. Clicking confirm releases the payment to the seller and starts your 90-day support window.

Was this article helpful?