Visual survey skin editor for business teams

The moment someone realizes they have a problem is when they export a survey link to send to customers and the survey looks like it was built in 2009 — wrong fonts, no logo, colors that clash with their brand — and they don't have time or patience to find the styling controls buried three menus deep.

This gap persists because survey tool vendors are primarily competing on logic features, integrations, and response limits. Styling is treated as table stakes, so it gets minimal engineering attention. The buyer — usually a CX manager or marketing lead — is often not the same person as the daily user, so the feedback that 'it looks childish' doesn't always surface loudly in sales conversations. The vendors have no structural incentive to overhaul something that doesn't directly drive churn numbers.

What existing tools get wrong for this exact case: the styling controls are there but they're scattered, the preview is small and doesn't reflect mobile rendering, and uploading a logo feels like a support ticket ('Some of the styling features could be easier and more intuitive, such as loading Logo files'). There's no way to save a brand kit — colors, fonts, logo — and apply it across all surveys in one click.

This is a business and not a feature because brand consistency is a recurring operational need. Every time a new survey is created — onboarding, NPS, event feedback, product research — someone has to re-apply styling manually or accept ugly defaults. A team that sends 20 surveys a year faces this 20 times. The cost is time plus the reputational risk of sending off-brand materials to customers or research participants. It recurs on every new survey, for every new team member who builds one.

What to build

Build a standalone survey skin editor where teams define a brand kit (logo, colors, fonts, button styles) once and export it as a CSS/embed config that injects into surveys built on the major survey platforms via a script tag or browser extension, without touching the survey tool's native editor.

Where to start

Start with a single survey platform that has a large user base and a known, stable DOM structure, and offer a free 'brand kit sync' for that platform specifically — so the first customers are self-selecting power users who already feel the pain acutely.

The hard part

Getting the CSS injection to work reliably across different survey platforms and their iframe sandboxing rules without breaking survey functionality is technically fragile — one platform update can silently break every styled survey a customer has deployed.

How it makes money

Monthly subscription per team, tiered by number of active surveys or number of brand kits; free tier limited to one brand kit and one platform to drive adoption.