Feedback on my micro SaaS website

Hi there!

I think the video front-and-centre is too much.

Quickly from the top
Headline : does what it says on the tin (Alternative suggestion: ‘Save your time for the good stuff’ (that sort of thing)
Summary text : lists are low energy to read in long-form text. So hard to read. Stick to the benefits, e.g. “All your dull Github tasks set up for automation in less time than it takes a kettle to boil.”
(Also, is that actually true? Because that video didn’t look like ‘all the tasks’, it looked like one task).

CTA/Button – Install on GitHub – free for now.

Next: benefits. Not just what it provides, or what it lets users do, but what they get from it, the things that would make them go ‘ooo yeah’. What problems does it solve for them? Can bullet point it or subhead each one with a beneficial message and a short explanation as to how the features make each benefit happen. You don’t have to get every feature in there. You can write a line or a paragraph, as long as it gets that info across.

Then: Video - give it a header: How it works. It was a little underwhelming, the video. I don’t know if you might be better with a How it works written breakdown, just for visual interest as much as anything.

Can list the features if it makes you feel better, but they might be better on an installation / pricing plans page? They’re arguably not much use other than for comparing your product with other products.

Need another button in there – different CTA to draw them in but button text can be same.

FAQs are fine

Need to follow some kind of structure that makes sense to the user.
e.g.
Headline – look how great this is
Summary – look what it will do for you
Benefits – this is why you need this
Stats – this is how much time you’ll save
How it works – this is how it works
Sample – video
Social proof – all these people thought it was great
Reviews/recommendations – these ones did too
Previous work – these were really successful apps of ours
FAQ – this is what answers any further questions you’ve got.
And get a couple of buttons in there with a compelling CTA.

I mean, none of this is set in stone, completely off the top of my head at 3am, so you do you. But in the background those are the questions and considerations you’re answering with the information you provide in the landing page.

What do they know? (they know what problems they're having)
What do they not know? (they don't know how your product will solve those problems).
Tell them what they don't know.

For me, I cannot access the website because there is no secure connection.

My 2 cents speaking as a software engineer with heavy DevOps background.

This honestly just seems like GitHub actions but with extra steps. Especially since, at least from my experience, engineers don't like no code tools, since more often than not, you'll hit some edge case which is not supported, and then you are again back on square one with having to do it yourself.

Another thing that's kinda important is that GitHub actions rarely get changed when after they are written, they might get and update here and there, but most of the time you just spend a few hours writing and testing them, and you just forget about them.

This is even more visible when you have some general action which you can then just copy paste wherever you need.

Another thing I notices is this part " right now it is in a public preview and has all the features fully available for free", does this mean that you'll lock out some features for the existing users if / when you introduce paid plans, cuz I'd honestly be pissed if that happened.

Hope this helps!

Video feedback: you can 2x, 3x the speed when you write something manually in an input field, it's slow for no reason otherwise

Landing page design is great

Like other commenters said, focus on use-cases rather than features so that my brain goes like ah-a

Congrats on the launch! I know how hard it is at the very beginning, but keep pushing!

I left some ideas here - https://visualdebug.com/show/codeherald.com