Roast my tiny Pinterest-to-Miro app before I talk myself into making it bigger

[u/Plastic_Catch1252]

Product: a small Miro app that turns a Pinterest board into a Miro moodboard. The use case is for people who collect references in Pinterest, then need to discuss or organize them in Miro.

Market: I think the real users are designers, brand teams, researchers, planners, and maybe agencies. I do not know if that is a real market or just a workflow itch inside a small group of people.

Competition: mostly manual copy/paste, screenshots, leaving the Pinterest board open in another tab, or rebuilding the board inside Miro by hand. The risk is that this should just be a tiny native Miro feature, not a standalone thing.

Stage: built and listed in the Miro Marketplace. Not raising money. I am trying to figure out if the narrow pain is worth pushing harder, or if I am overvaluing a task that only annoys me.

Customer conversion: find people already complaining about reference cleanup, moodboards, Pinterest boards, Miro boards, or moving visual research between tools. If they already describe the problem in their own words, then show the app. If they do not, I probably should not try to create the pain for them.

Why me: I built it because I kept seeing this handoff in planning and visual work. No special founder story. Just close enough to the workflow to notice the boring manual step.

Roast the weak parts. Is this a real workflow problem, or just a convenience? Does "Pinterest to Miro moodboards" sound clear, or does it sound too tiny to care about?

[u/Dull-Leg-3678]

The biggest red flag is you're solving a workflow problem for like 12 people who happen to use both Pinterest AND Miro regularly - most designers I know either live in one tool or have already figured out their own janky workaround that works fine.