
getuserfeedback.com
Grow your product faster with user feedback

Everything I build starts with research.
Before building Themes (skins for feedback widgets, basically) I wanted to understand the impact of look-and-feel customization on our business metrics and brand perception, and on our customers' metrics and their end-users' experience.
If you're building a B2B SaaS product not dissimilar to ours (a product for businesses that interfaces with their customers, a B2B2C), this research will be useful for you.
Emotional and perceptual benefits of customization
Allowing customers to tailor the visual design of an embedded widget or interface taps into a basic psychological driver: control. Giving users customization options increases their perceived control over the software, which in turn enhances their comfort and trust in using it.
When a company can make a third-party tool look and feel like an integrated part of their product, they feel more ownership over it. This sense of ownership and agency translates into higher satisfaction.
Customization also has an expressive and identity benefit. The option to skin a third-party interface, (an in-app survey or chat widget in our case) is emotionally important for clients to feel that the tool aligns with their brand’s personality.
Instead of an external service taking the spotlight, the client’s brand remains front‑and‑center, reinforcing their emotional connection with their end users.
Offering look‑and‑feel customization empowers customers and respects their brand identity. This can significantly boost client satisfaction and trust.
Cohesive branding, user trust and experience
End-user trust is the ultimate value we deliver to customers. Our base is startups and products at the earliest stages — when there isn't any trust yet between our customers and our customers' customers. So, everything we do is aimed at building that bridge.
On-brand look and feel is the logical next step.
From the end‑user’s perspective (the people interacting with the third party interface, like our embedded surveys, or a chat, or guide inside the client’s app), visual consistency is key.
Users form snap judgments about software credibility within milliseconds, and those judgments are overwhelmingly driven by visual appearance.
So if you're building let's say an embeddable widget, and its style clashes with the host application or carries a different brand name, it risks feeling off or unprofessional to users in those critical first moments. Consistency creates a seamless experience that feels reliable.
Effects on user engagement and response rates
One area where the impact of branding customization can be quantified is user engagement with surveys and in‑app prompts. When users trust and feel comfortable with an in‑app element, they are more likely to interact with it rather than ignore or avoid it.
Branding and familiarity can meaningfully lift response and interaction rates. For example, an email or notification coming from a known, trusted brand dramatically increases the chance a customer will open it and take action; if the same message comes from an unfamiliar third‑party, response rates drop and users might even flag it as spam.
The core insight: when users trust an element, they engage; when they doubt it, they bounce. Look‑and‑feel customization is a tool for earning that trust by leveraging consistency and familiarity.

Business outcomes for the SaaS provider and clients
Beyond engagement metrics, offering extensive customization options can influence broader business KPIs for both the SaaS provider (you) and B2B customers (your customers).
For the SaaS provider, one obvious impact is on customer acquisition and retention. In many B2B scenarios, especially when selling to mid‑to‑large enterprises, the ability to offer a white‑labeled or highly brand‑consistent solution is a make‑or‑break requirement.
Companies with strong brand guidelines may simply not purchase a tool that cannot be adapted to their look‑and‑feel, or they might favor a competitor that offers more customization.
It’s important to consider the user‑experience quality angle. If customization options are poorly implemented (for instance, allowing clashing color schemes or inconsistent UI patterns), it could backfire and harm the user experience.
Offering look‑and‑feel customization should go hand‑in‑hand with providing sensible defaults and guidance so that the integrated element remains user‑friendly and accessible.
When designing the Themes engine, we went above and beyond to make it hard to break the user experience. Despite unparalleled flexibility (more than 300 design tokens), it's resistant to ugly or broken combinations through intelligent defaults, extensive use of relative colors (eg border-color is dynamically set to be 10% darker than background-color, as opposed to defining both statically), as well as contrast checks, and AI-assisted editing.
This was a quick overview of the post we've just published on our website. Check it out to find more details, supporting stats, and links to the sources we used.
Feel free to check out the Themes feature, the landing page will give you a glimpse of what our AI theme editor can do. I think it's pretty cool how well it works.
Don't forget to like this post if you like it 😘
I thought it might be useful to others if I share the previous versions of our landing page that were not converting visitors into signups and the one that started converting at around 10% rate.
Feel free to skip to the last screenshot — the current version that works.
For context, the landing page is for a service that allows early stage startups to collect feedback from their users, act on it, and grow much faster as a result.
Version 1
(Before our designer joined the team, as you can probably tell)
Main idea: focus on the holy grail of any early stage startup — the product market fit. It's true that startups that actively solicit user feedback are more likely to win so we wanted to speak directly to that.
Ultimately discarded this version because it's too narrow a message for the main stage. Not a lot of traffic for these keywords, etc etc. We still use this messaging but on a dedicated landing page for the product-market fit survey (which is a great survey that everyone should run).
The visuals (in the grey squares) are irrevocably lost but honestly there wasn't much to look at in the first place.

Version 2
Main idea: focus on YC's mantra — "Make something people want". The first step in making something people want is finding out what is it that people want. We provide a pathway to that.
+ better visuals, more features, better feeling that this is a real product, not a landing page with a waiting list behind it (which was the case for the version above).
Discarded this version because it didn't resonate enough for people to convert.

Version 3
The main idea: differentiate ourselves from competition by using different language. The other guys™ typically focus on efficiency, managing large volumes of feedback, feedback portals, voting for features etc.
We wanted to focus on the stage before you need all that. The stage when no one wants to give you any feedback, yet. The very humble beginnings of a startup.
It's incredibly difficult to get feedback at that stage. A great way to cut through the indifference is by being very human, very approachable, present, proactive, etc etc.
We wanted our messaging to reflect that.
+ more refined visuals
+ more features
+ integrations
+ usecases
+ lower pricing
And yet, this landing page did not convert.
This messaging still describes really well how we're different but ultimately, it wasn't strong enough.
(there is an artefact on the screenshot: the sticky header didn't stick correctly)

Current version
This version sells. For high-quality traffic sources (like indiehackers and similar), it gives us about 10% conversion rate (visitor-to-successful-signup).
For this version, we spoke to a sales strategy consultant, and also a marketing person joined the team. I highly recommend talking to a professional if you're stuck.
Main idea: tie feedback to growth while still maintaining our human approach.
Everybody wants growth. It's also true that feedback leads to dramatic growth. In hindsight, it seems soooo obvious that this is the exactly correct framing.
+ beginning of templates
+ beginning of blog
+ better visuals
+ the whole page is more coherently connected with the messaging
+ everything is way more polished
Is this the best possible landing page? Absolutely not, but it was the difference between 0 and 1 (for us).
It can absolutely be better but it's no longer the bottleneck for the business.

Happy to answer any questions. Also feedback is very welcome.
Don't forget to like this post if you like it 😘
Like
21 Comments
21 Comments
-
2
I was searching for insights, and your post arrived at the right time; the way you have iterated is so effective that I could see the messaging change and how it relates at each stage.
A query. Where do Micro SaaS founders prefer to build their landing page if they are at the MVP stage or the 'just launched' stage? Is it Carrd, Notion, or WordPress, or would they prefer to have it custom-made? Are there other preferred platforms?
I am trying to provide a productized landing page service for micro SaaS founders; your feedback would be helpful.
-
1
Thank you! I’m using the same stack for landing pages as for the product itself — nextjs. No CMS, all hardcore. Just a bit of MDX with frontmatter for blog as it’s perfect for that.
It’s faster for me to do it this way as I’m very technical rather than to use something like Carrd. Also, I can be certain I can do anything I might need with the highest quality and precision.
Plus, the border between landings and product is blurry (eg a template can be installed/used right from its public page), they share styles and a few components.
-
1
Thank you, Ilya. The service I want to give pre-launch and just launched micro saas founders is Positioning and Messaging (I thought ' landing page copy with Carrd support would be the best way to offer it ), or would the founders need some other support? Please do suggest
-
1
Oh I think I misunderstood your original question.
If you’re asking what other support micro-saas founders might find useful aside from making a landing page on Carrd (or somewhere) — I can only speculate. I think that would be everything around the actual messaging. Iterating on it, suggesting how to test it, how to know when it’s time to pivot to another idea, etc. A lot of this work has to be done by the founder but guidance and expertise is useful.
Honestly though, that’s just what I think others might want, but I don’t include myself in that cohort. For me, I think it’s important that I do almost all of this work myself because it’s so critical for success.
I may still not understand your question. Feel free to reach out on twitter — @sirnovikov
-
-
-
-
2
Btw this is something I see early-stage startups struggle with all the time. Positioning and messaging are just as integral if not more to good design as visual aesthetics.
-
2
I like the iterations and how you are taking a measurable approach to the UX design! Best of luck!
-
1
❤️
-
-
2
Looks awesome! If you ever need help turning this into a mobile app (I build with Flutter), I’d love to help or brainstorm. I’m always down to collaborate with fellow builders. 🔧
-
1
❤️
-
-
2
So cool to see this comparison with real results!
As a potential user, I find the latest version much cleaner and more straightforward—it’s immediately clear what the tool does and how I’d use it.
But honestly, what really won me over was the new 'Free' option. Since it’s a new product, I really want to try it out before committing to a paid plan, and this model makes that possible. Super exciting!-
1
Thanks! Ah yeah I must have missed that version where we did introduce the free option and it wasn’t enough on its own to start converting.
Would love for you to try it out 😊
-
-
2
Fascinating thread. It seems you built this for desktop. Have you considered a mobile first approach? Can you talk about the CR split between desktop and mobile?
-
1
Thank you. Actually everything on the website is mobile first, including all internal pages (even the survey builder and survey pages themselves — the most complex ui ever) and all public pages.
Desktop traffic is almost 20x mobile. All conversions are on desktop.
-
-
2
this is great. welldone
-
1
Crazy how so many agencies just build pages their clients are happy with vs using focus groups to provide real insights on how to improve designs so that they convert. This should be apart of every design process.
-
1
Good share!
-
0
<h1>hello</h1>
I always thought that presenting yourself as a person — as opposed to hiding behind a brand name — makes it more likely for people to care about what you have to say. Be it a blog post, a survey, or any customer communication. It seemed kinda obvious but I didn't know if it was actually true.
Now, I've done some research. I wanted to do this research before adding features that support this sort of personalization in our product.
The full research with links to the sources is on the blog but here's the highlights.
Personal framing suggests accountability. Users tend to trust that their feedback will be acted upon when they know who is asking.
Asking personally creates a subtle social bond. The request becomes a human-to-human interaction rather than user-to-machine.
Users might empathize with a developer as a fellow human, feeling their feedback will directly affect that person's work.
Additionally, when you frame the feedback as a meaningful contribution, it is more believable when it comes from a person than a corporation.
The psychology at play involves social presence, reciprocity, and authenticity — users reciprocate personal effort with feedback and trust genuine appeals over robotic ones.
The upshot: making feedback requests personal and authentic tends to skyrocket participation rates and can influence the quality of feedback. In turn, that helps you grow the product much faster.
With this research done, we've just launched an ability to display your name, photo, and title in your surveys, onboarding flows, and feedback widgets.
Give it a go and let me know what you think!
Like
1 Comment
1 Comment
-
1
Link to the full blog post with research: Influence of personal vs generic survey requests on response rates
They say “make something people want”. But how do you find out what people want?
There is so many ways to do that: from simply running ads to see what message people click on — and all the way up to in-person deep user interviews.
Depending on what you're working on and the stage you're at, different strategies may work better for you.
For me, the most feedback-starved period for my products (as an indiehacker as well as a product manager at early stage startups) is in the early stages. When I already know the idea seems to have legs and I get some initial traction but it's not very clear what people want.
Not knowing what people want makes it really difficult to improve the product efficiently or at all. Yes, I can rely on my experience and product sense to figure things out but it only takes me so far.
Will users like this new feature I'm thinking about?
How do I make it 10x better?
Is there a hidden opportunity that would make my product 10x more attractive?
Is there an adjacent user segment I'm not thinking about?
Can I charge more?
What does it take to make the users fall in love with the product?
How can I improve user retention?
Am I doing something good for the world?
So many questions. And then, there is this.
People don't like to give feedback. It's time-consuming, they need to think, and they just don't care enough. Especially when you're early and you don't yet have a fanbase.
You want qualitative feedback (free-form thoughts, open-ended questions), not quantitative (pick a number on a scale). There isn't much to quantify when you're early but there is everything to figure out about the product.
People are bad at giving qualitative feedback. It's a skill that doesn't come naturally to most. They also don't know what you need to hear as they're not developers themselves.
People like to propose solutions ("I want a red button over there") but that's typically useless — you want to get to the underlying problem ("I often accidentally delete things I didn't intend to, because I'm a mom of 3 and I'm always distracted"). You're the professional who knows how to solve problems best, not the user.
There is danger in delivering what people literally ask for — you need to really examine the root problem and come up with the best solution within your constraints. More like "feedback-informed" less like "feedback-driven."
When you don't have many users yet, you want to understand each and every one of them as deeply as you can. That means exploring what they do in the product, contrasting that with the feedback they gave, and trying to understand their world and how your product fits into it. It's very much about the discovery and not that much about the numbers.
Well, someone might have thought long and hard about the problem and came up with a great solution 😉
Like
9 Comments
9 Comments
-
3
I totally get it! It's so hard to find out what users want. They don't like giving feedback and often give useless suggestions. How do you usually dig out the deep - seated needs? Share with me!
-
1
There are many many ways to go about it. I think the most simple and obvious one is just keep asking why — the famous Toyota 5 whys. Which is really nothing more than just asking why until you get to the appropriately fundamental problem. This way you get from symptoms/solutions to something deeper.
If you can just observe the user in their natural habitat — do that, too.
If you mean how to get the user to talk in the first place — increase your luck surface area, reduce friction, give incentives, make it clear it's worth it, close the loop.
You could, you know, use getuserfeedback to help with all of the above 😉
Let me know about your case more I'll give a better advice.
-
-
2
Your tool is good, and it is obvious that feedback matters. But why you don't have a blog section?
-
1
Thanks! What would you like to read about if we had a blog? Do you have any specific questions or themes you'd like us to explore? Presumably around feedback.
-
-
2
Your post really hits home for me. The early stages of product development can be so ambiguous, and user feedback is indeed the key to navigating through it. I agree that focusing on the underlying problems rather than users' proposed solutions leads to more effective product improvements. This is definitely something I'd like to implement in my own no-code development journey. Thanks for sharing such insightful and practical advice!
-
1
Glad it resonated! Curious to know how you plan to solve this.
-
2
This is just rough thinking right now but I plan to focus on these areas for now:
1) Holding regular feedback sessions or user testing session.
2) Tweaking my product based on the insights gathered.
Additionally from a fundamental approach, I plan to leverage online communities such as Reddit and Quora to gain insights from real users discussing related topics. Continuously reading on Indie Hackers will also help me stay updated on various pointers.Its still a ways but a good starter for me
-
1
Cool! Good ideas there.
Reddit is great for serendipitous discoveries and finding interesting niches. Haven't used Quora much, is it good?
I use Reddit at the pre-idea stage, where I'm just looking for new things to work on.
I've had some luck using Reddit to ask for feedback on my early prototypes and initial versions but it wasn't super successful.
I suspect that there is tension and it's the main reason it doesn't quite work (for me): users want to use things that are done by "professionals", whatever that image entails in their mind. When you ask them for feedback on Reddit, it breaks that image (maybe?). For some (most?) products that's deadly — like B2B dealing with customer data, or fintech, or sensitive private data, any business-critical data etc.
When it comes to regular feedback sessions, in my experience you can only talk to users that have some emotional response to your product, negative or positive. They need to be invested. It works when they have been using the product for a while and have strong opinions fuelled by emotions or strong unmet business need. When you're early, there isn't going to be any emotional response or a business need, there isn't any connection at all, they don't care, yet.
Maybe your experience is different!
In my view there is a huge gap between "Looking around on Reddit" (high effort, low reward) and "holding regular feedback sessions" (high effort, high reward) and that's exactly what I'm solving for with my thing (low effort, medium reward).
-
-
-
-
0
Hello everyone
Are you looking for a trusted receiver?
Here is the good news for you. I receive wire transfer, IBAN to IBAN transfer, ACH transfer (both bank and 3D PAYMENT GATEWAY)
Percentage is negotiable ✅
Payout is 24 hours✅
I assure you safe payments and prompt delivery because your security is my top priority✅
There is a famous phrase — commonly attributed to Paul Graham and YC — “make something people want”. We help founders find out what it is that people want, so that they can go ahead and make it.
In short
getuserfeedback.com enables communication between founders and users — a channel for users to provide feedback and for founders to act on it.
Founders grow their products faster with us, because they get high-quality feedback with our tools and turn it into product improvements that delight their users. Users provide even more great feedback when they see founders pay attention. This virtuous cycle fuels growth.
Functionality
Surveys & Feedback Widgets: Capture qualitative insights right when users are most engaged.
User-Centric Communication: Let users see that their input is valued—humanizing your product.
Closing the Loop: Proactively respond and iterate based on real feedback.
No-Code Integrations: Start collecting feedback in minutes.
Incentive Engine: Add incentives that motivate participation (a discount, a chance to win something, and more) and we'll manage the delivery.
AI Follow-ups: Minimal, unobtrusive AI guides users to provide richer, more actionable insights by asking contextual follow-up questions.
Give it a try — turn user feedback into product growth with our free plan today.
There wasn't a tool for that so we've built it
getuserfeedback.com is optimised for early stage startups: ideas that have a great promise but they're not developed enough yet (haven't found product-market fit). Later stage startups will benefit too but it's not as life-and-death for them.
Proactively asking users for feedback and giving them ample opportunity to express feedback when they have it unlocks rapid growth. That's why we've built surveys and feedback widgets that you can embed in your product (there are other channels as well). We recommend you start asking for feedback right after people sign up (or whatever the highest first engagement peak is for you).
Designed for tough crowds — users that are barely interested in your product yet — to get you as many responses as possible. We give you tools to establish a connection with your users, make it clear to them that their feedback is welcome, that there are humans on the other side that are eager to help, that their feedback matters and is acted upon, quickly and professionally. This creates a virtuous cycle that greatly speeds up your growth.
Qualitative feedback first — it's not easy to get people to respond but it's infinitely better than not even asking.
For users who don't know what you need to hear — and here we use a little bit of AI to gently guide users with auto-generated follow-up questions that are specific to what the user said. We help people express themselves more usefully and give you the insights you need to build something great.
We didn't really want to use AI or make it about AI at all — so it's very minimal, unobtrusive, and is genuinely useful.
Great for first-time founders — with guidance on what to ask, when to ask, and how to analyze the results. For example, there is a specific proven methodology for determining if you've hit product-market fit or not, and how to analyze results to get there faster. We'll help with that.
Sign up to see how we're dogfooding our own product.
Like
Comment
About
I've built getuserfeedback.com because I need it. I wanted feedback from my early users, so that I can quickly validate, iterate, and improve. Feedback is critical for product survival, especially when you're early.














1 Comment
really expect-able product!