All builds

Personal systems

One place that knows every policy I hold, and what it does not cover

Life, health, home, travel, an investment-linked plan, and the fine print on all of them. An agent reads the documents, keeps a coverage map, flags gaps and overlaps, and reminds me before anything renews.

Insurance is the one area where everyone is under-informed about something they pay for every month. I had a folder of policy documents, a rough sense of what was covered, and no idea what was not. So I gave the folder to an agent.

The coverage map

Every policy goes in: the schedule, the wording, the riders, the exclusions. The agent builds one map across every policy: who is covered, for what, up to how much, with which exclusions, from which insurer, renewing when. Questions that used to mean opening six PDFs (“are we covered for that abroad?”, “what is the hospital cash daily limit?”) are now one message to Telegram.

Gaps and overlaps

The map makes two things visible that the PDFs never did. Where two policies cover the same thing and one is wasted money. And where nothing covers something that matters. Both go into a short list with a recommendation and the reasoning, and I decide.

The investment-linked plan

One policy is an investment-linked plan, which means part of the premium is invested in funds. The agent reads the fund holdings, the fees, and the allocation, and writes a plain-English review of whether the mix still makes sense. That review sits next to Gordon’s letters in the same memory, so the two do not contradict each other.

Renewals and claims

Every renewal date is in the calendar with a reminder thirty days out and a note of what changed last year. For claims, there is a playbook per policy: what to collect, who to call, which form, in what order. The point is that the worst day is not also the day you learn the process.

What I would tell you

Do not start with the analysis. Start by getting every document into one folder with the insurer, policy number and renewal date in the filename. Everything else is built on that, and it takes an hour.

Newsletter · weekly

The Build Log

One system teardown a week. What I built, what it cost, what broke, and the exact prompts that did the heavy lifting. No tool listicles.

  • A full build teardown with architecture
  • The prompt or config that unlocked it
  • The failures, with root causes

Weekly. Unsubscribe in one click. Read past issues.