Plasmic's user base is in fact split about 50/50 designers/developers. And "visual CMS" exactly describes our most common use case—letting non-developers publish changes.

1. Developers can use it as a UI builder, removing the pain of things like CSS layout (for ex., we use Plasmic to build Plasmic; and engineers at companies small and large use it on their flagship websites/apps).

2. Designers versed in tools like Figma and Webflow are probably the segment with the highest "starting proficiency."

3. Currently Plasmic is most comfortable for designers and developers, but we very much want to accommodate the end-client persona (a "copy-only-mode" is on our roadmap).

Prioritization is heavily influenced by early users, so would love to hear your feedback on how this works for your team!