Dashboard density configurator for data-heavy PM views

The frustration crystallizes when a team lead opens their project dashboard and has to scroll through three screens to see what should fit in one — or when they notice the screen is half empty while critical task data is buried below the fold. Complaints specifically call out 'excessive scrolling,' 'lot of white/empty space,' and a desire for 'more boxes, tags' in the space that's already there. This isn't a feature request for new data — it's a request to see existing data without fighting the layout.

This gap persists for a structural reason: project management tool vendors design their default layouts for the least sophisticated user — clean, spacious, non-threatening. That's the right call for onboarding. But power users, operations teams, and anyone managing more than 20 active items simultaneously are penalized by that same design philosophy for the entire lifecycle of their use. Vendors can't easily offer a 'density toggle' because it means maintaining two full UI states across every view, which is expensive engineering work that doesn't show up in feature comparison sheets.

The specific complaint about the parking lot view — where the cleaner older interface showed full item lists without scrolling — is telling. Users aren't asking for a better design philosophy; they want control over information density in specific views. Today, the only option is to export to a spreadsheet (if export is even available) and manage there — which breaks the workflow entirely.

This is a business because the need is recurring and role-specific. Operations managers, delivery leads, and PMO teams who live in these tools all day have a qualitatively different need from occasional users — and the tool's vendor is always going to optimize for the median user, not the power user. Anyone who has tried to manage 40+ active items in a spacious, whitespace-heavy UI knows the daily cost in scroll time and missed context. A tool that lets them compress views, pin the data they care about, and reduce the visual noise pays for itself in reclaimed attention.

What to build

Build a browser-based view configurator for specific project management tools that lets users define column density, item visibility rules, and tag display preferences per view — storing configurations per user or team and injecting them on page load without requiring vendor API access.

Where to start

Start with the single most complained-about view in one specific tool — the Aha! ideas parking lot, which users explicitly called out as worse after a UI update — and build one reliable, maintained density configuration for that exact screen before expanding to other views or tools.

The hard part

Without vendor cooperation, you're entirely dependent on DOM injection or browser extension architecture — which means a vendor's minor frontend update can silently break configurations overnight, and you have no warning before customers notice.

How it makes money

Team subscription at $30–$80/month for up to 10 users, with per-seat pricing above that — sold directly to PMO leads who can expense it without IT procurement involvement.