About Feral Flow Digital
I've been doing this since before “web design” was a job title.
I built my first website in straight HTML in 1996. I've been building, troubleshooting, optimizing, and figuring out how things work ever since.
Today that means websites, SEO, integrations, tracking, and the assorted technical problems that tend to land somewhere between marketing and development.
Feral Flow Digital is where all of that lives under one roof.
Twenty-plus years under the hood.
he first time I touched a line of HTML was when I built a website for a local riding stable as a school project. The files never made it off the floppy disk I saved them on, but it started something for me.
By the early 2000s, I was customizing Angelfire sites and LiveJournal layouts by hand. In 2012, during the days of Panda and Penguin, I got my first professional exposure to SEO at Vocus. A legal case management software company came next, where I spent enough time inside WordPress to eventually start building sites for my own clients.
In 2015, I joined Coalition Technologies as an SEO technician, moved into project management, and eventually led a project management team. I spent those years diagnosing search problems, managing complicated projects, and working with clients across a wide range of businesses.
I kept building websites after leaving Coalition and returned briefly in 2025, partly to get firsthand exposure to how AI Overviews and generative search were changing SEO.
That return also confirmed that agency life wasn't for me. Managing 15 to 20 clients at a time left very little room to get deeply involved in any one business. I wanted fewer clients, more direct involvement, and work where my range was actually useful.
This is why I built Feral Flow Digital the way I did.
No handoffs or mystery team members. Projects have boundaries. I stay close enough to the work to understand what I'm looking at and why it matters.
I fix the weird problems that crop up.
Most businesses I work with already have capable people handling different pieces of the operation.
Someone manages marketing. Someone updates the website. A handful of tools are passing data back and forth. Everything works until one of those connections doesn't.
A payment gateway fails. Tracking stops working. An integration quits passing data. A customer gets the wrong email. The marketing person thinks it's the website; the developer thinks it's the third-party tool.
That's usually where I come in.
When K9Irby's payment system started sending “payment failed” emails on orders that had actually gone through, the issue wasn't obvious from the outside. The technical problem had to be traced through the systems involved while the business was dealing with confused customers and unreliable order messaging.
That's the kind of work I do best.
Tell me what's happening and what you've already tried. I'll work through the system, figure out where the problem lives, and tell you what needs to happen next.
I diagnose before I prescribe.
Sometimes the answer is an easy fix. Sometimes it isn't.
Some problems are straightforward.
Others expose a setup that's been patched too many times, a platform that's been outgrown, or a process that was never configured correctly in the first place.
I'll tell you what I find.
If the right solution is within my scope, I'll handle it. If the problem needs a specialist, you'll know what needs attention before you go looking for one.
That keeps you from bouncing between vendors trying to figure out whose problem it is.
When you hire Feral Flow Digital, you work with me.
I'm the person on the call, the person looking through the site, and the person doing the work. If we're working together over time, I also know why something was set up the way it was six months ago because I was there.
Projects have defined scope. Ongoing support has defined boundaries. If something falls outside what I do, I'll say so rather than learning it on your dime.
It keeps the relationship simple and gives me enough room to understand the business I'm working on.