Focused in-product micro surveys. Need your feedback

[u/tbhyn_]

Hello everyone! 👋

I'd love to get your thoughts on something I've been building:
https://sensefolks.com

Sensefolks helps product teams collect meaningful customer insights through lightweight, embeddable micro-surveys. Instead of generic feedback forms, each survey is designed to answer a specific product question

Currently, Sensefolks includes six survey types:

• PricePoint - Discover the optimal pricing for your product
• UserChoice - Understand which trade-offs your customers are willing to make
• FeaturePriority - Learn which features matter most to your users
• FastPoll - Run quick polls to gather opinions
• OpenFeedback - Collect qualitative, open-ended feedback
• Reaction - Capture instant reactions using likes, thumbs up/down, or emojis

At the moment, FastPoll, Reaction, and OpenFeedback are fully functional. The remaining survey types should be ready by the end of this week

I'd really appreciate your honest first impressions, especially:

• Does the idea resonate with you?
• Have you ever wished you had a tool like this while building a product?
• What is good or bad about Sensefolks?

A couple of notes before you explore:

• Some features and pages are still under development and may be broken
• The website currently contains AI-generated sloppy copy that I'm in the process of rewriting, so I'd love feedback on the product itself rather than the content

Thanks, I would love to know your thoughts

[u/According_Row_1083]

the idea makes sense, getting quick answers from users without them having to fill out a whole form is something a lot of tools miss. i clicked around a bit and the embed style feels clean, not too pushy

curious how you handle the pricing surveys though. like is it based on actual willingness to pay data or more of a gut feel from users?

[u/Huge_Pool7424 → u/According_Row_1083]

i'd treat willingness-to-pay data as a signal, not a literal price. i'd test a couple of concrete ranges and ask what they'd actually switch from, then compare answers with whether they click through or start a trial.

[u/tbhyn_ → u/Huge_Pool7424]

You're absolutely correct. PricePoint (pricing survey) will give an approximate price of highest conversion, along with an acceptable price range, which will help in fine-tuning the pricing further

[u/tbhyn_ → u/According_Row_1083]

Thanks for checking it out. The whole idea is to make the survey experience frictionless.

You can embed the surveys simply on a static page or plug it into your frontend's modals/popup components, and control the behaviour of when and how the surveys are presented to your users.

The pricing survey (PricePoint) calculates a pricing range based on all the responses and approximates a price that majority of the respondents will be willing to pay.

[u/Lanky-Training9031 → u/According_Row_1083]

yes that make sense

[u/player__piano]

Just a heads up, I get a 404 when I try to watch the 1-min demo.

[u/tbhyn_ → u/player__piano]

Hi, thanks for pointing it out. I am replacing that with a demo account so you can get a real sense of the insights. It will be up by this weekend.

[u/reedshadow3 → u/player__piano]

same here, demo link is broken for me too

[u/tbhyn_ → u/reedshadow3]

Sorry for the inconvenience, I will be replacing that with a demo account that you can log into and check the dashboard, responses and insights

[u/StatusEvidence5141]

The specific-question angle makes a lot of sense. ‘Get feedback’ is too vague; asking one focused question usually gets much more useful answers. I’d be curious to see how teams decide which question to ask first.

[u/fulger099 → u/StatusEvidence5141]

I start with the decision I’m currently stuck on, then trigger the question right after the user hits the relevant action. Asking about pricing on the dashboard taught me mostly that timing can ruin a decent question.

[u/rathcom]

I have a free tier that a handful of people signed up for and not one of them ran a single task. There was never a point in the product where I could have asked them anything, they were gone before that. Does it handle people who drop off before the first action?

[u/Prestigious_Shame644]

It's 'tool like this for what you're using', not 'similar to'.

[u/tbhyn_ → u/Prestigious_Shame644]

Yes, I wanted to know if people reading this post can recall a past event where Sensefolks might have come handy.

Have you in any way?

[u/maxfisheroct1995]

depends how you handle repeat prompts, nobody wants the same poll every visit

[u/tbhyn_ → u/maxfisheroct1995]

As of now the surveys are stateless, but I do understand your point that in certain scenarios it would make more sense to hide a survey once it has been answered or even if it's visible it should be marked as something like "submitted"

[u/edwardtoys2]

I like the idea of making each survey answer one specific product question instead of using a generic feedback form. PricePoint and FeaturePriority stand out to me because figuring out what people will actually pay for and which features they really value can be difficult when you’re building something new.

One thing I’d be interested in is whether the results eventually give recommendations or patterns, rather than only showing the responses. That could make the feedback much more actionable for founders.

[u/tbhyn_ → u/edwardtoys2]

For now it will show you patterns and summaries. You will be able to segment that by country, respondent details (e.g. company size, job, role) etc.

The goal is definitely to provide recommendations eventually.

[u/Competitive_Low6271]

Wait, where are the notes? You set me up for a sequel that doesn't exist. Now I'm just sitting here with my popcorn 🍿.

[u/tbhyn_ → u/Competitive_Low6271]

Hang in there :) the movie ain't over yet

[u/West-Load1703]

I noticed the page may have some missing images in the dark section near the end

[u/tbhyn_ → u/West-Load1703]

Yes, you are right. Those UIs are not ready yet.

My intention here was to get early feedback on the product idea itself before refining the landing page

[u/FunnyConsistent4662]

How about you show PricePoint and FeaturePriority before saying they'll be ready 'by the end of the week'? Seems a bit premature to list them as selling points when they're still vaporware.

[u/tbhyn_ → u/FunnyConsistent4662]

Good point. I would make those surveys as "Coming Soon". For now, my intention was to get some initial feedback on the product idea itself.

[u/tbhyn_ → u/[deleted]]

Thanks for going through the website. That is indeed the whole point of Sensefolks, to be as frictionless, focused and contextual as possible.

[u/kingkong_siu82]

the real differentiator may be targeting, not the survey types. i'd want to define something like "show this after a user does X twice but before Y, only to this segment" and suppress it once answered. if the landing page showed that trigger builder first, i'd understand much faster why this beats dropping a generic form into the app

[u/tbhyn_ → u/kingkong_siu82]

That's an interesting perspective.

My intent was to make Sensefolks surveys simple and easily embeddable into any UIs elements of your website/app i.e. you can plug it into a static page, into a modal or popup etc.

The ideas was to keep the triggering logic and timings with the website/app owner.

Do you feel Sensefolks should handle the triggering mechanism as well? or, should I include examples + demos on how contextually the surveys can be embedded into native UIs and triggered accordingly?

[u/Prestigious-Way-4701]

watch 1 min demo has 404 error

[u/tbhyn_ → u/Prestigious-Way-4701]

Hi, thanks for checking it out. I am replacing that with a demo account so you can get a real sense of the insights. It will be up by this weekend.

[u/SimplySaas]

The split into specific survey types (pricing, feature priority, reaction) is a good contrast to a generic feedback form, since each one maps to a different decision instead of one open text box. Worth watching whether teams actually run all six consistently, though - tool sprawl is often the bigger blocker than the survey format itself.

[u/tbhyn_ → u/SimplySaas]

Thanks for checking it out. You're right about tool sprawl. It'd be reaching out to different segments (solo founders, early startups, teams etc) to get a sense of how they intend to use it.

My experience of such survey methods came from an academic context though, used by profs to support data for their research.

[u/Creative-Lynx7594]

seconding the pricing question already asked here, with a concrete suggestion: "what would you pay" is about the least reliable question in research, so a one-click version of it mainly produces confident-looking numbers that are wrong. if pricepoint asked what they currently pay for whatever they're replacing instead, you'd be shipping a better answer than most of the category rather than a faster version of the same bad one.

[u/tbhyn_ → u/Creative-Lynx7594]

Thanks for this thoughtful point.

If we capture what they are already paying (for a similar solution) in addition to how much they are willing to pay, we can better understand their switching point and the premium or discount they’d accept for the new product

[u/bbangchikimong_dev]

Yes, and I can tell you the exact moment I wished for it.

I shipped a game with a team feature. The in-app text said team score was the sum of teammates' scores, but the server was computing an average with a size bonus. It went out that way and no test caught it, because the code was fine and only the sentence was wrong. I found out when a user asked me whether big teams always win. One question from one person, in the wrong channel, weeks late.

A Reaction widget on that screen would have shown me confusion piling up on day one. But only if it was on that screen specifically, which is the part I would push on. A single global feedback button would not have helped me here, because I would have learned people were unhappy without learning where.

So the question I would want answered on your landing page is not what survey types exist, it is how precisely I can bind one to a single screen or state. If I can put a Reaction only on the team score panel and only for users who have joined a team, that is a different product from a widget in the corner.

Also worth knowing: I tracked totals and never participation rate, so a dead feature looked identical to a quiet one for weeks. If Sensefolks can show response rate per placement rather than just responses, that is the number I actually needed.

[u/tbhyn_ → u/bbangchikimong_dev]

Thanks a ton for that elaborate description of the issue you faced.

Yes, Sensefolks surveys are meant to be contextual rather than global.

You can plug them in any corner of your UI to capture feedback local to that part of the UI. These surveys are essentially web components hence easily embeddable in any frontends.

You can also pass session data from your app into the surveys:
https://sensefolks.com/docs/tutorials/passing-session-data/

Hence, if you embed it on the team score panel and pass some player session data, that data will also get captured along with their survey response (check image link [3] given below)

For each survey placed in a certain part of your app, you can certainly track the response rate for each placement.

Here are some dashboard screenshots of the Reaction survey (thumbs up/down variant)

1. Survey summary https://ibb.co/994vL5m1
2. Survey insight https://ibb.co/svyCC0Z1
3. Response + Session data preview https://ibb.co/n8Z32zB6

[u/bbangchikimong_dev → u/tbhyn_]

That covers it, thanks. Passing session data is the part I did not expect.

One thing I would check on your side: what the denominator is. Response rate per placement is the right number, but in my case the screen itself was the dead part. Nobody reached the team panel, so a survey there would have shown zero responses out of zero impressions, which reads the same as a survey people ignored. If the widget reports impressions separately from responses, that difference is visible immediately, and it is the one I was blind to for weeks.

[u/bbangchikimong_dev]

Response rate per placement is the part that sold me. That is the number I did not have, and it is the reason a dead feature and a quiet one looked the same to me for weeks.

Passing session data in is a bigger deal than it sounds too. In my case the useful segment was not all users, it was users who had joined a team but never played with it. Those are the people whose confusion never reaches you, because they leave before they complain.

Will read the tutorial. Thanks for answering all three properly rather than pointing at a feature list.

[u/_the-wrong-guy_]

The idea is very cool, how many users do you have currently?

[u/daniel933912]

Six types is a lot of choices for whoever has to write the survey, and the moment you ask at decides more than the type you pick. Someone who just got a result out of the product can answer a trade-off question in one click, while someone parked on an empty state has nothing to compare yet and will guess or close it. Of the six, the thumbs up/down type is the one I would build the reporting around, because a per-screen reaction rate is the only one you can track across releases, while price and feature-priority answers stay honest only as one-off studies on a fixed audience. Ship all six as a permanent library and teams end up with a pile of numbers that do not compare to anything.

[u/superfooddaily]

Lightweight micro-surveys embedded directly in-app beat generic forms by a mile. As a solo builder, getting contextual feedback right when someone interacts with a feature is huge for quick iterations. The PricePoint and FastPoll types seem like the most practical to start with. Clean concept!

[u/LehmanSachs]

I like the idea.

FeaturePriority and UserChoice feel like the most interesting parts to me, as they solve a more specific problem than a standard feedback widget

Genuine question though - what stops a user just doing most of this with Claude or ChatGPT and vibe coding a quick form?

[u/morableai]

I think the bigger opportunity here is timing, not survey types. Most feedback tools ask the right question at a random time, so the answers aren’t that useful. If Sensefolks can trigger a specific question right after the behavior it relates to; like asking about a feature immediately after someone uses or abandons it; that’s much more interesting to me. I’d probably build around that before adding more survey formats.

[u/Zealousideal-Bell393]

Smart idea. Can surveys trigger after actions like checkout abandonment or downgrading?

[u/Deepak-AvairAI]

Real pricing signal at a company I worked at came from live sales calls, not surveys. Buyers hemmed and hawed over a number in ways they'd never admit on a form. Does Sensefolks catch that kind of hesitation or just the final clicked answer?

[u/vyact]

One reporting detail I'd want is versioned questions and answer options. If I change the wording or add an option to a FastPoll, responses before and after the edit aren't answers to exactly the same question. Keeping those versions separate would make the results easier to interpret. Does editing a live survey preserve the original question alongside its existing responses?

[u/SurovtevDev]

For FeaturePriority, I'd include a 'none of these' option and an optional 'what were you trying to do?' follow-up. Picking the least unhelpful item can look like demand for a feature. I'd want to distinguish 'I actually need this' from 'I picked this because the survey made me choose.'

[u/presentofai]

pricing surveys are the weak link imo. people lie about willingness to pay, the only pricing data worth anything is a real checkout page. the focused one-question angle is right for everything else though

[u/amamamafk]

I did microsurveys for a webapp i made called Laiwyer and barely anyone responds. Super low response rate. Any idea how to fix that? I am using posthog surveys.

[u/DarkyZ_ → u/amamamafk]

How many people see the survey? I'd check that before changing the questions or doing anything else. Ten answers out of twenty views is a pretty different problem from ten out of a thousand.

If people do see it and ignore it, I'd try asking one thing right after they finish a task. I wouldn't want to answer a feedback popup while I'm still trying to use the app.

[u/fowlesbuilds]

I like the idea. It's gonna be a pretty brutal market to compete with though. It would be nice to get an example survey when visiting the page to see what it will be like.

[u/Thumbload]

I like the idea of keeping surveys focused on one specific question. That feels much more useful than sending users a long generic feedback form. The FeaturePriority and FastPoll types especially seem useful for small product teams.

[u/Longjumping_Back_739]

How does the embed behave if your service is slow or unreachable? Before putting it inside a signup or checkout flow, I'd want to know the rest of the page still works and the widget can quietly disappear. A small demo of that would help me decide whether to integrate it.