h11g
Use the tools you know and love to set up email automation
post_sign_up_flow.yml:
name: 'post_sign_up_flow'
kind: 'Drip'
from:
name: 'Karl from h11g'
email: 'karl@h11g.com'
signature: ../signatures/karl-community-manager.md
steps:
- kind: DelayInterval
interval: '10 minutes'
- kind: Email
subject: '3 tips to set you up for success'
body: './3-tips.md'
- kind: DelayNext
time: '14:00'
- kind: Email
subject: You're killing it, ${contact.first_name ?? 'queen'}
body: './killing-it.md'$ h11g apply -f post_sign_up_flow.ymlYour plate is already full and overflowing. Waiting for that 10MB "visual email editor" to load is the little-death that brings total obliteration.
And you're already well-versed in git, yaml and markdown. Using them for email automation will let you focus on your customers.
Product, marketing - what's the difference? If you're experimenting with product-led growth, you should still be using traditional online marketing techniques. But beware. It's a trap!
It begins with "let's just send this one email from the product". Soon you're building an ad-hoc marketing automation platform. Unless you're a marketing automation startup, it's a complete waste of your time.
Having your email automation in git gives you all benefits of version control. This means - complete history, "code reviews", and collaboration in your git UI provider.
The declarative interface allows you to reuse components, define complex control flows, and create relations between campaigns.
Your IDE is the perfect tool for navigating hundreds of files. You already know the keyboard shortcuts.
Your needs are complex, but building email automation doesn't necessarily create value for your end-users.
Using h11g gives you the time to deliver value to your customers and work on that ever-growing backlog.
$29/mo