4 ms·
I explored this idea last year and suspect this will be your main problem (people are bad at discovering automation use cases), unless you want to spend all you
by ed 6y ago
I explored this idea last year and suspect this will be your main problem (people are bad at discovering automation use cases), unless you want to spend all your time fixing Craigslist scrapers. One possible solution is to keep writing these "templates", but publish them as Zaps, and ensure you rank when people google for solutions. I suspect the user-facing tool you have now could actually just be internal, used for writing as many zap automations as possible, to fill the gaps in Zapier's catalog. Use Zapier for distribution and find some verticals you can productize. Best of luck!
- yaseer 6y agoHa, you're pretty well versed in the pain-points! Yes, that's the playbook we want to follow - long-tail SEO. That worked amazingly well for Zapier, and if we had a cheesy tagline, it's 'plug gaps in your zaps' like you've suggested! One interesting side-effect we noticed - people take inspiration from templates for other use-cases and this has driven up usage. When we show a YouTube studio use case to one customer, they'll try do the same thing in Mixpanel. Starting a fire here may boil down to how many generalisable templates we can churn out, and how well we can train people on integrating them.