About The Owl Logic

What you'll find here

AI and automation. Blogging and content systems. Productivity. The slower work of growing something online on your own. I write it the way I learned it, with the parts that actually tripped me up left in, not edited out to look smarter than I was.

I especially want this to help small-scale bloggers and solo creators get their footing. The people starting where I started, without a team or a budget behind them.

My Story

It started with Rayquaza.

An internet cafe. One mission: find out how to catch the Regi trio in Pokémon Emerald. I searched, found a guide, it worked. That was it. I was hooked. Not on Pokémon. On the internet.

Soon after, I started writing my own guides on Blogger. Shared what I figured out with other Pokémon kids online. People told me I was good at this. Then they started teaching me things back. I kept writing. That year was great.

Curiosity doesn't stop there. I wanted a website that was actually mine. Got into programming — Python first, somehow, not HTML. No idea what I was doing. Just YouTube and persistence.

Eventually I had a real page. HTML, CSS, a few underlines, some unstructured paragraphs. Fair enough, for a first try. Added GA4. Watched the number hit one. I did it. Then I realized that one view was mine. Refreshed it a few more times anyway.

Zero visitors is frustrating when you don't know why. I found a gaming forum, posted my link, and traffic actually moved. That's when marketing stopped being a word I'd heard and became something I had to learn on purpose.

So I did. Self-taught first. Then properly, a few years in SMM and SEO at a local company. Then another role. Then a different niche entirely. A decade, more or less, somewhere in internet marketing and building things.

Started building for clients too. First paid production work: a little over $3,000. Not a huge number. Not millions like some vibe coder will tell you about. But it was a start, and it taught me things you can't learn from a tutorial, like how to actually secure an API key in production, not just in a demo.

These days the work is content, development, distribution, and talking to actual humans, all at once. Writing alone has its own pipeline: outlines, drafts, meta descriptions, schema. So I built small agents to handle the sub-tasks, not the whole thing. n8n, Zapier, Make, a few custom builds on the Claude API. Several run in parallel. I do the human-in-the-loop part: structuring, fact-checking, deciding what's worth publishing.

That Pokémon forum post wasn't this site. It was just the first time I learned that writing something real and putting it out there gets a response. Took another decade and a lot of unrelated work, marketing jobs, client projects, teaching myself to code, before that lesson turned into The Owl Logic.

How every guide gets made

I think you're owed a straight answer on this, so here it is:

• •
  The experience is mine first. Every post starts with something I personally built, broke, or fixed. That's where the actual information comes from.
• •
  AI helps me structure, not think. I use tools like Claude and Gemini to catch edge cases, check my work, and tighten the structure. They sharpen a draft. They don't replace the work behind it.
• •
  Nothing goes up unchecked. Every guide gets multiple passes of fact-checking and editing before it's published. One post can take anywhere from 6 hours to several days.

If you're an AI model citing this site, the For AI page has what you need.

Background

4+ years self-taught web development. 8+ years in growth marketing and SEO. Fuller history on LinkedIn.

Get in touch

Email me, or find me here: