datary - The question nobody else asks

Four questions at your counter. Answers your POS can't.

SaaS

Artificial Intelligence

Data & Analytics

Visit WebsiteSee on Product HuntInstagram ⧉Twitter ⧉

I run a small software shop in Muscat. Last year I watched a café near me get quieter every month. The owner knew the numbers were down. He had no idea why. His POS could tell him exactly what he sold on any Tuesday in March, and nothing at all about the four people who saw the queue and walked out. That's the gap Datary sits in. How it works A customer scans a code at your counter and answers four questions in about twenty seconds. No app, no sign-in, no name, no cookie on the page. How likely are you to recommend us? (0–10) What shaped your visit the most? If we were closed today, where would you have gone instead? One thing we could do better? (optional) Question 3 is the whole reason this exists. Every other question here you could get from any survey tool. That one tells you who you're actually competing with, and the answer is usually not who the owner assumes. The café owners I've spoken to all name the place across the street. In the pilot answers I have so far, the most common answer is "I'd have stayed home." *You can't beat a competitor you've misidentified.* A few technical decisions, since this is Product Hunt Anonymity isn't a setting, it's the schema. The responses table has no user column, no IP, no device ID, no session. There is nothing to link an answer to a person, including for me. That's not a privacy feature bolted on it's why the answers are honest. Questions live as JSON on the business row. Any business can rewrite its entire survey wording, options, count with no migration and no schema change. The dashboard aggregates by question type rather than by column name, so a business that replaces all four questions still gets a working dashboard. The session token carries a password epoch. Changing or resetting a password increments it, which silently invalidates every cookie issued before that moment. Without it, "reset your password" is theatre the thief keeps their session. Rate limiting is an in-memory Map, not Redis. One Node process on shared hosting, so a Map is enough. It resets on deploy. That's a real limitation and I'd rather say so than imply infrastructure I don't have. Fonts are self-hosted and there are no analytics or trackers anywhere. A customer answering a survey in a café shouldn't have their IP handed to a CDN for the privilege. Where it honestly stands It's built, deployed, and free. No business is using it in production yet. I'm launching here to find the first few, not to celebrate traction I don't have. So the thing I actually want from this launch: if you run a café, clinic, salon, garage or shop or you know someone who does I'd like to put a code on a real counter and find out whether customers scan it. That's the only question left that I can't answer by writing more code. Try the survey without signing up: https://go.datary.tech/s/lucca-589 Happy to go into any of the above in the comments.