Alexis Bouchez

~ / startup analyses / 100 Startup Ideas With Distribution Built In

100 Startup Ideas With Distribution Built In

AI-generated (Claude). Starting price: $99 one-time. Distribution mechanic noted for each.

The best early distribution is the kind you don't have to pay for. The product spreads because it's useful, because it leaves a trace somewhere public, or because using it forces exposure to new audiences. These 100 ideas are organized by distribution mechanic.

2. 1. GitHub bots that open PRs

The product delivers value as a pull request. Every collaborator on every onboarded repo sees the bot's name. Merged PRs live in the git history forever.

  1. README Doctor -- Opens a PR improving structure, adding usage examples, fixing formatting. Maintainers almost always merge a README improvement. Every collaborator sees the bot. Upsell: org-wide README quality dashboard.
  2. License Bot -- Detects repos with no license or a mismatched one (MIT used where GPL is required). PRs the correct file. Simple, always mergeable. Upsell: license compliance audit for engineering orgs.
  3. CONTRIBUTING.md Scaffolder -- Reads the repo's stack (detects npm/cargo/go, parses CI config) and generates a tailored CONTRIBUTING.md. Every future contributor to that repo reads your file.
  4. SECURITY.md Adder -- PRs a security policy file with your vulnerability disclosure platform as the reporting channel. Routes all future security reports through your product.
  5. Broken Link Fixer -- Crawls markdown files (README, docs, CHANGELOG) and opens a PR replacing dead external links. Maintainers hate broken links, never fix them manually.
  6. Changelog Generator -- Repos without a CHANGELOG.md get a PR generating one from git history. Weekly follow-up PRs keep it updated. Upsell: hosted changelog page with email subscribers.
  7. i18n Stub Generator -- Detects a UI with no i18n support and PRs the scaffold (locale files, config, string extraction). Upsell: translation management SaaS.
  8. Docker Modernizer -- Finds outdated Dockerfile base images, deprecated layering patterns, missing multi-stage builds. PRs a modernized version. DevOps engineers are the buyer; they have budget.
  9. CI Config Optimizer -- Analyzes GitHub Actions workflows for slow patterns (no caching, sequential jobs that could parallelize) and PRs improvements. Every CI minute saved is quantifiable ROI.
  10. OG / Meta Tag Fixer -- Scans static site repos for missing og:title, og:description, og:image. PRs the fixes. Every personal site and docs site has this problem. Upsell: social preview monitoring dashboard.
  11. .env.example Generator -- Reads the codebase for env variable usage and PRs a documented .env.example file. New contributors to any repo with this bot merged immediately have a better onboarding experience.
  12. GitHub Actions Version Pinner -- Scans workflows for unpinned action versions (uses: actions/checkout@main instead of @sha) and PRs pinned, secure versions. Security and supply chain compliance angle.
  13. Issue Template Generator -- PRs a .github/ISSUE_TEMPLATE/ directory with bug report, feature request, and question templates. Every person who opens an issue on that repo from then on interacts with your generated file.
  14. Pull Request Template Bot -- PRs a PULL_REQUEST_TEMPLATE.md. Meta: the bot distributes itself by adding a template that every future PR author sees. Could add a small "generated by X" footer.
  15. Dependabot Config Generator -- Many repos know about Dependabot but haven't configured it. A bot that PRs a sensible .github/dependabot.yml based on the repo's package managers. Rides Dependabot's own brand awareness.

3. 2. Embeds and widgets

"Powered by X" in the footer or a small attribution link is enough. Every site using the widget is an impression for a new potential user.

  1. Public Roadmap Widget -- A hosted, embeddable roadmap for SaaS products. Users vote on features. "Powered by X" link drives new signups from every product that embeds it. Upsell: private roadmap, priority support.
  2. Changelog Widget -- Embeddable "what's new" panel that pulls from a hosted changelog. Every SaaS product needs this. The "powered by" link is the entire distribution strategy. See: Beamer, Headway.
  3. NPS / CSAT Widget -- Embeddable one-click sentiment survey. Lightweight, privacy-first. "Powered by X" drives curiosity. Works for any web product, not just SaaS.
  4. Status Page Widget -- Embeddable uptime status indicator for websites and APIs. "Status powered by X" on every product using it. Upsell: incident management, on-call alerting.
  5. Social Proof Ticker -- Shows recent signups, purchases, or "X people are using this right now" -- embeddable. Popular on landing pages. Each embed carries attribution.
  6. Testimonial Wall Widget -- Collect and display testimonials as an embeddable grid or carousel. "Powered by X" on every product page using it. Simpler, cheaper alternative to Testimonial.to.
  7. Scheduling Button -- Dead-simple "Book a call" button that embeds in websites, email signatures, and GitHub READMEs. Cal.com has this but the $99 one-time angle opens a self-hosted/indie niche. "Schedule via X" attribution.
  8. Live Visitor Counter -- Embeddable "X people reading this now" badge for blog posts and docs. Adds social proof. Each embed links back to the product. Privacy-first angle vs. Google Analytics.
  9. "We're Hiring" Banner -- Embeddable hiring widget that pulls from a hosted jobs page. Startups embed it on their product; every developer who sees it is a potential customer and candidate. "Hiring via X."
  10. Donation / Sponsorship Button -- "Buy me a coffee" alternative with lower fees and better customization. The button embeds everywhere. Each click from a non-user is a distribution touchpoint.
  11. Cookie Consent Banner -- Hosted, embeddable, GDPR-compliant. Every site deploying it adds "Privacy managed by X" to their footer. Tens of thousands of sites need this. Upsell: data deletion request handling.
  12. Public API Explorer Widget -- Paste your OpenAPI spec, get an embeddable interactive API explorer for your docs. "Try it live, powered by X." Every developer-facing product is a potential user.
  13. Upvote / Feature Request Widget -- Embeddable feature voting board. Simpler than Canny. "Suggest a feature, powered by X" at the bottom of every board.
  14. Knowledge Base Search Widget -- Embeddable search bar that indexes your docs or help center. "Search powered by X." Every user of every product using it sees the attribution when searching for help.
  15. Release Notes Popup -- Embeds as a floating "What's new" button on any web app. Shows release notes from a hosted feed. "Release notes by X." Automatic distribution through every product that embeds it.

4. 3. Badges and public artifacts

Badges live in READMEs, on websites, in email footers. They are permanent, link back to you, and are seen by every visitor.

  1. Uptime Badge -- A dynamic SVG badge showing a repo's API or site uptime. Maintainers add it to their README. Every visitor clicks it and lands on your monitoring product.
  2. Test Coverage Badge (self-hosted) -- Codecov alternative. Generates a coverage badge from CI uploads. The badge is on every README, linking to a hosted coverage report. Lower price than Codecov for small teams.
  3. "OSS Health Score" Badge -- Rates a repo on documentation, test coverage, CI setup, license, activity. Maintainers want the green badge. Each badge links back to the full report on your site.
  4. Build Status Badge (self-hosted) -- Like shields.io but hosted on your infrastructure with a dashboard. Upsell: custom badge styles, team analytics.
  5. Downloads / Installs Badge -- Shows npm, PyPI, or crates.io download counts as a live badge. Maintainers love showing traction. Every README visitor sees the badge and your brand.
  6. "Deploy to X" Button -- A one-click deploy button for popular cloud providers, like the Heroku button or Vercel's. You host the redirect infrastructure. Every open source project that adds the button drives deploys through your platform.
  7. Security Score Badge -- Runs a basic security audit (known vulnerabilities, outdated deps, no security policy) and issues a badge. Green badge = incentive to merge fixes. The badge is on the README forever.
  8. "Last Released" Badge -- Shows how long ago the last release was. Maintenance signal for users evaluating a dependency. Each badge is a backlink and brand impression.
  9. GitHub Profile Trophy Generator -- Customizable achievement trophies for GitHub profile READMEs. Viral among developers who care about their GitHub profile. "Trophies by X" credit.
  10. "Built With" Badge Marketplace -- A directory of technology badges. Add "Built with Postgres," "Built with Go," etc. to your README. You become the canonical source of these badges, driving traffic from every README.

5. 4. Directories and listings

Being listed drives SEO and referral traffic. Listing others is the distribution mechanic: they link back, share the listing, and bring their audience.

  1. OSS Alternatives Directory -- "Open source alternative to Slack/Notion/Figma" search engine. Devs share these comparisons constantly. Upsell: sponsored listings, newsletter.
  2. Indie Hacker Tools Directory -- Curated list of tools solo founders actually use. Submissions drive backlinks from the submitter's own site and audience. Upsell: featured placement for $99.
  3. GitHub Apps Marketplace (niche) -- The official GitHub Marketplace is hard to discover. A curated, searchable directory of the best GitHub Apps, organized by use case. Each app listed drives a backlink from that app's maintainer.
  4. Self-Hosted Software Directory -- Comprehensive, searchable list of software you can run on your own server (like Awesome Self-Hosted but with better UX). Huge SEO surface. Upsell: hosted deployment guides.
  5. Founder CRM Database -- A public database of how founders built their early user lists, with filters by industry, geography, B2B/B2C. Founders share their own entry because it's free marketing. Upsell: private entries for sensitive tactics.
  6. Launch Archive -- Database of every Product Hunt, HN Show HN, and indie launch post with outcome data (upvotes, comments, signups if disclosed). People submit their launches. Each submission drives traffic.
  7. Developer Newsletter Directory -- Searchable list of newsletters by topic, audience size, and engagement. Newsletter authors submit for free backlinks. Readers discover new ones. Upsell: verified audience stats, ad placement.
  8. MCP Server Registry -- With Model Context Protocol gaining traction, a community-maintained registry of MCP servers with docs and install commands. Every MCP tool maintainer wants to be listed.
  9. "Powered by Open Source" Directory -- Companies that disclose their OSS stack. Startups submit their stack for visibility. OSS projects get featured users. Each submission is a backlink.
  10. Failed Startups Archive -- Documented post-mortems and shutdown stories with lessons. Founders submit their own. Media picks these up constantly, driving recurring traffic.

6. 5. Things that live in READMEs

READMEs are read by thousands of developers evaluating a dependency, contributing to a project, or just browsing. Anything that gets added to a README has a long, public life.

  1. Live GitHub Stats Component -- Dynamic README card showing stars, forks, contributors, open issues in a beautiful SVG layout. Maintainers add it. Every visitor sees it. "Stats by X."
  2. Contributor Spotlight Generator -- Auto-generates a "Contributors" section with avatars and stats, hosted as a live SVG. "Powered by X." Maintainers love celebrating contributors.
  3. API Usage Example Generator -- Paste your API spec, get a README-ready code snippet section with tabs for Node, Python, Go, curl. "Examples generated by X."
  4. Benchmark Badge -- Runs performance benchmarks in CI and adds a live "X requests/sec" badge to the README. Performance-focused OSS projects love this.
  5. Demo GIF Generator -- Takes a terminal session recording (asciinema or similar) and generates a looping GIF optimized for README embedding. "Demo by X."
  6. Sponsor Showcase Block -- Auto-generates a sponsors section in the README from GitHub Sponsors or Open Collective data. Beautiful layout. "Sponsors section by X." Every OSS project with sponsors wants this.
  7. "Who Uses This" Section Generator -- Companies using a library can submit their logo. The bot PRs an updated "Used by" section to the README monthly. Logos are a trust signal; companies want to be listed.
  8. Dependency Graph Visualizer -- Generates a dependency graph as a SVG badge for the README. Devs evaluating a library want to understand its dependency footprint. "Graph by X."
  9. Localized README Generator -- Takes an English README and PRs translated versions (README.zh.md, README.fr.md). OSS maintainers want international reach. "Translation by X."
  10. Security Advisory Block -- Auto-generates a "Known vulnerabilities" section in the README, live-updated from CVE databases. "Security data by X." Upsell: private security scanning for paid repos.

7. 6. Network effect tools

Each new user makes the product more valuable for existing users, or the product only works when multiple people use it.

  1. OSS Maintainer Support Forum -- A Stack Overflow specifically for open source maintainers. Questions and answers are public and SEO-indexed. Maintainers invite contributors; contributors invite others. Critical mass in a niche is enough.
  2. Public API Contract Registry -- Teams publish their API contracts (OpenAPI specs) so consumers can track breaking changes. Each team that publishes invites consumers to subscribe. Consumers are potential customers.
  3. Shared Test Data Repository -- A community-maintained library of realistic fake datasets for testing. Contributors add datasets; every project that uses the library links back. Upsell: private datasets, data generation API.
  4. Dev Environment Config Sharing -- Publish and discover dotfiles, dev container configs, and IDE setups by language and framework. "My setup, powered by X." Sharing is the discovery mechanic.
  5. Code Snippet Social Network -- GitHub Gists with better discovery: tags, likes, forks, follows. Each snippet shared outside the platform links back. Simpler than Replit, more social than Gist.
  6. OSS Dependency Co-ownership Network -- Match companies who share critical OSS dependencies and co-fund maintenance. Companies list their critical deps; others see who else depends on the same libs. FOSS funding is a growing pain point.
  7. API Key Rotation Coordinator -- When a team member leaves, rotating all their API keys across 30 services is manual hell. This tool tracks keys by person and sends rotation PRs. Every team that onboards invites new members who become users.
  8. Incident War Room Tool -- Real-time incident coordination with automatic status page updates, Slack integration, and a post-mortem template. Each incident page is public by default, driving organic discovery from people Googling the incident.
  9. Shared Runbook Library -- Teams publish runbooks for common incidents (database down, SSL cert expiring, deployment rollback). Others discover and fork them. "Runbook by X" in the footer.
  10. Architecture Decision Record (ADR) Hub -- A hosted, searchable platform for publishing Architecture Decision Records. Teams link their ADRs from their README. Developers browsing GitHub find the ADR hub through those links.

8. 7. Open source with a hosted upsell

The OSS version distributes itself through GitHub stars, forks, and contributions. The hosted version monetizes the people who want it without the ops burden.

  1. Self-Hosted Analytics (Plausible-style) -- Privacy-first web analytics you can self-host. OSS repo drives discovery. Hosted version at $99/year. Every public site using it can display a public stats page as social proof.
  2. Self-Hosted Uptime Monitor -- Cron-based uptime checks with a beautiful public status page. OSS on GitHub, hosted for $99/year. Status pages are shared publicly, driving discovery.
  3. Self-Hosted Link Shortener with Analytics -- Own your short links. OSS on GitHub, hosted for $99 one-time. Every short link is a brand touchpoint if you use a custom domain.
  4. Self-Hosted Form Backend -- Receive form submissions without a backend. OSS on GitHub, cloud-hosted for $99/year. "Powered by X" in the form confirmation email drives new signups.
  5. Self-Hosted Email List Manager -- Listmonk-style. OSS, hosted version for $99/year. Every newsletter sent from the hosted version has "Sent via X" in the footer.
  6. Self-Hosted Feature Flags -- Unleash-style feature flag system. OSS, hosted for teams that don't want to run it. Each flag evaluation that calls your hosted API is a retention touchpoint.
  7. Self-Hosted Cron Job Runner -- Schedule HTTP jobs without a server. OSS core, hosted for $99/year. Job failure alerts and history are the upsell hooks.
  8. Self-Hosted Error Tracker -- Sentry-lite for small teams. OSS on GitHub, hosted for $99/year. Every error alert email mentions the product name.
  9. Self-Hosted Feedback Board -- Canny-lite. OSS, hosted for $99/year. Public boards are indexed by Google; users googling "feedback for X product" land on your hosted instance.
  10. Self-Hosted Documentation Platform -- Gitbook-lite. Write docs in markdown, host them beautifully. OSS core, hosted for $99/year. "Docs by X" in the footer of every hosted docs site.

9. 8. Attribution-based distribution

The product leaves a trace: a footer credit, a watermark, a "generated by" line. That trace is the distribution channel.

  1. Invoice Generator -- Beautiful PDF invoices for freelancers. "Invoice generated by X" in the footer. Every client who receives an invoice is a potential user. No login required; $99 removes the footer.
  2. Proposal / Contract Generator -- Template-based proposals and contracts. "Proposal created with X." Every prospect who reads a proposal sees your brand.
  3. Email Signature Generator -- Drag-and-drop HTML email signature with "Made with X" link. Millions of emails sent with that signature every week. Free plan has attribution; $99 removes it.
  4. Resume / CV Builder -- Clean, typographically strong resumes. "Resume built with X" in the footer. Shared everywhere during job searches. Each PDF is a distribution event.
  5. Technical Documentation Generator -- Paste a codebase, get a human-readable technical spec. "Docs generated by X." Shared internally and externally as project documentation.
  6. Terms of Service Generator -- Generates a plain-English privacy policy and ToS. "Generated by X." Every startup that uses it adds your brand to a page that gets real traffic from users and investors.
  7. Screenshot Beautifier -- Wrap terminal or browser screenshots in a beautiful frame. "Created with X." Every screenshot shared on Twitter/X is an ad. Used by every developer who writes a blog post or posts a product screenshot.
  8. Architecture Diagram Generator -- Text-to-diagram (like Mermaid but more beautiful). "Diagram by X." Architecture diagrams are shared in READMEs, blog posts, and presentations constantly.
  9. Open Graph Image Generator -- Auto-generates beautiful og:image cards for blog posts. "Image by X." Every article shared on social media shows the card, which visually carries your brand if the design is distinctive enough.
  10. Startup Landing Page Generator -- Fill in a form, get a beautiful single-page HTML site. "Built with X" in the footer. Free plan has attribution; $99 removes it. Every landing page is live marketing.
  11. Pitch Deck Exporter -- Export a Notion or markdown file to a beautiful presentation PDF. "Pitch deck built with X." Every deck shared with investors is a touchpoint.
  12. Postmortem Report Generator -- Fill in the incident timeline, get a formatted post-mortem document ready to share. "Postmortem generated by X." Engineering teams share these publicly; they get indexed and read.
  13. Job Description Generator -- Structured, bias-reduced job descriptions from a template. "Written with X." Every job posting on LinkedIn or Greenhouse that used your tool carries attribution in the meta.
  14. Weekly Engineering Update Generator -- Formats git activity and issue data into a readable team update email. "Update generated by X." Sent to the whole company every week. Non-engineers at those companies are potential buyers for their own teams.
  15. Startup Equity Calculator -- Dilution modeling, option pool scenarios, exit waterfall tables. Beautiful, shareable link. "Modeled with X." Founders share equity scenarios with co-founders, investors, and future hires.
  16. Conference Talk Abstract Generator -- Helps developers write compelling CFP submissions. "Abstract crafted with X" in the submission notes. Conference organizers start recognizing the format.
  17. Dependency Audit Report Generator -- Generates a beautiful PDF audit of a project's dependencies (licenses, vulnerabilities, maintenance status). "Audited by X." Shared with security teams and compliance officers.
  18. Release Note Writer -- Turns git commits into readable release notes. "Release notes by X." Published with every version, linked from npm/PyPI/GitHub releases. Seen by every person who evaluates upgrading a dependency.
  19. API Documentation from Code Comments -- Generates hosted API docs from inline code comments, no config required. "Docs by X" in the footer. Every developer who reads the API docs is a potential user.
  20. Support Documentation Auto-Generator -- Scans a product's UI and GitHub issues to draft FAQ and help center articles. "Help center powered by X." Every user who reads a support article is a potential customer's customer, and potential future buyer.

10. The meta-pattern

Every idea here follows one of four mechanics:

  1. The PR is the product. Value delivered as a pull request. Every collaborator on every onboarded repo sees your name. (Snyk, Dependabot, ideas 1-15.)
  2. The embed carries attribution. "Powered by X" or "Built with X" in a visible place. Every end user of every customer is a distribution event. (Beamer, Testimonial.to, ideas 16-30.)
  3. The artifact lives publicly. Badge in a README, PDF with a footer, public report page. Permanent, indexed, linked. (ideas 31-50, 81-100.)
  4. The network is the moat. Each user adds value for other users, or the product only works when multiple parties use it. Harder to start but harder to kill. (ideas 61-70.)

The $99 one-time price point is not a growth strategy. It is a filter. It selects for buyers who are serious enough to pay but price-sensitive enough that a free tier would stall them. The goal is to get as many people as possible using the product, so that the distribution mechanic has more surface area to work on. You charge to cover costs and to qualify users. You grow because the product does it for you.