This is the most personal thing I've written here, and probably the most exposed I've felt writing one. For over a year now I've been building JourneyLoop — heads-down, beta after beta, quietly spending my savings to do it. This week, that chapter ends: we're charging money for the first time. I wanted to write down what this moment actually feels like, and what the last year taught me while I'm still standing in the middle of it.

For a long time I told myself that one day JourneyLoop would have paying customers. I pictured that day as a finish line. It's here now, and it doesn't feel like crossing a line — it feels like standing at the edge of a cliff.

I've been building and building and building, burning through my savings to do it. Beta after beta, heads down, for longer than I planned. And it worked, in the way I most needed it to: we have people using the platform now. We've proven there's value in it. We've iterated and iterated until it became something real. After years of not knowing whether any of this was a good idea or an expensive delusion, that question finally has an answer, and the answer is yes. I'd be lying if I said there wasn't relief in that. The moment I'd been waiting for is here.

And now comes the part no one prepares you for. We actually have to charge money for it — to put a price tag on the thing and figure out how this becomes a business at all. That part is scary. Because the moment you ask someone to pay, they have to decide: is this thing Marco built actually worth it, or not?

So. Scary.

There's a deeper fear underneath that though, and I might as well be honest about it. For as long as I was still building, I never had to confront it: The act of building in and of itself was somewhere for me to hide (I wrote about that back in November). You can't fail at something you haven't finished, right? Charging money (finally) ends that. It hands the verdict to someone else. Phew!

So that's where I am: relieved and terrified in the same breath. The thing I wanted is here. Now what?

Here's what I've learned in the year since: I knew how to build the product. I had almost no idea how to build the business.

I'm an engineer. Give me a hard technical problem and I'll happily disappear into it for a week. But a year ago, nearly everything else it takes to turn a thing you built into a thing people pay for was foreign to me. I didn't know how to price something. I'd never written a line of marketing copy, and didn't know what made it good or bad. I couldn't have told you what a value proposition actually was, not really. Selling made me uncomfortable. Talking to customers about money made me more uncomfortable. And there I was, bootstrapping a company from the ground up, having to learn every one of those from zero.

A few things, in particular, rewired how I think about things today and moving forward.

The first thing that cracked open for me was this: people care about outcomes. They don't care about your tech. They don't really care about you. They care about what you can do for them — what actually changes in their life because you exist.

As an engineer, that one stung a little. I wanted the craft to count. I'd built something I was proud of under the hood, and the honest truth is that nobody on the other side could see it or needed to. They only wanted to know what it would do for them. It was one of the toughest lessons to learn.

Once that landed though, pricing stopped being a mystery and became a single question: how much will someone pay for the outcome you can give them? That's it. And the part I found genuinely fascinating is that the answer is completely independent of how you deliver it. It doesn't matter whether I solve someone's problem with software, or a spreadsheet, or an hour on a call — all that matters is that the outcome is worth something to them and that I can deliver it in a way that satisfies their needs. The delivery is interchangeable. The outcome and the price are the real things. That realization, more than any other, is what turned me from an engineer into something closer to a businessperson.

Which leads to the thing I'd do differently if I started over. I began the way an engineer begins: "here's a cool thing I could build — maybe people would pay for it." Backwards.

If I did it again, I'd start from the person and the problem. Who am I trying to help, what is actually painful for them, what would they pay to make that pain go away — and only then, figure out how to deliver it. Because sometimes the best way to solve someone's problem isn't a tool at all. Sometimes it's just getting on a call and walking them through it. And guess what - you can charge money for that without writing a single line of code. The engineer in me reaches for something to build. More and more, I've learned the answer could have been a conversation.

So here's where it all lands: a few people actually want to pay for the thing I built. After the year I just described — the savings, the betas, learning every part of the business from scratch — I can't really put into words how big that feels. Someone looked at what I made and decided it was worth their money. That's the whole game. That's the thing I wasn't sure would ever happen. It still feels unreal.

Before I could ask anyone to pay, I had to believe it was worth paying for — and that turned out to be its own quiet battle. I'd watched coaches I work with freeze at the exact same threshold: good at what they do, certain the work has value, and still unable to say a price out loud without flinching. I understood them completely, because I was doing it too. Putting a number on your own work and holding it there, without apologizing, is harder than it sounds.

And then there's the honest part I'm not going to dress up. A few paying customers is a milestone, not a salary. It won't cover rent in San Francisco yet, and my savings are running low after funding this whole thing myself.

So the real puzzle in front of me now isn't whether JourneyLoop is worth building — the people signing up answered that. It's how to keep building it without burning through the last of my runway. I'm looking at a few ways to bring in income alongside the work, ways that let me keep my hands on JourneyLoop rather than walking away from it. It's not the romantic version of the founder story. But it's the honest one, and I've made my peace with it.

There's one more thing this year taught me, and it caught me off guard as much as the business lessons did: building alone is hard. Not hard like a difficult problem — hard like a slow erosion. I've spent most of this stretch heads-down by myself, and somewhere in there I realized how much that isolation was costing me, and how much I'd undervalued simply being around other people doing the same thing.

So I'm working on it — which, for an engineer who'd happily never leave his desk, is its own uncomfortable skill to learn from scratch, right up there with sales. I've started actively looking for communities and guilds here in San Francisco to be part of. I recently came across Noisebridge and want to go check it out soon. I'm also looking into groups like Tribe AI and South Park Commons — rooms full of people building serious things, where the whole point is that you don't do it alone. I don't know yet which of these will stick or if I’m even considered worthy (lol). But I know the version of me that tries to do everything in isolation is not the version that makes it.

There's a line I keep on the front page of this very website, from Epictetus: make the best use of what is in your power, and take the rest as it happens. I've thought about it a lot this year. I've done everything in my power — built the thing, learned the business, put it in front of real people, and now asked them to pay. Whether it becomes a company from here isn't entirely mine to decide. I can control the effort. I have to release the outcome.

So that's where I am. Charging money for the first time, a little scared, genuinely proud, savings low, reaching out for the first time instead of building in a cave. It's the hardest thing I've ever done. I'd do it again tomorrow.