After my last exit, I took time off. A lot of time.
To be a good dad and husband. Or at least dad.
I went to every soccer game. Every dance recital. I was there for bedtime. I cooked dinner. I did the fucking school pickup.
I taught myself to code something other than PHP, because I've always known engineers were the coolest people in the room.
Then I decided to build Cerebral.
And I forgot how much startups suck.
The Ugly Baby
You know what a startup is?
It's a new baby in the family. Except this baby isn't cute. Nobody wants to hold it. Everyone hates it.
Even you hate it sometimes.
The kids hate it because dad's always working. My wife hates it because I'm physically sitting at dinner but mentally debugging why the Context River is dropping mandatory SOPs. I hate it because it's 2 AM and I'm rewriting the execution engine for the third time because LLMs don't follow fucking instructions.
But you can't abandon it. Because it'll die. And you'll have wasted six months of 15-hour days and your kids will barely remember what you looked like during Q3.
The Thread
Here's the problem with building complex interconnected systems: you have to hold the entire architecture in your head.
All 16 services. How they communicate. What depends on what. Where state lives. How memory flows through the context river. Which service owns which data.
You lose that thread, you're fucked.
Someone asks you a question — even something simple like "Can you help with homework?" — and you lose it.
That mental model you've been building for three hours while writing the governance engine? Gone. Now you need 20 minutes to reconstruct it.
So you have two choices:
Look up when they talk to you. Be present. Answer the question. Help with homework. Be a dad. Lose the thread. Spend 20 minutes getting back. Realize it's now 11 PM. Work until 2 AM. Wake up exhausted. Repeat.
Don't look up. Keep coding. Hold the thread. Ship the feature. Your daughter asks for help with math and you grunt "Ask mom." Your son wants to show you something and you say "Not now." You're there. But you're not there.
The Guilt
Both choices suck.
Look up → You're falling behind. The platform isn't done. Customers are waiting. Every day you don't ship is a day competitors might catch up.
Don't look up → You're a shitty dad. Your kids will remember that you weren't there. Your wife is handling everything alone. You're missing their childhood for a company that might not even work.
There's no winning.
The Reality
I'm writing 250,000+ lines of production code while raising three kids. 15-hour days. 7 days a week.
I wake up at 6 AM. Kids need breakfast. School dropoff. Then code until they get home. Help with homework. Dinner. Bedtime. Then code until 2 AM.
Weekends? Same thing. Soccer game at 9 AM? I'm there. But I'm on my laptop during halftime fixing a bug. Birthday party? I'm there. But I'm thinking about how to implement dry-run approval workflows.
Physically present. Mentally absent.
What My Wife Says
"You came out of retirement for THIS?"
She's not wrong. We were comfortable. I'd sold a company. We had money. I could've just... not done this.
Instead, I'm grinding 15-hour days to build infrastructure for synthetic labor while she handles three kids, the house, everything.
She calls herself a "trophy wife." I call her "the reason this company exists." Because without her handling everything I'm not handling, this doesn't work.
Why I'm Doing This Anyway
Because I think this is the biggest opportunity I'll see in my lifetime.
Synthetic labor is going to be a multi-trillion-dollar market. Not AI assistants. Not productivity tools. Actual labor replacement. AI employees that do the work instead of humans.
Somebody's going to build the infrastructure for that. I think we can be the ones who do it.
The Tradeoff
Right now, I'm a mediocre dad. I'm there for the important stuff. But I'm distracted. I'm not fully engaged.
If this works, I can be a great dad later. Not because of the money. Because I'll have built something that doesn't require me to grind 15-hour days forever. Infrastructure scales. Once it's built, it runs.
That's the bet. Grind now. Build the foundation. Then be present. Actually present. Not physically-there-but-mentally-debugging-Redis present.
The Bottom Line
If you're thinking about starting a company while you have young kids: it's going to suck. You will miss things. You will be distracted. You will feel guilty. Your spouse will carry more than their share.
And you'll do it anyway.
But she married an entrepreneur. Her dad is an entrepreneur. Her grandad is an entrepreneur. She is an entrepreneur. And with any luck, her kids will be entrepreneurs too.
So here we are.
Ben Jenkins
Founder