Opportunity area · theme founders discuss · intermediate

Community opportunity: thinking about designing framer templates

Discussion · Thinking about designing framer templates: if five strangers in martech tell the same war story, you have a theme; if they name the same workaround cost, you have a wedge. First metric beats first feature. Original insight: if onboarding costs more than the pain, you built a tutorial, not a company.

Problem

ex-agency builders describe the same loop: notice the mess late, patch it manually, promise a system later, repeat next month. Unexpected challenge: the economic buyer and the daily user disagree on what “done” means for “thinking about designing framer templates.” Hidden cost: rewriting the offer every week instead of iterating the same wedge.

Target user

Builders with domain scars related to “thinking about designing framer templates”

Proposed solution

If angle is validation: freeze features; maximize evidence. If distribution: freeze features; maximize channel reps. Discussion filter: if the thread is mostly status and jokes, demand is weak—move on. Counter-intuitive advice: shrink the ICP until it feels almost too small. Breadth is how clones are born. Distribution bottleneck: community fame without CRM hygiene is a leaky bucket. One caution: avoid “platform” language in year one. Platforms are earned after a wedge works. One recommendation: write a kill date on the calendar; themes expand forever, attention does not. Practical next step: identify one integration/import that makes this feel native to martech workflows. Real-world pattern: Notion stuck when teams refused to leave their system of record—aim for that habit depth on a smaller job. Straight take: keep the story small until numbers force it wider. Venture slides that promise to own all of martech are usually fiction.