Weâre in the final testing phase of our platform (MK1) â it analyzes entire newsletter ecosystems and produces competitor insights automatically.
My CTO has a strong philosophy: âDoesnât matter how smart your backend is â if the UI doesnât make people feel like theyâre using something powerful, they wonât.â And honestly⊠heâs right. So before we push this out publicly, I wanted to get some honest feedback on the UI from founders, designers, newsletter operators, and copywriters who care about clean product experiences. Here are a few screens from the current build: (You can find 3 screenshots attached) đ Quick context (non-technical explanation): MK1 basically takes multiple newsletter issues â breaks them down into structured insights â and shows patterns across the entire niche. The UIâs job is to make all of that complexity feel simple. Some things the UI needs to communicate clearly: - Tone + intent of each issue - Niche-wide benchmarks - Issue-level metrics - Structure breakdowns (titles, sections, visuals, CTAs, etc.) - Engagement patterns (vs word count, vs structure) - Individual issue summaries - Consistency markers across creators The backend is⊠not small.Itâs a full distributed pipeline (scraping â TOON compression â issue-level LLM runs â aggregation), but none of that matters if the UI doesnât let people understand the story instantly. đ§ What Iâm specifically looking for feedback on: 1. Does it feel intuitive at first glance? 2. Are the insights easy to digest, or does it feel âdashboard complicatedâ? 3. Which parts feel unnecessary or too heavy? 4. Do the cards/graphs help or distract? 5. Does this UI make you want to explore deeper? 6. If you ran a newsletter or content team, would this type of layout actually help you? Weâre still tweaking visual hierarchy, spacing, and how much data to surface at once â so Iâm open to brutal honesty. đŹ The bigger question (UI philosophy): Do you think products like this succeed because of UI,or despite it? Some founders believe âif the model is good, UI is secondary.âMy CTO believes the UI is the major part of a product, and everything else is invisible unless the UI communicates it well.