SaaSEarly tractionExample Boost
YOUR POSITIONING
Fuzzy.Needs more clarity

RepoClean faces a fundamental positioning problem selling a paid solution in a market flooded with free alternatives. The core issue is competing on features where 'good enough' free solutions exist.

What makes you different

Zero-configuration GitHub app for org-wide branch cleanup with dashboard visibility

Who you serve best

Small teams and indie developers who value time over money, plus enterprises with many repositories

Key Discovery
competitive intel

Pull Panda Acquisition Reveals Market Gap

GitHub acquired Pull Panda for code review features, not branch cleanup. This suggests GitHub sees value in repository hygiene but hasn't built comprehensive tooling yet.

Pull Panda blog analysis

Why it matters: Validates the space but shows GitHub's focus is elsewhere - opportunity to own the branch cleanup niche

KEY PRIORITIES
#1

Add activation tracking (time-to-first-cleanup, feature adoption)

Instrument key user actions to understand activation patterns

ICE24
#2

Add exit survey for churned users

3-question survey for users who uninstall or don't return

ICE23
#3

Create GitHub Marketplace listing with 'why paid vs free' positioning

Position against free alternatives with clear value prop

ICE22
#4

Prepare and execute improved HN Show HN launch

Frame around insight not product, acknowledge free alternatives

ICE20
#5

Build 'org-wide dashboard' feature showing all repos' branch health

Unified view across entire GitHub organization

ICE19
#6

Write definitive 'Repository Hygiene Guide' for Dev.to

Comprehensive guide covering all options including competitors

ICE19
#7

Start answering branch-related questions on Stack Overflow/Reddit weekly

Weekly helpful answers building toward soft promotion

ICE19
#8

Implement 'before/after' visualization on first run

Dashboard showing branch cleanup results and impact

ICE18
TRAFFIC COMPARISON
github.com48.0M/mo

4,758,886 ranking keywords

pullpanda.io191/mo

131 ranking keywords

repoclean.dev(you)0/mo
MARKET PULSE

Our team's repo has started to become bloated with stale branches

Reddit r/git

Stale branches confuse developers who can't tell what's active, waste time in branch lists and autocomplete, create ambiguity about what's deployed

Pull Panda blog

I got tired of manually cleaning up stale local git branches

Reddit r/commandline

In my company, we manage multiple microservices, each with its own repository. Over time, stale branches accumulated—some dating back months

dev.to article
KEY METRICS
FINDING YOU

Weekly signups

10

TRYING YOU

Signup → Install rate

Measured

TRYING YOU

Install → First cleanup rate

Measured

COMING BACK

7-day retention

Measured

COMING BACK

Monthly churn rate

<10%

PAYING YOU

MRR

$450

KEY DISCOVERIES
pattern

Per-Repo Setup Fatigue Is Real Pain Point

Free Actions require YAML configuration per repository. For orgs with 20+ repos, this becomes genuinely painful setup and maintenance burden.

Competitive research

Clear differentiation opportunity - org-wide setup vs per-repo configuration

finding

CI/CD Slowdown Is Enterprise Pain Point

Dev.to article detailed how stale branches cause GitHub API rate limiting and Jenkins pipeline slowdowns. This is a cost/performance argument for larger teams.

Research data

Potential enterprise positioning around performance impact rather than just cleanliness

opportunity

The '100 Branches Problem' Is Common

Multiple Reddit threads mention repositories with 50-200+ stale branches where manual cleanup becomes genuinely painful and free Actions feel inadequate.

Reddit analysis

Target users who've crossed the threshold where free solutions become insufficient

risk

Stale Bot Backlash Creates Positioning Opportunity

HN thread titled 'GitHub Stale Bots – A False Economy' shows developers frustrated with aggressive bots closing legitimate issues.

Hacker News research

Can position as 'intelligent cleanup that doesn't annoy contributors' vs dumb automation

DEEP DIVES

RepoClean faces a fundamental positioning problem. You're selling a paid solution in a market flooded with free alternatives—multiple GitHub Actions (Remove Stale Branches, Cleaning up Stale Branches, actions/stale) do essentially the same thing at zero cost. GitHub itself offers automatic branch deletion after merge as a native setting. Pull Panda, which had similar functionality, was acquired by GitHub and made free. Your 4-month plateau isn't a marketing problem—it's a market signal.

The good news: the pain point is real. My research surfaced developers consistently complaining about branch sprawl, stale branches slowing CI/CD, and confusion about what's active. Stack Overflow threads, Reddit discussions, and dev.to articles confirm this is a recurring frustration, especially on teams with many contributors. The problem isn't demand—it's that free solutions exist and "good enough" is winning.

Your path forward requires one of two pivots: either go radically simpler than free alternatives (one-click setup, zero configuration, beautiful dashboard that shows the mess before/after) targeting developers who don't want to write YAML, or go deeper into enterprise repository governance where free Actions fall short. Given your 10 hours/week constraint, I recommend the former—become the "set and forget" option for small teams and indie developers who value time over money.

StageCurrent StateAssessment
Acquisition~8-10 new signups/month (estimated from "barely covers churn")Weak. Single HN post, tiny Twitter, Reddit removing posts. No sustainable channel.
ActivationUnknown free-to-active conversionUnknown. Critical gap—you need to instrument this.
RetentionChurn roughly equals new signupsPoor. 4-month plateau suggests ~10-15% monthly churn on free tier.
Revenue$380 MRR from 28 customers (~$13.50 ARPU)Low ARPU suggests pricing may be too cheap for the value delivered.
ReferralNo evidence of referral program or organic word-of-mouthNon-existent. No viral mechanics.

The core issue: You have an activation and retention problem masquerading as an acquisition problem. Getting more signups won't help if they're not converting and not staying. However, since you specified acquisition as your focus, I'll optimize for that while flagging where acquisition efforts will fail without fixing downstream.

CompetitorTypePriceStrengthsWeaknesses
GitHub native settingsBuilt-inFreeZero friction, already thereOnly handles post-merge deletion, no stale branch detection
Remove Stale Branches ActionGitHub ActionFree44 stars, active maintenance, configurableRequires YAML setup, no dashboard, no cross-repo view
Cleaning up Stale Branches ActionGitHub ActionFreeSimilar functionalityLess popular, fewer features
actions/staleGitHub ActionFreeOfficial GitHub action, well-maintainedFocused on issues/PRs, not branches
Custom scriptsDIYFreeExactly what you wantMaintenance burden, no UI
Pull Panda (acquired)Was SaaSFree (now part of GitHub)Was the market leaderAcquired, core features absorbed into GitHub

Key insight: There is no successful paid competitor in this exact space. Pull Panda was acquired before proving the standalone market. This is either a massive opportunity or a warning that the market won't pay. Given the proliferation of free alternatives, I lean toward the latter for the core feature set.

ChannelFitEffortExpected CACPriority
Hacker News (retry)HighLow~$01
GitHub Marketplace listingHighLow~$02
Targeted Reddit (non-promotional)MediumMedium~$03
Dev.to articlesMediumMedium~$04
Twitter/X (building in public)LowHigh~$05
SEO/ContentLowHigh~$06
Cold outreach to eng managersMediumHighUnknown7
Paid adsLowMediumLikely $50-150Not recommended

Channel Explanations

Hacker News (retry): Your first attempt underperformed. The key is framing—don't post "I built a GitHub app for branch cleanup." Post a genuine observation or pain point: "Ask HN: How do you handle branch sprawl in repos with 10+ contributors?" or a Show HN with a hook that acknowledges the free alternatives exist and explains why you built something different anyway. Timing matters—weekday mornings US time, avoid major news days.

GitHub Marketplace: If you're not listed, you're invisible to developers browsing for solutions. The marketplace is low-traffic but high-intent. Your listing copy needs to immediately address "why pay when free Actions exist."

Reddit (non-promotional): Your posts got removed because you were self-promoting. The Reddit playbook for dev tools: answer questions genuinely in r/git, r/github, r/devops, r/webdev. When someone asks "how do you handle stale branches?", give a real answer with multiple options, mention yours as one option with full disclosure. Build karma and credibility over 2-3 months before any direct promotion.

Dev.to: Write the definitive guide to repository hygiene. Cover all the free options, the tradeoffs, the edge cases. Mention RepoClean as your solution at the end. This is SEO and credibility building combined.

Twitter (deprioritized): With 200 followers, you're shouting into the void. Building a Twitter following takes consistent daily effort over 6-12 months. Not compatible with 10 hours/week when you have a product to maintain.

  1. Stop random Twitter posting. 200 followers means zero distribution. Either commit to a 6-month daily building-in-public strategy or redirect those hours elsewhere.
  1. Stop trying to out-feature free alternatives on core cleanup. You won't win by having more YAML configuration options than a free Action. Win on experience, simplicity, or scope.
  1. Stop treating this as purely an acquisition problem. You don't know your activation rate. You don't know why people churn. Spending more to fill a leaky bucket wastes effort.
  1. Stop one-shot marketing attempts. One HN post, then nothing. One Reddit post, removed, then quit. Compounding requires consistency over months.
  1. Stop hiding the price. If your pricing isn't crystal clear on the homepage, you're attracting freebie-seekers who will never convert. Filter early.
ActionImpactConfidenceEaseICE Score
Add activation tracking (time-to-first-cleanup, feature adoption)89724
Create GitHub Marketplace listing with "why paid vs free" positioning77822
Build "org-wide dashboard" feature showing all repos' branch health96419
Write definitive "Repository Hygiene Guide" for Dev.to67619
Prepare and execute improved HN Show HN launch85720
Add exit survey for churned users78823
Implement "before/after" visualization on first run76518
Start answering branch-related questions on Stack Overflow/Reddit weekly57719

Track weekly starting now:

MetricCategoryCurrentWeek 2 TargetWeek 4 Target
Weekly signupsAcquisition~2-3510
Signup → Install rateActivationUnknownMeasuredMeasured
Install → First cleanup rateActivationUnknownMeasuredMeasured
7-day retentionRetentionUnknownMeasuredMeasured
Monthly churn rateRetention~10-15% (est)Measured<10%
MRRRevenue$380$380$450
Paying customersRevenue282832
NPS/satisfactionReferralUnknownSurvey sentScore measured

Template 1: Dev.to Article Structure

Title: "GitHub Repository Hygiene: The Complete Guide to Branch Cleanup in 2025"

Get a Boost like this for your business.

Real research on your market, your competitors, your opportunities.