3 ms·

Your product puts an emphasis on user friendliness. If your target user has not deployed to cloud before, you’ll need to show clearly just how much easier/clear

Your product puts an emphasis on user friendliness. If your target user has not deployed to cloud before, you’ll need to show clearly just how much easier/clearer/more manageable/$improvement having Revolv is. For prospective users who have cloud experience, they have already developed workarounds and/or gripes with tooling and management. Consider adding quotes from your user research to illustrate the benefits ( plus what you already mentioned as in the pipeline). How fast can you digest the blog content into the current product copy? Having the info easily available will be better for conversion. Lastly most companies prefer to known their expenditures ahead of time, and respond strongly to less uncertainty. You’ll get more traction with a pricing scheme that is independent of the variable $ cloud charges.

jeremylevy 6y ago
Wow! Thanks you very much for this insightful comment. It's very interesting. Honestly, I've created Revolv for my own needs, as a "full-stack" developer. I've often found myself wanting something like this: "A Terraform with Heroku-like features". We've planned to target users that have low to medium cloud experience, so we need to show clearly how cloud architecture creation is easier by using Revolv. The pricing is something we've been thinking about for a while. Currently, I don't have enough data to make a decision. It's very difficult because it's not something that have been done yet.
- ignoramous 6y ago
  > "A Terraform with Heroku-like features". I think, AWS Amplify (Firebase, I guess, in GCP's case?) gets a low/medium cloud experience engineer almost all the way there, and they're continually improving their offering by integrating with multiple AWS services but there's too much magic and if there's a need to customize anything whatsoever, or if anything breaks, then it quickly becomes a nightmare to deal with, but that's a feature not a bug due to prevalence of the aforementioned "magic". I guess, currently, their support for other AWS services isn't broad enough and mostly geared towards Mobile and Web, so may be they're not squarely competing with your offering, yet.

jeremylevy 6y ago

Wow! Thanks you very much for this insightful comment. It's very interesting. Honestly, I've created Revolv for my own needs, as a "full-stack" developer. I've often found myself wanting something like this: "A Terraform with Heroku-like features". We've planned to target users that have low to medium cloud experience, so we need to show clearly how cloud architecture creation is easier by using Revolv. The pricing is something we've been thinking about for a while. Currently, I don't have enough data to make a decision. It's very difficult because it's not something that have been done yet.

ignoramous 6y ago
> "A Terraform with Heroku-like features". I think, AWS Amplify (Firebase, I guess, in GCP's case?) gets a low/medium cloud experience engineer almost all the way there, and they're continually improving their offering by integrating with multiple AWS services but there's too much magic and if there's a need to customize anything whatsoever, or if anything breaks, then it quickly becomes a nightmare to deal with, but that's a feature not a bug due to prevalence of the aforementioned "magic". I guess, currently, their support for other AWS services isn't broad enough and mostly geared towards Mobile and Web, so may be they're not squarely competing with your offering, yet.