WordPress Backend Consulting

Stuck on a WordPress backend problem? I can probably help.

WordPress Backend Consulting

This is WordPress consulting for dev teams and agencies - not generic WP help. If you're dealing with a backend architecture decision, a performance bottleneck, or a plugin that doesn't scale, that's what I do.

Book an hourly session See retainer details

Toptal top 3% · Upwork Top Rated · Fiverr 4.9 · I take max 2 retainer clients at a time

15+
Years WordPress
50+
Plugins Built
Top 3%
Toptal Screened
22+
Upwork Jobs
Who This Is For

Recognize any of these?

Most WP performance problems aren't solved by a caching plugin. They're slow queries, autoloaded options, or a plugin firing 40 extra DB calls on every page load. If you're stuck on something like that, I can probably spot it in an hour.

Your WP plugin is getting slow under load

Worked fine at 100 users. Now it's dragging. You've looked at the code but can't isolate why. That's a MySQL and query architecture conversation.

You're not sure if your plugin architecture will scale

You're building something new and want a second opinion before you commit to a data structure or hook design. Easier to fix now than in 6 months.

You need a senior backend eye before you ship

Code review from someone who's maintained plugins with 100K+ active installs. I know what breaks at scale because I've seen it break at scale.

Recurring WP backend questions on your team

You don't need a full-time hire. You need someone you can ask "is this the right approach?" once a week. That's what the retainer is for.

Scope

What I advise on

These are the areas where I actually have something useful to say.

MySQL query optimization
Slow queries, missing indexes, N+1 problems, autoloaded options bloat. I read EXPLAIN output and know what to do with it.
Plugin architecture
Class structure, data storage decisions, how you expose settings, REST API design, plugin lifecycle. Built 50+ plugins - I've made most of the mistakes.
WP hook system design
Action and filter architecture, priority ordering, passing data between hooks cleanly. When to use hooks vs. direct calls.
Database schema decisions
Custom tables vs. post meta vs. options. Which to pick depends on volume, query patterns, and WP compatibility needs.
Security architecture
Access control design, nonce strategy, capability planning, REST API permissions. Not a checklist scan - actual design review.
wp-config + server config
PHP-FPM settings, WP_MEMORY_LIMIT, query logging, object cache config. The stuff between your code and the database.
Caching strategy
Object cache (Redis, Memcached), transient design, fragment caching, query result caching. Not "install WP Super Cache".
Migration planning
Plugin upgrades, data migrations, schema changes on live sites with thousands of users. I've done these. The failure modes are specific.
Process

How it works

Two engagement models. Pick the one that fits your situation. If you're not sure, start hourly.

Path A - Hourly Advisory
1
Book a session via cal.com

30-min or 60-min slot. Minimum 1 hour billed. Pick a time that works for you.

2
Prep your question

Share code, schema, or a written description 24h before. I'll read it so we don't spend the session on context.

3
Async Loom review or live call

Your choice. Some questions are easier to answer on video. Some need back-and-forth. I'll suggest which.

4
Written summary sent after

Key decisions, recommendations, and follow-up items in writing. You have a record of what we agreed on.

Path B - Monthly Retainer
1
Get in touch to discuss scope

Email or book a short call. I want to know what your team is building and how often questions come up.

2
Agree on the engagement

4 hours per month, async. We set up a shared channel (email or Slack) and you can send questions as they come up.

3
Ongoing async access

Loom video reviews, written Q&A, architecture feedback. Priority response within 24 hours. Rollover hours don't carry over.

4
Cancel anytime

Month-to-month. No contracts, no 3-month minimum. I take max 2 retainer clients at a time - check availability first.

Pricing

Two ways to work together

No packages, no upsells, no setup fees. Hourly if you have a specific question. Retainer if you have ongoing decisions to make.

Hourly Advisory
$150 /hour
Minimum 1 hour · Pay per session · Book via cal.com
  • Architecture questions and second opinions
  • Code reviews before shipping
  • Performance deep-dives
  • Live call or async Loom review
  • Written summary sent after every session
Book a session
Monthly Retainer
$500 /month
4 hours/month async · Priority 24h response · Cancel anytime
  • Everything in hourly, used across the month
  • Async Q&A via email or Slack
  • Loom video code and architecture reviews
  • Priority response within 24 hours
  • Max 2 clients - check availability first
  • Hours don't roll over month to month
Check availability

Not sure which fits? Start with one hourly session. You'll know after that.

Why This Matters

Product WordPress, not agency WordPress

I've seen what breaks WP plugins at 100K active installs - because I've maintained them. That's a different problem set than building client sites.

15+

Years WordPress Backend

Ex-CTO at CreativeMinds (2010-2024). Not a generalist. WordPress backend is the thing I've done longer than anything else.

50+

WordPress Plugins Built

Products with thousands of active installs. I've hit the scaling issues, the upgrade migration failures, the data corruption bugs. First-hand.

Top 3%

Toptal Screened

Toptal accepts top 3% from 100,000+ applicants. The screening process is specific about PHP and WordPress depth - it's not generic.

95%

Upwork Job Success Score

Top Rated, 22+ jobs completed, 1,000+ hours billed. You can verify all of this on their platform. Click through and check.

"I'm not going to tell you to install a caching plugin if your problem is slow queries. In my experience, most teams know something is wrong - they just need someone who's seen the same pattern before to confirm it and point at the fix."

- Marcin Dudek

FAQ

Common questions

What is the difference between hourly and retainer WordPress consulting?
Hourly is pay-as-you-go - you book when you have a question. Minimum 1 hour, $150. Retainer is 4 hours per month async for $500. If you have sporadic questions a few times a year, hourly makes more sense. If your team hits WP backend decisions every couple of weeks, retainer is cheaper and you get priority access.
Do you do frontend or WordPress site-building work?
No. Backend only - PHP, MySQL, plugin architecture, security, server config. I don't do Elementor, page design, theme work, or site-builds. If that's what you need, I'm not the right person and I'd rather say so upfront than waste your time.
What counts as one hour of WordPress consulting?
One hour covers the session itself (live call or async Loom) plus a written summary with recommendations. If you share materials 24 hours in advance, reading your code before the session is included - we don't spend the hour on context.
Can I share code repositories for the review?
Yes. Private GitHub repo or a zip via WeTransfer. For commercial codebases or anything sensitive, I can sign an NDA before you share anything. Code is never shared with anyone else, yeah that goes without saying but I'll say it anyway.
What if my question takes more than the booked time?
I'll flag it during the session. We can continue and I'll bill the extra time, or I'll send a written follow-up covering what we didn't get to. Either way, I won't just stop mid-answer at 60 minutes. Complex questions sometimes take longer - that's ok, we figure it out.

Book your first session

One hour, $150. Bring your architecture question, your slow query, or your code review. If I can't help, I'll say so at the start and you won't be charged.

Book via cal.com