Gator

Smart scheduled delivery for your Slack messages

Visit Website
July 30, 2020 Reached $1k in MRR

Nine months after launch, Gator has cracked $1k in MRR. Here's a peek at my Stripe Billing dashboard:

Gator revenue

Overall I'm really pleased - it was never a certainty that this night-and-weekends SaaS business would get this far. Looking back on the past nine months, here are a few decisions I'm happy about and some I'd do differently:

✅ Keeping the product tight and reliable - I've aspired for this to be a tool that "just works", and I've gotten feedback from my superusers that they appreciate that. I've gotta believe that's a big part of why some of them became paying customers.
✅ Paying for the right services - Running on Heroku isn't the cheapest option (approx. $150 a month) but I haven't regretted it for an instant. Same with building the marketing site on Webflow - I could've taken the time to beef up my frontend skills, but that wasn't the right path. Even using Stripe Atlas to set up my LLC felt worth it.
✅ Pricing higher than competitors and offering the annual plan - I have about 29 paid Slack workspaces now, but three of those are from the same person who bought the annual plan three times over in a single month. That $1,500 in revenue felt like a pleasant surprise.
✅ Building the dashboard - I used Google Data Studio to build a dashboard showing my non-revenue growth stats for Gator. It's set to email me a copy every morning, which is a great way to start the day.

❌ Picking a generic brand name - When I launched, Gator was called "Later". I got enough Twitter buzz on launch day to receive a trademark cease and desist letter from another company that goes by "Later." Rebranding took a lot of time and, truthfully, was a demoralizing speed bump to hit two months after launch
❌ Still haven't found a scalable marketing tactic - About 2-5 new Slack workspaces install Gator every day, a number that could be much higher. I did a few months of Google Ads, but that didn't move the needle and just wasted $400 per month.
❌ No Enterprise Plan customers - A few months ago I finished implementing a few smaller features that I bundled in an "Enterprise Plan." But I haven't had any takers yet (though one customer is serious about licensing Gator to run on-prem)

Looking forward, I want to focus on marketing Gator and accelerating adoption. My hunch is a content marketing strategy focused on remote work topics could be promising. And though I don't have much free time to write myself, I've got enough revenue to pay a ghostwriter to churn out some blog posts for me.

I'd love folks' advice on what marketing tactics might be fruitful here. Also happy to answer any questions about the journey so far. This community has been super helpful for me and I'd love to give back.

12 Comments

  1. 2

    Congrats Andrew! Thanks for sharing! All the night and weekend work is paying off 🎉

  2. 2

    Nice, congratulations!

  3. 2

    Nice work Andrew, thank you for the insights!

  4. 2

    Congrats Andrew!

  5. 2

    Congrats on your milestone! 🎉

  6. 2

    Congrats Andrew! Thank you for sharing your learnings, I suppose with every single word name there is always some risk of some other company defending it. I hope that's a rare thing to happen

  7. 2

    V. Significant milestone, congrats. You say that you haven't found scalable marketing tactic - what has got you this far? Cold outreach?

    1. 2

      Thanks!

      It’s been hard to attribute installs because the final step is through Slack’s site, but I’m pretty sure most people are finding Gator by either searching for “schedule” in the Slack App Directory or because I snagged a spot in the App Directory’s “New and Noteworthy” section: https://slack.com/apps/category/At0EFT67V3-new-noteworthy

      1. 2

        Quick idea: Embed an easter egg of some sort, which is how you get to DM the user. And in context of that attention, ask them how they discovered you.

  8. 2

    Impressive! Congrats Andrew! 👏

  9. 1

    Reading the post I was thinking about HostGator :D
    In fact, HostGator and Gator are different brand names, but personally, I was a little bit confused.

    Anyway, congrats with milestone 😎

  10. 1

    This comment was deleted 6 years ago

    1. 1

      I actually started with a three month free trial and then reduced it down to six.

      I wanted to structure my trial in a way similar to how Slack does - giving enough time for usage to proliferate through an organization, increasing the chance that one user is willing to upgrade for everybody.

      A couple months ago I looked at my usage stats and saw that six weeks was the magic number - if a Slack team hadn’t upgraded after six weeks, they were unlikely to ever do it. And waiting longer for revenue isn’t a problem for me - Gator’s cheap to operate and I’m not trying to draw a salary from it.

      1. 1

        This comment was deleted 6 years ago

October 28, 2019 Launch day: 250 trial users, first paying customer

Last Wednesday Later was featured in the "New and noteworthy" section of the Slack App Directory. I took the morning off from my day job to try and capitalize on that placement and "launch" Later.

I knew that whether I got a pop on launch day or not, this is just the beginning of building the marketing machine for this app. But I was pleasantly surprised!

On Tuesday night Later was installed in 15 Slack teams, mostly from emails to friends and a little effort on Twitter. My goal for Wednesday was to reach 50 Slack teams - the thinking there being that if 2% of them converted at the end of their trial, I'd have one paying customer 😄

By that measure, launch day was great.

I ended the day with Later installed in over 100 Slack teams. It's now up to 150, with 250 individual users between them.

I was also shocked to get my first paying customer that day too, signing up for my $50 per month "Startup" plan. That was a real surprise because there's no restriction during the free trial and no serious nudge to upgrade until you're close to the end of the trial.

Reflecting a little bit on the day, here's how I'd sum it up:

What went well

  • Launching on Twitter with a tweet from my personal account: My personal following overlaps pretty well to the types of folks who might find this interesting. That's what got the whole ball rolling.
  • Endorsements from my early adopters and beta testers: I've been working on Later since April. There are a handful of people who have been happily using it weekly, and they showed up on Twitter to help spread the word. I'm extremely grateful.
  • I learned a ton about how people perceive this product: I'm still not exactly sure how I should position this tool (is it "the essential Slack app for remote teams" or just "intelligent scheduled send for Slack"?) but I've got a lot more data now than I did a week ago. There's a lot I can go on now for refining the next phase of my marketing.

What I'll do differently next time

  • Wasting time on some long shots: I posted on ProductHunt and Hacker News, even knowing it was a long shot, and got basically zero upvotes in each. I should have just skipped them and accepted that I wasn't ready for sites like that yet.
  • Pricing wasn't easy to find on my website: My hypothesis with Later is that it needs a lengthy, three-month free trial to prove its value to enough people in a Slack team. Because I don't require a credit card up front and because the first person to install Later in a Slack team might not be the person who sees the most value in it three months down the line, I didn't make pricing information easy to find on my site. That was a mistake: a few people explicitly asked about it, and implied they considered it reckless to trial Later without knowing how much they might have to pay eventually. I fixed that halfway through the day. Still, a good lesson learned.
  • A few small bugs: Overall the service has stood up really well this week, in part because I'm not skimping on Heroku resources. But launch day exposed a few bugs: Later broke when people would send messages to guest Slack users (I've never used this feature) or when testing Later in a DM with Slackbot (should have expected this one). More through testing might have helped me catch some of these.

Overall, though, I couldn't be happier with this week. After almost a decade of working as a professional software developer, I've never had a paying customer for a side project — and that feels pretty good. This business' greatest (and quite likely 😅) threat is that Slack realizes this is a missing feature and builds it in a sprint. But at least I'll always be able to say I got this far.

One last fun story: a few emails came in to the help@slashlater.com address throughout the day. One was someone asking about how I keep messages secure (short answer: encrypt them as rest, erase them as soon as they're delivered). After exchanging a few emails he just said "Want to call me?" and gave his phone number. I gave him a call and we talked for 15 minutes. They're a remote startup in the healthcare space and they were excited about using Later but they're wary of Slack apps because of all the personal health information in their conversations. After talking him through how I store and erase messages, he said he was satisfied and decided to turn on Later for everyone at the company to use.

Didn't expect to take a sales call on day 1 😂

14 Comments

  1. 6

    Nice product. Well done on getting a paid customer :)

    Do you think you're leaving money on the table with such a high starting price?

    • Why such a long trial period?
    • Might be good to add an FAQ to explain security etc
    • PH launches require your full effort and a few days planning
    • Get testimonials from your beta users
    • Get rid of coming soon for enterprise and change it to contact us
    • Get rid of home and help from the navbar :)

    Some quick questions for you

    • Did you look at templates?
    • Did you look at landing page builders?
    1. 1

      Hi! I appreciate you taking a peeking at Later and dropping some thoughtful feedback. Most of that seems like non-controversial good advice :D

      On the long trial period: it's possible three months is too long. The real answer is I'll have enough usage data soon to see how many users authorize Later within a Slack workspace in the first two weeks vs. 30 days vs. 60 days, etc.

      One factor I know will slow down some trials, though, is Slack administrators being cautious about turning on Slack new apps for all users in a workspace. Maybe I'm over-optimizing for customers at larger companies, but I'd hate for a Later trial period to end before more than a couple users see its value.

      But again, it wouldn't take much data to prove that hunch wrong. I'll do a "30 days in" milestone update and include some data to share the answer.

      As for templates and landing pages: I did buy my template off Themeforest. I thought about a builder (web design is obviously not my strength 😅) but I knew I needed a custom page to run Stripe Checkout on for the upgrade transaction - I didn't think a landing page builder would let me add a custom page like that too.

      1. 2

        The landing page is nice and clean :) You could probably have used a page builder (depends on which one you chose), but not having used one impacts your speed in a positive way. The one suggestion I have is to move you .back-to-top icon (perhaps a bit higher) because the Intercom chat icon overlaps with it and makes for a confusing little corner.

        Congrats on the first paying customer!

  2. 2

    Really cool!

  3. 2

    That's a great story, thanks for sharing !

  4. 2

    Good job Andrew!

    "That was a real surprise because there's no restriction during the free trial and no serious nudge to upgrade until you're close to the end of the trial". My suggestion is to add a discount for people who upgrade early. Maybe a discount that decreases in amount with time, to leverage fomo. Send it to people who are still using it after 2-3 days.

    God job again ;)

    1. 1

      Genius! Added to the backlog - thank you!

  5. 2

    Congrats on getting to market!

  6. 2

    Congrats on the successful launch and thanks for the write up! It's always cool and encouraging to hear stories like this :)

    Did you do any research/validation for this idea? Or is this a "scratching your own itch" kind of product?

    1. 2

      This was very much a "scratch my own itch" project, since I lead a remote team at my day job.

      And I definitely feel that the most likely end to this business is Slack building this feature themselves in a single sprint. So I'd never bet my career on this idea, but I'm having a lot of fun building and growing this business so far :D

      1. 1

        Awesome! Fun is definitely important :)

  7. 2

    Little tiny feedback, and this is totally preferential;

    "The essential Slack app for remote teams." doesn't say much when you see this. Maybe the name implies what the slack app is all about, but this hero text seems a little cheesy to me, its like saying "This slack app is good".

    I would have expected the hero text to tell me that later is a fast scheduling app in slack.

    On the other side, I think the landing page tells what the app does, maybe If I were building this product I would do some AB testings with the hero text.

    Don't know about others, but when I'm in the buying mode, hero text is very important for me.

    Also I started giving feedback, but I hope it is ok. I love the app and easy to use command interface!

    1. 1

      Feedback is what I was hoping for from this community! Thank you!

      And yeah, can you tell I've struggled with how to position this app? "Scheduled send for Slack" is largely accurate but doesn't hint at the value that feature unlocks, especially for a remote team. But there's not much to Later besides that core feature, so positioning it as something more has felt like a stretch 🤔

  8. 1

    Great job! Great story!

    • trial for max 30 days.
    • build onboarding so users get enough value at 14 days, so subscribing at day 30 is a no brainer
October 23, 2019 Featured in Slack's "New and Noteworthy" apps

Later got listed today in the Slack App Directory's "New and noteworthy" apps.

I'm capitalizing on that momentum to essentially make today "launch day" for Later, starting with some launch content on Twitter (https://twitter.com/slashlater).

I'd love some ideas on other ways I can get the word out about this app. I suspect Slack's App Directory will never be a huge acquisition channel (I think people mostly go there to find apps for services they already use outside of Slack). My hunch right now is that focusing my marketing on remote teams is my best bet, even though Later's useful to non-remote teams too.

6 Comments

  1. 2

    Congrats on the new and noteworthy placement!

    Could you use this as a prompt to get some user/customer examples and case studies of how the product has helped them?

    1. 1

      I'm hoping so! Getting some logos on the site is definitely top of mind.

      I want to watch my usage data over the next few weeks. I'm really interested in figuring out how quickly Later can proliferate through a Slack team. It should be easy to spot the workspaces that understand and value the service, and then follow up with them.

      1. 2

        It also seems like the kind of theme you could get on some podcasts to talk about: slack team etiquette, the problems with being always available, etc etc. If you have some articles to show off how you think about the problem, you can focus on the problem more than the product in a podcast interview. I think that'd be a pretty easy sell into any number of shows focused on remote work!

        1. 1

          Ooh - I like that idea. And meshes well with my personal experience leading a remote team these past few years. I'd definitely have a few nuggets of wisdom to share beyond just promoting Later

  2. 2

    Maybe don't feel the pressure of turning into a (big) launch. The situation reminds me of this post from @alexhillman - https://stackingthebricks.com/how-often-to-launch/

    1. 1

      Sound advice! And I agree - this "launch" to me is mostly about taking advantage of that temporary placement in Slack's App Directory and a quiet Wednesday at my day job.

      I've definitely made the mistake with past projects of putting too much pressure on a single day. No matter what happens today, this will feel like just the beginning :D

October 11, 2019 Live in the Slack App Directory!

After a couple weeks of revisions, Later has passed Slack's review process and is now live in the Slack App Directory:

https://slack.com/apps/ANPGHD2F8-later

And so Later is officially open for business. But my hunch is the Slack App Directory won't drive much of an audience to Later unless I get included in their "popular" or "new and noteworthy" lists. So it's time to get busy laying the marketing plan...

2 Comments

  1. 1

    Congrats!
    How do you handle payment? Is it through slack app dir ?

    1. 1

      Thank you!

      I handle payments myself through Stripe. It's all wired up, though my theory is that this app needs a long free trial for Later to spread through Slack teams and make its value clear. So I'm starting with a three month free trial, which means folks won't be entering payment info for a while yet.

      And based on my experience I'm not sure Slack's App Directory would ever want to do payments. My impression is that their focus is more on making sure apps exist for other SaaS products their customers already pay for (e.g. Zendesk, JIRA, Salesforce) than apps which purely extend Slack, like mine.

About

I built Gator to solve a problem I've had every day since joining a remote team: I want to keep our conversations in Slack, but don't want to intrude on my coworkers after hours when they're in different time zones.