About — Lifr

I built the thing I couldn't find while I was drowning.

In my thirteenth year of healthcare IT, I was working 13-hour days and traveling three to four weeks a month — while Michelle and I ran an organization that has fostered more than 200 animals, kept a household going, and I managed my own health on top of it. On paper I was "optimized." In reality I was drowning — not because my life was too complex, but because managing that complexity had become a full-time job on top of my full-time job.

I tried every tool: Todoist, Evernote, Notion, Habitica, Things. Each one assumed the same thing — that the problem was me. I spent 25 minutes every week just maintaining lists, carried constant background anxiety about what I might be forgetting, and treated every missed task as evidence I was broken.

"The problem was never the complexity. I wanted the complexity — the animals, the work, the full life. The problem was friction."

In the spring of 2025 I started building Lifr for exactly one user: me. The first feature was auto-balance — the system looks at your week, sees what won't fit, and quietly moves it, so you only ever face what you can actually do. No guilt. No overload. Everything since has followed the same belief: remove the friction so people can manage real complexity without drowning in the administration of it.

Lifr isn't venture-backed and it isn't sprinting toward a billion users. It's infrastructure for people who, like me, have lived through seasons where just staying afloat was the achievement. If that's you — welcome. There's a chair for you here.

— Alex

A short, honest timeline.

Every milestone below happened. No revenue inflation, no team-size theater, no pretending the dark months didn't exist.

The Epic years

Thirteen years of complexity

Healthcare IT product work at some of the country's top hospitals. 13-hour days, constant travel, 200+ foster animals at home — and a slow burnout that every productivity tool made worse.

Spring 2025

First build

Lifr starts as infrastructure for one person: its founder. Auto-balance is the first feature — the system bends around your week instead of blaming you for it.

2025–2026

Built in private

The task core grows into an ecosystem of connected modules, dogfooded daily on a real, complicated life before anyone else touches it.

2026 — you are here

Open early access

The web app is live and free at app.lifr.global. Built in public from here on.

The ecosystem launch

Lifr launches as a family of modules that talk to each other — later this year, when it's ready.

Five permissions we grant every person who opens Lifr.

Permission to stop blaming yourself.

If you've failed every system you've tried, it's not a character flaw. Systems designed for calm lives don't survive complex ones.

Permission to live a complex life.

Caregiving, chronic illness, ADHD, multiple jobs, small kids, old parents, grief. All of it counts. All of it fits.

Permission to rest without guilt.

Rest isn't what happens when the list is empty. The list is never empty. Rest is a task too — and Lifr treats it like one.

Permission to adapt instead of grind.

Low energy today? Lifr hands you the low-energy tasks. High-focus window? Deep work surfaces. Plans bend around you, not the other way around.

Permission to let the system carry the load.

You don't have to hold the list in your head anymore. Put it down. The infrastructure has it.

If the software you use doesn't grant you at least one of these, it's probably making your life harder. Switch.

Eight stubborn principles.

These aren't marketing copy. They're the filters we use when deciding what to ship, what to refuse, and what to rewrite.

Validate before you solve.

Empty states don't scold. Notifications don't nag. The first message Lifr sends when a task's been sitting a while says "that makes sense" — not "you have 14 overdue tasks".

vs. the productivity-industrial complex

Design for low energy, not high.

If a feature only works when you're already functioning, it's not a feature — it's a filter. We build for the worst Tuesday of your worst month.

vs. "this works great when you're consistent"

Invisible labor becomes visible.

The person keeping the house running does 60% of the work and gets 0% of the credit. Lifr's household view makes every rotating task legible. No more invisible labor.

vs. "did you remember to do the thing"

Completion over perfection.

We celebrate the task you finished on low energy in 40% of the time, not the one you planned beautifully and never did.

vs. "optimize your system"

No dark patterns. Ever.

No streak held over your head. No red badges of shame. No "people like you also bought". Cancel in two taps, export everything, keep your data.

vs. growth-at-all-costs

Slow software, fast app.

We ship constantly and enable carefully — every feature lands behind a flag and proves itself before it reaches everyone. The app still opens fast.

vs. move-fast-break-things

Words are interface.

Every microcopy choice grants or denies a permission. "Task removed" not "task deleted". "Snoozed to tomorrow" not "failed to complete". Copy is a feature.

vs. default system strings

Build in public, build with users.

Built in public. Every feature ships behind a flag and is validated before broad enable. If we fail, you'll hear it from us.

vs. glossy launch posts only

One founder, one thesis: you're not broken. Your system was.