Opportunity area · theme founders discuss · intermediate

Distribution approach for starting tea

Distribution · Starting tea spreads when the artifact (checklist, report, invite, invoice) pulls the next user—not when the landing page gets adjectives. Industry pocket: proptech. Original insight: if onboarding costs more than the pain, you built a tutorial, not a company.

Problem

In proptech, the default stack almost works—until “starting tea” forces spreadsheet archaeology and Slack archaeology at the worst moment. Unexpected challenge: pulling clean context out of the buyer’s existing tools takes longer than the first UI. Hidden cost: content that educates competitors while never converting readers into calls.

Target user

Builders with domain scars related to “starting tea”

Proposed solution

Run a concierge cohort first. Deliver the result manually, log every exception, automate only what repeated three times. Distribution sprint (30 days): one channel, daily reps, weekly conversion review. Features only if activation is already clear. Counter-intuitive advice: shrink the ICP until it feels almost too small. Breadth is how clones are born. Distribution bottleneck: marketplaces and app directories tax you twice—once in fees, once in attention. One caution: shipping unreliable automation in a trust-sensitive job burns the only channel that mattered. One recommendation: ship a concierge version, log exceptions, automate only the repeats. Practical next step: rewrite the offer in one sentence without “platform,” “ecosystem,” or “AI-powered.” Real-world pattern: Stripe won by removing friction on a job merchants already had—copy the posture, not the category. Straight take: one paid pilot beats a polished multi-feature build with zero distribution reps.