For most of this year, I was the only person on earth who knew what Arlo actually was.
Every half-finished idea. Every internal nickname. Every room in the code only I knew how to walk through. It all lived in one head.
You don’t notice the weight of that until it lifts.
I built it alone because I’d built things alone before. Ship alone, fix what’s broken at 3 AM alone, sit with the bad numbers alone at 9. There’s a certain pride in it. There’s also a thing it does to you over time, where you stop being able to tell where your taste ends and the product begins. The product becomes a posture you hold in your shoulders.
The loneliest part of solo building is that the only person you have to argue with is a tired version of yourself. Every decision gets made twice. Once when you make it. Once a week later when you’ve forgotten why and have to reconstruct the reasoning from memory.
Two weeks ago, Usman and Fahed walked into the room I’d been pretending wasn’t empty.
Usman and I had been circling the same problem from different angles for months. The problem is memory. The kind that doesn’t survive Monday morning. The kind that lives in five different tools and three different heads and gets stitched back together every week from screenshots and old Slack threads. I’d been building Arlo as my answer to that for one person. Usman’s company needed the version that worked when two hundred people were all carrying different fragments of the same truth.
He was across the table at the first real enterprise conversation we ever had for Arlo, the one I went in expecting to pitch and spent mostly listening through. By the end of it, Arlo wasn’t the same product. It had grown a second life, one where the memory belonged to the org instead of to each person separately.
I’ve known Usman for years. He’s the one I message at midnight with half a thesis and a screenshot. We’ve talked about building things together for as long as I can remember. This time, the thing we’d both already been building turned out to be the same thing.
A few days after he came in, he walked me through what shared memory actually looks like inside a company. Who sees what. Whose context stays private. Where a person ends and a team begins. By the end of the call, I could finally see the seam.
Fahed I’ve known a long time too.
He’s one of my favorite people to think out loud with. We’ve spent years swapping ideas, occasionally getting close enough that we’d both start arranging the room in our heads, then the timing or the shape of our lives would slide out of alignment again. There was a version of this team I tried to assemble once before. It almost happened. It didn’t. I think I’d been holding a seat for him without ever naming it.
This time the timing held.
The first real test came that Thursday.
I’d written a design doc the night before. The first full picture of how we’d take Arlo to companies that wanted to run it on their own servers, without us in the loop. Fourteen steps. A check at each one. The piece I’d been carrying in my head for weeks, finally on a page somebody else could read.
It was the first time on Arlo I wrote something and didn’t expect to be the person who carried it across the line.
Fahed read it the next morning. By lunch he was inside it. By dinner he’d shipped about fifteen separate things. Small, each of them. Stacked together they meant a real customer could stand up the product on their own setup without us touching it. The kind of work nobody sees. The kind you don’t get to tweet about, because it’s just supposed to work.
It looked like a week’s work. It was an afternoon.
Two days later, more landed. Including a small automated check that flagged three real bugs before they could have reached a customer. The bugs matter less than the fact that something was watching. Eyes on the work that didn’t belong to exhaustion. A second pair of hands that knew what good looked like.
I’d forgotten what that felt like. Or maybe I’d never quite had it on something I was carrying this deeply.
There’s a quieter thing underneath the velocity.
For most of my building life, I was the person in the room who cared about the thing the most. Caring that hard, alone, requires constant translation. You’re always converting the heat in your own chest into a version someone else can hold for an hour before handing it back to you.
In the new room, I don’t translate.
The product is moving fast. There’s a deadline. There’s a pilot. There are a thousand decisions ahead of us we’ll get wrong, and a handful we’ll get right in ways that will matter later.
What I keep noticing is the quiet.
A different quiet than I’m used to. The kind you get when you stop being the only voice in your own head about the thing you’re building.
The kind that means somebody else is in the room.