Votelyra

Collecting feedback usually means one tool to build the survey, another to analyse the answers and a spreadsheet in between. Teams lose the thread between the question they asked and what they should do about the answer.

Most teams already had a survey tool, but the answers lived somewhere else. Exporting responses, cleaning them in a spreadsheet and building charts by hand meant insight arrived days after the feedback did.

Ownership was just as scattered. Product, marketing and customer success each ran their own surveys with their own logins, so nobody could see the full picture or reuse what another team had learned.

Acting on the answers was the weakest link. Following up with an unhappy respondent or alerting the right person about a low score depended on someone remembering to do it.

The platform had to close that loop: one place to ask, analyse and respond, with each team kept in its own workspace and its own permissions.

Built as one typed stack: a Next.js frontend and a dedicated Fastify + tRPC API over PostgreSQL, so the builder, the response store, the analytics and the engagement tools share the same types end to end.

The builder, the response store and the analytics share one schema, so a question added in the builder shows up in every chart and export without a separate integration.

Engagement sits next to the data it acts on. A low NPS score can trigger an alert, and a follow-up email goes to the respondent from the same workspace that collected the answer.

Each team works in its own workspace with its own roles, and billing runs through Stripe so plans scale with the number of responses rather than the number of tools.

Keeping team data separate while sharing one database. Every query is scoped to a workspace and checked against the member's permissions in the API, so access control does not depend on what the UI chooses to hide. Billing follows the same rule: Stripe webhooks are verified by signature before a plan changes, and plan limits are enforced on the server.