I Built a Mental Health App While Working Full-Time
The 9pm Shift
My day job ends around 6. Dinner, family time, normal human stuff. Then around 9pm, the second shift starts.
That's when I open my laptop and work on Daylogue. An AI journaling app with voice check-ins, personality profiling, and a patent-pending narrative engine that reads your life back to you. I've been building it nights and weekends for over a year.
During the day, I'm the IT Director at Liquid IV. I manage infrastructure, security, systems that serve a billion-dollar brand. It's real work. I like it. But it's someone else's vision.
Daylogue is mine.
Why This App
I built Daylogue because I needed it.
I've always been a processor. I think by getting things out of my head. But traditional journals never worked for me. The blank page felt like a test I hadn't studied for. I'd sit there, pen in hand, and think: "What am I supposed to write?"
Then I started exploring what it would look like if the journal talked back. Not in a chatbot way. In a "hey, I noticed something about your last two weeks" way. What if your journal could read your entries and say: "You mention work stress every Thursday. Have you noticed that?"
That question became an app. The app became a company. Two patents pending. A growing user base. A narrative engine that generates serialized stories from your check-in data. All built between 9pm and 1am.
What Nobody Tells You
The founder narrative is always about the leap. Quit your job. Burn the boats. Go all in.
Nobody talks about the other path. The one where you keep your job, keep your health insurance, keep your mortgage paid, and build the thing anyway.
It's slower. It's unglamorous. Some nights you write three lines of code and fall asleep at your desk. Some weekends you choose the app over everything else and then feel guilty about it. Some weeks you don't touch it at all and the guilt is worse.
But here's what the "burn the boats" crowd doesn't mention: constraints breed clarity. When you have four hours a night instead of fourteen, you make better decisions. You cut features ruthlessly. You don't build things just because you can. Every line of code has to earn its place.
Being bootstrapped with a full-time job forced me to build something lean and focused. Daylogue does a few things exceptionally well instead of doing everything adequately. That constraint is baked into the product's DNA.
The Irony
The irony of building a self-awareness app is that it constantly forces self-awareness on you.
I use Daylogue every day. I check in. I see my patterns. And more than once, my own app has shown me something I didn't want to see.
Like the pattern where my stress peaks on Sundays. Not because of work. Because I'm already dreading Monday's context switch from my own project back to my day job. Seeing that pattern in my own data was uncomfortable. It was also exactly the kind of insight the app was designed to surface.
I built a tool that catches what you miss. Turns out, I miss things too.
Two Patents, Zero Investors
Daylogue has two provisional patents filed. One covers the narrative engine, the system that generates longitudinally coherent stories from check-in data. The other covers the voice extraction pipeline, real-time structured emotional data from voice conversations.
Nobody in the AI journaling space has patents. Not Rosebud. Not Day One. Not Daylio. We're the first.
We're also completely bootstrapped. No venture capital. No angel investors. No board to answer to. The company is funded by my day job and built with my time.
That means we move at our own pace. It also means every decision is made by the people who use the product, not the people who funded it. When we say "user-first," there's no shareholder to contradict us.
What I Learned
Building Daylogue taught me something I should have known from the start: consistency beats intensity.
The nights I forced myself to code for five hours were less productive than the nights I worked focused for ninety minutes. The weeks I took off and came back fresh produced better work than the weeks I ground through exhaustion.
That principle ended up in the product itself. Daylogue doesn't push you to check in every day. No streaks. No guilt. Just show up when you can. Consistency without pressure.
Thirteen years in tech leadership taught me how to build systems. Building Daylogue taught me how to build something that matters to me. Those are different skills. Both are hard.
If you're building something on the side and wondering whether the 9pm shift is worth it: it is. Not because of the outcome. Because of who you become in the process.
[Daylogue](https://daylogue.io) is the journal that reads your life back to you. Built nights and weekends. Available now.