Video summary
Upwork & WordPress Success: Expert Tips from Brian Gardner (WP Engine)
Main summary
Key takeaways
What’s changing in WordPress (and why freelancers should care)
Brian Gardner argues that WordPress adoption is still booming, but the market’s ability to build on modern WordPress is lagging.
- WordPress has moved ahead, especially since Gutenberg / WordPress 5.0.
- Many designers and developers still rely on “classic” workflows, creating a timing gap (estimated ~6–24 months) between what the platform can do and what freelancer workflows are ready to support.
- Because WordPress must remain backward compatible, changes often arrive “mid-flight,” making it harder for freelancers to trust, standardize, and confidently adopt new workflows.
- At the same time, the lag creates opportunity for freelancers who adapt early.
Bottom line: there’s risk in the ecosystem being in motion—but advantage for those who align their workflow with where WordPress is going.
Key business opportunity for freelancers: become a “Builder”
Brian’s repeated positioning is that the market is bifurcating:
- Legacy “developers/implementers”
- Primarily configure or implement existing themes using tools
- Historically may write PHP/JS when needed
- Modern builders
- Design + implement using block-based WordPress workflows
He recommends that freelancers brand themselves as WordPress Builders—a one-stop shop—because clients increasingly want fewer handoffs (design → dev).
Framework / playbook ideas embedded in the advice (action-oriented)
Adopt a block-first workflow
- Learn what a block theme is and how it’s composed.
- Build using patterns and the site editor, rather than relying on heavy “old style” theme customization.
Template acceleration via reusable assets
- Maintain a library of block patterns so you can assemble sites quickly.
- Target outcome: reduce delivery time dramatically (see KPI targets below).
Productize your service
Choose what you sell:
- Education / products (for recurring revenue)
- Implementation services (specialized niches)
- A focused plugin or micro-product
Tool-agnostic positioning to avoid “digital sharecropping”
If your expertise is tied to third-party tools (e.g., Elementor, Gravity Forms), position your identity around something more stable, such as:
-
“Marketing specialist + WordPress integration” rather than
-
“Elementor expert” alone.
Concrete examples & actionable recommendations
Block theme + site editor editing
Common tasks can often be done without writing code:
- Adjust colors, fonts, spacing
- Add templates
- Build pages using blocks and templates via the editor
Genesis / StudioPress lesson (strategic caution)
Brian notes he was uncertain about Genesis’s future value, which contributed to StudioPress being sold.
Lesson: platform shifts can “cannibalize” ecosystem products—so freelancers should avoid over-dependence on a single underlying system.
AI-assisted code snippets for plugins
- He claims to have built multiple plugins using ChatGPT-style prompting and testing.
- Recommendation: treat AI as a productivity tool, but validate and QA what it generates.
Specialization areas still worth it (advanced backend)
High-end freelancing remains valuable where expertise is hard to outsource:
- Security
- Performance engineering
- Database architecture / deeper WordPress engineering
These typically suit longer contracts more than small gigs.
Key metrics / targets mentioned (time & opportunity sizing)
- Market volume signal (Upwork)
- 7% of jobs posted on Upwork are directly related to WordPress.
- Time-to-deliver claim
- With patterns and block-based mastery, he asserts you can build a $5,000 website in ~3 hours (presented as “not stretching the truth”).
- Ecosystem adoption lag
- Estimated 6 months to 2 years lag between WordPress capabilities and developer workflow adoption.
What to sell: where the “money” opportunity is likely to be
-
Service → productization / recurring revenue
- Brian suggests the biggest money opportunities come from:
- Education
- Products
- Brian suggests the biggest money opportunities come from:
-
A niche within WordPress
- Build micro-products or plugins for specific use cases (examples referenced conceptually, including ecosystems like Gravity Forms).
- Goal: recurring revenue and a sustainability model (conceptually aligned with “4-hour work week” outcomes).
-
Integrations as a specialization (with the right positioning)
- Integrate marketing tools into WordPress, but avoid letting your brand become hostage to a single tool.
- Example positioning:
- “WordPress + marketing integration specialist”
- Preferred tool stack examples mentioned: HubSpot, ConvertKit, Mailchimp.
Risks / constraints called out
-
Digital sharecropping risk
- If your career depends entirely on a third-party theme/plugin ecosystem, you risk collapse if the ecosystem changes, is acquired, or sunsets.
-
Headless is not for everyone
- Headless WordPress is described as valuable but often too expensive / not worth it for small brochure sites.
- Best fit: major sites with specific needs.
Headless WordPress (high-level business execution guidance)
- Headless isn’t positioned as a universal opportunity for most freelancers.
- Recommendation for general freelancers:
- Don’t chase headless first.
- Master modern block-based WordPress, since it supports faster, cheaper outcomes for typical marketing sites.
- Opportunity exists for specialists or adjacent teams that can handle headless tradeoffs (performance, architectural complexity), though Brian says he personally lives mostly in the classic marketing site use cases.
Presenters / sources
- Brian Gardner
- Principal WordPress Advocate (WP Engine)
- Co-creator of the Genesis framework
- Founder of StudioPress
- Sean
- Host of the show