# Revenue Pipeline Outreach Targets

Status: current
Updated: 2026-05-04T19:52:57.729Z

This file mirrors the evidence-backed GTM queue in `docs/marketing/gtm-target-queue.jsonl`.
It is the qualification screen and send surface for the current Workflow Hardening Sprint revenue loop, not a raw GitHub scrape.

## Current Queue
- Revenue state: post-first-dollar
- Headline: Verified booked revenue exists. Keep selling one concrete Workflow Hardening Sprint first, then route self-serve buyers to Pro.
- Follow-ups now: 0
- Warm discovery ready: 4
- Self-serve closes ready: 3
- Cold GitHub ready: 9
- Sales ledger tracked leads: 18
- Proof rule: Use proof links only after the buyer confirms the workflow pain.

## Qualification Rules
1. One workflow with business value.
2. One buyer or champion who owns the rollout.
3. One repeated failure pattern or rollout blocker that is expensive to repeat.

## Follow Up Now
- No in-flight follow-ups are currently tracked.

## Warm Discovery
### 1. Deep_Ad1959 — r/cursor
- Temperature: warm
- Current stage: targeted
- Contact surface: https://www.reddit.com/user/Deep_Ad1959/
- Evidence score: 10
- Evidence: warm inbound engagement, workflow pain named: rollback risk, already in DMs
- Why now: Warm Reddit engager already named a repeated workflow risk, so the fastest path is a founder-led diagnostic.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Your question about rollback rates when context changes is exactly the right one. I am looking for one AI-agent workflow to harden end-to-end this week: repeated failure, prevention rule, and proof run. If you have one workflow where context drift or rollback risk keeps showing up, I can harden that workflow for you. Worth a 15-minute diagnostic?

Pain-confirmed follow-up:
> If your workflow really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'reddit_deep_ad1959_r_cursor' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on rollback risk.'`

### 2. game-of-kton — r/cursor
- Temperature: warm
- Current stage: targeted
- Contact surface: https://www.reddit.com/user/game-of-kton/
- Evidence score: 9
- Evidence: warm inbound engagement, built serious memory systems, workflow pain named: stale context and conflicting facts
- Why now: Warm Reddit engager already works on advanced agent memory, so discovery should center on one repeated failure pattern.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Your ACT-R engram work is fascinating, especially the conflict resolution for opposing facts and the decay model. I am looking for one serious AI-agent workflow to harden end-to-end this week. If your memory system has one recurring failure mode such as stale context, opposing facts, bad handoffs, or unsafe tool calls, I can turn that into a prevention rule and proof run. Open to a 15-minute diagnostic?

Pain-confirmed follow-up:
> If your workflow really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'reddit_game_of_kton_r_cursor' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on stale context and conflicting facts.'`

### 3. leogodin217 — r/ClaudeCode
- Temperature: warm
- Current stage: targeted
- Contact surface: https://www.reddit.com/user/leogodin217/
- Evidence score: 9
- Evidence: warm inbound engagement, mature multi-step workflow described, workflow pain named: review boundaries and context risk
- Why now: Warm Reddit engager already described a mature workflow, so the next step is a targeted diagnostic on one failure mode.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Your arch-create to sprint workflow is one of the most mature agent processes I have seen anyone describe. I am looking for one AI-agent workflow to harden end-to-end this week. Your workflow already has phases, review boundaries, and context risk, so it is a strong fit: pick one repeating failure and I will help turn it into an enforceable Pre-Action Check plus proof run. Worth 15 minutes?

Pain-confirmed follow-up:
> If your workflow really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'reddit_leogodin217_r_claudecode' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on review boundaries and context risk.'`

### 4. Enthu-Cutlet-1337 — r/ClaudeCode
- Temperature: warm
- Current stage: targeted
- Contact surface: https://www.reddit.com/user/Enthu-Cutlet-1337/
- Evidence score: 8
- Evidence: warm inbound engagement, responded to adaptive-gate positioning, workflow pain named: brittle guardrails
- Why now: Warm Reddit engager already understands the adaptive-gate thesis, so offer one concrete workflow hardening diagnostic.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Appreciate the kind words on the Thompson Sampling approach. You nailed the core insight: most guardrails are brittle prompt hacks that break when context shifts. I am looking for one AI-agent workflow to harden end-to-end this week: repeated failure, prevention rule, and proof run. If you have a workflow where brittle guardrails keep failing, I can harden that workflow with you. Open to a 15-minute diagnostic?

Pain-confirmed follow-up:
> If your workflow really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'reddit_enthu_cutlet_1337_r_claudecode' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on brittle guardrails.'`

## Self-Serve Closes
### 1. agynio — gh-pr-review
- Temperature: cold
- Current stage: targeted
- Contact surface: https://agyn.io/
- Evidence score: 15
- Evidence: workflow control surface, business-system integration, self-serve agent tooling, 144 GitHub stars, updated in the last 7 days
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- CTA: https://thumbgate-production.up.railway.app/guide

First-touch draft:
> Hey @agynio, saw you're building around `gh-pr-review`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

Pain-confirmed follow-up:
> If you want the self-serve path for `gh-pr-review`, here is the live Pro checkout: https://thumbgate-production.up.railway.app/checkout/pro Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_agynio_gh_pr_review' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 2. greenpolo — cc-multi-cli-plugin
- Temperature: cold
- Current stage: targeted
- Contact surface: https://github.com/greenpolo
- Evidence score: 14
- Evidence: workflow control surface, business-system integration, self-serve agent tooling, 72 GitHub stars, updated in the last 7 days
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- CTA: https://thumbgate-production.up.railway.app/guide

First-touch draft:
> Hey @greenpolo, saw you're building around `cc-multi-cli-plugin`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

Pain-confirmed follow-up:
> If you want the self-serve path for `cc-multi-cli-plugin`, here is the live Pro checkout: https://thumbgate-production.up.railway.app/checkout/pro Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_greenpolo_cc_multi_cli_plugin' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 3. levnikolaevich — claude-code-skills
- Temperature: cold
- Current stage: targeted
- Contact surface: https://levnikolaevich.com/
- Evidence score: 14
- Evidence: workflow control surface, agent infrastructure, self-serve agent tooling, 447 GitHub stars, updated in the last 7 days
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- CTA: https://thumbgate-production.up.railway.app/guide

First-touch draft:
> Hey @levnikolaevich, saw you're building around `claude-code-skills`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

Pain-confirmed follow-up:
> If you want the self-serve path for `claude-code-skills`, here is the live Pro checkout: https://thumbgate-production.up.railway.app/checkout/pro Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_levnikolaevich_claude_code_skills' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on the proof-backed setup guide and local-first enforcement before any team-motion pitch.'`

## Cold GitHub
### 1. montenegronyc — backporcher
- Temperature: cold
- Current stage: targeted
- Contact surface: https://numberfortyeight.co/
- Evidence score: 17
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, 13 GitHub stars, updated in the last 7 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @montenegronyc, saw you're shipping `backporcher`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `backporcher` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_montenegronyc_backporcher' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 2. Abhi268170 — Stagix
- Temperature: cold
- Current stage: targeted
- Contact surface: https://github.com/Abhi268170
- Evidence score: 15
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, self-serve agent tooling
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @Abhi268170, saw you're shipping `Stagix`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `Stagix` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_abhi268170_stagix' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 3. Adqui9608 — ai-code-review-agent
- Temperature: cold
- Current stage: targeted
- Contact surface: https://github.com/Adqui9608
- Evidence score: 15
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, updated in the last 7 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @Adqui9608, saw you're shipping `ai-code-review-agent`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `ai-code-review-agent` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_adqui9608_ai_code_review_agent' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 4. dolutech — engine_context
- Temperature: cold
- Current stage: targeted
- Contact surface: https://dolutech.com/
- Evidence score: 15
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, 8 GitHub stars
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @dolutech, saw you're shipping `engine_context`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `engine_context` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_dolutech_engine_context' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 5. kamaldhingra — AI-Agents-QA-Automation
- Temperature: cold
- Current stage: targeted
- Contact surface: https://github.com/kamaldhingra
- Evidence score: 15
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, updated in the last 7 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @kamaldhingra, saw you're shipping `AI-Agents-QA-Automation`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `AI-Agents-QA-Automation` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_kamaldhingra_ai_agents_qa_automation' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 6. borghei — Claude-Skills
- Temperature: cold
- Current stage: targeted
- Contact surface: https://borghei.me/
- Evidence score: 14
- Evidence: production or platform workflow, agent infrastructure, self-serve agent tooling, 106 GitHub stars, updated in the last 7 days
- Why now: Lead with rollout proof for one production workflow that cannot afford repeated agent mistakes.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @borghei, saw you're shipping `Claude-Skills`. If one deploy, release, or incident workflow keeps needing extra guardrails, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `Claude-Skills` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_borghei_claude_skills' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on rollout proof for one production workflow that cannot afford repeated agent mistakes.'`

### 7. nihannihu — Omni-SRE
- Temperature: cold
- Current stage: targeted
- Contact surface: https://github.com/nihannihu
- Evidence score: 14
- Evidence: workflow control surface, production or platform workflow, business-system integration, agent infrastructure, updated in the last 30 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @nihannihu, saw you're shipping `Omni-SRE`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `Omni-SRE` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_nihannihu_omni_sre' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 8. DGouron — review-flow
- Temperature: cold
- Current stage: targeted
- Contact surface: https://dgouron.fr/
- Evidence score: 13
- Evidence: workflow control surface, business-system integration, agent infrastructure, 36 GitHub stars, updated in the last 30 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @DGouron, saw you're shipping `review-flow`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `review-flow` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_dgouron_review_flow' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

### 9. freema — mcp-jira-stdio
- Temperature: cold
- Current stage: targeted
- Contact surface: http://www.tomasgrasl.cz/
- Evidence score: 13
- Evidence: workflow control surface, business-system integration, agent infrastructure, 12 GitHub stars, updated in the last 7 days
- Why now: Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

First-touch draft:
> Hey @freema, saw you're shipping `mcp-jira-stdio`. If one approval, handoff, or rollback step keeps creating trouble, I can harden that workflow for you with a prevention gate and proof run: https://thumbgate-production.up.railway.app/#workflow-sprint-intake

Pain-confirmed follow-up:
> If `mcp-jira-stdio` really has one repeated workflow failure blocking rollout, I can send the Workflow Hardening Sprint brief plus the commercial truth and verification evidence: https://thumbgate-production.up.railway.app/#workflow-sprint-intake Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

Track next step: `npm run sales:pipeline -- advance --lead 'github_freema_mcp_jira_stdio' --channel 'manual' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

## Core Links
- Sprint intake: https://thumbgate-production.up.railway.app/#workflow-sprint-intake
- Proof-backed setup guide: https://thumbgate-production.up.railway.app/guide
- Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md
- Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
