4 ms·

Neat! I feel like I have a reasonably good idea of what this does, but I'd love to see an example to make it really come to life. I see on the website you have

Neat! I feel like I have a reasonably good idea of what this does, but I'd love to see an example to make it really come to life. I see on the website you have a gif where you're setting up an automation. I'd love a similar gif (or set of gifs) where you have a before (ugh I have to do this manually), the middle (your current gif), and an after (axiom doing it automatically).

yaseer 6y ago
You've hit the nail on the head for our biggest problem - many people don't realise axiom can solve their problem! We realised, the best way to do this is start producing templates with solutions to common problems. Here's one: https://web.axiom.ai/recipe/loop-through-pages https://web.axiom.ai/recipe/loop-through-pages As you say, visual guides work well. I think we have a lot to do here. We're gradually building up a library on the link above. One day, we'd like people to share their solutions openly (like airtable). We'd need to do security checks on our side though.
- 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 ago
    Ha, 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.

yaseer 6y ago

You've hit the nail on the head for our biggest problem - many people don't realise axiom can solve their problem! We realised, the best way to do this is start producing templates with solutions to common problems. Here's one: https://web.axiom.ai/recipe/loop-through-pages https://web.axiom.ai/recipe/loop-through-pages As you say, visual guides work well. I think we have a lot to do here. We're gradually building up a library on the link above. One day, we'd like people to share their solutions openly (like airtable). We'd need to do security checks on our side though.

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 ago
  Ha, 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.