I Can Build Anything. It Still Isn't Paying Me.

There's a specific kind of broke that hits when you can build almost anything and none of it is paying you yet. It's different from regular broke. Regular broke is not having the skills. This is having the skills and watching them not convert.

I'm going to say the thing that most people building in public don't say: I have legitimate skills — real ones, not resume skills — and they still aren't converting into income. The bills get paid by the day job, not by anything I've built. The market isn't impressed by my agent architecture. No customer has ever once asked how many tests pass in my repos.

I'm writing this because I think a lot of people are in this exact place right now, and nobody's saying it out loud. Everyone's performing progress. I want to just be honest about what this actually feels like.

what it is and isn't

This isn't a post about failure. I'm not quitting, I'm not spiraling, I'm not looking for sympathy.

This is about a specific gap that doesn't get named enough: the distance between what you can do and what you're currently converting into income. That gap can be enormous, and it can coexist with genuine skill, genuine output, and genuine forward motion.

I work a day job training healthcare workers on clinical systems. It's real work and I'm good at it. After hours I'm building — agents, products, systems, infrastructure. I've shipped things in the last six months that I'm genuinely proud of. And I'm still looking at the gap between what I've built and what it's earned, doing the math I don't want to be doing.

That's the thing I want to name.

the AI world makes it harder to admit

Here's what the AI moment does to this feeling: it makes it seem like everyone else figured it out.

The feed is full of people shipping products, closing deals, hitting MRR milestones, building in public with apparently clean and linear trajectories. The failure stories exist too, but they come out later, polished, framed as growth. The real-time version — the one where you're not sure if you're going to make it this month — almost never makes it onto the timeline.

So you look around and wonder what you're missing. What's the unlock everyone else found? What do they know about converting skill to income that I don't?

The honest answer: sometimes it's distribution. Sometimes it's timing. Sometimes it's cash runway — the ability to survive the gap while something builds. Sometimes it's a piece of luck that looks, from the outside, like strategy.

None of those are skill problems. Which is exactly what makes it disorienting when you've got the skills.

the midnight builder math

There's a specific version of this that I think is common and rarely discussed.

You work all day. You come home. Family obligations exist and they're real and they matter — dinner, time, presence, the actual reason you're building anything in the first place. Then somewhere after the house is quiet, you sit down and you build. An hour, two hours, maybe three if you can hold yourself together.

The math of that session — what you can ship in a compressed window while running on fumes — is different math than a well-rested founder with eight hours and a clear runway. It's not bad math. It's just limited. And the product you're building on that math takes longer to reach revenue than you'd like, which means the gap persists longer than you'd like.

I'm not looking for a different situation. This is the situation I'm building inside of, and I'm building inside of it on purpose because the other things — the family, the day job that funds the gap — are worth it.

But I want to be honest that this is slower than it looks from the outside.

what actually moves the needle (and what doesn't)

I've been doing this long enough to have learned a few things about the gap between skills and income.

Shipping more doesn't close it by itself. I've shipped a lot of things. The gap isn't a product shortage. It's a distribution and conversion problem. You can have excellent products that nobody knows about. You can have people who know about them and haven't pulled out a card yet. Both of those are different problems from "can I build this."

The gap closes through surface area — making contact with actual buyers, consistently, over time. That's not glamorous and it doesn't compound as fast as shipping does. But it's the part that actually connects capability to income.

Talking about what you're building, in public, is work. I say this because I've historically underweighted it. Writing this post is work. Posting about a project is work. The builder tendency is to keep shipping and trust that the work will be found. That's not a strategy. That's hope.

Cash runway is the variable nobody talks about honestly. If you can survive the gap — if your day job covers the bills while the product builds — you have something a lot of people don't. That's worth naming too. The people who build their way out of the gap fastest usually aren't doing it because they're more skilled. They're doing it because they had enough runway to survive until something converted.

what I'm actually doing about it

I'm doing a few things differently than I was six months ago.

I'm forcing myself to talk about what I'm building before it's finished, which is uncomfortable and also necessary. I'm making the work visible because invisible work doesn't attract buyers.

I'm getting more deliberate about which projects have revenue potential in the next 90 days versus which ones are infrastructure plays that pay off later. Not abandoning the long games — just being honest about the timeline.

And I'm sitting with the discomfort of the gap without pretending it isn't there. Because pretending it isn't there doesn't make it smaller. It just makes you feel like you're the only one dealing with it.

You're not the only one dealing with it.

the thing I want you to take from this

If you are skilled and still broke, you are not doing it wrong. You may be in a gap that has nothing to do with your capability. The gap is real and it's common and it's survivable and it's also genuinely hard.

The way out of it isn't more skill. It's distribution, it's surface area, it's surviving long enough for something to convert. Those are learnable and doable. They're just different problems than the technical ones that got you here.

I'm working on them. Most days I think I'm making progress. Some months the math doesn't agree.

Both things are true at the same time.

— Dru Edwards