Sometimes the best people we meet in WordPress show up in the most ordinary way, a random post, a quick reaction, and a moment of second-guessing. In this episode of our podcasts, we sat down with Ryan Logan, the WordPress influencer and founder of InfluenceWP whose digital marketing insights stand out, to talk about trust, maintenance work that nobody brags about, and why WordPress still rewards people who do the unglamorous parts well.

If you run an agency (or you’re trying to start one), this conversation hits close to home: plugin chaos, client admin access, vendor partnerships, and what it looks like to build a real social media presence without turning your audience into affiliate bait.

How we almost blocked Ryan before we ever met him

We spend a lot of time working behind the scenes in the WordPress community and eLearning space, so we’ve learned to be cautious. That’s what made this story funny in hindsight.

We saw a post from InfluenceWP on a LifterLMS-related property and our first instinct was, “Who is this spammer?” Fingers were already hovering over the delete button.

Then that little instinct kicked in, the hair on the back of the neck moment, and we paused long enough to ask a simple question internally before taking action. A quick Slack message to Chris Lema confirmed it: there was a real partnership conversation happening, and that post belonged.

A few quick details that set the scene:

• We do a lot of “shadowy” background work supporting platforms and communities.
• The near-block happened fast, because that’s what moderation requires.
• That one pause turned into a podcast guest we’re genuinely glad we got to know.

It’s also a reminder: in a space as crowded as WordPress, reputation and context matter. Even WordPress developers can view a legit project as suspicious if they only see a single post out of the full story.

Ryan Logan’s path from IT to a WordPress agency built on maintenance

As an entrepreneur, Ryan’s background starts far away from themes and plugins. He began working in IT in 1997, climbed the ranks for years, and eventually reached interim CIO at a high-frequency trading firm. The way he described it sounded intense, high stress, long hours, and the kind of environment where you can’t hide behind vague updates or poor communication.

Around 2019, he stepped out of that world. Before that full exit, he ran an IT agency providing consulting services, and clients kept asking for websites. For years the answer was “no,” until WordPress became the practical choice that finally turned the request into a service.

He transitioned into web design and web development services around 2014 and launched his WordPress agency officially in 2016. From there, he added side businesses, including InfluenceWP and newer projects we’ll get into later.

When we asked him to pick a specialty, he didn’t default to design or development. He chose the work most clients forget to value until something breaks: website care and maintenance.

That choice makes sense when you connect it to his IT roots. In a high-stakes environment, support and clear communication aren’t “nice to have,” they keep businesses running. He also admitted he’s creative and loves visuals, to the point that he could imagine retiring as a painter. Still, his core agency strength is keeping client sites stable, secure, and supported over time.

InfluenceWP and the push for honest deals and unbiased reviews

InfluenceWP came from a problem many of us have seen: fake deal sites that promise discounts, send you through a link, and quietly swap in their affiliate tracking. You buy thinking you got a deal, but the price never changed. Meanwhile, someone gets paid for “referring” you without adding value.

Ryan built InfluenceWP around two practical pillars.

First, he wanted a one-stop place for deals that people can trust in the WordPress ecosystem. Most of the offers are WordPress-related (he described it as about 99 percent), and the goal is consistency: partners get treated evenly, and users don’t get pushed toward whoever pays the biggest commission.

Second, he produces content that comes from a real user’s point of view. That includes giveaways (free to enter), plus videos where he opens a product as if it’s his first time seeing it. His content creation focuses on honest feedback that benefits plugin development, and since it isn’t structured around affiliate payouts, the review process can stay honest. That helps users understand what they’re walking into, and it also gives vendors feedback they can act on.

He mentioned finding issues like confusing wording, missing changelogs, incomplete about pages, and even bugs. Those aren’t flashy critiques, but they affect trust, refunds, and support load.

We also talked about his weekly newsletter, a key part of his email marketing strategy, which is still relatively new. At the time of the conversation, he had published 23 weekly editions. The point is simple: stay top of mind, because nobody can keep up with thousands of plugins and SaaS tools.

A detail we appreciated: he also shares non-partner launches on social media. If someone ships a free plugin to the WordPress repository or releases a new project, he’ll help spread the word without needing a payout to justify it.

This approach builds trust similar to industry benchmarks like WPBeginner and Syed Balkhi, while highlighting Ryan’s unique angle on honest deals and unbiased reviews.

If you want to see what he’s building, visit the InfluenceWP deals and reviews hub.

Vetting products, client admin access, and why agencies end up with the mess

The moment you publicly recommend tools, you inherit a new problem: quality control. Ryan described a vetting process that starts with research. He checks what a company is doing, how their site performs (including hosting services and SEO), and whether the basics are handled. If a website takes 20 seconds to load, he’ll push back before he ever considers a partnership.

Sometimes the warning signs are less measurable. We both recognized that “spidey sense” moment when something just feels off. Ryan’s response is polite pressure, questions, and occasionally a firm “no.” He’s turned down plenty of would-be partners, and he also described scrapping videos when a product looks so bad that publishing the review wouldn’t help anyone.

Quality beats quantity when your name is attached to the recommendation.

From the agency side, we connected this to a familiar pain: foundational tools that start fine, then slowly become unstable. A page builder update breaks layouts. A marketing plugin update crashes sites. When you support dozens of sites, one mistake from WordPress developers can become your entire day.

Ryan sits in an interesting middle spot. He can’t fix the tools he lists, but he can pass feedback to partners. Sometimes that ends partnerships. Other times, it means pushing back on complaints that are more about user behavior than actual product failure.

That user behavior piece showed up in our own story about automation. A client asks for a system that enrolls users, triggers notifications, and issues certificates. Six months later, certificates “stop working,” only to discover the team bypassed the process and started doing manual entry. The automation didn’t break, the workflow did.

This is where platform knowledge matters. In the LifterLMS ecosystem, for example, the core plugin is powerful on its own, and then add-ons and integrations expand payments with WooCommerce, memberships, notifications, and eLearning workflows. Depending on the build, teams might accept one-time or recurring payments through gateways such as Stripe, PayPal, or Authorize.Net, and they may connect marketing automation tools for lead generation through supported integrations (in some cases via connectors like WP Fusion). When someone changes the process, the tech stack can’t cover for that gap.

To make this concrete, here’s a simple way we see “broken features” show up during support.

Symptom clients report	What’s often really happening	What we check first
Certificates not sending	Team bypassed the intended workflow	Who changed the process, and when
Site suddenly looks “off”	Plugin update or new plugin conflict	Activity logs, recent installs, recent updates
Forms “stopped working”	Overlapping plugins or removed dependency	Existing forms tool, plugin list changes

The admin access debate also matters here. Some builders argue clients should never have admin access. In real agency life, we’ve seen both sides. Ryan described giving admin access to long-time, trusted clients, paired with activity logs and strong communication. He also runs a directory-focused business where clients must have admin access to approve and manage listings, so full lockdown simply doesn’t work there.

The biggest threat he called out wasn’t malicious clients. It was new team members who “know web” and start installing overlapping plugins, removing tools they don’t understand, or making stack decisions without looping in the person paid to maintain the site.

We’ve lived that too. We built a feature-rich WordPress LMS site with advanced web design and web development for memberships and e-commerce, then a newly hired marketer moved everything to Squarespace because it was easier for her. The client paid more for fewer features, and we all learned the same lesson: internal politics beats technical logic more often than we’d like.

Passion projects, open-source confusion, and the life Ryan wants next

Ryan was clear about something many people won’t say out loud. If InfluenceWP disappeared tomorrow, he’d have more time and would likely make more money. His agency pays the bills. InfluenceWP and his other projects exist because he enjoys helping the WordPress community that helped him build a good life.

He also mentioned a newer project, ChangelogWP, plus another product in development that will be paid from day one. That one is intentionally financial, not a “give it away and hope” experiment.

We also talked about the way open source confuses people outside tech. When we speak to business groups about WordPress, someone always asks, “Where does the money come from?” They expect one clear owner, one clear revenue stream, and one company calling the shots. WordPress doesn’t work like that as an open source CMS steered by Matt Mullenweg and Automattic, and neither do many businesses around it. Agencies, product shops, and educators build revenue while still contributing time, code, or support back into the community.

The conversation ended on the most human part of all this. Ryan described himself as a simple guy who likes being outdoors, sitting outside with his dogs, and enjoying craft beer and bourbon. He even talked about someday shutting it all down to buy or start a landscaping company, partly because tech keeps changing (including the impact of AI), and partly because he wants more time outside away from social media.

We also found shared ground in the fun stuff: smokers, mountain biking, WordCamp, and the fact that real relationships in this space often happen with WordPress developers because someone says, “Come visit, we’ll ride trails.”

Closing thoughts

This episode reminded us that trust is built through repetition: consistent reviews, honest feedback, and the day-to-day work of website management that keeps client sites alive. If we want better outcomes in digital marketing, SEO, WooCommerce, email marketing, automation, e-commerce, and eLearning, we can’t treat support as optional.

To follow Ryan’s work, much like fellow leader Joost de Valk in theme development, check out the Pine Digital agency site, browse the InfluenceWP WordPress deals and reviews, and explore what he’s building at ChangelogWP. Active in WordCamp events, social media, and the WordPress community, Ryan is a rising WordPress influencer. If you’re running an agency, we’d love to know what you’ve learned the hard way about plugins, process, and protecting your clients from their own best intentions.