Landing page live. A bit unconventional, isn't it?
Hey there! Just joined this community after listening to an IndieHackers podcast with Sergio, sounds like a place worth sticking around!
So, I'm building a side project, a very simple analytics solution for collecting custom metrics (number of signups, server-side errors, how much disk space there is left on your server, what is the average response time, number of times someone opened a specific page in your native iOS app etc…).
It will work from any codebase, have a dead simple API and no extra dependencies for collecting such events. Here's the site: https://statbrew.io/
I'm really scratching my own itch with this one - I've been frustrated a lot by some of the big players out there, for example Firebase analytics or Google Tag Manger. They are often bloated and provide way too much for products which are in the beginning stages of development.
PS. I validated the usefulness of such a tool by using an mvp of it while monitoring my previous for-fun project Waymark where I collected around 30000 events. I really believe dogfooding is perfect when building your things!
Anyway, I got a landing page up, it's a bit unconventional I believe. As this will be a developer-focused tool, I'm expecting this to be a bit vague at this point before I have concerete examples live, but I'm wondering whether the page gives at least a sort of an understanding of what it is going to be?
Again, that's the site: https://statbrew.io/
Cheers,
R
Welcome to our community!
IMHO though: I'm not sure I like it. If I come into a landing page, I don't expect nor want to read an essay to find out what your value proposition is.
Advice: add a TLDR before the explanation.
Cheers fam!
EDIT: You know what… I'd just change the first sentence. Remove it. The second one explains PERFECTLY and the first one just takes away from that. At a glance, it lets me know what the reading is about. I see you took cues from the hey.com one - they do that. They clearly indicate in the first sentence what the product is: it's about email. It's a perfect hook.
That's great feedback, I see your point. Updated!
I don't expect nor want to read an essay to find out what your value proposition is.
One of the benefits of this type of landing page is that it filters out people who are not immidiately sold on the propositon (briefly discussed in the latest IH podcast with the author of The Mom Test). For example you mentioned hey.com, they make it even more difficult by not including a subscribe box - the user has to send an email themselves.
In any case, I will post an update when I have a more mature landing page with some product screens up.
Thanks
PS. loving the new design on the site
@rainer Your assumption works when the person immediately grasps the proposition. I didn't - I saw a wall of text and left.
Your updated page does make it much easier to grasp the proposition: I still think your first sentence is too heavy, and requires optimization.
I'm building an analytics solution capable of collecting custom metrics from any codebase with a simple API and no extra dependencies.
This is too wordy. There's too much jargon. What is a "dependency"? What is a "custom metric" or "API"?
Value propositions appeal to basic human needs and desires - they're not features - it's great practice to not utilize industry jargon and stick to the basics. Explain your product simply and concisely.
Your first sentence is the hook - you don't (and shouldn't) explain your features here. If the customer is interested, they'll keep reading. Explain what value your product provides and forget features.
Cheers!
Please sign in to leave a comment.