4 ms·

I changed the heading to: AI-Powered API Performance Testing No-Code, Self-Learning! Since AI learns how to interact with the API and validates every path in

I changed the heading to: AI-Powered API Performance Testing No-Code, Self-Learning! Since AI learns how to interact with the API and validates every path in it. Is the new sub-heading any better than the previous one? Also, shortened all the other sections. Thank you so much for the feedback!

YossarianFrPrez 3y ago
You are on the right track, but you haven't reached your destination, so to speak. "Value" isn't a property inherent to the copy on your website (or any text, for that matter), it's a property of the relationship between the copy and the reader. One way in which people recognize value is when they gently realize that they are (at least a little bit) wrong. What are people wrong about re: API testing? You currently have: > AI-Powered API Performance Testing > No-Code, Self-Learning! None of this implies that I have a problem. And this is because if I am building a website, I already test my API.* So it doesn't matter that your product is automatic, no-code, and self-learning. Instead, you have to point out how my testing of my API is incomplete. *Or so I may think. I might be convinced that I am testing my API even doing something as simple as '> rake routes'... But users will likely respond to the following value propositions: > Most people don't even know they aren't testing their APIs properly... > Doing it right is actually quite tricky, due to... (e.g. effort, time, money) > By relying on unit tests, engineers miss the forest for the trees... > For example... ^^ Build this out first, and a snappy way of wording it, as well as a heading / tagline will follow. The more you understand your true audience, the more you can "tune" this copy to specific issues they might have in their API test coverage. If I build a Rails site in a month by myself, am I likely to need your product? What about if I'm at the scale of Shopify? Or is your intended audience somewhere in between?
- intesars 3y ago
  I used to have this line earlier. I changed it after criticism from the other users. I agree that your suggestions is valid to have a reason as well. I'll add this line back. "According to Google poor API performance leads to negative user experience and high-churn. Deliver High-Performance APIs with our Self-Learning and No-Code platform."
  - YossarianFrPrez 3y ago
    I think you are better off with only the second sentence. The first sentence is something your users likely already intuit.
    - intesars 3y ago
      thanks

YossarianFrPrez 3y ago

You are on the right track, but you haven't reached your destination, so to speak. "Value" isn't a property inherent to the copy on your website (or any text, for that matter), it's a property of the relationship between the copy and the reader. One way in which people recognize value is when they gently realize that they are (at least a little bit) wrong. What are people wrong about re: API testing? You currently have: > AI-Powered API Performance Testing > No-Code, Self-Learning! None of this implies that I have a problem. And this is because if I am building a website, I already test my API.* So it doesn't matter that your product is automatic, no-code, and self-learning. Instead, you have to point out how my testing of my API is incomplete. *Or so I may think. I might be convinced that I am testing my API even doing something as simple as '> rake routes'... But users will likely respond to the following value propositions: > Most people don't even know they aren't testing their APIs properly... > Doing it right is actually quite tricky, due to... (e.g. effort, time, money) > By relying on unit tests, engineers miss the forest for the trees... > For example... ^^ Build this out first, and a snappy way of wording it, as well as a heading / tagline will follow. The more you understand your true audience, the more you can "tune" this copy to specific issues they might have in their API test coverage. If I build a Rails site in a month by myself, am I likely to need your product? What about if I'm at the scale of Shopify? Or is your intended audience somewhere in between?

intesars 3y ago
I used to have this line earlier. I changed it after criticism from the other users. I agree that your suggestions is valid to have a reason as well. I'll add this line back. "According to Google poor API performance leads to negative user experience and high-churn. Deliver High-Performance APIs with our Self-Learning and No-Code platform."
- YossarianFrPrez 3y ago
  I think you are better off with only the second sentence. The first sentence is something your users likely already intuit.
  - intesars 3y ago
    thanks