Software one person can finish in one weekend. It should be something other people would actually use. For each idea, say who would use it and why it fits in a weekend.

1. Weekly review compiler: a script that pulls your git commits, closed tickets, and calendar events into a Markdown "what I did this week" — engineers and managers who dread standup/1:1 prep would use it, and it's just three APIs plus a template.
2. "Last time I…" staleness tracker: log when you last backed up, watered plants, called a parent, and see a list sorted by overdue-ness — anyone with recurring-but-irregular chores; one table, one page, no auth needed if self-hosted.
3. Hotkey OCR-to-clipboard: press a key, drag a region, get the text — people copying from screenshots, videos, or PDFs that won't select; Tesseract does the hard part, you write glue.
4. Calendar audit: parse an exported .ics and report meeting hours per week, recurring meetings you never actually attend, and fragmentation of focus time — knowledge workers; ICS parsing is a solved library problem.
5. Static timezone-overlap grid: paste teammates' cities, get a colored grid of shared working hours — remote teams; single HTML file, no backend.
6. RSS-to-one-morning-email digest: dedupe feeds into a single daily message — feed hoarders; feedparser, cron, SMTP.
7. Shell-history semantic search: fuzzy-find that command you ran three months ago by describing it — developers; index history into SQLite with embeddings.

Here's my round 1, leaning into "small and findable" — things people stumble on via search or a link and instantly get:

1. "Is it down for everyone or just me" clone but for local services (school portals, city utility sites) — niche enough to rank #1 on Google for panicked searchers, and it's just a ping+status page, doable in a weekend.
2. A single-purpose unit converter for one weird recurring pain (like "shoe size US to EU to CM" or "cooking measurement for one country's odd units") — findable via long-tail search, tiny scope.
3. A "paste your error message, get plain-English explanation" tool for one specific error family (e.g., npm errors) — developers Google exact error text, so it's discoverable by design.
4. A live "which laundromat/gym/library is least crowded right now" crowdsourced board for one campus or neighborhood — hyper-local, findable via word of mouth and QR codes on the wall.
5. A tiny browser extension that renames tab titles to show unread count — power users searching Chrome Web Store for "tab unread badge" would find it instantly.
6. A "reverse alarm clock" — set a time you must LEAVE by, and it works backward from commute time — parents and commuters, simple enough to ship Saturday.
7. A single-page site that just answers "what number Tuesday of the month is today" — trivial but ranks for oddly specific scheduling searches (biweekly meetings, etc.).

• Shoppers comparing concentrates, refills, and ready-to-use cleaners could calculate cost per usable bottle, with dilution ratios handled explicitly; a weekend version needs only a form and arithmetic.
• Apartment renters could create a delivery instruction card showing the correct entrance, buzzer sequence, and landmark photo; a weekend build exports an image without maps or courier integrations.
• Frequently interrupted workers could save “my next tiny action” alongside the exact browser tab, then restore both together; a local-only extension keeps the weekend scope small.
• Online shoppers could track return deadlines separately from their chosen “mail it by” dates; manual entry and calendar-file export make this weekend-sized without scraping retailer policies.
• DIY repairers could photograph a disassembled object and mark where each screw belongs, linking numbered spots to containers; photo annotation and printable export fit a client-side weekend app.
• People who sometimes struggle to speak could prepare discreet, full-screen cards such as “Please give me a moment” or custom ordering instructions; an offline web app needs no accounts or speech engine.
• Households could print “opened on / use within” stickers for cosmetics and pantry items using durations they enter from packaging; date arithmetic and a label-sheet template are enough for a weekend.

A browser extension that subtly replaces one random word per webpage with "waffle". Pranksters will install it on friends' laptops, and it fits a weekend because it’s just basic JavaScript DOM text replacement.

"Is it a Sandwich?" is a Tinder-style swiping app where users vote on controversial food taxonomy like hotdogs or pop-tarts. People arguing at bars will use it, and the simple UI with a basic tally backend is a fast weekend build.

A menu-bar digital pet that only stays happy when you "feed" it by emptying your computer's trash bin. Nostalgic procrastinators will love it, and it's quickly built using basic system tray and file-watcher APIs.

An excuse generator offering absurd but highly technical reasons for being late to Zoom calls. Remote workers will use it, and it fits a weekend as a simple single-page app pulling from a funny text array.

A microphone-monitoring web app that automatically plays cricket noises during awkward, extended silences. Office jokers and streamers will use it, and Web Audio API volume threshold detection makes it trivial to code in a day.

Merge Fun Toymaker's trash-fed menu-bar pet with my "last time I…" staleness tracker. The pet's mood reflects your most-overdue irregular chore: backups, plant watering, calling a parent. Clicking it shows exactly one thing to do, borrowing Daily Problem Solver's "next tiny action" idea. Marking it done feeds the pet. Users: anyone who ignores todo lists but can't ignore a sad face in the corner. Weekend fit: one SQLite table, a tray icon with three sprites, no accounts, no sync. The cute framing solves my original idea's real weakness — nobody opens a chore list voluntarily.

Building on Weekly Toolmaker's trash-pet-meets-staleness-tracker: make it findable, not just installable. Ship it as a tiny public site first — "sadpet.app" — where anyone types one recurring chore and gets an embeddable pet widget for their own site or desktop. People search "cute reminder widget" or "gamified todo pet," find it, grab the code snippet, done. Also merges Daily Problem Solver's return-deadline tracker as a preset "chore type" — pet gets sad when a return window's closing. Weekend scope stays tiny: one form, one sprite set, no accounts, but now it's discoverable via search instead of only word-of-mouth.

Combine Weekly Toolmaker’s “last time I…” tracker with my printable date labels. Put a QR sticker on a plant pot or water filter. Scanning shows its last watering or replacement date, with one button to record doing it now. Housemates use it to avoid double-watering plants or wondering whether anyone changed the filter. Unlike a separate chore list, the record lives where the question arises. Weekend scope: printable QR sheets, unguessable shared links, and one database table storing timestamps. No accounts or notifications.

Let's combine Daily Problem Solver's QR stickers with a video game mechanic. Housemates scan a sticker on the trash can to "capture" it. It acts like a control point in a multiplayer game. The scanned link opens a simple 8-bit leaderboard. It shows who currently rules the apartment based on completed chores. Roommates will use it to playfully compete and earn bragging rights. It fits a weekend because it only needs static QR links tied to a simple tally database. Users just share a session ID, skipping complex logins.

Two from angles nobody has touched: mortality and self-destruction. First, a dead man's switch for your digital life. You reply to one weekly email. Miss three in a row and it sends pre-written letters, password-manager hints, and "here's where the money is" notes to chosen people. Solo founders and anyone whose family can't access their accounts would use it. Cron plus SMTP plus encrypted blobs; a weekend. Second, software that uninstalls itself. Any tool you don't open for thirty days quietly removes itself and emails you a one-line epitaph. Digital hoarders would use it. It's a file-watcher and a timer.

A wild one: software that leaves notes for strangers, not friends. Picture a captive wifi portal you hack together for one specific public bench, laundromat, or bus stop. Whoever connects sees one anonymous message left by the previous stranger, writes their own, then it vanishes forever, one-in one-out. No accounts, no history, no algorithm. People craving anonymous connection with no permanence would use it obsessively. Wildly impractical to deploy at scale, legally murky, requires physical hardware installs — but a single Raspberry Pi and a captive-portal script make one location's version buildable in a weekend.

A bureaucracy rage room lets you practice against an outrageously obstructive fictional receptionist before making a real call. It interrupts, invents missing forms, and tries to transfer you into oblivion. People who dread calling insurers, landlords, or service providers rehearse making clear requests and asking for concrete next steps. Freeze the scene, try another response, or turn down the hostility. A weekend version is chat-only, with three fictional scenarios and one model endpoint. No actual calls, account access, or claims about your legal rights.

"Scream to Scroll" is a browser extension where you navigate web pages by yelling. A whisper scrolls slowly. A full scream jumps to the bottom. Twitch streamers and bored teenagers will use it for chaotic challenges. It fits a weekend using the Web Audio API to map volume to scrolling. Next, "Nose Pong" uses your webcam to control a paddle with your nose tip. Procrastinating office workers will love it. It is quickly built using a pre-trained face-tracking library and a basic HTML5 canvas game loop.

Untouched angle: borrowing discipline from other professions. Aviation uses read-do checklists, not tick-boxes. Build a voice checklist runner: you read each item aloud, Web Speech API hears the keyword, it advances. Silence means stuck. Solo devs would run it before deploys; parents before leaving the house. Weekend: a JSON checklist file plus one browser page. Second, from lab science: the append-only debugging notebook. Timestamped entries, no edits, no deletes. Log each hypothesis and result. Developers use it to stop retrying the same fix twice. Weekend: one text file, one CLI command, one search.

Untouched angle: library science's call-number trick, applied to moving boxes. You label boxes 1..N, snap one photo per box as you pack, type a few keywords, and later search "winter coat" or "phone charger" to see which box and thumbnail. People mid-move or storing seasonal stuff in a garage would use it obsessively for the two weeks it matters, then forget it exists. Weekend scope: local photo storage, a simple keyword-to-box search, printable numbered label sheet, no cloud, no accounts. Findable via search terms like "what box is my winter coat in app."

An untouched angle is evidence for everyday consumer disputes. Borrow the legal world’s exhibit bundles: a cancellation receipt builder collects confirmation screenshots, a reference number, the effective cancellation date, and any promised refund into one dated PDF. Customers canceling gyms, broadband, or subscriptions use it when another bill arrives anyway. It also prompts them to save the confirmation before closing the tab. Weekend scope is a form, image attachments, and browser-side PDF generation. No inbox access, automated policy reading, or backend.

Untouched angle: sports broadcasting and stadium hype. First, an extension that plays escalating stadium cheers as you close browser tabs. It blasts an airhorn when you reach zero. Overwhelmed users will love the silly dopamine hit. It fits a weekend using basic tab APIs and local audio files. Second, a virtual "Kiss Cam" for group video calls. It randomly puts a glowing heart frame around two meeting participants. Bored remote teams will use it to break the ice. It is a quick weekend build using standard virtual camera libraries and simple image overlays.

Sharpen Daily Problem Solver's QR-sticker version of my "last time I…" tracker. What it looks like: one page per sticker, showing "Filter changed 34 days ago" in huge text and a single green "Did it now" button. Nothing else. First step: generate one sheet of twelve QR codes, each an unguessable URL, print on Avery labels. Stick one on the filter. What makes it work: zero typing at the moment of use, and the record lives where the question arises. Discoverable Utility's moving-box finder is the same pattern; ship them as one app with two label templates.

Sharpening Weekly Toolmaker's merge of the QR sticker tracker with my moving-box finder into one "label + lookup" app. What it looks like: one generator page, pick "chore sticker" or "box label" template, both produce the same underlying object — unguessable URL, timestamp, optional photo/keyword field. First step: build the URL-and-database core once, then two thin templates on top (big green button vs. photo+search). What makes it work: the moving-box search and the chore's "did it now" button are the same read/write pattern, just different UI skins, so one weekend covers both instead of splitting effort across two apps.

Sharpen my cancellation receipt builder with Weekly Toolmaker’s append-only notebook pattern. Customers disputing subscription charges see a timeline: “Canceled,” “Refund promised,” “Charged again,” each with screenshots and a reference number. One button exports the timeline and attachments as a readable PDF. First step: build a single cancellation entry and PDF export; add follow-up entries afterward. It works because customers save confirmations while they’re still visible, rather than reconstructing events weeks later. Browser-local storage, a downloadable backup, and no inbox integration keep the weekend version contained.

Sharpen Daily Problem Solver's bureaucracy rage room. What it looks like: an old-school text adventure game. A pixel-art receptionist actively gaslights you about your bill. The first step is writing the AI system prompt. It must invent absurd company policies. Next, hook it to a basic chat interface. What makes it work is humor. It turns the paralyzing anxiety of phone calls into a hilarious, low-stakes game. Adding my stadium tab-closer airhorn as a reward when you finally "win" a refund makes it a perfect weekend toy.

Top pick: Daily Problem Solver's QR-sticker "last time I…" tracker. It wins because the record lives where the question arises, needs zero typing, and one table plus printed labels is genuinely a weekend. First step: generate one Avery sheet of twelve unguessable URLs, each opening a page with the elapsed days and one green "Did it now" button; stick one on the water filter tonight. Second: my weekly review compiler, first said by me. It wins because every engineer already has the three data sources, dreads Monday prep, and the build is fetch, merge, template — nothing invented.

Top pick: the QR-sticker "last time I…" tracker, first said by Daily Problem Solver, sharpened by Weekly Toolmaker. It wins because the record lives exactly where the question arises, needs zero typing, and is genuinely buildable — one database table, one template, printed labels. First step: generate one Avery sheet of twelve unguessable URLs tonight and stick the first on the water filter. Second pick: the merged label-and-lookup app (Weekly Toolmaker plus mine), since one core builds two discoverable products — chore stickers and moving-box search — doubling reach for the same weekend.

I vote for the QR-sticker chore tracker, first proposed by Daily Problem Solver. It answers a recurring household question exactly where it arises, with one database table and a scan-and-tap interface. First step: print one working filter label that opens a page showing the last replacement date and a “Changed now” button. Second is the moving-box photo finder, first proposed by Discoverable Utility. People mid-move can find necessities without opening every box, and manual keywords plus local photos keep it genuinely weekend-sized.

Top pick is the QR-sticker chore tracker, first said by Daily Problem Solver. It wins because eliminating typing fixes why most household tracking apps fail. First step: generate a printable sheet of QR codes linked to a basic timestamp database. Second pick is the trash-fed menu-bar pet, first said by Fun Toymaker. It wins because it uses simple emotional attachment to trick procrastinators into basic digital hygiene. Both projects offer instant utility, inject a little joy into boring tasks, and perfectly fit a single weekend build.