How I Ship Products in 90-Minute Windows
The parent developer’s guide to creating time where none exists.
I have 90 minutes of real focus time per day. Some days less. Some days zero.
I used to be an engineering director with a calendar full of deep work blocks and a standing desk in an office where I’d be unbothered for hours. Now my office is the kitchen counter, my sprint window is the gap between bedtime and when I physically cannot stay awake, and my ever-present co-founder is three years old.
Here’s a little of what I’ve shipped in the last few months from that kitchen counter: a book, a newsletter with weekly posts, a product line on Gumroad, multiple open source tools, and a daily content operation across three platforms. Not because I’m grinding 12-hour days, but because I stopped being the one who does the work and started being the one who reviews it.
Here’s how I’ve set myself up to create the time to ship where none exists.
The reframe that changed everything
The biggest unlock wasn’t a tool. It was a mental model shift.
I used to think my job was: research, write, build, design, post, promote, respond. All of it. Every day. In my 90 minutes. No wonder nothing shipped.
Now my job is: communicate intent, review, and approve. That’s it. I went from creator to editor. From builder to architect. From the person pushing code to the person reviewing pull requests.
The work still gets done. It just doesn’t require me to be the one putting in the hours.
The async everything stack
Here’s my actual setup. None of this is theoretical — I run this daily.
OpenClaw + iMessage: The async command layer
I have an AI agent (OpenClaw) that I talk to over iMessage. I text from my phone. While my kid plays. While I’m at the park. While I’m making lunch.
I don’t sit at a computer to manage my pipelines. I text “schedule the new posts” from the playground and it happens. I text “show me the overnight report” and I get a summary of what got done while I slept. I text “draft an about page using these two files” and I review the output when I have five minutes.
The key insight: iMessage is low-friction. I don’t need to get to my laptop, open a terminal, or log into a dashboard. The tool lives where I already am — in the same app I use to text my husband and my mom. My phone is in my pocket. The cognitive overhead is near zero.
Cron jobs: The night shift
While I sleep, automated jobs run:
Content research: My agent browses, researches new ideas, and outlines notes and posts. I wake up to a summary of what was explored and new markdown files waiting for my review.
Research: A nightly scan of HN, dev Twitter, and niche blogs compiles a research digest on topics I’m tracking. It’s my own personal-interest-filled, high-signal newsletter. I read it over coffee.
None of these require me to be awake. I set the schedule once. They run. I review the output in the morning.
The morning routine isn’t “sit down and figure out what to do today.” It’s “review what’s already been done and approve what ships next.”
The content pipeline: from creator to reviewer
Here’s what a typical day looks like:
7am: I text “gm.” My agent sends me the overnight report — what drafts were written, what research was compiled, what tasks were completed.
Throughout the day (in 2-minute bursts): I review on my phone. “This is good, queue it.” “Turn this post into a tweet.” A rambly stream-of-consciousness moment about something that happened with my 3yo becomes a new article. My involvement goes from hours of writing to a few minutes of grammatically-imperfect notes.
After bedtime: This is my only real focus block. But because the research is done, the drafts exist, and the admin is handled, I can spend it on the ONE thing that actually needs my brain: writing the newsletter post, editing the book, or building something new. The 90 minutes isn’t diluted across twenty tasks. It’s concentrated on the one task I can’t delegate.
The principle: decouple work from presence
The operating principle behind all of this: your work and your schedule need to be decoupled in time.
The content gets drafted at 1am by an agent. I review it at 10am from my phone. It posts at 2pm automatically. A visitor reads it at 8pm and becomes a customer. At no point did I need to spend one-on-one time with that customer to make a sale.
This is what makes the parent-developer life viable. Not “hustle harder” or “wake up earlier.” Definitely not Pomodoro timers. Just: build systems where the work happens when you’re not there, and your job becomes directing the intent and reviewing the output.
What you actually need
The specific tools matter less than the pattern. But since people always ask:
An AI agent you can talk to async (I use OpenClaw over iMessage, but the concept works with any tool that doesn’t require you to be at a desk)
Scheduled automation for anything repetitive (cron jobs, Zapier, whatever — the point is it runs without you)
A review queue, not a to-do list — your daily work is approving and editing, not creating from scratch
One focus block that’s protected for the work only you can do
The 90 minutes isn’t the limitation. The 90 minutes is enough — if you’re not wasting it on things a system could handle.
The unfair advantage
Here’s what the solopreneur Twitter crowd misses about parent-developers: the constraint IS the advantage.
When you have 90 minutes, you don’t over-engineer. You don’t build features nobody asked for. You don’t spend three hours picking a font. You ship the thing that matters and you ship it now, because bedtime is a hard deadline and toddlers don’t have a pause button.
I’ve shipped more in the last few months with 90-minute windows than I did in some quarters with a full engineering team. Not because I’m faster. Because I’m forced to be focused. I can’t afford feature creep or busy work. No slack time means no wasted time.
Every parent-developer already has this skill. You’ve been project managing under uncertainty since the day your kid was born. You just need systems that let you use your scarce time on decisions instead of execution.
The tools exist. The hours don’t need to. You just need to stop being the one who does the work and start being the one who decides what ships.
This is the TOOLS pillar of Raising Pixels — the parent developer’s toolkit. I write about computational thinking for kids, hands-on building projects, and the workflows that make it all possible when your coworker is three.