4
4 Comments

Feedback on my cost savings tools available on the AWS marketplace

I recently released a couple of cloud cost optimization tools through the AWS marketplace.

I'd really appreciate your honest feedback about them regarding the clarity of the copy, pricing, whether they're appealing enough, etc.

Also if you know someone who might benefit from them feel free to share the links.

Thanks in advance!

https://aws.amazon.com/marketplace/pp/prodview-6uj4pruhgmun6

https://aws.amazon.com/marketplace/pp/prodview-ryzl67mmq3ghk

on September 5, 2021
  1. 1

    I use spots for most of my aws workloads. Not sure why I would need a tool for that. Maybe my set up is not sophisticated enough. I didn't get how your tool would help me.

    What you wrote there is more like a white paper. You are trying to educate the customer and go to a great level of detail. Can you cut it down by 90% and just tell me what I need to know:

    • why I need it
    • how much it will save me
    • how it works
    • what's involved in the set up

    One sentence per bullet point.

    Post the current version on Medium, Dev.To or wherever you can post it. It's actually not bad - just too much for Marketplace. Have a look at https://aws.amazon.com/marketplace/pp/prodview-a5pysxaz4x4gg

    "This heavily depends on your configuration." - saying "it depends" is a sure way to tick off many readers. Somehow we don't like that kind of answer. I didn't get the EBS optimiser at all. How do you know how much space I need? I have a multi-node ElasticSearch set up. It has 3 times the storage I need, but I do need that empty space to re-index or reconfigure it. Would your tool help me? Again, there was so much text to read I skimmed over and moved on.

    The ideas are solid. I can see a need for myself and others. Consider also building a tool for finding unused resources. E.g IAM accounts, random EBS snapshots, old Lambdas, etc. Give me that list with the total how much I'm wasting on it and I'd happily give you a share of my savings :)

    Hey, I'd be very interested in your feedback to my https://github.com/stackmuncher/stm_app

    1. 1

      Thanks for the thoughtful feedback, I really appreciate it.

      I agree I have a lot of text, I had much less/to the point text but then saw people who had no idea about the concepts so that's why I added some background information.

      I then struggled fitting everything I wanted to say within the 5000 characters limit :-)
      But this is very fair feedback, I'll cut it shorter. Less is almost always more :-)

      To explain a bit, AutoSpotting is designed especially for companies who have a large footprint, don't currently run Spot and would like an easy way to adopt it without having to convince everyone to update their configuration. You just install it and it takes over the existing ASGs and converts them to Spot without launch configuration/template changes, just need to tag the groups with spot-enabled=true or make it select ASGs based on some tags you already use. I'll probably just add this at the top and keep some basic explanations for people who have no idea what all this means.

      EBS Optimizer doesn't look inside the volumes, all it does is changing the EBS volume type and sometimes set some provisioned IOPS/Throughput to match the performance of the original volume.

      There are tons of instances still using GP2 volume types which could use GP3 for up to 20% savings on the volume costs (biggest offender is EMR, but also tons of instances launch from GP2 AMIs). Also, there are cases where people use IO1 and IO2 volumes with small IOPS, that could be also replaced by GP3 for up to 85% savings. The tool just switches the volume type to the cheapest option, keeping the performance the same.

      Regarding feedback to your tool, I like the idea, but I'd like to se an easy/automated way to query a given public github profile. For example https://stackmuncher.com/<gh-user> currently just returns a 404, I would expect it to automatically be populated with data from the public github repos of that user and added to the site, much like https://pkg.go.dev/github.com/namsral/flag does for golang packages.

      1. 1

        Chris, I have to take back some of what I said in my previous comment. I didn't realise your project is open source and is quite popular. Good on you :)

        A few random ideas ...

        1. Have one home for the project. If you are not actively maintaining the website, make your GitHub page the canonical home.
        2. Make it prominent in your commercial offering that it's FOSS, link to GitHub.
        3. Make it prominent on your GitHub page that there is a commercial offering, link to it.
        4. Consider 2-tier pricing: $10 a month for some basic features and >$100 for some advanced features with support , etc, etc. You don't need to hide the features behind closed source - just don't enable them in that container.
        5. Can you get some testimonials from contributors?
        6. Re-write your ReadMe as a marketing copy.

        If you can't find a marketer to re-write your pages I'm happy to help you with a draft. Ping me directly if you want to know the rationale behind my 1-6 suggestions.

        I reckon you are onto something there.
        Good luck! :)

        1. 1

          Thanks for the kind words and for offering to help, I'm actually looking for a partner, see this other IH post of mine for more details on that and let me know if this sounds interesting to you https://www.indiehackers.com/post/looking-for-a-sales-marketing-copywriter-partner-b4c61cb574

          1. For a lot of time I had a basic website at autospotting.io where I can run a mailing list, show a few testimonials and a customer-facing FAQ. I recently started to migrate some of my content to cloudutil.io as a home for both my projects, instead of creating a website for each of them, as I may launch more tools in this space going forward.
          2. I was reluctant to do that as it would probably cause some people to just use the OSS version and impact my revenue.
          3. I'm pointing to the Marketplace but I should probably make it more prominent.
          4. I've been also offering multiple such tiers on Patreon and Github Sponsors but noticed that the vast majority of the people opted to a single tier, so I tried to simplify my offerings by just charging a flat percentage of the savings, which makes it very inexpensive to get started and grows with the usage.
          5. I had some on autospotting.io, but I can ask for more.
          6. I'm not sure about how that would look like, and as I said I'm actually looking for collaborators on that side of things. My superpower if I may call it like this is coming up with ideas for such tools and building them, but I'm honestly struggling with the marketing/sales side of things so any help there would be greatly appreciated.