The moment this becomes a real problem: an analyst has a specific visualization in mind — say, a layered area chart with custom color bands representing thresholds, or a geographic heat map using internal region codes — and after an hour of fighting with their analytics platform's chart editor, they realize the tool simply cannot produce it. The choice is now to either ship a worse chart or spend two days building something custom in code.
This gap persists for a structural reason: analytics platforms compete on data connectivity and governance, not on design tooling. Their chart editors are built to be 'good enough for most people' because the platforms are sold to data infrastructure teams who evaluate them on uptime, connector count, and row-level security — not on whether a marketing analyst can style a gradient correctly. The people who feel the visualization pain most acutely (analysts, data storytellers, product managers building internal tools) have no voice in procurement.
What users describe isn't just 'more chart types' — it's the combination of missing types and missing control. 'Poor graphical customization on graphs', 'the visualization is not very interactive', 'can't always create what I have in mind' — these are people who know exactly what they want and are blocked by a rigid editor. A visual chart builder that works outside the analytics platform, lets someone configure exactly the chart they want with real styling controls, and then exports it as a reusable component or data definition that can be dropped back into the analytics environment solves this without requiring anyone to abandon their existing stack.
This is a business because every new report, every new stakeholder request, every quarterly business review is a fresh opportunity to hit the same ceiling. Analysts don't switch platforms over this — they suffer through it repeatedly. That recurring friction, multiplied across a team of ten analysts each hitting it monthly, adds up to real hours. The buyer is a data team lead who is tired of hearing 'we can't make it look like that' from their team.
What to build
Build a browser-based chart configuration tool where analysts design charts using a visual editor with full styling control, then export the chart as a Vega-Lite spec or platform-specific plugin file that can be imported directly into Superset or rendered as a standalone embed elsewhere.
Where to start
Launch exclusively with Vega-Lite export first, since Superset natively supports Vega-Lite charts — this gives you a working end-to-end story for one platform without needing custom integration work, and Superset's open-source community is searchable and reachable.
The hard part
The export compatibility problem is brutal early on — each target platform has a different plugin or custom visual format, and supporting even two of them properly before launch means significant format-specific engineering work with little overlap.
How it makes money
Free for individual use with watermarked exports; team plan charged per seat per month that unlocks full styling controls, export to multiple formats, and a shared chart template library.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Analytics Platforms.
More ideas in Analytics Platforms