Tweeks.io

What do they actually do

Tweeks.io is a Chrome extension that turns plain‑English requests into small, site‑specific browser scripts you can install, edit, enable/disable, and share. The extension captures the page structure, sends the page plus your prompt to an AI service to propose deterministic transformations (CSS selectors, DOM edits, and short scripts), and then runs those changes locally in your browser as a persistent userscript onboarding HN launch. Generated scripts are editable and persist across page loads; they can be shared via links or profiles example share link.

People use Tweeks for common annoyances and light automation: hiding YouTube Shorts, filtering Hacker News posts, retheming Google, adding timers/modals on Reddit, extracting LinkedIn author data and POSTing it to a server, and helpers for NYT Games HN examples shared example. The current UX works best for power users; broader ease‑of‑use is on their roadmap via a gallery and improved onboarding onboarding HN roadmap.

Scripts run in‑page in the user’s browser. Code generation uses external AI services; per their privacy policy, generated scripts may be retained and reused to improve the service, and users are responsible for complying with site terms when running scripts privacy. The product launched publicly with demos on Hacker News and is available via their site HN launch homepage.

Who are their target customer(s)

• Power users who constantly tweak their web experience and share fixes: They want quick, page‑specific changes without hand‑coding or maintaining scripts; existing tools require manual code edits and per‑site setup HN launch tweeks.io.
• Non‑technical users who want to remove annoyances on popular sites: Site settings don’t cover needs like hiding promoted posts or Shorts, and traditional userscripts/themes are too technical to install and maintain HN examples onboarding.
• Professionals needing lightweight, page‑specific automation or data extraction: They face repetitive copy‑paste or fragile scrapers; they need quick, local scripts to extract/send small bits of data without building full automation stacks shared example HN thread.
• Community curators and everyday users seeking vetted, discoverable tweaks: Finding safe, reliable scripts is hard; they want a curated gallery and profiles with one‑click installs they can trust share/profile roadmap HN discussion.
• Developers and product folks prototyping UI changes or micro‑features: Packaging and shipping single‑site extensions is slow; they want to generate and persist small, editable in‑page scripts to iterate quickly HN product flow privacy/implementation.

How would they acquire their first 10, 50, and 100 customers

• First 10: Directly onboard engaged commenters and early script‑sharers from the HN launch, help them create and install a first Tweek, and ask for public share links and quotes for social proof HN launch example share.
• First 50: Publish clear walkthroughs for high‑demand tweaks (e.g., hide YouTube Shorts, filter HN) to Reddit, userscript communities, and X, seeded with one‑click install links; pair with outreach to niche reviewers/bloggers for 3–5 writeups HN demos onboarding.
• First 100: Launch a small curated gallery and user profiles, surface top Tweeks per site with one‑click installs, and invite early users to claim/curate pages; use SEO, social shares, and backlinks from the gallery as the main funnel profile pattern onboarding.

What is the rough total addressable market

Top-down context:

The technical ceiling for a Chrome‑extension product is roughly the desktop Chrome user base, estimated around 1.5B users (≈3.8B Chrome users × ~40% desktop share) Chrome users StatCounter device share DataReportal context.

Bottom-up calculation:

A core userscript audience of ~11M (Tampermonkey users) plus a fraction of broader extension users (e.g., 50–200M of ad‑block/utility users) suggests a realistic SAM in the tens to low hundreds of millions, with an early obtainable market in the tens of thousands to low millions Tampermonkey listing ad‑block users.

Assumptions:

• ~40% of Chrome usage is on desktop and is a reasonable proxy for extension‑capable users.
• Tampermonkey’s ~11M users approximate the core userscript/power‑user base.
• Only a small subset of ad‑block/extension users will adopt curated Tweeks, yielding 50–200M broad SAM.

Who are some of their notable competitors

• Tampermonkey: The most popular userscript manager for installing and running custom JavaScript on pages; Tweeks overlaps on running site‑specific scripts but adds AI generation from plain English and in‑extension editing/sharing Tampermonkey HN launch.
• Greasy Fork: The largest public catalog for author‑written userscripts; Tweeks competes on discovery/installation but generates scripts on demand and aims for curated, non‑technical installs via a gallery Greasy Fork HN roadmap.
• Stylus (userstyles): An extension and community for installing CSS themes; overlaps with Tweeks on look‑and‑feel changes, while Tweeks also handles DOM edits and light automation from natural language Stylus listing Stylus GitHub.
• Refined‑style curated extensions (e.g., Refined GitHub): Single‑site extensions that bundle many vetted tweaks; preferred by non‑technical users, but Tweeks offers per‑page, on‑demand customizations and user‑editable scripts instead of a fixed feature set Refined GitHub repo Chrome Store.
• Zapier and browser automation extensions: Tools for non‑developers to automate cross‑app workflows; overlaps with Tweeks on light automation/data extraction, but Zapier focuses on hosted workflows rather than small, persistent in‑page scripts that run locally Zapier overview.