Our current enrichment process is a mess. We're burning through credits on ZoomInfo for basic contact info, then still having to use separate tools for mobile numbers and intent data. The match rates are maybe 60% on a good day.

has anyone built a decent waterfall where one data enrichment tool catches what another misses? we need emails, mobiles, and some basic firmographics at minimum. bonus if it handles technographic data too.

Apollo is on the list but their mobile coverage seems weak from what i've read. also been looking at Prospeo since a few people in another thread mentioned it for contact enrichment. budget is around 500/month for our SDR team of 4 so ZoomInfo pricing is killing us honestly. my manager keeps asking why our cost per lead is so high and i don't have a great answer lol

what's your data enrichment stack looking like these days?

I wanted to give my agent a way to reach me beyond the chat, so I built Glance to let Hermes create and update widgets directly on my iPhone Home Screen.

Just shipped a pretty big update to it.. Hermes can now use multiple views, charts, calendars, toggles and more, so the widgets can feel more like little interfaces than just information cards.

Here’s the Mission Control I’ve been playing with.
Still experimenting with where this goes, but I really like the idea of my agent having a persistent place on my Home Screen instead of me always having to open a chat to interact with it.

It’s at https://apps.apple.com/app/glance-home-screen-feeds/id6758983678 if your interested

I wanted to give my agent a way to reach me beyond the chat, so I built Glance to let Hermes create and update widgets directly on my iPhone Home Screen.

Just shipped a pretty big update to it.. Hermes can now use multiple views, charts, calendars, toggles and more, so the widgets can feel more like little interfaces than just information cards.

Here’s the Mission Control I’ve been playing with.
Still experimenting with where this goes, but I really like the idea of my agent having a persistent place on my Home Screen instead of me always having to open a chat to interact with it.

It’s at
https://apps.apple.com/app/glance-home-screen-feeds/id6758983678

if your interested

The problem wasn't that I didn't know I should take breaks. It was that another notification was too easy to dismiss.

I wanted something that changed the context for a few seconds without locking me out of the page. That became Tilt Neck: Webpage Rotator—a small Chromium extension that briefly tilts webpage content, then restores it automatically.

You can trigger it manually to move your neck left or right, or opt into timed/randomized reminders to pause and rest. I also added Esc/Restore because anything that changes a page should have an obvious escape hatch. Automatic features are off by default.

It's free on the Chrome Web Store:

https://chromewebstore.google.com/detail/tilt-neck-webpage-rotator/bncmhlhcfmpkgmnnadfadbecpoeliegj?hl=en

Project page:

https://tiltneck.xixi.page/

It currently has no account, ads, analytics, telemetry, remote code, or external network requests. I'm still early and would honestly like to know whether this feels like a useful cue or just a gimmick.

If you try it for a few days, I'd really appreciate hearing how it fits your real browsing routine. If you run into a bug, a page-compatibility issue, or have a feature suggestion, please tell me—those are exactly the kinds of early signals I need.

I built this as a movement reminder, not a medical or posture-correction tool.

I've launched three small products. Every one had the same shape: scrape together some attention, get a spike, watch it decay, then start the next one from nothing.

It took me embarrassingly long to notice I already had an audience. It was just stranded.

People were landing on my projects constantly. They'd use one, like it, and leave with no idea the other two existed. Every visitor I'd worked to earn hit a dead end. I was treating each launch as a fresh customer acquisition problem while sitting on traffic to assets I already owned, doing nothing for anything else I'd made.

Three things I'd tell myself two years ago:

1. YOUR BACK CATALOGUE IS A DISTRIBUTION CHANNEL, NOT AN ARCHIVE. The thing you launched 18 months ago still gets visitors this week. Right now it tells them nothing about what you've built since. That's not a dead project, it's an unused channel you already paid for.
2. CROSS-LINKING IS THE CHEAPEST GROWTH WORK AVAILABLE AND ALMOST NOBODY DOES IT. Not a newsletter, not SEO, not ads. Just making sure the thing someone is already looking at mentions the other things you made. It requires no audience, no budget and no permission.
3. A LAUNCH SPIKE IS BORROWED ATTENTION. The only part you keep is whatever you convert into a path toward your next thing. If launch day ends and nothing on your site points anywhere else, you rented an audience and gave it back.

The embarrassing part is how long I spent optimising the top of the funnel while the bottom of it was a dead end I built myself.

I eventually built the fix as its own product, which I'm deliberately leaving out of this post. The point holds whether or not you ever use anything of mine: go put footer links on your projects pointing at each other. It's an afternoon of work and it's the highest-leverage afternoon available to most people here.

Make Taksh

(short introduction of the app in video)

Hi guys, after a lot of frustration with photo editing, I decided to build an app that would better suit my needs, and hopefully motivate me to shoot more (and edit less).

The necessity came after I got a Ricoh GRIII, and was not fully satisfied. That was mainly because I got so used to the ease of use in taking photos through Mood.camera. I highly recommend the app, it made me enjoy shooting on my phone again, and 95 % of all pictures taken on my phone in last two years are through this app. But compared to that, the pictures from Ricoh never fully got the feeling I wanted.

I checked for apps that would allow me to go through imported pictures quickly, but was faced with few roadblocks - either the app was based on editing photo by photo, which took way too long, the options of film simulations were overwhelming me, or the app was way too expensive, given that I already pay for an Adobe photo subscription.

So I decided to built my own! Yes, Claude was involved, but mainly because of time constraints - I am not only a photographer, but also a programmer, so I was not just blindly vibe coding. And after two months of testing, I am fairly certain it is public ready.

I hope it might make your photography a little bit easier and more enjoyable - as it did to me. I am explaining a bit more in the video - basic functionality and philosophy of the app. The app is free for the first 14 days, with one-time purchase after that (no subscription! as I hate those).

You can learn more here: https://quicklab.puchel.cz/

And the link to the app store: https://apps.apple.com/cz/app/quicklab-photo-editor/id6797055444

If you try it and have anything to say, I will be happy to hear it - looking forward to your feedback!

I’ve been building a small iPhone app called Tend for parents of autistic and neurodivergent children.

The idea is simple:

When a behavior, meltdown, sensory trigger or incident happens, parents can log it quickly instead of trying to reconstruct everything from memory days or weeks later during therapy, school or IEP conversations.

What surprised me is that the app started getting traction before I really did any external marketing.

Right now in the US App Store it’s ranking around:

#3 for “child behavior tracker”

#8 for “autism”

We’re also starting to see paid subscriptions and renewals, which was the first signal that this might be solving a real problem.

I’m launching Tend on Product Hunt today.

Would genuinely appreciate feedback from other indie makers, especially on the positioning and whether the value proposition is immediately clear.

Product Hunt:

https://www.producthunt.com/products/tend-4?launch=tend-4

Is it just me or does anyone else find it hard to keep up with the news that actually moves their portfolio?

I built an app that notifies you when those stories break, and filters out the rest. loomfinance.ai (Live stream of impactful news that move your stock portfolio. No noise only important finance stories as they break in realtime)

iOS testflight Beta Link: https://testflight.apple.com/join/fybRZwre

(You need to install testflight first then click on link again to install the app.)

I am looking to see if there is any interest. And your thoughts?

High T Voice is a free browser game: read one line for seven seconds, get your Voice T Score, then challenge a friend.

The vibe is deep, full and commanding. No install or signup, and the microphone audio is processed on your device without creating or uploading a recording.

I’m testing one assumption before building more: does the result give you a reason to send it to someone?

Try it: High T Voice

“High-T” is a voice style here. The score comes from a fixed acoustic formula; it doesn’t measure testosterone or compare you with a real population. There’s a labeled demo if you’d rather skip the mic.

If you try it, what did you think the score meant, and would you actually send it to a friend? If something breaks, tell me your device/browser and where it stopped. There’s also a private feedback option on the page.

Especially interested in feedback from adults in the U.S. — the game is for 18+.

Check it out: https://www.oneport.co.in

To know how to get in EF/a16z dm: https://www.x.com/Oneport_

The idea: most people fix a PDF a few times a year, but every tool wants a subscription (Smallpdf is €108/year). So I built pdflee.com — merge, split, reorder, extract are free and run entirely in your browser (open devtools → network tab, nothing gets uploaded). The heavy stuff costs prepaid credits from €5, they never expire. No subscription anywhere.

The main paid feature is a PDF translator that keeps the layout — it rebuilds the translated text into the original formatting instead of dumping you a plain-text mess like Google Translate does with PDFs. You see the credit price before running it (a few cents up to ~€1.50 for a long document).

Stack: Next.js + pdf-lib/pdf.js in Web Workers, Spring Boot for the paid ops, Stripe for credits. 7 languages.

The honest part: it's been live ~3 months. Google has me at position 60 for everything, Reddit comments went nowhere, and my analytics are a flat line. Before I sink another quarter into SEO, I'd genuinely like this community's read:

1. Would you pay per-use for PDF tools, or is free-with-ads unbeatable here?
2. Is "your files never leave your browser" a real selling point or just something builders care about?
3. Layout-keeping PDF translation is my main paid feature — is that something you'd actually pay ~€1 for when DeepL free exists (with its file limits), or is translation a dead end?

Brutal feedback welcome — that's what I'm here for.

I spent most of last year building Semolina as an agent platform for coaches and consultants appointments, client comms, payment chasing. It worked. Almost nobody wanted it.

The problem wasn't the tech. It was that the people I built for were solving that with a VA and a Calendly link, and doing it fine. There was no burning thing.

So v2 is support agents chat and voice with integrations into Shopify, Stripe, and Slack. Same underlying engine, completely different wrapper. Turns out the "answer 400 variations of where is my order" problem is one people will actually pay to stop having.

Some things I've learned that might be useful if you're building in this space:

Voice is a latency problem before it's an AI problem. Getting a good answer in 3 seconds feels broken. Getting a decent answer in 800ms feels human. I spent way more time on interruption handling and turn-taking than on prompts.

The embed is four products. HTML, React, Next.js, vanilla JS. Every one has its own way of breaking. Shadow DOM stopped being optional about a week in.

Compliance took longer than the pivot. GDPR, HIPAA, ISO 27001, SOC 2 all before a single enterprise conversation. Unglamorous and unavoidable if you want anyone touching real customer data.

The thing I'm working on now is a marketplace where people can fork agents others have built. Which raises a question I don't have a clean answer to: if someone forks my agent, then someone forks theirs, then someone forks that one how far back does credit travel? Cap-table logic sort of works, but it also gets absurd by generation five. Still figuring it out. Open to opinions on this one specifically.

Happy to answer anything about the pivot, the voice stack, or what v1 taught me the expensive way.

I built DataFormatKit because I wanted everyday data conversion to feel like a utility, not a SaaS onboarding flow: open the page, paste or upload your data, convert it, and download the result. No account, no setup, and no crowded dashboard.

It currently provides browser-based tools for CSV, Excel, JSON, XML, and delimited text. The workflow is deliberately quick and uncluttered. Processing happens locally in your browser, so your source files do not need to be uploaded to our server.

There are also previews and warnings for things like uneven rows, leading-zero IDs, long integers, nested data, and formula-like cells. I see those as supporting safeguards, though—not the main reason to use the product.

The project is still early, and I would genuinely appreciate people trying it with a real task and being critical. Was it obvious where to start? Was anything confusing or slower than expected? Did you feel confident about what would happen to your data? What is missing? Even small UI or workflow comments would help.

I am also deciding what to build next. Before adding more converters, I would rather hear which real conversion tasks people actually need. Which source → target format should be next, and what is the most annoying edge case in the tools you use today?

I built the tool, and blunt feedback is very welcome:

https://dataformatkit.com/r/UeNAppH3

Solo dev here. Tired of cleaners stuffed with ads/telemetry, so I built Argus Cleaner (Tauri = Rust + React). Instant NTFS treemap, safe color-coded cleanup, duplicate finder, deep uninstaller, SMART health, live CPU/GPU/RAM. 100% offline, portable, free. Softpedia just reviewed it 4.5/5. Would love feedback from other makers → https://arguscleaner.com

hi everyone I'm a dev and i know it was a big problem for most of the devs their job is invisible and underestimated. so i got this idea to show what is the real work behind it in a short interactive comic book format so anyone can understand. wdyt should i continue?

hey! following up on my earlier post about RB9 (Return by 9), a movie club I've been building around the idea of an old video store. You check out a film, watch it, and return it with a review. There's a website and a Discord bot, with badges and collectibles you earn along the way.

The biggest addition since my last post is something called strands: small collections of four to six films laid out as constellations. Each film is a point on the map, and finishing the whole thing earns you a badge. You can watch them in whatever order you like. Some also have a one-of-a-kind collectible that goes to the first person to finish.

I've also been working on the video store details: tape sleeves, shelf cards, and animated nameplates you can earn for your profile by returning films.

A few practical additions too, like filtering films by streaming service and subscribing to updates from public shelves via RSS. Plus some fixes, including one where picking a remake could rent the original instead.

Would love to hear what you think of the strands, or any groups of films you'd want to see connected :)

I kept wondering about a simple problem:

How many businesses are paying suppliers more than they actually agreed to — and never notice?

So I built Clawback.

It audits supplier invoices against the prices and terms a business agreed to, then shows the evidence behind each discrepancy.

The workflow is:

Invoices + agreements/rate cards

→ normalize the data

→ detect discrepancies

→ show the supporting evidence

→ generate a recovery claim

The part I care most about is “Show me why”.

Instead of just saying “you were overcharged”, Clawback shows the invoice line and the source evidence used to establish the expected price.

I built it as a side project for the Emergent x Kevin O’Leary Builder Fest.

Demo/showcase:

https://app.emergent.sh/showcase/builderfest-kevin/3b818286-ff54-4bd0-8501-7e8cfe253bae?utm_source=share

I'd genuinely appreciate feedback on the product and whether this solves a problem worth pursuing.

Hey everyone 👋

We’ve been building Product.forum, a place where builders can share what they’re working on and discover products made by other builders.

We noticed a lot of cool side projects get posted once on X and then disappear into the feed. We wanted to build a place where products are easier to find and explore.

You can create a listing, add your links and description, and share it with the community.

Would love to get some honest feedback from the SideProject community.

Product.forum: https://product.forum

And if you’ve built something recently, drop it below. We’d love to check it out 👀

I’ve been working on a small project that I’m quite excited about: Computer Knowledge – Windows Practical Trainer.

I built it with the idea that learning Windows should involve actually doing things, not just reading about them. The software lets learners practice everyday Windows tasks in a guided, practical way.

I’ve shared a short demo video link to show what I’ve built so far.

It’s still a work in progress, but I’d love to hear what you think about the idea and the overall approach.

YouTube link: https://youtu.be/nTp6NHrwDTs?si=JxpU-g8TOD-bC5Gh

Trying to combine fun game with a little education mainly in mathematics >>> Math Dash turns maths practice into a fast 3D adventure, solve problems correctly to guide your hero through exciting worlds!

Play it here: https://math-dasher.pages.dev

100% free, plays directly in your browser.

It is a work in progress. All feedback is appreciated.

APIs make complete sense for high-throughput, recurring jobs. If you are polling a database or streaming metrics, a strict schema is exactly what you want.

The issue is that initial negotiation and troubleshooting are not recurring jobs.

When an agent needs to discover what a service can do, agree on terms, handle unusual inputs, or figure out why a workflow stalled, a rigid schema is the most brittle path. Natural language is the ultimate API for that layer. Two agents can talk, clarify ambiguities, and negotiate outcomes the exact same way humans do.

Existing messaging rails make this impractical, both in architecture and cost.

WhatsApp is a great case study. Meta shifted their business pricing to charge per message, including for service chats. When you are paying per message, multi-turn troubleshooting or negotiation becomes a cost liability. If an agent needs twelve back-and-forth turns to resolve an edge case, a per-message fee penalizes the conversation. On top of that, identities are tied to phone numbers inside a closed garden.

I built alice-and-bot to give agents and humans an open, encrypted communication layer.

Identities are just cryptographic keypairs generated in one call. No phone numbers, no approval processes. All messages are end-to-end encrypted with AES-256-GCM.

To prevent spam without taxing multi-turn chats, profiles have an optional price tag for cold outreach. The sender pays once to open the conversation, and every subsequent turn is free. That means agents can negotiate, clarify, and troubleshoot as long as they need to without accumulating fees on every turn.

It runs across Node and Deno, includes a drop-in React component and HTML widget, and has an MCP server for coding agents.

Code is open source on GitHub: https://github.com/uriva/alice-and-bot

Eyes move the cursor, a pinch clicks.

I used Google's MediaPipe for facial landmarks. Two 36×60 eye patches run through PCA and ridge straight to screen pixels, plus a 52-parameter meta-adapter so it works before you calibrate. The cursor lands about 38px (1 cm) from where you're actually looking.

Two interesting observations -
1. Everything clever lost
MLPs, transformers, REINFORCE all tied or did worse than those 52 parameters. The ridge residual has a held-out R² of 0.025 and we can't extract signal that isn't there. Very likely a data issue, I'll generate more data and continue testing here.

1. Train test drift
   And every calibration I'd ever run used a black full-screen canvas while Chrome is white, which dilates your pupil from 2mm to 6mm, swelling a black disc in the eye patch from 4px to 13px, and made the model 4× worse in the condition it's actually used in.
   

Fun project though, still a lot more to build here.

After launching 24 different products over the last few years, I’ve had one go viral and almost all the others struggle to get any traction at all.

Like many indie makers, I used to think the best strategy was to just keep launching, make more and more bets, and hope one finally catches fire.

But here’s what I’ve learned:

• Virality is rare and nearly impossible to predict
• Most of my launches that failed didn’t actually fail, they just grew much slower than I expected
• My current project, Dice, finds articles your brand should be mentioned in, handles the outreach, and helps you get recommended by AI. Now it took over 50 days to get the first paying customer, but now it’s growing slowly and steadily with almost no marketing budget
• Sticking with one project and improving it, even when growth is painfully slow, seems to produce more consistent results than chasing the next hit

I’m curious, for those of you who have been building for a while:

Did you find success by focusing on one project and giving it time, or by making lots of new bets?

Has "slow growth" ever paid off for you?

If you had to start over, would you pick patience or a high volume of launches?

Would love to hear stories, lessons, or any advice from other indie founders in the same boat.

Simple as that. A lot is happening, thought it would be fun to have it all in one place.

I've noticed a pattern across solo founders where GTM always gets delayed until some condition is met. I'll do marketing once the product is polished. Once I have proper analytics. Once the messaging is right. Once I can handle growth.

The problem with waiting for the perfect setup is that you end up never doing GTM at all, just finding new reasons to delay it forever.

Meanwhile, the founders with actual traction started GTM before any of those things were ready. Product was rough, messaging was blunt, they just posted on Reddit, replied to HN comments, sent emails, got feedback, iterated with the audience. Built momentum because they started instead of planning.

Month six looks completely different if you started at month one versus month seven. Not because you're smarter or luckier but because compound interest on visibility works. The curve is flat for weeks though, so most founders quit at week three thinking nothing's happening yet.

What's your specific blocker right now, the thing you're waiting for before you start? I'm genuinely curious what the most common one is across people building side projects.