I need to tell you something I've been keeping to myself for longer than I wanted.
Not because I was protecting a strategy or waiting for the right moment to reveal it. It's just that I had convinced myself that the person I used to be was someone I needed to leave behind.
I'm a builder.
Not a house builder (not yet anyway) but an online builder. Always have been.
There's something in me that comes fully alive when a half-formed idea in my head starts taking shape in the real world - when the logic clicks, when the thing works, when something that existed only in my imagination becomes something real people can experience online and move through.
That's my creative outlet and it's how I express things words alone can't hold.
1 of 4
The vow I made to myself
A few years back, I had a SaaS project fail spectacularly. The full story is coming in Letter 027, because it deserves proper telling, but the short version is this: I put real time, money, and belief into something, and it crashed in a way that left a mark.
And so I made myself a vow. Apps? Dashboards? Never again.
Stay in your lane. You're not a developer so stop pretending you can build things.
When the AI wave started, that vow became my armor. Every time something in me started getting excited, every time I caught myself sketching an idea or thinking "what if I built this", I had a ready-made answer:
Remember what happened last time?
And for a long time, that worked. I convinced myself it was discipline and knowing my limits.
Then someone whose opinion I respected reflected something back to me that landed harder than it should have: you're avoiding your real work by hiding in builder mode.
I didn't push back.
2 of 4
What I was actually doing
The thing about suppressing a part of yourself is that it doesn't just disappear.
It finds other shapes. It leaks into your energy, your enthusiasm, the way you show up for the work you've decided you're "supposed" to be doing.
What I was calling discipline was costing me something I couldn't quite name.
Over the past few months, I've had to be honest about that with myself. The builder in me wasn't a distraction. It was the part of me that generates the clearest vision and the deepest enjoyment in the work.
I wasn't avoiding something by building. I was avoiding something by not building.
The realization that followed felt almost embarrassingly simple once it landed: being a builder doesn't exclude being a mentor, a strategist, or a writer. It just happens to be the role I enjoy most. The medium through which I can fully express what I see.
For some people, that medium is making reels on socials. For others, writing. For some it's being in rooms with people, connecting and energizing conversations into motion.
The medium doesn't really matter. What matters is whether you've found yours or whether you've locked it away because someone, or some past version of events, told you it wasn't worth trusting.
3 of 4
What became real yesterday
I've been building for the past several months. Quietly, and with more excitement than I've felt in years.
It first started with a 72-hour hackathon to see how fast I could build AI agents using a dedicated app.
Then I started building mini apps to solve daily business challenges (like SignalFlow and FlowOne). I also started offering BuildFlow sessions with others to help create similar mini solutions for their business challenges.
The two apps I built when I first let the builder back in are in letter 023 (FlowSignal) and letter 023b (FlowOne).
And finally, I've decided to tackle my white whale.
A vision I've had for a long time: a better way to take care of clients without living inside client delivery for most of the day. A system where AI doesn't just help me work faster, but helps clients produce better work themselves - and where every client experience feels personal, not templated.
Yesterday, that vision became real. Real people went through FlowOS - the human-led, AI-supported client delivery platform for the first time.
At one point, I was doing some final checks, and I just stopped. I sat with what had actually just happened - and I started crying.
Not from stress. Just the opposite, because the thing I'd told myself was stupid, impossible, and evidence of bad judgment had just become something beautiful that actually works.
Letter 027 is where I'll tell you all of it: how the old SaaS failure and this new launch connect, what I built, and what it means for the direction of this work. That letter needs space I don't have today.
Today I just needed to say this and ask you a question.
4 of 4
What I want you to sit with
If there's a creative role or a version of who you are that you've been keeping down - I want you to think about where that vow came from.
Was it a real lesson, or was it a wound dressed up as wisdom?
Was it something you genuinely decided, or something someone without your vision told you, and you believed them because the timing made it easy to?
I can tell you from the inside of this moment: I haven't felt this driven, this in the flow, this much like myself in years.
It "just" took finally letting the part of me that builds come back out, without apology.
So if you needed someone to tell you it's okay to let that side of you out - I'm telling you.
Do it.
Until next week,
Filip "builder" Sardi 🌊
PS. Wanna help me fine-tune the FlowOS client experience? I still have a few testing spots open. and I'll share the details.
Client Flow Letter
If this was useful, the next one will be too.
Retention strategy for coaches and founders — every week. No filler.
