The Roblox Update I Almost Pitched to BIL

It was a Tuesday night, maybe ten o'clock, and I was sitting at the kitchen table with my laptop open to the Roblox Studio build we'd been tinkering with for three weeks. The kids were in bed. The house was quiet in that specific way where you can hear the refrigerator hum. I had a half-eaten bowl of cold fried rice next to the keyboard and I was genuinely, earnestly excited about a new game mechanic my oldest had sketched on the back of a homework sheet.

And then — I don't know exactly how it happened — I started doing the math out loud to nobody. The update had pulled in a small spike of players. Not a lot. Not quit-your-job numbers. Not even quit-your-evening numbers. But enough that I opened a notes file and started writing down what I'd say if someone asked me to explain the model. That someone, in my head, had a very specific face. The face of a man who has pitched me a vending machine route, a pressure-washing franchise, and at least one cryptocurrency I still can't explain.

My brother-in-law. I was about to pitch him something. That's when I knew I needed to go to sleep.

How a Homework Sketch Almost Became a Slide Deck

The backstory is that my kids and I have been building Roblox games together for a while now. It started as a way to spend time, turned into a genuine project, and has produced — I want to be honest here — the kind of revenue that looks meaningful until you remember what an hour of your time is worth. We keep doing it anyway. That part doesn't bother me.

This particular update was a map expansion. My oldest had drawn out a whole new zone on notebook paper — little labeled squares, a boss area, a "secret room" with a question mark that they refused to explain to me until it was built. We spent a few weekends in Studio, me handling the scripting, them handling the layout decisions with the confidence of someone who has never once had to Google a Lua error at 11 p.m.

When we pushed it live, something small but real happened. The daily active player count bumped. Not viral-bump. Not press-release-bump. More like: a Tuesday-afternoon-bump that made the graph look less flat. My oldest checked the analytics before school and came back to the kitchen with a look like they'd just won something. Which, in the context of everything we'd put into it, maybe they had.

"Dad. We're at forty-seven. That's the most ever."

Forty-seven concurrent players. I told them that was great and meant it. Then I made the mistake of sitting with that number after they left for school.

The Notes File I'm Glad Nobody Saw

Here's what I actually wrote in that notes file. I'm paraphrasing because I deleted it, which was the right call: proven concept, engaged audience, recurring update cycle, monetization layer already in place, low overhead, kids handle QA. I used the phrase "update cadence." I wrote "kids handle QA" like that was a feature of the business and not just what happens when your children are more invested in the game than you are.

I was building a pitch. Not a formal one. Not a PowerPoint. But the mental architecture of a pitch — the kind you run through in your head before you say it out loud to someone who might actually respond to it. And the person I kept imagining saying it to was my brother-in-law, who has a long and documented history of hearing an opportunity and immediately wanting to make it bigger than it needs to be.

The version in my head went something like: we've got traction, we've got a content pipeline, we need capital to commission some asset packs and maybe run a few ads. He'd ask how much. I'd say a number. He'd say he knew a guy. And then six months later I'd be explaining to my kids why our game now has a branded loading screen for a pressure-washing franchise in Dothan.

I sat with the notes file for maybe twenty minutes before I closed the laptop. The thing is, this particular update had already done the thing it was supposed to do — it got players back in the door, it made my kid feel like the work mattered, it gave us something to build on. Bringing in a third party with money expectations would have turned "something to build on" into "something to report on." Those are not the same thing.

What the Notes File Actually Cost Me (Not Much, Which Is the Problem)

Financially, nothing happened. I never made the call. I deleted the notes file. The brother-in-law doesn't know any of this happened, which is probably for the best and definitely for mine.

But I spent a real evening on it. Not building anything. Not scripting anything. Not even playing the game with the kids, which is the part they actually remember. I spent it constructing a pitch for an audience of zero, for a deal that never existed, for money I was already deciding not to take. That's a specific kind of waste that doesn't show up in a ledger but sits with you anyway.

The update itself cost us maybe four or five weekend hours across two or three weeks. Asset work, scripting, my oldest's design sessions at the kitchen table, a couple of late nights where I was debugging collision boxes while something was compiling for my actual job in another window. The spike in players lasted about nine days before it leveled back off. I don't know the exact Robux number from that window and I'm not going to estimate it, but I will tell you it did not cover the asset packs I was mentally budgeting in the notes file. Not even close.

What I'm saying is: I got excited about forty-seven people and almost turned it into a business meeting. That's the cost. My own enthusiasm, pointed slightly in the wrong direction, for one Tuesday night.

What I Kept From the Night I Almost Made It Weird

I kept building with the kids. That part didn't change. The update cycle continues at whatever pace my oldest's notebook paper allows, which is faster than I can sometimes ship and slower than any investor would tolerate, which is exactly right.

I also kept a rule I'd already known but needed to re-learn: the brother-in-law is for hearing out, not for pitching to. That's the dynamic. He brings the ideas; I nod and ask questions and occasionally say "that's interesting" in a tone that means "I will never do that." The moment I show up with something of my own, the energy inverts and I lose control of the narrative. I've seen it happen. He's not a bad guy — he's enthusiastic and genuinely means well — but enthusiasm plus capital plus someone else's project is a combination I've watched go sideways enough times that I've stopped being curious about it.

The Roblox thing works, in its limited way, because nobody external has expectations for it. We built it without an audience and we've kept building it that way. The forty-seven players are real people who found us without a pitch deck. That's the whole appeal.

I did not delete the notes file because the idea was bad. I deleted it because the idea was fine and "fine" was enough. That distinction took me an embarrassingly long time to write down, and then I deleted that too.

The brother-in-law texted me that same week about a storage unit auction opportunity. I told him I'd look into it. I have not looked into it. The Roblox game is still running. My oldest is already drawing the next zone.

Note: Everyday Hustle Jeff is the written side of a digital series. These accounts are composite and dramatized. Any figures are what they were on the day, for one person, and are not a projection, a track record, or advice.