# Roo Sunset Demand Pack

Updated: 2026-05-04T15:13:16.404Z

This is a sales operator artifact. It is not proof of sent outreach, installs, paid revenue, or partner approval by itself.

## Objective
Turn Roo shutdown urgency into tracked migration clicks, proof-backed setup demand, and paid intent without inventing traction.

## Positioning
- State: post-first-dollar
- Headline: Turn Roo shutdown urgency into memory-portable paid intent.
- Short description: ThumbGate gives Roo migrants one durable asset to keep: local lesson memory that survives the move to Cline and becomes enforceable Pre-Action Checks.
- Summary: Verified booked revenue exists. Keep selling one concrete Workflow Hardening Sprint first, then route self-serve buyers to Pro.

## Canonical Identity
- Display name: ThumbGate
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- Homepage: https://thumbgate-production.up.railway.app
- 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

## Demand Surfaces
### Roo shutdown notice
- Buyer signal: Roo users facing a hard May 15, 2026 shutdown who need a successor and a way to keep lesson memory.
- Operator use: Use as the time-bound trigger only to establish why Roo users need a migration path now.
- Surface URL: https://docs.roocode.com/
- Support: https://roocode.com/blog/sunsetting-roo-code-extension-cloud-and-router
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### ThumbGate Roo migration guide
- Buyer signal: Roo users who have not yet accepted the successor path and need a migration rationale before they ask for the exact install doc.
- Operator use: Primary first-touch surface when the buyer needs the migration story, the successor recommendation, and the next install step in one owned page.
- Surface URL: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_migration_guide&utm_content=guide&campaign_variant=owned_surface&offer_code=ROO-MIGRATION_GUIDE&cta_id=roo_migration_guide&cta_placement=pack_surface&surface=roo_migration
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/adapters/cline/INSTALL.md
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Cline install guide
- Buyer signal: Roo users who already accepted Cline as the successor and want the shortest install path plus local memory continuity.
- Operator use: Use after the owned migration guide lands and the buyer asks for the exact install path.
- Surface URL: https://github.com/IgorGanapolsky/ThumbGate/blob/main/adapters/cline/INSTALL.md?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_cline_install&utm_content=install_doc&campaign_variant=migration_path&offer_code=ROO-CLINE_INSTALL&cta_id=roo_cline_install&cta_placement=pack_surface&surface=roo_migration
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/adapters/cline/INSTALL.md
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Proof-backed setup guide
- Buyer signal: Operators who want a clean self-serve path and only then want the paid lane.
- Operator use: Use after the migration story lands and the buyer wants proof, install clarity, and pricing guardrails.
- Surface URL: https://thumbgate-production.up.railway.app/guide?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_setup_guide&utm_content=setup&campaign_variant=proof_backed_setup&offer_code=ROO-SETUP_GUIDE&cta_id=roo_setup_guide&cta_placement=pack_surface&surface=roo_migration
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/public/guide.html
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Verification evidence
- Buyer signal: Pain-confirmed Roo migrants who need evidence before choosing Pro or a workflow sprint.
- Operator use: Send only after the buyer confirms the workflow pain or asks for proof and commercial truth.
- Surface URL: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

## Follow-On Offers
- ThumbGate Pro: $19/mo or $149/yr
  Buyer: Solo Roo migrants who want the self-serve dashboard, proof-ready exports, and local-first lesson continuity after the Cline move.
  CTA: https://thumbgate-production.up.railway.app/checkout/pro?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_follow_on_pro&utm_content=pro&campaign_variant=self_serve_follow_on&offer_code=ROO-FOLLOW_ON_PRO&cta_id=roo_follow_on_pro&cta_placement=post_install&plan_id=pro&surface=roo_follow_on
- Workflow Hardening Sprint: Intake-led sprint, then Team at $49/seat/mo with 3-seat minimum after qualification
  Buyer: Teams that already know their Roo migration touches one production workflow with approval boundaries, rollback risk, or bad handoffs.
  CTA: https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_follow_on_sprint&utm_content=workflow_sprint&campaign_variant=team_follow_on&offer_code=ROO-FOLLOW_ON_SPRINT&cta_id=roo_follow_on_sprint&cta_placement=post_install&surface=roo_follow_on#workflow-sprint-intake

## Operator Queue
### Roo user who needs lesson memory to survive the move to Cline
- Evidence: Roo officially documents the May 15, 2026 shutdown and recommends Cline as the open-source successor. ThumbGate already ships the Cline install guide and keeps lessons in a local SQLite file.
- Proof trigger: They can name one correction from Roo they do not want to reteach after migrating.
- Proof asset: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline
- Next ask: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_queue_guide&utm_content=guide&campaign_variant=memory_migrant&offer_code=ROO-QUEUE_GUIDE&cta_id=roo_queue_guide&cta_placement=operator_queue&surface=roo_migration
- Recommended motion: Roo migration guide -> Cline install guide -> setup guide -> Pro only after one saved correction is concrete.

### Team migrating one risky workflow off Roo
- Evidence: 6 workflow-control target(s), 3 business-system target(s), and 7 sprint-fit target(s) already favor workflow hardening over a generic plugin pitch.
- Proof trigger: They can point to one approval boundary, rollback risk, or repo workflow that cannot afford repeated mistakes during migration.
- Proof asset: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Next ask: https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_queue_sprint&utm_content=workflow_sprint&campaign_variant=migration_workflow&offer_code=ROO-QUEUE_SPRINT&cta_id=roo_queue_sprint&cta_placement=operator_queue&surface=roo_outreach#workflow-sprint-intake
- Recommended motion: Workflow Hardening Sprint first. Use proof only after the workflow risk is explicit.

### Local-first buyer who wants the tool path before founder-led help
- Evidence: 3 self-serve target(s) in the live queue already skew toward guide-first evaluation once the migration urgency is understood.
- Proof trigger: They ask for install, pricing, or the dashboard path instead of workflow consulting.
- Proof asset: https://thumbgate-production.up.railway.app/guide
- Next ask: https://thumbgate-production.up.railway.app/guide?utm_source=roo_sunset&utm_medium=migration_pack&utm_campaign=roo_queue_guide&utm_content=setup&campaign_variant=self_serve_interest&offer_code=ROO-QUEUE_GUIDE&cta_id=roo_queue_guide&cta_placement=operator_queue&surface=roo_migration
- Recommended motion: Setup guide -> commercial truth -> Pro after the buyer asks for the tool path.

## Outreach Drafts
### GitHub DM or founder reply — Roo user who wants their corrections to survive the move to Cline
Roo can sunset. Your lesson memory should not. The clean first step is the migration guide: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_outreach_guide&utm_content=guide&campaign_variant=memory_migrant&offer_code=ROO-OUTREACH_GUIDE&cta_id=roo_outreach_guide&cta_placement=outreach_draft&surface=roo_outreach . It explains the Cline successor path, why portable lesson memory matters, and where the exact install doc lives when they are ready.

### Pain-confirmed follow-up — Buyer who already named one repeated workflow failure
Once the migration risk is concrete, move from urgency to proof. Send Verification Evidence plus Commercial Truth first: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md and https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md . If they want the self-serve lane, use https://thumbgate-production.up.railway.app/guide?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_outreach_guide&utm_content=guide&campaign_variant=proof_backed_setup&offer_code=ROO-OUTREACH_GUIDE&cta_id=roo_outreach_guide&cta_placement=outreach_draft&surface=roo_outreach then https://thumbgate-production.up.railway.app/checkout/pro?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_outreach_pro&utm_content=pro&campaign_variant=self_serve_follow_on&offer_code=ROO-OUTREACH_PRO&cta_id=roo_outreach_pro&cta_placement=outreach_draft&plan_id=pro&surface=roo_outreach . If they want help hardening one workflow before rollout, route them to https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_outreach_sprint&utm_content=workflow_sprint&campaign_variant=migration_workflow&offer_code=ROO-OUTREACH_SPRINT&cta_id=roo_outreach_sprint&cta_placement=outreach_draft&surface=roo_outreach#workflow-sprint-intake .

### Founder note — Team owner migrating one production workflow off Roo
A Roo-to-Cline move is not the hard part. Keeping one risky workflow from relearning the same repo, approval, or rollback mistake is the hard part. If that workflow already exists on your side, use the Workflow Hardening Sprint intake here: https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=operator_outreach&utm_campaign=roo_outreach_sprint&utm_content=workflow_sprint&campaign_variant=migration_workflow&offer_code=ROO-OUTREACH_SPRINT&cta_id=roo_outreach_sprint&cta_placement=outreach_draft&surface=roo_outreach#workflow-sprint-intake .

## Active Channel Drafts
### Reddit — Migration post
- Audience: Roo user evaluating Cline as the successor
- Evidence: The public Roo shutdown notice creates urgency, but the strongest first-touch angle is still memory portability rather than abstract governance.
- CTA: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=reddit_post&utm_campaign=roo_channel_reddit&utm_content=guide&campaign_variant=memory_portability&offer_code=ROO-CHANNEL-REDDIT&cta_id=roo_channel_reddit&cta_placement=channel_draft&surface=roo_reddit
- Proof timing: Lead with the migration path first. Hold proof links for replies or DMs after the buyer names the repeated mistake.
Roo sunsets on May 15, 2026. Cline is the obvious successor, but the real migration question is whether your agent keeps its corrections. ThumbGate keeps those lessons in a local SQLite file so the move is not “reteach everything from scratch.” Migration guide: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=reddit_post&utm_campaign=roo_channel_reddit&utm_content=guide&campaign_variant=memory_portability&offer_code=ROO-CHANNEL-REDDIT&cta_id=roo_channel_reddit&cta_placement=channel_draft&surface=roo_reddit .

### LinkedIn — Founder post
- Audience: Platform or AI-product lead migrating one workflow off Roo
- Evidence: 7 sprint-fit target(s) plus 3 business-system target(s) make workflow-risk migration the strongest B2B Roo angle.
- CTA: https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=linkedin_post&utm_campaign=roo_channel_linkedin&utm_content=workflow_sprint&campaign_variant=migration_workflow&offer_code=ROO-CHANNEL-LINKEDIN&cta_id=roo_channel_linkedin&cta_placement=channel_draft&surface=roo_linkedin#workflow-sprint-intake
- Proof timing: Public post can reference the shutdown, but hold proof links until the buyer confirms one workflow risk.
Roo shutting down is a forcing function, not the real problem. The real problem is migrating one live workflow without reteaching approval boundaries, rollback rules, and repo-specific mistakes from zero. If your team already has that workflow in mind, start with the Workflow Hardening Sprint here: https://thumbgate-production.up.railway.app/?utm_source=roo_sunset&utm_medium=linkedin_post&utm_campaign=roo_channel_linkedin&utm_content=workflow_sprint&campaign_variant=migration_workflow&offer_code=ROO-CHANNEL-LINKEDIN&cta_id=roo_channel_linkedin&cta_placement=channel_draft&surface=roo_linkedin#workflow-sprint-intake .

### Threads — Short post
- Audience: Solo Roo builder who wants the cleanest self-serve move
- Evidence: 3 current self-serve target(s) already support a guide-first motion once the buyer accepts the memory-portability story.
- CTA: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=threads_post&utm_campaign=roo_channel_threads&utm_content=guide&campaign_variant=proof_backed_setup&offer_code=ROO-CHANNEL-THREADS&cta_id=roo_channel_threads&cta_placement=channel_draft&surface=roo_threads
- Proof timing: Keep first touch on the Roo-specific guide. Send proof links only after the buyer replies with a concrete migration or workflow risk.
Roo can go away without taking your agent memory with it. ThumbGate keeps the lessons local, then turns them into Pre-Action Checks after you move to Cline. Start with the Roo migration guide: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=threads_post&utm_campaign=roo_channel_threads&utm_content=guide&campaign_variant=proof_backed_setup&offer_code=ROO-CHANNEL-THREADS&cta_id=roo_channel_threads&cta_placement=channel_draft&surface=roo_threads .

### Bluesky — Short post
- Audience: Local-first evaluator burned by vendor-scoped memory
- Evidence: 4 warm target(s) and the Roo sunset itself reinforce the local-first point: vendor-scoped memory is operational debt.
- CTA: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=bluesky_post&utm_campaign=roo_channel_bluesky&utm_content=guide&campaign_variant=local_first&offer_code=ROO-CHANNEL-BLUESKY&cta_id=roo_channel_bluesky&cta_placement=channel_draft&surface=roo_bluesky
- Proof timing: Lead with the local-first claim and the Roo-specific guide, not proof links, on the public post.
Roo shutting down is a reminder that vendor-scoped memory is a bad design. Keep the lessons in your repo, move to Cline, and turn them into enforceable checks instead of another lost context window. Start here: https://thumbgate-production.up.railway.app/guides/roo-code-alternative-cline?utm_source=roo_sunset&utm_medium=bluesky_post&utm_campaign=roo_channel_bluesky&utm_content=guide&campaign_variant=local_first&offer_code=ROO-CHANNEL-BLUESKY&cta_id=roo_channel_bluesky&cta_placement=channel_draft&surface=roo_bluesky .

## Evidence Backstop
- Warm targets: 4
- Self-serve targets: 3
- Sprint-fit targets: 7
- Workflow-control targets: 6
- Business-system targets: 3

## 90-Day Measurement Plan
- North star: roo_migration_to_paid_intent
- Policy: Treat Roo migration traffic as acquisition evidence only after a tracked install-doc click, setup-guide click, qualified sprint conversation, or Pro checkout start exists.
- Minimum useful signal: One tracked install-doc click plus one paid-intent event sourced from a Roo-tagged migration surface.
- Strong signal: Three tracked paid-intent events across sprint conversations or Pro checkout starts sourced from Roo migration surfaces.
Tracked metrics:
- roo_install_doc_clicks
- roo_setup_guide_clicks
- roo_sprint_intake_submissions
- roo_qualified_workflow_conversations
- roo_pro_checkout_starts
- paid_orders_by_source_roo_sunset
Guardrails:
- Do not claim revenue, installs, or marketplace approval without direct command evidence.
- Do not lead first-touch outreach with proof links before the buyer confirms pain.
- Keep pricing aligned with COMMERCIAL_TRUTH.md.
- Keep proof claims aligned with VERIFICATION_EVIDENCE.md.
Milestones:
- days_0_30: Exploit the shutdown window with one migration story: keep lesson memory, move to Cline, then route to proof-backed setup or one workflow sprint. Decision rule: Do not broaden the angle beyond Roo migration unless the tracked clicks fail to produce qualified replies or paid intent.
- days_31_60: Promote the better-converting Roo lane: self-serve Pro or workflow sprint. Decision rule: If clicks exist without paid intent, move the proof-backed setup and commercial-truth handoff earlier in follow-up copy.
- days_61_90: Retire the event-specific Roo framing unless it still produces paid-intent evidence versus broader workflow-hardening lanes. Decision rule: Only keep the Roo-specific pack prominent while it still outperforms broader memory-portability positioning.
Do not count as success:
- shutdown-post impressions without tracked clicks
- install-doc clicks without paid-intent evidence
- unverified revenue, install, or partner-approval claims

## Proof Links
- https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md
- https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- https://docs.roocode.com/
- https://roocode.com/blog/sunsetting-roo-code-extension-cloud-and-router
