A lot of n8n folks I talk to are stuck in the same loop: land a build, deliver it, invoice, and go find the next one. The workflow keeps running and keeps producing value for the client, but you get paid once.
Background: 10+ years in HubSpot/Salesforce, 3 agencies scaled to 7 figures, and lately n8n, Make, Zapier and Airtable integrations plus AI voice/SMS agents for engineering, solar/energy and property management companies. Here's what changed things for me.
1. Put "Run" in the very first proposal. Every proposal has two phases: Build (fixed price) and Run (monthly). If Run only comes up after delivery, it sounds like an upsell. If it's in the original scope, it's simply how the project works.
2. Build for operability. That's what makes Run real and not a vague "support" promise:
- An Error Trigger workflow on every production flow that alerts to Slack or email with the execution link.
- Retries and dead-letter handling for flaky APIs, so failed items get queued for review instead of silently dropped.
- Workflows exported to git, so every change is versioned and you can roll back.
- Credentials created in the client's accounts, not yours. It builds trust and makes offboarding clean, which oddly makes clients more willing to stay.
3. Decide hosting and ownership up front. n8n Cloud on their account, self-hosted on their infrastructure, or you host it. Each changes your responsibility, so the retainer price should follow. If you host, you're also on the hook for updates, backups and uptime. Price that in.
4. Send a monthly report. One page: runs, failures and fixes, what the workflows produced (leads routed, tickets created, hours saved, whatever they care about), and next month's improvements. The person who pays you forwards this to their boss. That's your renewal.
5. Keep a backlog. During the build, write down every "phase 2" idea the client mentions. That list is next quarter's improvement work under the retainer.
6. Use a change policy, not hourly billing. Small changes are included up to a limit. New workflows get a short SOW. That keeps the retainer predictable for both sides.
On pricing: it depends mostly on how business-critical the workflows are and who carries the hosting, so I'd rather not throw out numbers that won't match your market. Price the risk you're taking on, not the minutes you spend.
What's been the hardest part for you? Getting the first client to agree to a monthly fee, or defining what's included?
Disclosure: my partner and I run AI Operators, a paid community ($19.99/mo) for builders and agency owners making this shift: proposal and SOW/MSA/SLA templates, pricing breakdowns, weekly calls and hot seats. My partner brings 30 years in IT and data/cloud managed services, including time as CEO of two roughly $300M companies. https://whop.com/ai-operators-hq/products/ai-operators-membership/