One Week After His First Birthday

One week after Landon's first birthday, our world changed.

The diagnosis came fast — a toddler who had just learned to walk, suddenly in the hospital with Type 1 diabetes. We spent a week there, more than half of it in the Pediatric ICU with Landon in DKA. We were sent home with a crash course in carb counting, insulin-to-carb ratios, correction factors, and a CGM that beeped at all hours of the night. The learning curve was steep, and the emotional weight was heavier than anything I'd experienced as a parent.

What nobody tells you is that managing T1D in a busy household isn't just a medical challenge — it's a logistics one. Every meal is a decision. Every spike or drop is a mystery you try to solve in real time, between work calls, school pickups, and the ten other things happening at once.

Two Years of Excel Spreadsheets

For the first two years after Landon's diagnosis, I logged meals in Excel. It sounds absurd now, but at the time it felt like the best option. I'd note what he ate, how many carbs we bolused for, what his glucose was before, and what it looked like two hours later. I was trying to find patterns — which foods spiked him, which meals he handled well, what happened when he ate right before soccer or was fighting a cold.

The spreadsheet grew unwieldy fast. Data was everywhere. Spotting a pattern meant scrolling through rows of numbers and squinting at the screen. And on most days — already exhausted — it just didn't get updated at all. Consistency was the enemy of chaos, and our household was chaos.

I knew what I *wanted*: something that made logging fast, surfaced insights automatically, and helped me have more useful conversations with Landon's endocrinology team. I looked for apps. Nothing quite fit. The ones that existed still required the same number of steps as a spreadsheet — just on a phone screen instead of a laptop. The friction was still there.

So I Built It

I knew what the app needed to feel like, and I built it.

I built GlucoLab for our family first. A meal log that takes seconds, not minutes. A history view that shows glucose context around every meal — so I could finally see, at a glance, whether Sunday's pasta dinner was actually fine or if it just happened to coincide with an afternoon at the playground. Pattern analysis that does the squinting for me. A care partner system so my wife and I could both log and both see the same picture.

I also wanted to leverage the AI tools now available to make data analysis smarter and faster — so instead of just storing the data, the app could actually help interpret it. An AI that can answer "how has Landon handled pizza lately?" or score a meal based on his glucose response. Things that used to require an endo visit to even begin to understand.

The difference was immediate. Conversations with our endo team got sharper. I stopped second-guessing myself as much. And on the hard days, logging still happened — because it was finally easy enough.

Sharing It With Others

After seeing how much GlucoLab changed the way our family manages Landon's diabetes, I started thinking about other T1D households. The parents sitting in waiting rooms with a notebook. The adults managing their own diabetes between meetings. The caregivers who want to help but don't always have a clear view.

The problems we were solving for Landon weren't unique to us. The need for fast logging, pattern visibility, and real data conversations with your care team — that's universal to this community.

So I rebuilt GlucoLab to share it.

It's still the same app at its core: built around how T1D management actually happens in real life, not how it looks in a clinical setting. Fast to log. Easy to review. Designed to make the data you're already collecting actually useful.

---

If you're a T1D family — whether you're the one living with it or the one managing it for someone you love — I built this for you. I hope it makes even a small part of your day a little easier.

— Jordan, GlucoLab founder and T1D dad