I have run a software company, a care home, and a cafe at different points, sometimes more than one at once. None of the numbers I actually watched closely lived in a report. Revenue and margin mattered, obviously, but the thing that actually kept me up was smaller than that, a client who had gone quiet, a shift that was one call away from falling apart, a lead I told myself I would follow up with and then did not. None of that shows up on a P&L until it already cost something.
Curious how other people running a small or solo operation actually track that layer. Do you keep it in your head, write it down somewhere, or has anyone found something that actually surfaces it before it becomes a problem?
Hi all, there's a distinction I keep thinking about: apps built with AI (Cursor, Claude, Copilot writing the code) vs apps that depend on AI APIs at runtime to function.
I'm in the first camp. I used AI-assisted coding heavily to build Briskly (a cleaning app that scans your room and generates a timed task list), but the app itself makes zero LLM API calls. The scanning runs on Apple's Vision framework, entirely on-device. No tokens, no per-user inference costs, no latency, works offline, and my privacy label is basically empty.
I'm new to the Product Hunt world. I've been building my product solo for the past 8 months and I'm launching this Thursday so I've been obsessively reading launch advice and building a checklist.
Here's what I've got so far, split into 3 phases. Please tear it apart and tell me what I'm missing
1 Pre-launch Engage genuinely in the PH community (not just drop links) Get the coming-soon page live so people can follow Make sure supporters have accounts that aren't brand new (warm-up matters) Warm up your audience outside PH too LinkedIn, X, communities DM people ahead of time so launch day isn't a cold ask
