🧠 How do you organize client workflows (VPS, APIs, onboarding, etc.)?

I’m curious to know how you structure everything once a client signs and pays.

For example:

What do you do right after closing the deal?
Do you ask for all credentials (domain, VPS, APIs, etc.) so you can set it up yourself?
Or do you send videos/tutorials for the client to create the APIs and then pass them to you?
When you need a technical environment (N8N running in a VPS in my case), do you set up a dedicated VPS for that client (with their domain, EasyPanel, etc.), or do you use your own VPS?
If you use your own VPS, do you create a new project in EasyPanel, or integrate the client into your existing N8N instance?
And in general, how do you handle technical and administrative onboarding? (Forms, automations, communication, etc.)

I’m mostly interested in how you manage everything outside of the N8N workflow itself, like the environment setup, organization, and client tech relationship.

👉 Feel free to share examples, templates, or just your step-by-step process. It’d be great to compare workflows and see best practices 🔧

3 comments