I'll be straight with you: I'm not a back-end developer.

I have a front-end background. I understand design, I understand how things should look and feel, and I can hold my own in a conversation about code. But building the kind of infrastructure that a real product needs — databases, server logic, API integrations, automated pipelines — that was always where I'd hit a wall.

StickyFlow exists because I refused to let that wall stop me.

Why StickyFlow Had to Exist

I started StickyFlow because I saw something coming that most businesses weren't ready for: AI was going to change how every company operates, and the companies that didn't adapt were going to fall behind fast.

That's not a prediction anymore. It's happening right now. The speed at which AI and automation technology is moving has genuinely surprised even me — and I've been watching this space closely. Tools that felt cutting-edge six months ago are already being replaced by something better.

Most businesses don't have time to keep up with that. They're running operations, serving clients, managing teams. They need someone who's already in the weeds on this stuff — someone who can look at how they work and say, "Here's what AI can handle for you, and here's how we build it."

That's the gap StickyFlow fills. But to fill it credibly, I had to build it the same way I'd build it for a client: using the actual tools.

The Partnership That Made It Possible

One of the first things I did was partner with The Tink Tank. They're builders who think about AI the same way we do — not as a novelty, but as infrastructure. Together, we used Claude Code as the foundation for building StickyFlow's own platform.

That word — foundation — is important. Claude Code isn't a shortcut we used to skip the hard parts. It's how we thought through architecture, worked through problems, and executed at a speed that wouldn't have been possible otherwise. Two people with complementary skills, using AI as the connective tissue, building something that would have required a full engineering team a few years ago.

That experience changed how I think about what's possible for a small team.

What "Not Super Technical" Actually Means in 2026

People hear "I'm not a back-end developer" and assume there are hard limits on what I can build. That used to be true. It isn't anymore — not if you're willing to learn how to work with AI tools the right way.

Claude Code doesn't require you to know how to write a database schema from scratch. It requires you to know what you want the database to do. It doesn't require you to understand server-side rendering at a deep level. It requires you to describe the behavior you need clearly enough that Claude can implement it.

The skill that matters now isn't syntax. It's specificity. Can you describe a problem precisely enough for AI to solve it? Can you read what it builds and know whether it's right? Can you iterate quickly when something doesn't work?

That's what I do. And Claude Code meets me there.

What We've Been Able to Do for Clients

The proof isn't in how we built StickyFlow — it's in what we've been able to do since.

One of our first major partnerships was with a marketing company that was drowning in manual processes. Campaign tracking done by hand. Client reporting pieced together from three different platforms. Approvals happening over email chains that nobody could find later. The team was capable — they just had too much work that didn't require their intelligence.

We built them a set of AI workflows that changed that. Data pulling automatically. Reports generating on schedule. Approval flows running through a single system. They didn't hire more people — they freed up the people they had to do the work that actually required them.

That's what this is all about. Not replacing teams. Removing the friction that keeps good teams from doing their best work.

Why We Use the Tools We Sell

There's a simple reason we built StickyFlow with Claude Code and the same AI workflow stack we offer clients: we had to know it actually worked.

You can't sell conviction you don't have. When I tell a client that AI automation will change how their business operates, I'm not guessing. I'm talking from the inside of a company that runs on those systems right now. The newsletter you're reading, the client portal, the content workflows, the admin infrastructure — all of it was built with the same approach we bring to client work.

That's the thing about this technology that still catches me off guard sometimes: the speed. The gap between "I wonder if AI could handle this" and "AI is handling this" is getting shorter every month. What used to take a team and a quarter now takes a few sessions with the right tools and the right approach.

The businesses that figure that out — and do it now — are going to have a real advantage over the ones that wait.

That's why StickyFlow exists. And it's why we built it the way we did.

---