How to come up with startup ideas when you don't have one

"I want to start something but I don't have an idea" is the most common opening line we hear. The standard advice — solve your own problem — is fine if you happen to have a burning one. Most people don't, and the advice quietly becomes "wait for inspiration", which is not a method.

Ideas are findable. They sit in public, written down by the people who will later become customers. Here are seven places to look, roughly ordered by how directly the evidence translates into a business, with examples from the data we collect at 1dea.io.

1. Other people's complaints about software they pay for

Reviews on G2, Capterra and app stores are years of unsolicited customer interviews. The middle ratings — two to four stars — are the useful ones: written by people who kept paying and still had something specific to say. When the same complaint appears across competing products, no single vendor can fix it, and that is a market.

This is our core method, and it is entirely manual-friendly: pick a category, read the middle reviews of every product in it, count repeated complaints. "Feature overload makes AI writing tools unusable" appears 117 times across 10 different products. "HR support that never resolves anything fast" appears 433 times. The full step-by-step is in how to validate a startup idea with complaints.

2. Founder revenue threads

Every day, founders post revenue numbers in r/SaaS, r/startups, r/indiehackers and r/SideProject. Each credible post is proof that a specific kind of customer pays for a specific kind of product — which means adjacent gaps, other niches for the same model, and underserved geographies are all open. A hotel QR concierge doing €4,941/month through one hotel is not just one business; it is evidence that hospitality staff shortages convert into software revenue.

We sweep these threads automatically and screen each claim against its own comment thread to drop ads and unbacked numbers — the result is the Traction feed. Read it the way you'd read the reviews: not to copy the product, but to see which customers demonstrably pay.

3. The workaround economy: spreadsheets, exports and shared drives

Wherever people maintain a spreadsheet next to the software they pay for, the software has a gap with a budget attached. Payroll admins exporting the same reports to a shared drive every fortnight are one spreadsheet away from being customers of scheduled HR report delivery. QA teams keeping JMeter files in Git because the vendor has no history are the wedge for settings recovery for test plans. Ask anyone in a back-office role what they keep in spreadsheets that "the system should really do" — every answer is a lead.

4. Pricing pages that make people angry

Read the pricing page of any category leader, then read what users say about it. Per-seat pricing that punishes growth (155 complaints across five ops platforms), subscriptions forced on occasional users (eight SEO suites), paywalls with unclear boundaries (eight photo editors). Each pricing complaint suggests two businesses: a re-packaged competitor (sell by the unit, not the seat) or a cost-visibility tool the vendor will never build.

5. Support queues that never answer

When a vendor's support is famously bad and the product is famously entrenched, the gap is not a competitor — customers won't migrate — it is a service that gets people unstuck. The biggest pain point in our entire database is HR support (433 complaints, three payroll platforms). Nobody is ripping out their payroll system over it; plenty would pay for escalation playbooks or an after-hours expense support desk.

6. Trigger moments: migrations, audits, new hires

Steady-state problems are hard to sell into; moments of change sell themselves. Scan for events that force budget: a company switching expense tools (every employee becomes a new user — policy onboarding), an email platform migration (batch MBOX-to-PST conversion), a first finance hire who suddenly owns the cloud bill (database cost governance). If you can name the trigger, you know when the customer buys.

7. Your unfair audience

Last, invert the usual order: instead of picking an idea and finding customers, pick the group of people you can already reach — a professional community you belong to, an industry you've worked in, a language market you're native in — and go looking for what they complain about. A mediocre idea with distribution beats a brilliant one without. The idea database is organised by market for exactly this: start from the audience you have, not the idea you wish you had.

What not to do

• Don't brainstorm in a vacuum. Lists generated from imagination optimise for what sounds impressive, not what anyone pays for.
• Don't start from a technology. "What can I build with AI" produces products looking for problems; every list above starts from a person with a documented problem.
• Don't collect ideas indefinitely. One afternoon of sourcing, one week of validation, then five conversations with real people. Volume of ideas is not progress.