The dashboard that nearly didn't happen

The moment we realised dashboards weren't optional

Mobile app studios aren't like SaaS companies with one product. A studio founder running two, five, or ten apps lives in a different universe. They need to see patterns across their entire portfolio. Are voters consistent? Do certain feature requests matter to the whole user base, or just one app?

The problem was that existing tools like Canny treated each app as a silo. You could log in, see votes for App A, log out, log into App B, see votes there. But you'd never see that the same person voted for 'dark mode' in three different apps. You'd never know if a feature request was genuinely popular across your portfolio or just loud in one corner.

I remembered that message for weeks. A founder shouldn't have to guess. He should be able to sit down with five minutes before a product meeting and know exactly what his users want, and whether they want it consistently.

Building for founders who don't have time for dashboards

We knew our dashboard had to be different from the usual 'more data, more options' trap. Founder time is scarce. If the dashboard required setup, configuration, or interpretation, it would sit unused.

So we started with a single question: what must a founder know the moment she logs in? Not what could she know. What must she know.

The answer was: How many voters does she have across all apps? What are the top features being voted on right now, and are they the same across apps or fragmented? Which features actually shipped, and did voters get notified? Are voters engaged, or are signups stalling?

We built the dashboard to show those four things instantly. No custom filters to fiddle with. No date-range pickers. Your portfolio summary appears the moment you land. Below that, you see your top features, ranked by cross-app momentum. If a feature shipped, it lights up. If voters got their push notification, you see that too.

The analytics feed pulls from every app in your portfolio using Shpd's Passport system. That's our cross-app voter identity layer. One person, one vote count, visible across your entire studio. It made all the difference.

What we almost got wrong

Early versions of the dashboard had dozens of toggles. Export features. Custom date ranges. Advanced filtering. Heat maps. I built features I thought a founder might want, not features a founder actually needed.

Then we put it in front of five studio founders. Not one of them touched the advanced filters. All five went straight to the main summary and the top features list. One founder spent 90 seconds on the dashboard, found what she needed, and left.

That taught me something. Founders don't want to become data analysts. They want insight delivered. Not raw data with a promise that meaningful patterns might exist if they dig hard enough.

We cut the advanced filters. Kept the basics. The dashboard now shows you what matters, fast. If you want deeper analysis, the data is there in the API for studios on Scale and Portfolio plans. But the default experience is clarity, not choice.

The studio fleeing Canny that changed our roadmap

Around the time we finalised the dashboard, Canny announced their December 2025 price change. A lot of studios woke up to bills tripling overnight. We started hearing from teams that had used Canny for years, happy until the invoice came.

One of them, a studio with 12 apps, sent us a message. They loved Canny's interface, they said, but they needed a tool built for their world. Multiple apps. One voter identity across all of them. And a dashboard that told them something useful, not just pretty graphs.

That studio landed on Shpd with Studio plan and grew to Scale within three months. Their founder told me the dashboard was the reason. Not because it was feature-rich, but because it was honest. It showed her exactly what her users wanted, without making her guess or dig.

That migration taught us that clarity wins over complexity. Always.

Why Passport matters to every number on that dashboard

The founder web dashboard only works because of what happens behind it. Passport, our cross-app voter identity system, matches voters across your entire portfolio automatically. When someone votes on a feature in App A and then votes on a different feature in App B, Shpd knows they're the same person.

Without that layer, a dashboard is just six silo views stitched together. With it, you see genuine portfolio sentiment. You see which features matter to your entire user base, not just the loudest subset in one app.

That's why we built the iOS and Android SDKs as native libraries, not web forms. Users vote inside your app, where they already are. Passport captures that vote, tags it with the voter's identity, and feeds it into the portfolio. The dashboard lights up with real signal, not guesses.

What happens the day after a feature ships

Here's a detail people often overlook. Shipping a feature is only half the story. The voters who requested it need to know it landed.

In the dashboard, you mark a feature as shipped. Shpd sends a push notification to every voter who backed that feature, in their native app. They see exactly what you promised and what they got. That moment matters. It closes the loop.

Studios using the dashboard tell us that shipped features and their notifications are the part that build loyalty. Voters feel heard. They come back to request more features. The feedback loop becomes real.

The dashboard shows you this too. You can see which features you shipped last quarter and how many voters got notified. It's a reminder that feature voting isn't about winning arguments inside your product team. It's about listening to your users and proving you listened by shipping.