9
23 Comments

Launched early access page. Looking for feedback.

Hi all,

Just launched an early landing page to test the market and collect initial feedback about the product.

Problem statement is listed in previuos post here. However, you can just open the page and most of the crucial info is there.

What do you think? Do you know what the product is about? Is the page clear?

Thanks everyone!

on May 22, 2021
  1. 6

    Hey.. I like the overall design of the page. There's a visual hierarchy that moves me from the title to subtitle..

    but there is a lot of text up front. If I'm honest, I've needed to look at the whole page to figure out what the problem really is you're addressing.. it could be much clearer.

    I'm short on time so apologies if some things come across a little bluntly. Please take all this feedback as its intended - with great respect for the work you've done:)

    I'll try to tell you what I think you're saying in the titles..

    Title: Re-Shape Any No-Code API. With No Code.
    Subtitle: No-code tool APIs often don't connect out-of-the-box. Use Reshape on any no-code API data - automate, transform, clean and wrangle in minutes.

    Here's where I think the rest of the page is missing the mark slightly:

    • the transformations are at the end, but should be the second or third thing I want to see.
    • your first image has a grammar mistake - "so can I" instead of "so I can"
    • the alignment of the "Show me an API" buttons on the left is all over the place. People think that this makes the image more dynamic or interesting, but actually (IMO) it would visually convey the brand and product better to either show the interface or tidy up the alignment of the webflow-->Zapier images.
    • the before and after is underwhelming. This seems like an opportunity to reinforce the transformations that can be done and actually show them.
    • "here's how this tool works" I'd change to "Here's how Reshape works". At this point on the page I've forgotten what your product is called unless you keep reminding me.
    • "select one of our transforms". The word "our" sticks out here. Maybe try "Transform Anything" as the header there and actually list the transforms underneath. Link this to the image I've just seen above - you showed me the tool can add " " around a string and now you haven't actually told me what any of the transformations are. Change the image and then you can connect his section to that.
    • Real time transformations! Why didn't you say so sooner - that seems like a nice feature. Add the word real-time into your sub header maybe? A gif / animation here would be nice to really see how nice it is to have as a feature

    last couple of things users might be thinking [and what you could do to address it]:

    • What apps does this fit between? [show all the no-code app logos you integrate with or plan to integrate with]
    • this talks to zapier but doesn't this do a similar thing? [ you need to position yourself in the market more clearly against zapier, integromat, automate.io. The users you are talking to are probably not that technical if they need a no-code data transformation tool (not enough to code python data transformation scripts anyway). Help them understand where you fit in their workflow]
    • the "we're secure" explains way too much for me. What standards and things that I as a user have heard of do you do? [An ISO number.. some badges I might recognize that make me feel safer. Show me, don't tell me. Are your users going to know what Laravel is or why that matters to security? I don't get how this is the same customer segment that wants a no-code API data wrangling tool. Just tell me "We use the most secure encryption method on the planet" or whatever is accurate.]
    1. 2

      I especially second the recommendation to show all the logos of the folks you can integrate with. You only have room to show a narrow case or two on the main page but bomb me with logos so you can spur my imagination - then I will think past your examples to MY SPECIFIC PROBLEMS or at least in that direction.

    2. 1

      Absolutely kickass respone @typeofgraphic. Thank you very much. Now that we see that this thing has potential. Time to update the landing page to a v2 and make it more cohesive. Thanks again for your detailed and honest feedback. Means a lot.

      1. 1

        You're welcome, I'm glad something in there is helpful. I'll keep an eye out for your next update, maybe you could reply to this post to let us all know? I for one would like to see how things change :)

  2. 4

    100%

    If you can turn any api endpoint into https://supabase.io/ format you'll have a winner.

    • Airtable
    • Google Sheets
    • Headless CMS's
    • Notion
    • Coda

    Are some examples

    1. 1

      Yes please!:)

    2. 1

      Thanks man! I will pass this on to my colleague.

  3. 3

    Hey @arthurleonov! This is interesting. But what is the lifecycle for this? In other words you seem to explain everything from the starting point of an "API response" all the way to passing the data to Zapier (through your forthcoming ReshapeAPI Zapier integration I assume) or through an outgoing webhook:

    Pass it the response along to Zapier or using your own web-hook

    That's all clear, but what's not clear is how you are getting this "API response" that you keep referring to in the first place. What makes ReshapeAPI decide to make this request? What triggers it all?

    The demo (e.g. "from Webflow show New Order") seems to imply this all gets kicked off with a webhook (e.g. Webflow's ecomm_new_order webhook trigger) I would just say that the tool "transforms data passed into it by webhooks" or something similar vs. "shape and mold your API responses". By definition incoming webhooks are called into with requests, data is not passed in as a "response".

    Or if Reshape stands up a new API to use in place of the "reshaped" API (and this new API is a proxy to the original) then I'd say that (but that doesn't seem to make as much sense with the rest of what you explain).

    Also I would remove all references to "your API". If I have an API ("my API" to me, "your API" when talking to me) I'm sure I could just reshape it myself as me or my team developed it. You seem to be referring to third party APIs (not under the customer/user's control) so you should clarify this by removing every instance of "your" when referring to the API to be reshaped.

    Hope this helps.

    1. 1

      Very fair point. I will work on removing the API part as it is not exactly correct. Thanks @mvpcto

  4. 3

    Hi Arturas

    I would add again the scrollbar, it is useful using the mousepad.
    I would add a tentative pricing or early adopter pricing.

    1. 1

      Not a bad idea. Thanks a lot! We're still trying to figure out the pricing part.

  5. 2

    sorry I'm new here, how do you access the landing page? I just see an image of it :(

  6. 2

    @arthurleonov Your website looks stunning! It's designed so well and structured nicely! Did you design the illustrations yourself?

    Also, I've created a detailed feedback for you. You can check it out on https://app.ruttl.com/share/XPmfYSCEItwRaXK4xbUR

    Hope this helps you!

    1. 1

      Thanks @harshvijay!!!

      1. 1

        Happy to help!

  7. 2

    The site is visually appealing. I would consider if the "Console" and "Ever had this problem?" sections are informative. I did not understand what was happening until I started reading "Here’s how this tool works".

  8. 2

    Congratulations, I liked the contents and could understand the product features. However, I had problems due to the browser scroll is hidden.

  9. 2

    Hi there. The simplicity of the page is a good start, good job!

    The missing pricing can be a problem. When there's no pricing it usually means it's too early or too expensive.
    The motivation to sign up could be stronger. At this point am I sold on the idea for the core features? Do I care about the premium features? What are the premium features even?

    You could make the example more remarkable. It's easy miss the quotes on a number to string conversion. You could have a conversion of a date for instance.

    Why are you saying "mold and shape" and not reshape like the name of the site?

    I'm not the target audience, so I may be nitpicking. Best of luck! :)

  10. 2

    There are quite a few mistakes in the page, grammar and typos, that makes me always facepalm a bit...😉

    I don't really understand what the point of the picture is: it only partially changes, it doesn't add a ton of value to the page especially for no code devs.

    When you say: have you ever had this issue...and it's actually really confusing what you mean...api response, you mean the payload response right? You're trying to be a middleman transform to parse your endpoint and feed it to tools like zapier by autoformatting the code?

    1. 1

      Very good questions. Yes the payload response. I will look into the copy once more. Thanks @orliesaurus

  11. 2

    I am not in the no code space, but I here are some general things.
    First, I don't understand the before and after code. They are the same. You could make more clear what changed before and after.
    And on the first signup stand 118/200 spots left and on the second stands 170/200 left. They should be equally.

    However, I think you have a pretty nice product and I wish you a lot of success.

    1. 1

      Thanks for finding the sign up bug. Something is off with the backend. Will fix it.