Building Automation Products

There's a large and underserved market for vertical-specific automation products — tools that automate a specific workflow for a specific industry without requiring the buyer to understand n8n or Zapier. If you can identify a painful, repetitive workflow in an industry you know, you can build and sell an automation product. Automation products come in two main forms. The first is a packaged service: you build and maintain the automation on behalf of clients, who pay a monthly retainer. You use n8n (or similar) behind the scenes. The client gets the output — the automated Slack reports, the email sequences, the lead enrichment — without knowing or caring how it works. This is a high-margin service business. The second is a SaaS product: you build a product that wraps automation capabilities in a user interface. Users configure their automation through your UI (no n8n knowledge required), and you run it on their behalf. Revenue is subscription-based, and the unit economics improve with scale. The best opportunities are workflows that: affect multiple companies in the same industry, involve significant manual time (30+ minutes/week), have a clear measurable outcome (time saved, leads generated, errors reduced), and don't require complex customization per customer. Examples: a Shopify review monitoring and response tool for ecommerce stores, a real estate listing-to-social-post automation for agents, a legal document first-draft generator for small law firms, a job application tracking and follow-up automation for recruiting firms.

Turning a workflow into a product requires additional infrastructure: multi-tenancy, configuration storage, billing, and a UI. Here's the minimal viable architecture. Multi-tenancy in n8n: each customer needs their own set of credentials (their CRM API key, their Slack webhook, their Gmail account). N8n supports this through its Credentials system and through workflow parameters. The simplest approach: one workflow per customer instance. At scale, use n8n's API to programmatically create and manage workflow instances. Configuration storage: build a simple web form (Next.js or even a Typeform) where customers input their API keys and configuration preferences. Store this in your database. When the n8n workflow runs for a customer, it fetches their configuration from your database at the start. Billing: Stripe's subscription API is the standard. Integrate it early — customers should need to pay before they can configure their automation. Use webhooks from Stripe to pause workflows when subscriptions lapse. A UI layer: for the simplest products, you may not need a custom UI at all. Use a Notion template, an Airtable base, or a simple Google Form as the 'interface'. Customers fill it in, and your automation reads it. This lets you validate demand before investing in a proper frontend. Go-to-market strategy: sell the outcome, not the technology. 'Save 3 hours a week on lead follow-up' outperforms 'automated email sequences' as a value proposition. Charge for the time saved, not for the tool.