Does feedback actually shape the product?

You've probably already seen our roadmap, where we share our plans for Pachca. So where do those plans come from? 90% of them come from user requests. In this post, we'll walk you through how to share a request, what happens to it next and how to help us ship it sooner.

Four ways to share feedback

• Message our support team on Telegram or MAX. They carefully collect every user request and pass it on to the development team.
• After you sign up, you'll get a welcome email. Feel free to reply to it with your suggestions.
• If you're in touch with one of our managers at Pachca, you can share your feedback with them.
• We regularly survey Pachca customers about their experience with the app. The survey has dedicated questions where you can describe your wishes in detail.

What happens to your request next

Feedback from every channel goes into a shared database that we go through every day. First, we check whether the request is clear to us. If it isn't, we reach out with follow-up questions.

The next step is prioritization. Only requests we fully understand make it to this stage. Our top priority goes to requests about the product working correctly and reliably. When setting priorities, we also consider which platforms and how many users an improvement will affect, how it will impact our metrics and so on.

After prioritization, the request goes into our backlog. From there, the rule is simple: the more often a request comes up, the higher its priority. This helps us figure out which improvements matter most to users. Sometimes we also bump a request's priority manually if there's a good reason it's urgent (for example, if we can't ship another high-priority improvement without it).

Then the development team picks up requests in order of priority: they dig into the problem, look for the best solution and build it.

How to help us understand your request

As we mentioned, at the first stage the most important thing is for us to understand the request: what it is, why the improvement matters to you and so on. Here are a few tips to help us understand your feedback better:

• Describe your request in as much detail as possible and explain why it matters. It's best to start with the problem and then, if you can, describe a solution. For example: "Our team is distributed and everyone is in a different time zone, so sometimes push notifications come in at 2 or 3 a.m. To avoid that, I have to fully mute my iPhone or turn on Sleep mode, which I don't usually do. Flexible notification settings in Pachca would really help, so I could set hours when I don't get push notifications." By the way, this example is from real life: we shipped flexible notification settings in July 2026.
• Tell us which platform your request is about (web, iOS/Android, desktop app for Windows/Linux/macOS), plus your browser or OS version and device name. This is especially important if you've run into a bug. Without this info, it's hard for us to reproduce it and find the cause.
• Break your suggestions into separate points and try to describe each one in plain language. That way, we can quickly split your feedback into individual requests and add them to the database.
• Tell us which company you work for.

It would be great if you followed these tips. They help us understand your request and why it matters faster, find a possible solution and build it.