User expresses a need for a lightweight system to help run follow-up sequences, as they struggle with inconsistent follow-ups and losing deals.
Most early GTM advice starts with tactics. Write better outbound. Post more. Run ads. Clean up your ICP. Pick a CRM. Automate follow-ups. I’m experimenting with a different order of operations—because tactics only work when they match the playing field. So I’m building a daily signal log from founder/sales communities. The goal isn’t to collect “hot takes.” It’s to build a map: what people are actually trying to do, where they’re getting stuck, and what that implies strategically. This is Day 1. --- ## What showed up (the field, not the playbook) The loudest cluster wasn’t about copywriting, positioning, or cold email. It was operational failure. The biggest theme by far was **Spreadsheet/Zapier workflow failure** — the “GTM glue stack” that looks like forms → Google Sheets → Zapier → Slack/email. People are using it to route inbound leads and track pipeline, and it’s breaking often enough to create a very specific fear: > “I’m losing leads and I won’t even know it.” Around that were smaller but revealing clusters: - **AI for GTM tooling** (personalization, lead gen, follow-ups) - **Founder-led sales discomfort** (follow-ups, rejection, the “we keep building instead of selling” loop) - **Tool shopping** (“what do you use instead?” decision windows) - Early “upmarket pressure”: **pricing** and **SOC2** questions --- ## The playing field: what teams seem to be optimizing for Zooming out, Day 1 rhymed around three constraints: 1) **Reliability** (can I trust the revenue motion?) 2) **Cognitive load** (can I keep operating without breaking?) 3) **Credibility** (do I look ready for the next league?) --- ## Pain hypotheses (testable claims, not conclusions) ### 1) Reliability is the wedge **Claim:** Founders will switch/pay for *lead-loss prevention + auditability* before they pay for feature depth. **Voice of the user:** - “Anyone using Zapier for lead routing? It’s breaking. We’re routing inbound leads into Sheets + email using Zapier. It breaks weekly and leads slip. What do you use instead?” - “We’re pushing leads between forms → Sheets → Slack → email. Zapier is flaky and expensive. What do you use?” - “Anyone using Google Sheets for pipeline and it’s a mess? We’re tracking pipeline in Sheets.” **Falsifier:** If your current system dropped 5% of leads silently, how would you detect it? ### 2) Follow-up failure is emotional + operational **Claim:** The constraint isn’t only reminders—it’s avoidance, context loss, and fatigue. **Voice of the user:** - “Follow-ups take forever. I forget threads. Any AI to help run follow-up sequences?” - “My follow-ups are inconsistent and I lose deals. What’s a lightweight system that works?” - “We keep building and not selling. How do you break the loop? We default to building because it’s safe. Sales feels like rejection.” **Falsifier:** What’s harder: knowing the next step, or making yourself do it? ### 3) Credibility pressure shows up earlier than expected **Claim:** SOC2 and enterprise pricing questions are often proxies for “are we legit?” **Voice of the user:** - “Prospects ask about SOC2. We don’t have it. Does it block deals? What did you do?” - “We have 2 pilots. Enterprise prospects ask for pricing but we have no idea. How do you set pricing without anchoring too low?” **Falsifier:** Was compliance/pricing truly the blocker—or did you lose confidence and slow down the deal? --- ## Methods & practices (short) - I collect real prompts from founder/sales communities and **preserve the exact wording**. - I tag each signal (persona, workflow, tools, urgency) and **cluster repeating themes**. - I use JTBD (**functional / social / emotional**) to identify what’s really being “hired.” - I turn clusters into **pain hypotheses** (testable claims), then publish: **constraints → pain hypotheses → tomorrow’s tests**. - This is **iterative field research**, not a representative survey. --- ## Question Where does your system fail first: **capture**, **routing**, **assignment**, **follow-up**, or **status tracking**? (Posted by Jonathan Colton / distribution coach. I’m iterating this format daily.)