What went wrong with my product?

First just want to say that you have a really great designed product here that looks impressive! Congratulations, that is a huge accomplishment.

Here are some of my initial thoughts:

• I'm not real clear who this is targeted towards. I would imagine anyone who has the ability to write functions for the cloud probably already has their systems in place and wouldn't really need this.
• I'm guessing a lot of the initial enthusiastic feedback was from two groups of people:
  • Group 1 is developers who probably already have systems in place. They were probably giving feedback thinking "I don't really need this, but this is really cool."
  • Group 2 is non-developers who don't understand AWS and can't write functions. They were probably giving feedback thinking "I don't completely understand this and couldn't use it myself, but this is really cool."
• Tiny Function does not have any pricing listed. It has a Pricing section but all it basically says is - I'm going to charge for this at some point. This gives me the impression that it is an "alpha" version of the product and could disappear at any time. There are tons of products that are in alpha and not charging that disappear everyday (you can just look back through IH projects). I would imagine most people don't want to spend time testing out a project that could disappear tomorrow.

All that being said, you have what looks to be a really great product here. Here are the action steps I would recommend:

1. Start charging. Keep the price low if you want but list actual pricing. Charging makes it a real product. Until there is a price, it is an experiment that doesn't inspire confidence.
2. Find users who need the service. I would encourage reaching out one-on-one (after you have pricing in place) to start getting feedback from users - maybe offer them a free trial or help them set up some examples of ways they can use it.
3. I would imagine most developers who are familiar with AWS don't really need this. It may be a nice to have but probably not worth money to spend on. My recommendation would be to focus on the No-Code community. They may understand the benefits of AWS but can't really make use of it themselves. I would hand-hold No-Code users who couldn't set up AWS themselves, and help them solve specific problems in their workflow. Maybe check out No-Code forums/reddit and start helping people - when your product makes sense, you could mention it in conversations.
4. Get rid of all the "Coming soon" features and text. It makes the product look incomplete and still in development. You want to look like a completed and fully working app. You want it to look professional (from a design aspect it looks very professional and like a complete project). However, the copy seems to indicate the opposite ("Coming soon", pricing not clearly defined). The copy makes it seem like an experiment that you are working on from time to time.

Hope that helps! I think you've got a really great product here from what I'm seeing. You just need to focus on getting paid users one-by-one.

I really like your landing page (especially that you can instantly test the product) and I was pretty impressed that it worked so easily.

That being said, as a developer, this got me excited at first, but when I thought of a use-case I couldn't find any. I didn't even consider pricing, but I think for me, it's easier to just launch a Node.js server on DigitalOcean and paste the JS files directly there, where I have a lot more control of what I can do and not do.

So, personally, I think the product would just save me a few seconds it takes to set up a new Node.js server but come at the cost of using another service, sending my data to a 3rd party, having unpredictable pricing, being limited to what I can run in my cloud functions, etc.

I don't have a use for this service but I'll say that any service not listing pricing is not worth my time.

Safari 15.4 shows a blank page... Same on iOS iPhone...

I took a glance at it. From what I can make out there is currently no way to persist data between calls and you can't write to any file storage. How about authentication- once a function is deployed can't anyone just call it from anywhere?

I like the pricing model where you pay into a wallet and draw down based on usage. This removes the risk of adopting it, plus you can a free tier.

I also can't see what use cases would be. Maybe you want to include some use cases where people would want to pay to use your service?

I dont see anything wrong./..

The site looks great and the functionality makes sense.

It's CodePen for serverless functions, but where is all the independent contributor content applying it in their workflows?

Where is this best used, I could see this being great for educational content.

While rebuilding and establishing a better product is essential, the other side of the coin is making sure that your product is being talked about, if I would have never read this post, I would have never heard of it.

I live in DevRel world at the moment, and I interact with a ton of educators.

This should be something that could be regularly used for example, and then the paid user use cases will surface over time.

I would focus on IC traction and getting it embedded into the content.

It might not drive immediate dollars, but it will drive ideas and advocates, which will result in morphing your product into a sustainable product over time.

Congrats on being 3rd on Product Hunt, that's huge!

Have a few questions for you:

• How many PH visitors ended up converting to being users? Sometimes there is a big difference in traffic and actual converting users, if there was, that might be a good clue (key features missing causing lack of consistent users?)
• What marketing have you tried since?
• What was your revenue before hiring devs?

I highly recommend adding some clear use cases to your website to help customers understand in what cases paying for a simple cloud function is clearly better than doing it directly via AWS/GCP/etc. I am a software developer myself, and I personally feel more worried about potential limitations down the road and I am already comfortable enough with AWS and GCP.