Opportunity area · theme founders discuss · intermediate

Community opportunity: days

Discussion · Days shows up when developers with a domain scar describe a weekly mess nobody productized cleanly in martech. Industry pocket: martech. Original insight: the unfair advantage is usually access (scars, audience, data)—not a clever name.

Problem

Buyers already tried freelancers, generic SaaS, and internal scripts. They still cannot get a repeatable outcome on this theme without a specialist babysitting the process. Unexpected challenge: support load rises when it works—users shove messier edge cases into the pipe. Hidden cost: content that educates competitors while never converting readers into calls.

Target user

developers with a domain scar in martech who feel “days” as a weekly tax

Proposed solution

Treat “days” as one path: intake → decision → output for a single ICP in martech. Charge for the outcome, not “platform access.” Discussion-to-product bridge: turn the three most common thread questions into a checklist, then sell implementation help. Counter-intuitive advice: fewer “would you use this?” chats; more reconstructions of last week’s failed attempt at “days.” Distribution bottleneck: cold outbound only works if the first sentence names “days” in buyer language. One caution: multi-angle roadmaps (discussion + validation + distribution at once) create thrash—pick one mode this month. One recommendation: define one success metric, put it on a one-page offer, and reject scope that does not move it. Practical next step: schedule the next user call before the next coding session. 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: one paid pilot beats a polished multi-feature build with zero distribution reps.