This is my first attempt at a SaaS. This is also my first Django and Bootstrap project I've released into the wild.
My background/day-job is electrical engineering, but I've been involved in the programming/web-dev world for many years...though mostly as an advanced hobby. I typically shy away from front-end design work, but this was a solo project.
Probably a bit of both - it feels too excited. Podcasts tend not to be things you shake your fist in the air for - that's more winning the lottery territory.
Looks interesting! I'll be honest took me a little longer than you'd want to work out what the product was.
I know now that it is in the name! However I'm used to ignoring names to understand what a product does. Replacing the "connecting organisations with ears" tag line with something like "Access your podcast via the phone, and get more listeners" would be more clearer even if it's not as clever.
Great idea. On the pricing page, I wouldn't have a free plan, because you don't. Just a free trial (which is cool). What do people convert to after the free trial ends?
Hmm...interesting. Yea, I've been fumbling a bit with the pricing structure. I thought a subscription model would be easiest for users to understand, and would give them some assurance that they're not opening themselves up to large costs that could come from per-a-minute billing.
The idea is that you use the free trial to show The Approver of Funds this works, then convert to whatever tier you think you need. Upgrade and downgrade as needed based on how many minutes you need.
I'm new to using Stripe with subscriptions and was following the basic framework from a tutorial. I plan to revisit how I do subscriptions, but I'm not sure what that will look like yet. Thought?
It was important to me to make this an MVP and ship it and then iterate on it.
I'd probably either have a trial that converts to a paid plan after 14 days (unless they cancel) or a forever free plan that always allows Y minutes/month.
I'm always a fan of charging people up front, so I'd probably go with the former.
Oh interesting, I hadn't come across them in my research. I did find zenoradio.com (which used to be http://www.audionow.com/) and they have a Call-to-listen feature with a fixed number for each podcast. However, can't get a number right away, you have to complete a certain number of sessions before they'll assign you a number (https://intercom.help/zenotools/en/articles/1843279-how-can-...).
I've also seen a few church have their own "Dial a Podcast" feature for their own sermons (which is what this originally started out as, although that was done through our self-hosted FreePBX box).
My primary target audience is smaller churches with existing podcasts who want help to reach members who don't have internet access, or are less technology inclined (not a judgement, it's just what they're comfortable with). This generally tends to be older members, so that's who I designed it in mind for.
I think having a fixed phone number and code (versus Bullhorn's rotating number) is key because you can write it on a post-it note, give it to them, and then they can call it any time. I mean, it doesn't get much simpler than, "Grandma, call this number and when the person starts talking press x-x-x-x-x-x".
Also having it be simple for churches to setup and administer is important. I've gotten several calls from other churches this year about how we do our online streaming services. Having this be a low-cost fire-and-forget was important.
12 comments
[ 0.18 ms ] story [ 187 ms ] thread-- 123456 (Messiah Lutheran Church)
-- 391587 (Make Me Smart)
This is my first attempt at a SaaS. This is also my first Django and Bootstrap project I've released into the wild.
My background/day-job is electrical engineering, but I've been involved in the programming/web-dev world for many years...though mostly as an advanced hobby. I typically shy away from front-end design work, but this was a solo project.
Would love any feedback, thoughts, etc!
That stock photo is terrible though.
I know now that it is in the name! However I'm used to ignoring names to understand what a product does. Replacing the "connecting organisations with ears" tag line with something like "Access your podcast via the phone, and get more listeners" would be more clearer even if it's not as clever.
The idea is that you use the free trial to show The Approver of Funds this works, then convert to whatever tier you think you need. Upgrade and downgrade as needed based on how many minutes you need.
I'm new to using Stripe with subscriptions and was following the basic framework from a tutorial. I plan to revisit how I do subscriptions, but I'm not sure what that will look like yet. Thought?
It was important to me to make this an MVP and ship it and then iterate on it.
I'm always a fan of charging people up front, so I'd probably go with the former.
I've also seen a few church have their own "Dial a Podcast" feature for their own sermons (which is what this originally started out as, although that was done through our self-hosted FreePBX box).
My primary target audience is smaller churches with existing podcasts who want help to reach members who don't have internet access, or are less technology inclined (not a judgement, it's just what they're comfortable with). This generally tends to be older members, so that's who I designed it in mind for.
I think having a fixed phone number and code (versus Bullhorn's rotating number) is key because you can write it on a post-it note, give it to them, and then they can call it any time. I mean, it doesn't get much simpler than, "Grandma, call this number and when the person starts talking press x-x-x-x-x-x".
Also having it be simple for churches to setup and administer is important. I've gotten several calls from other churches this year about how we do our online streaming services. Having this be a low-cost fire-and-forget was important.