Opportunities › Safe feature flag removal automation › Proposed app
Flagtidy
Find stale feature flags and get a tested pull request that removes them
- Score
- 39
- confidence 39
- Evidence
- 1
- items on the page
- Rivals
- 0
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2019
- Established market · AI estimate
ScreensConcept
Desktop app: Developers review usage maps, examine pull requests and cleanup reports during coding work at a desk. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Cleanup queue
5 of 23 shown23 stale
About this appAI proposal
Flagtidy finds feature flags that are stale, fully rolled out or switched off for good, and maps every place the code refers to them. It then opens a pull request that removes the flag and keeps the code path the flag has settled on.
It is for engineering teams that use a feature flag platform and have let old flags pile up because removing them by hand is slow and easy to get wrong. Each removal is a small, reviewable change with a plain-language summary of what was kept and what was deleted.
Flagtidy does not touch your code without review. It never merges on its own, and it runs your existing CI checks on every pull request. If a flag is used in a way it cannot read with confidence, it flags the spot for a person instead of guessing.
- Tagline
- Old flags out, working code kept.
- Voice
- PlainCarefulPractical
- Why this name
- Flag plus tidy: it says the job in two plain syllables, a small regular chore done carefully rather than a big rewrite.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Stale flag finder
Compares flag state in your flag platform with references in code and lists flags that are fully on, fully off or no longer evaluated.
No member yet
Usage map
Shows every file, branch and test that reads a flag, including wrappers and helper functions, before anything changes.
No member yet
Removal pull requests
Opens one pull request per flag. It keeps the winning code path, deletes the dead one and cleans up unused imports.
No member yet
Confidence labels
Each change is marked safe, review or manual. Odd patterns are left for a person instead of being rewritten blindly.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F4D3FDeep Moss · primary#F6F4EEPaper · surface#1B2421Ink · text#E9A820Marigold · accent#B5533CClay · warning data#8FB39CSage · secondary data
Typography
Aa
Flagtidy
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, scaled by repositories and removal jobs as the opportunity suggests.
Free
Free
- 1 repository
- Stale flag finder and usage map
- 3 removal pull requests a month
Team
$49 a month
- Up to 10 repositories
- Unlimited removal pull requests
- CI validation summaries
- Debt report
Org
$199 a month
- Unlimited repositories
- Multiple flag platforms
- Owner assignment and snooze rules
- Priority support
Would you pay Team · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Each removal pull request is seen by every reviewer on the team. Its description carries a short note that Flagtidy produced it, and the debt report can be shared by link.
- Do they become customers?
- Reviewers are engineers who may also run their own repositories, so some may sign up. Test whether pull request viewers click through and whether they start a free trial.
- First customers
- Engineering leads at web product companies with 20 to 100 engineers, one main TypeScript repository and a flag platform already in use.
- Where to reach them
- Hacker News: Follow up on the thread where developers asked for this, offering free cleanup of one flag.
- Engineering communities: Post worked examples of removing a real flag from an open-source repo in dev forums and Slack groups.
- Direct outreach: Message engineering leads who have written about flag debt, offering a free scan of one repository.
- First milestone
- Five teams run a scan and merge at least three Flagtidy pull requests each, and two of them pay for the Team plan.
Why people already pay for this
- Public claimDevelopers would pay for a service to safely remove old feature flags from code
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Code analysisSyntax-tree parsing library per languageSafe removal needs real code structure, not text search, to keep the right branch.
- This app · Repository accessGit hosting app integrationNeeded to read code and open pull requests with limited permissions.
RisksAI inference
- TechnicalFlags are used in many styles: wrappers, dynamic names, config files. Wrong removal could break behaviour, so the first version must support one language and one flag pattern well.
- CommercialThe only evidence is one public claim on Hacker News. Teams may prefer to do cleanup by hand or with in-house scripts, so willingness to pay is untested.
- PlatformFlag platforms or code hosts may add their own cleanup tools, or change their APIs and app permissions.
- DataCustomers must grant read and write access to private source code. Trust, security reviews and data handling will slow early sales.
- AIIf AI is used to rewrite code, it can produce plausible but wrong changes. Rule-based edits plus tests and human review are safer for the first version.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.