Unioo serves two wildly different customer groups - volunteer association boards and bank compliance departments. Consequently, standard CX doesn't work when expectations are that different. Here's how we solved it.
Two customer segments that couldn't be more different: volunteer board members and bank compliance departments. One dashboard that captures both
1/3 of all Danish financial institutions use Unioo for KYC. When your customer base includes banks, your feedback needs to match their expectations for professionalism
Furthermore, customer feedback linked directly to product roadmap - development based on data, not on whoever shouts loudest
For a startup with fresh investment, documented customer satisfaction isn't just nice to have - it's investor communication
Unioo serves volunteer board members in associations and compliance departments in banks. Think about that for a moment. On one side: a sports club chairman using the platform in the evening after work. On the other: a compliance officer at a Danish savings bank who needs to meet legal requirements for KYC and AML.
Their expectations are fundamentally different. Specifically, the association person wants things to be easy, fast, and intuitive. Meanwhile, the banking person wants data security, uptime, and documentation. Send them the same survey and you get data that's impossible to act on.
Unioo was founded in 2019 in Randers, Denmark. They already assist 1/3 of all Danish financial institutions with KYC collection for association customers. With over DKK 6 million in investment from Ugly Duckling Ventures and Compounding Capital, they're in full scaling mode. Therefore, that's precisely where customer satisfaction becomes critical.
Before SurveyGauge, the product team built features based on two things: internal assumptions and whoever had most recently written a support email. It's a common trap for startups. The customer who shouts loudest gets the most attention - however, that's rarely the customer who represents the majority.
As a result, there was no way to prioritise development effort based on what actually created the most value - or the most frustration. For a startup that had just secured investment and needed to scale quickly, that's a risk. You can spend three months building a feature nobody asked for, while the problem that's actually driving churn remains unsolved.
Associations: onboarding and ongoing satisfaction. New associations receive a short CSAT survey after their first month. Focus: was onboarding intuitive? Does the platform meet expectations? Active associations get a biannual measurement. Short, respectful of the fact that these people are volunteers.
Financial institutions: implementation and operations. Entirely different flow. Tailored to the professional context. Measures satisfaction with setup, data quality, and ongoing operations. Quarterly relational measurement on top. Because when your customer is a bank, your feedback process needs to match their expectations for professionalism.
One dashboard, two perspectives. All data collected centrally, but filterable by segment. Leadership sees the full picture. The product team can drill into each segment's specific needs.
Feedback that steers the roadmap. When multiple customers point to the same thing, it gets prioritised. Development based on data, not whoever shouts loudest. It sounds simple. Yet it fundamentally changed how Unioo prioritises.
Startups tend to believe customer satisfaction measurement is for "when we've grown big enough." In fact, it's the opposite. During growth phase, feedback is most valuable because that's when you can still course-correct without it costing a fortune. Accordingly, Unioo started CSAT while still in early growth - and that meant they could fix mistakes quickly, before they scaled them.
Key Points:
A volunteer association chairman and a compliance officer at a bank have fundamentally different expectations. For instance, association people want usability and quick support. In contrast, banks want data security, uptime, and SLAs. Ask them the same questions, and you get data that's impossible to act on. Instead, separate flows with unified reporting gives the best of both worlds.
From day one. Not because you need perfect data immediately, but because otherwise you're building your product on assumptions. Indeed, Unioo started CSAT measurement while still in early growth phase - and that meant they could course-correct quickly. In other words, wait until you have 500 customers, and you've already built features nobody asked for.
We start with a conversation, not a sales pitch. For example, book a demo and let us look at your situation together.