A short project brief makes estimates clearer and defines implementation and handover responsibilities.
Describe the current process
Write down the trigger, the steps an employee takes and the final outcome. Use a real business example after removing personal data. Include exceptions instead of only the ideal path; exceptions often reveal the real implementation complexity.
List systems and permissions
List tools, subscription plans and API documentation where available. Do not put passwords in the brief. Agree a secure method for granting limited permissions during implementation and revoking them afterwards. Define who owns accounts and billing.
Sample data and acceptance tests
Provide dummy data with realistic field names and formats. Define expected outcomes for a successful run, missing field, external error and repeated submission. Specify where errors are recorded and who receives alerts.
What will you receive?
Make a clear list: exportable workflow, setup documentation, variables and connections, operating instructions and a recovery plan. Arrange a handover session where someone on your team can run the workflow and find error information.
Project boundaries and changes
Specify exclusions, revision rounds and support duration. Adding another channel or a different CRM may change scope. Agree a small first version and document change requests instead of adding undefined tasks during implementation.
A quick decision checklist
Clear scope, known requirements, acceptance tests, documentation and someone responsible after handover. Clarify any missing item before buying.
Sources and next step
Review official n8n documentation and N8N Central listings. Use our starting guide to prepare your requirements and read the editorial methodology to understand the limits of this comparison.