7
6 Comments

10 published posts on the Gleebeam blog!

I started writing a blog immediately after launching Gleebeam in October. Now looking back at it, it looks like I've written around 1 post per week. Not a lot but probably not bad either, considering all the other marketing I've had to do to get any traffic to Gleebeam's site!

My aim with the blog has been to publish guides for different Gleebeam use-cases to see over time, which of the use-cases gather most attention. I don't have a target audience nailed for Gleebeam yet and the blog should provide one of the data points necessary for nailing it!

To celebrate, I've also finally created a Gleebeam Twitter account!

🎉 https://twitter.com/gleebeam

, Founder of Icon for Gleebeam
Gleebeam
on November 28, 2019
  1. 2

    Hey @viestursm! Writing consistently is itself a huge ask. Glad you're able to commit to that.

    Do you have a blogging strategy in place? Are you focusing only on use cases or planning to write general educational stuff as well? We're working on having a proper blogging strategy in place and are looking at what other startups are upto :)

    1. 1

      Hey, I can't say I have a formal strategy for blogging. I'm writing about things that are relevant to what I now see as the primary use-cases for Gleebeam. I do this, as I mentioned in the post, to gather data about what users are interested in, but also to provide guidance with setting the app up.

      That said, I have a task currently that says 'come up with a content strategy' so I will be thinking about it sometime soon. I will probably try to understand if I can figure out something to write about that's just interesting to my target audience, and not necessarily a tutorial for Gleebeam.

      1. 1

        Cool! That makes sense. Use-cases is a great way to find out what your target audience is looking for. Since we're only starting out with a proper content strategy, we're not sure use-cases are going to help us in terms of SEO and visibility. We're kind of stuck thinking about that.

        1. 1

          I think it also depends on the use cases themselves. It makes more sense to write about use-cases if they solve problems that are getting a lot of searches and might be interesting to writers elsewhere who are aggregating content.

          I don't have a lot of wisdom in the field so I'm afraid I can't give advice for getting unstuck, but my unprofessional opinion is that it's good to write regularly about different things relevant to what you do, share them around and see what's gaining traction. Once you have some experience with what works and what doesn't, you can go ahead and build a strategy on top of this data.

  2. 2

    Congrats. Writing is hard. Writing consistently even more so. Great job 🙌

    1. 1

      Thanks. I hope my writing skills and speed will grow the more I write, I just have to be persistent!

Trending on Indie Hackers
I spent $0 on marketing and got 1,200 website visitors - Here's my exact playbook User Avatar 41 comments Why Early-Stage Founders Should Consider Skipping Prior Art Searches for Their Patent Applications User Avatar 22 comments I built eSIMKitStore — helping travelers stay online with instant QR-based eSIMs 🌍 User Avatar 20 comments Codenhack Beta — Full Access + Referral User Avatar 20 comments Veo 3.1 vs Sora 2: AI Video Generation in 2025 🎬🤖 User Avatar 18 comments Day 6 - Slow days as a solo founder User Avatar 13 comments