You're a Builder.
This Is Built for You.
No paywalls. No polished theory from someone who forgot what it felt like to start. Just a self-taught, AI-native founder shipping real tools and documenting the whole messy journey — every twist, wrong turn, and breakthrough — in real time.
Full access to the tools and community built for AI-native builders who are figuring it out as they go.
I'm Not the Developer You'd Expect
— A non-linear path
My path here wasn't linear — and honestly, that's probably why it's useful to you.
Before I wrote a single line of code, I spent years working across marketing, product management, design, and project management and did a fair share of side quests. Each of those roles felt like a detour at the time. They weren't. They were layers compounding quietly in the background.
I'm not a developer with decades of experience. My route here was chaotic. But that cross-functional foundation — knowing how products get built and marketed and shipped — is what I hope makes this content different.
The code slice matters, but so does the full picture. That T-shaped perspective is what I bring to everything I share — and what I believe makes it worth your time.
The Moment I Stopped Learning and Started Building
— The pivot that worked
This wasn't my first attempt. I'd tried to learn coding before — multiple times. Each run followed the same arc: motivation, tutorials, syntax drills, follow-along projects that evaporated the moment I closed the tab. Then life got in the way, and I'd quietly shelve it.
The gap between the lesson and the shipped product always felt enormous, and every day in that loop made it feel wider.
The attempt that finally stuck started about 1.5 years ago. And what made it different wasn't willpower or a better curriculum — it was timing. AI tools had arrived, and it changed everything about what was actually possible for someone learning to build.
That's when I made the real decision:
Stop chasing syntax mastery. Start learning architecture, system design, and AI-assisted workflows.
Stop trying to memorize the language — start learning how to design the system and let the tools handle the rest.
That pivot wasn't a shortcut. It was a strategy. And it worked. Since making it, I've shipped multiple tools and built a complex SaaS product from scratch. I'm only now starting to document the journey — and honestly, I wish I'd started sooner.
What You Actually Get Here
— A work log, not a curriculum
This isn't a curriculum. It's a work log from an active build. What I share tends to fall into a few natural areas — not because I planned it that way, but because they're what I'm living inside right now.
Development & AI Workflows
Architecture decisions I actually made, patterns that held up under pressure, tools I reach for daily.
Marketing & Distribution
Experiments I designed, ran, and reported on honestly, including the ones that flopped.
Takeaways & Resources
When I pick up a book or sit with an idea long enough to actually absorb it, I share those takeaways — not summaries, but what stuck and why.
What I'm Currently Building
What shipped this week, what broke, what I'm figuring out as I go.
The common thread is that none of it comes from above the process. It comes from inside it. That's what makes it worth paying attention to.
The Tools I'm Shipping
— And why they exist
Building is getting easier. Distribution is still brutally hard.
That's the problem Campaign Weaver was built to solve — a tool that helps solo founders and small teams plan, structure, and execute marketing campaigns without needing a full marketing team behind them. It came from a problem I hit personally while building products. So I built the solution.
Campaign Weaver is the anchor, but it's not the only thing in the works. I've also shipped tools for financial planning and runway management — each one born from a real founder problem, built from scratch, and shared with the community.
You're not a consumer here. You're a collaborator. Early access, alpha testing, feature requests — your feedback shapes what gets built next. If you're a founder hitting the same walls I was, I want to hear about it.
Come Be Part of the Build
Here's what joining actually looks like:
Real build updates before they're polished
Frameworks extracted from live experiments
Early access to tools as they ship
Direct line to shape the roadmap
This isn't a newsletter you'll archive. It's a front-row seat to a build in progress — and an open invitation to bring your own problems, ideas, and experiments into the conversation.
The next chapter isn't written yet — and you're not too late to be part of it.
Come join us.