Wanting to help an IH? Roast my landing page: Jotcode - Serverless scripting platform
Hi there,
Like some of you here, I'm trying to build something that I really believe in. Hopefully, I like to code, so, after a few months, I've finally been able to launch an app that I am very proud of: it's called Jotcode, and, it's an online scripting platform.
However, marketing and designs are not my primary skills. Like many of you, I'm even not a native English speaker. So, I'd like to ask for a bit of your help.
May I ask you for a bit of feedback on the landing page for my product: https://jotcode.io ?
Especially, I'd love to know:
- Do you find the concept of a serverless scripting platform clear?
- What about my website design? Does it look professional?
- If you were of my primary target (the people who write scripts at work), would you be confident signing in my product?
- Of course, any other feedback would be welcome
If you have a bit of time to answer these questions, it would really help me a lot to understand what should I focus on for the next months (branding, design, copy, features, or anything else).
Thanks in advance
I'm not a person that's familiar with coding and script writing that much so I'll just keep my thoughts to the content of your website.
I feel like there should be a little more info about the product. For example, some use cases would help in my opinion. In addition, some FAQs and reasons that set you apart from the competition would help.
No?
While I can tell it was designed by a developer, it looks alright. Like the dark mode.
No. First of all, my company has a policy to pretty much strictly use AWS and GitLab. Second of all…
My main problem is that I don’t understand how you’re better than or even different than AWS Lambda and serverless.
The AWS Lambda UI (which I rarely use) has a similar style box for coding and allows you to run the code with custom payloads and return results.
Serverless, which I always use, allows me to use TypeScript as well as easily save, version, and run my code. Just with a bit more initial setup.
Bluntly and honestly, I don’t see what the hook or appeal is over existing solutions. Please enlighten me.
Thanks a lot for such an honest feedback. This really helps me.
In terms of differentiation, we want to act as an additional layer on top of lambdas to make them easier to use to write adhoc scripts.
Basically it would be the exact same as serverless, but focusing on ad-hoc tasks instead of building apps (ex: if you need a script for data extraction, backup, transformation, ...).
Good point about the interface, which we'll have to make as intuitive as possible, as we don't only target professional developers.
Do you think with this explanation that it makes more sense?
Thanks
Sure, that makes a bit more sense.
I just can’t say I see it working out at companies I’ve worked at. Even if you did make it more intuitive and what-have-you, we just wouldn’t let you have access to sensitive information as we have to uphold SOC 2 Compliance and have QA (perhaps devs) look at it first. Just a bunch of hurdles higher than let’s run the thing! At that point, it’s probably easier to tell a dev to do it.
As a tech founder using AWS Lambda for most of my projects, I still would probably just use AWS Lambda. And I use it for cron tasks, s3 events, uploads and more, not just putting apps inside it. I need to keep my code in git repos and worry about vendor lock-in.
As for low-code folks, I’m not that market. So maybe it would work for them. I’m just not really seeing features that markedly catch my eye.
Minor typo: 'Unleach' should be 'Unleash'
Perhaps a demo would be useful - I get the general idea, but the details are still pretty vague (but then I don't have a specific need for your product, yet, at least, and so maybe someone who does would have a clearer idea of what your product experience would be).
What does the user actually get? A management console? A script editor? A command line? Something else?
Thanks a lot for the comments! Indeed, it looks like there were a few typos. So, I ran everything through Grammarly to fix that. Thanks a lot.
Very good point about the product description. I'll try to make sure to improve it.
About the design, what do you think, does it look professional?
The design looks fairly 'minimalist' to me - it does look clean and uncluttered, with a logical layout, although some people might find that having a single background color throughout the entire page is 'boring' or amateurish (perhaps the logical separation between different sections of the page might be improved by the use of more visual cues such as different background colors for different sections).
The use cases section might be improved by making each use case pop up or link to more details, or an example, or a user testimonial, if the user clicks or hovers their mouse over a use case.
I do think that the copywriting could be improved in many ways and in many sections of the page - for example, 'the serverless scripting platform for every use' sounds to me like an extravagant claim and perhaps even as an amateur writer's clumsy attempt to craft some marketing language. "Every use"? Really? Language that focuses on the benefits to the user might be better there.
There are other parts of the copy that sound a bit 'overblown', for example, the security section.
Adding a 'call to action' below the pricing section might be a good idea.
So, while I think that it is a good start, it could definitely be improved.
Thanks again for such a detailed answer. That's exactly the kind of feedback I was looking for. I'll definitely have a look at how we can use more of a standard bicolor pattern on the website.
Adding a CTA on pricing is quite easy. So my main work after that will be on the copy. The other comments indeed seems to indicate that the value proposition is not very clear, as well as the examples. I'll definitely work on that. Thanks a lot!