Over the past year, I’ve been exploring ideas across scheduling platforms, healthcare software, church management tools, internal automation, and AI-assisted workflows. Most of these ideas will never become standalone products, and that’s perfectly fine.
The value hasn’t come from finding the perfect idea. It has come from noticing patterns that keep appearing across different problems, industries, and conversations. Here are a few observations that have stood out.
Technology Is No Longer the Moat
Building software has become dramatically easier. Modern frameworks, cloud platforms, managed services, and AI-assisted development tools allow small teams—or even individuals—to create products that would have required significantly more resources a few years ago.
The ability to build is no longer rare. The real challenges are elsewhere: understanding a problem deeply, reaching the right audience, creating trust, delivering a good experience, and staying focused long enough to make something useful.
Technology still matters, but it is rarely the limiting factor.
Many Product Ideas Are Really Workflow Ideas
One pattern I keep seeing is that many new ideas are not entirely new products. They are new ways of interacting with existing processes: a support assistant instead of a knowledge base, a conversational interview instead of a traditional screening form, or guided onboarding instead of documentation.
In many cases, the underlying work remains the same. What changes is how people move through it.
The most interesting opportunities often come from reducing friction rather than adding functionality.
Every Repetitive Task Becomes a Candidate for Automation
AI has changed how I look at routine work: support requests, candidate screening, bug triage, documentation, and monitoring. Tasks that once required manual effort now invite a different question: should a human be doing this step at all?
That does not mean removing people from the process. It means allowing people to focus on the parts that actually require judgment, context, and decision-making.
The challenge is finding the balance between automation and simplicity.
Simplicity Is Underrated
The more products I explore, the more I appreciate restraint. Adding features is easy. Removing unnecessary complexity is difficult.
Many successful products are not successful because they do more. They succeed because users immediately understand what they do and why they are useful.
A product that solves one problem clearly often creates more value than a product that attempts to solve ten problems at once.
Building Creates Better Questions
One of the most useful outcomes of exploring ideas is not finding answers. It is discovering better questions. Ideas that seem obvious can fall apart when they meet real users, while ideas that initially appear unremarkable sometimes reveal themselves as genuine problems worth solving.
The gap between theory and reality remains one of the best teachers.
No amount of reading about startups, software, or AI can fully replace the experience of building something and watching how people respond.
Looking Ahead
I don’t know which of the ideas I’m exploring today will become products. Some will be abandoned, some will evolve, and a few may become something meaningful.
What I do know is that the process of exploring, building, testing, and learning continues to reveal patterns that would be impossible to see from the sidelines.
For now, that feels like a worthwhile reason to keep experimenting.