5.7KB
As a professional developer, the best app idea is usually not found by asking “what app should I build?” It is found by asking:
“What painful, repeated, expensive problem do I understand better than most people?”
A good web app idea sits where these overlap:
- You understand the domain
- People already struggle with the problem
- They are already paying with time, money, spreadsheets, Access databases, manual work, or frustration
- You can build a simpler tool for a narrow audience
YC’s “Requests for Startups” is useful for seeing broad market demand, but for you I would start closer to your real-world experience: print workflows, campaign tracking, Access-to-web migrations, internal tools, appointment systems, CSV/data cleanup, dashboards, and legacy-system modernization. (Y Combinator)
A practical way to find what to build
Start with a problem inventory.
For one week, write down every annoying workflow you see at work, at home, in congregation/volunteer work, or in your own development process. Look for phrases like:
“We always have to manually…” “This spreadsheet keeps breaking…” “Only Bob knows how to do this…” “We need Access, Excel, email, and a shared folder just to finish this…” “Customers keep asking the same thing…”
Those are app ideas.
Then score each idea from 1–5:
| Question | Score |
|---|---|
| Do I personally understand this problem? | 1–5 |
| Does it happen repeatedly? | 1–5 |
| Does it cost time or money? | 1–5 |
| Are people already using a bad workaround? | 1–5 |
| Could I build a small useful version in 2–4 weeks? | 1–5 |
| Is there a clear buyer or user? | 1–5 |
Anything scoring 22+ out of 30 is worth exploring.
Use “Jobs to Be Done”
A helpful format is:
“When ___ happens, I want to ___, so I can ___.”
Example:
“When I receive messy customer CSV files, I want to clean and validate them before import, so I can avoid production errors.”
That could become a web app.
Jobs-to-be-Done interviews are useful because they focus on the user’s real situation, not just feature requests. A common JTBD structure is: “When [situation], I want to [motivation], so I can [desired outcome].” (agileseekers.com)
Ideas that fit your background
Based on the type of work you do, these are stronger than random SaaS ideas:
1. CSV/Data Cleanup Web App
Upload CSV, validate columns, fix casing, quote fields, detect bad rows, export clean file.
Good for print shops, mail houses, nonprofits, agencies, and small businesses.
2. Access-to-Web App Generator
A tool that reads an Access schema and helps generate CRUD screens, reports, import/export pages, and migration SQL.
This fits your Access, Classic ASP, C#, SQL Server, and internal-tool background.
3. Campaign Tracker SaaS
You already created something in this space. Turn it into a focused app for small print/mail/marketing teams:
jobs, due dates, client files, proofs, mail dates, status, notes, and reporting.
4. Variable Print Job Dashboard
A web app for tracking print jobs from data receipt → proof → approval → production → mailing.
This is niche, but niche is good.
5. Small Business Appointment + Intake App
Not just scheduling. Add forms, file uploads, payment, reminders, and simple CRM.
6. “Excel/Access Replacement for One Workflow”
Pick one painful workflow and replace only that. For example:
donor survey entry, resident list cleanup, jurisdiction mailing exports, print proof approval, customer data intake.
This is often better than building a big generic platform.
Validate before coding too much
Before building, talk to 5–10 people who might use it. Do not ask, “Would you use my app?” Ask:
“How do you do this today?” “What is annoying about it?” “How often does it happen?” “What happens if it goes wrong?” “What do you use now?” “Have you paid for anything to solve this?”
The goal is to find pain, frequency, and budget. Recent startup validation advice still emphasizes not skipping the validation process before committing to an idea. (Indie Hackers)
My recommendation for you
I would not start with a consumer app. I would start with a boring business web app.
Your strongest lane is:
Internal business workflow tools for companies still using Excel, Access, email, shared folders, and manual data cleanup.
That is where your professional experience gives you an advantage.
A very strong first product could be:
“Data Intake & Cleanup Portal for Print/Mail Shops”
Customers upload CSV/Excel files. The app validates required columns, detects bad addresses, flags missing fields, previews records, creates an approval report, and exports a production-ready file.
Why this is good:
It solves a real business problem. It fits your print/data background. It can start small. It can be sold B2B. It is not dependent on hype. It gives you room to add features later.
Start with one narrow promise:
“Upload messy customer data and get a clean, validated production file in minutes.”
That is much better than “a platform for managing everything.”