Honestly, it started with watching people around me pay for insurance year after year without really knowing what they were paying for. My family, my friends, even me at one point. Everyone has a policy sitting in a drawer or an email somewhere, and almost nobody has actually read it. The problem usually shows up at the worst possible time, when someone files a claim and finds out something wasn't covered. I kept thinking, if AI can summarize a long article or explain a legal document, why can't it just read my insurance policy and tell me what I actually have? That was the spark. What problem were you trying to solve? Three things really. First, insurance policies are written in a language that feels designed to confuse you. Even educated people struggle to tell what is covered and what is not. Second, the important stuff is usually hidden. The exclusions, the fine print, the limits. These are the things that decide whether your claim gets paid, and they are buried on page 27. Third, there is nobody neutral to ask. Your agent wants to sell you something. Google gives you generic answers. You needed a way to ask a simple question like "is this covered?" and get a real answer based on your actual policy. So I built something that lets you upload your policy, get a clear summary, see a coverage score, get flagged on risky clauses, and chat with it like you would chat with a friend who happens to understand insurance. How did your approach or process evolve while working on this launch? A few things changed along the way. In the beginning I wanted the app to do everything. Policy comparisons, claim tracking, vendor ratings, reminders, the whole thing. I slowly realised that was a mistake. So I cut it down to one simple job. Upload a policy, understand it. Everything else went into the roadmap. The AI part also changed. The first version of the chat would sometimes make things up. That scared me. Insurance is not a place where you can guess. So I rebuilt it so the AI only answers from the actual document you uploaded. If the answer is not in your policy, it says so. That took longer but it was worth it. I also decided early to support English, Spanish, and Hindi. A lot of people own policies written in English but think in another language. Shipping with three languages from day one opened the app up to way more people. And finally, the App Store review process taught me a lot. Things like privacy, account deletion, clear pricing, and refund policies felt like paperwork at first. But going through it changed how I think about building products. These are not extras. They are part of earning trust. Next time I will build them in from the first day instead of adding them at the end. If I had to sum it up, I learned that building a consumer app is not just about the product. It is about trust. People will only use something like this if they feel safe, if the pricing is honest, and if the app respects them. That became the real focus by the time we launched.

Explain My Policy

Your Insurance, Finally in Plain English

Your Insurance, Finally in Plain English