SiteWalk: Voice-to-Report Automation for Field Contractors

Your three options are categories, not problems. "Self-learning app", "help desk SaaS", "small tool that does one thing well" describe shape, not who is hurting. Every one of those is crowded with people who are better funded than either of us, and none of them tells you what to build on Monday. The thing that actually separates projects right now is not the idea and not the stack. It's access. Pick the niche where you already know people who do the work, because that's the only place you'll hear the specific complaint that turns into a product. Mine came from family in the construction trade. The complaint was never "we need software". It was that the site walk takes 30 minutes and the write-up afterwards eats the evening. So I built a thing that turns a spoken job walk into a structured estimate. I would never have guessed that problem from the outside, and no amount of market research would have handed me the sentence "the 9pm write-up is the part I hate". Two things I got wrong that might save you time: The AI part is the easy half, and it's getting easier every month. That also means it's worth almost nothing on its own. The hard half is the domain: making "three new GFCIs" become a line item with a quantity, a unit and a price nobody made up. That's where the months go, and that's the part a reviewer of your portfolio will actually find impressive, because it proves you understood something other than an API. Shipped and used beats big and unfinished. Ten real users will teach you more, and read better to a client, than an ambitious half-built platform.

Your three options are categories, not problems. "Self-learning app", "help desk SaaS", "small tool that does one thing well" describe shape, not who is hurting. Every one of those is crowded with people who are better funded than either of us, and none of them tells you what to build on Monday. The thing that actually separates projects right now is not the idea and not the stack. It's access. Pick the niche where you already know people who do the work, because that's the only place you'll hear the specific complaint that turns into a product. Mine came from family in the construction trade. The complaint was never "we need software". It was that the site walk takes 30 minutes and the write-up afterwards eats the evening. So I built a thing that turns a spoken job walk into a structured estimate. I would never have guessed that problem from the outside, and no amount of market research would have handed me the sentence "the 9pm write-up is the part I hate". Two things I got wrong that might save you time: The AI part is the easy half, and it's getting easier every month. That also means it's worth almost nothing on its own. The hard half is the domain: making "three new GFCIs" become a line item with a quantity, a unit and a price nobody made up. That's where the months go, and that's the part a reviewer of your portfolio will actually find impressive, because it proves you understood something other than an API. Shipped and used beats big and unfinished. Ten real users will teach you more, and read better to a client, than an ambitious half-built platform.