Opportunity area · theme founders discuss · intermediate

Community opportunity: starting metalworking

Discussion · Starting metalworking: 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. Reject “for everyone in martech.” Original insight: community volume predicts attention, not willingness to pay—price a tiny pilot early.

Problem

People circling “starting metalworking” still run on inconsistent tools, DMs, and last-minute heroics. The cost is delay and rework, not a dramatic outage. Unexpected challenge: support load rises when it works—users shove messier edge cases into the pipe. Hidden cost: integration debt you promised in the pilot to win the logo.

Target user

PMs turning into founders in martech who feel “starting metalworking” as a weekly tax

Proposed solution

Own checklists, data shapes, and approval rules for this theme so switching costs are process depth, not chat novelty. Discussion-to-product bridge: turn the three most common thread questions into a checklist, then sell implementation help. Counter-intuitive advice: say no to custom work that does not teach the core path. Distribution bottleneck: cold outbound only works if the first sentence names “starting metalworking” in buyer language. One caution: avoid “platform” language in year one. Platforms are earned after a wedge works. One recommendation: open the [Idea database](/ideas) siblings for this theme (discussion / validation / distribution) and keep only the angle you can execute. Practical next step: sketch trigger → mess → your path → proof. If proof is vague, you still have a vibe. Real-world pattern: Shopify went deep on merchant workflows instead of being every app—depth beats horizontal novelty. Straight take: green-light only if you already have access to PMs turning into founders or a scar that makes “starting metalworking” personal. Cold pure-tech starts in noisy martech categories are a grind.