🎙️ Co-host at slowandsteadypodcast.com
🛠️ Ruby, Rails, Ember.js, PostgreSQL
❤️ Loves music, food, and cooking
🥁 Plays the drums
benediktdeicke.com
I'm Benedikt, a full stack software engineer turned (mostly) bootstrapped founder 😄
Together with my co-founder I run and build Userlist, an email marketing automation platform for SaaS businesses 💌
Mostly working with Ruby on Rails, Ember.js, and PostgreSQL at the moment 🛠️
It’s more powerful to admit a mistake, than to persist when everyone else knows it’s a mistake.
It’s a mistake either way, but only one way means you’re either oblivious or disingenuous.
It’s more powerful to admit a mistake, than to persist when everyone else knows it’s a mistake.
It’s a mistake either way, but only one way means you’re either oblivious or disingenuous.
Still, I’m glad that for the most part, we’ve built a company that we enjoy working at, despite the challenges thrown at us regularly 🤗
Still, I’m glad that for the most part, we’ve built a company that we enjoy working at, despite the challenges thrown at us regularly 🤗
It's all my best ideas -- and best writing -- on how to grow your company with your existing budget and team.
And yes, I read the audiobook myself. :-)
(1/5)
It's all my best ideas -- and best writing -- on how to grow your company with your existing budget and team.
And yes, I read the audiobook myself. :-)
(1/5)
▪️Don't be afraid to email more
▪️Treat this as a process with continuous improvement/expansion, rather than a one-off project
▪️Be helpful
▪️Keep your messages short and focused
▪️DON'T OVERTHINK
Simple, not easy.
▪️Don't be afraid to email more
▪️Treat this as a process with continuous improvement/expansion, rather than a one-off project
▪️Be helpful
▪️Keep your messages short and focused
▪️DON'T OVERTHINK
Simple, not easy.
Any recommendations on how to spend those hours? 😄
Any recommendations on how to spend those hours? 😄
It's just a mattress.
It's just an ESP.
It's just a mattress.
It's just an ESP.
Enjoy!
#Ruby
Enjoy!
#Ruby
Also, who makes comments this long and awesome?
Also, who makes comments this long and awesome?
Split testing is the obvious use: create different user journeys, then compare using email metrics or conversion goals. Classic.
Split testing is the obvious use: create different user journeys, then compare using email metrics or conversion goals. Classic.
But seriously?
But seriously?
This week I stumbled upon transcription for Since U Been Gone by Kelly Clarkson, and I'm having way too much fun with it than I care to admit 🤣
This week I stumbled upon transcription for Since U Been Gone by Kelly Clarkson, and I'm having way too much fun with it than I care to admit 🤣
This blew our mind.
So we set up a simple workflow (took me 15 minutes).
This blew our mind.
So we set up a simple workflow (took me 15 minutes).
That’s great… but it also means that there isn’t a good time to “wind down” 😵💫
However, I realized cooking dinner is my way to do this these days 👨🍳
That’s great… but it also means that there isn’t a good time to “wind down” 😵💫
However, I realized cooking dinner is my way to do this these days 👨🍳
Your best next step is: a workflow for your paying customers.
It runs at a slow pace (every 1-2 weeks) and combines educational content, feature nudges, and customer loyalty interventions (asking for referrals, reviews, etc).
Your best next step is: a workflow for your paying customers.
It runs at a slow pace (every 1-2 weeks) and combines educational content, feature nudges, and customer loyalty interventions (asking for referrals, reviews, etc).
A single post won’t impact your LinkedIn account. A hundred of them might.
A single email won’t impact your growth. A hundred of them might.
Zero emails… Safe bet.
#bdtpblurbs #emailmarketing
A single post won’t impact your LinkedIn account. A hundred of them might.
A single email won’t impact your growth. A hundred of them might.
Zero emails… Safe bet.
#bdtpblurbs #emailmarketing
Still a bit intimidated by the thought (and the complexity), but also intrigued by the new possibilities 👀
Still a bit intimidated by the thought (and the complexity), but also intrigued by the new possibilities 👀
This week, for the first time in my 20+ year career of writing Ruby, I went a bit further and changed a class to freeze itself after initialization 🧊
This week, for the first time in my 20+ year career of writing Ruby, I went a bit further and changed a class to freeze itself after initialization 🧊
The advice is: solve your own problem, then find more people like you.
The problem? You probably wouldn't pay $50/month to solve that problem, so people like you probably won't either.
The advice is: solve your own problem, then find more people like you.
The problem? You probably wouldn't pay $50/month to solve that problem, so people like you probably won't either.
People will just forget you. Quickly. You have to be very explicit to help them remember.
People will just forget you. Quickly. You have to be very explicit to help them remember.
Now you can send messages related to billing cycles, monthly check-ins, or annual reminders landing on a specific day.
Give it a try in your workflows.
Now you can send messages related to billing cycles, monthly check-ins, or annual reminders landing on a specific day.
Give it a try in your workflows.