Here is what makes this choice so slippery: a good share of the “agencies” you are comparing do not build anything. They are a sales front that subcontracts your project to a white-label team, adds a markup, and plays telephone between you and a developer you will never meet. The wrong pick is not just a bad site — it is paying agency rates for a middleman. This framework is about seeing through that, so you know exactly who will do the work and what you are paying for.
Choosing the wrong WordPress development company is expensive. You end up with a slow site built on a page builder, code you can’t maintain, and a support relationship that disappears after launch. Choosing the right one is transformative — a fast, secure, scalable site that you own and can grow.
This guide gives you a systematic evaluation framework: what to look for in a portfolio, the technical questions to ask, red flags to reject immediately, and how to structure your contract. If you specifically want a bespoke, scratch-built site, start with our custom WordPress web design guide.
Lorem ipsum dolor sit amet...
Before evaluating companies, clarify your actual requirements. Custom WordPress development exists on a spectrum:
- Custom theme from scratch: No page builder, hand-coded PHP/HTML/CSS, optimized for performance
- Custom Gutenberg blocks: Reusable block components built with register_block_type and block.json
- Custom functionality: Custom post types, taxonomies, REST API endpoints, third-party integrations
- Custom design + existing theme: Child theme of a premium theme with significant modifications
Most “custom WordPress development” offered at low prices is option 4 with Elementor or Divi, not options 1–3. Be explicit in your brief about what you need.
Step 1: Define What “Custom” Means for Your Project
Before evaluating companies, clarify your actual requirements. Custom WordPress development exists on a spectrum:
- Custom theme from scratch: No page builder, hand-coded PHP/HTML/CSS, optimized for performance
- Custom Gutenberg blocks: Reusable block components built with
register_block_typeandblock.json - Custom functionality: Custom post types, taxonomies, REST API endpoints, third-party integrations
- Custom design + existing theme: Child theme of a premium theme with significant modifications
Most “custom WordPress development” offered at low prices is option 4 with Elementor or Divi, not options 1–3. Be explicit in your brief about what you need.
Step 2: Portfolio Evaluation
What to Look For
- Sites that are clearly NOT built with Elementor/Divi/WPBakery visual appearance
- Performance scores — ask for real PageSpeed Insights URLs on portfolio sites
- Complexity signals: membership functionality, custom dashboards, multi-language, API integrations
- Code samples on GitHub, GitLab, or portfolio sections showing actual PHP/JS
- Testimonials from clients in your industry or with similar technical requirements
How to Test Portfolio Sites
Run any portfolio site through PageSpeed Insights. A genuinely custom theme should score 80+ on mobile. Run the site through a “What WordPress plugins?” checker — excessive plugin count suggests lazy architecture. View source and look for elementor or et- CSS class names that reveal page builder usage.
Step 3: Technical Vetting Questions
Ask these questions in your discovery call. Genuine WordPress developers will answer them directly:
- “Do you build custom themes without page builders?” — Yes/No. Any hesitation is a red flag.
- “How do you handle WordPress security?” — Should mention: login protection, update management, file integrity monitoring, role-based permissions.
- “Can you show me a custom Gutenberg block you’ve built?” — Should be able to show block.json and a render.php or JS component.
- “What’s your process for database migrations and staging?” — Should describe: staging environment, migration scripts, testing protocol, rollback plan.
- “How do you manage WordPress core and plugin updates?” — Should describe a managed update process, not “the client handles it.”
- “Do you use version control (Git)? Can we have access to the repo?” — Answer must be yes. If they don’t use Git, walk away.
Step 4: Red Flags to Reject
- They describe Elementor or Divi as “custom development”
- They can’t share a GitHub repo or code sample
- They don’t mention staging environments or testing
- They don’t ask about your technical requirements before quoting
- They promise unrealistic timelines (complex custom theme in 1 week)
- They don’t discuss WordPress version and plugin update management
- The quote is based on “per page” pricing rather than scope-based
- They’re unwilling to put deliverables and milestones in writing
Step 5: Pricing Benchmarks
Understanding market rates helps you identify under-priced (quality risk) and over-priced work:
- Simple custom theme (5–8 pages, static): $5,000–$10,000
- Business site with custom CPTs and ACF: $10,000–$20,000
- WooCommerce with custom functionality: $15,000–$40,000
- Membership site or LMS: $20,000–$60,000+
- Headless WordPress (REST API/WPGraphQL + Next.js): $30,000–$100,000+
Hourly rates: $75–$150/hr for US/UK agencies; $40–$80/hr for Eastern European agencies; $15–$40/hr for Asian agencies. Note that offshore projects often require more revision rounds, offsetting the cost savings.
Step 6: Contract Essentials
- Detailed scope of work with specific deliverables listed
- Milestone-based payment schedule (not 100% upfront)
- IP ownership clause — you own all code on delivery
- Access to hosting, domain, staging environment, and Git repository
- Post-launch support window (minimum 30 days)
- Change request process and rate for out-of-scope work
- Performance benchmarks (e.g., LCP < 2.5s, Lighthouse score ≥ 80)
- Timeline with specific milestone dates
Agency vs. Freelancer: Which to Choose
The right choice depends on project size and risk tolerance. For projects under $5,000, a specialist freelancer can be excellent value. For projects over $15,000, consider that:
- An agency has redundancy — if the lead developer is sick, the project continues
- Agencies have structured QA processes; freelancers often don’t
- Ongoing maintenance is more reliable with an agency retainer than a freelancer who takes on too much work
- Agencies carry professional liability insurance; freelancers often don’t
Who Will Actually Build Your Site (The White-Label Question)
This is the question that quietly decides your whole experience, and almost no one asks it. Many web “agencies” are sales-first resellers: they win the client, then hand the actual build to a white-label development team and mark it up. You talk to an account manager on every call; the person writing your code is two layers away and never speaks to you. That telephone game is where scope gets lost, timelines slip, and “small changes” take a week.
To be clear, an offshore or outside team is not the problem — plenty of excellent work is built that way. The problem is a sales layer you are paying a premium for without knowing it. So ask directly: is the development done in-house or subcontracted? Can I talk to the developer who will actually build this? If it is outsourced, what is the markup? A company that builds its own work will answer these in one sentence; a reseller will get vague.
The cleanest version of this is working straight with the senior team that writes the code — no account-manager layer between you and the build. That is the whole model behind our custom WordPress development: you brief the people who ship it.
Frequently Asked Questions
Custom WordPress development means hand-built code — a bespoke theme, custom Gutenberg blocks, custom post types, and tailored functionality — rather than assembling a site from a prebuilt theme and a page builder like Elementor or Divi. The difference shows up in performance, maintainability, and how closely the site matches your exact requirements. Much of the ‘custom development’ sold cheaply is actually a modified premium theme with a page builder, so be explicit in your brief about which you need.
Custom WordPress development projects typically range from $5,000–$15,000 for small business sites to $20,000–$80,000+ for complex web applications. Hourly rates range from $75–$150/hr for US/European agencies. Offshore rates are lower but quality varies significantly.
Key questions: Do you build custom themes or use page builders? How do you handle WordPress security? What’s your testing process before launch? Do you provide post-launch support? Can I see examples of custom PHP or Gutenberg block work you’ve built?
Look past screenshots — open their live sites. Check page speed (run Lighthouse or PageSpeed), view source for clean semantic markup versus page-builder bloat, and test on mobile. Confirm the work matches what you need: if you want a hand-coded theme, make sure their portfolio shows custom themes, not just Elementor builds. Ask which parts they actually built versus inherited, and request a reference from a project similar to yours.
Red flags include: excessive reliance on Elementor/page builders for ‘custom’ work, inability to show GitHub code samples, no documented testing process, vague pricing, no maintenance plan offered, or lack of experience with staging environments.
Agencies offer more stability, broader skill sets (design, dev, SEO), and don’t have single points of failure. Freelancers offer lower cost and more direct communication. For projects over $10,000 or requiring ongoing support, agencies are generally safer.
A straightforward custom theme typically runs 3–6 weeks; a larger site with custom post types, integrations, and custom Gutenberg blocks runs 2–4 months. Timeline depends mostly on the number of unique templates, custom functionality, and how ready your content and designs are. Be wary of quotes promising a complex custom build in days — that usually signals a page-builder template, not custom development.
At minimum: a clear scope and deliverables, who owns the code and intellectual property (you should), source-code and repository handover, a defined revision and acceptance process, payment milestones tied to deliverables, and post-launch support and warranty terms. Clarify hosting, maintenance, and what happens if the relationship ends — including access to the codebase. Vague scope and unclear IP ownership are the most common sources of disputes.
Review their portfolio and live sites, check references and reviews, ask about their process and tech stack, and give a small paid test task or detailed technical questions. Look for clean code practices, security awareness, performance focus, and clear communication – not just attractive designs.
Good companies offer post-launch support: updates to core, themes, and plugins, security monitoring, backups, bug fixes, and a clear channel for change requests. Clarify response times, what is included versus billed hourly, and whether they offer a maintenance plan before you commit.
Both can deliver excellent work – what matters more is proven skill, clear communication, and reliable process. Offshore teams often offer better value; local teams offer time-zone and in-person convenience. Judge on portfolio, references, and responsiveness rather than location alone, and confirm overlapping working hours.
You should. With a reputable company you own the site, the custom code, the content, and all accounts once paid, with no lock-in. Put ownership, handover of credentials, and source files in the contract up front so there are no surprises if you change providers later.
Ask directly, and watch how cleanly they answer. Say: is development done in-house or subcontracted to a white-label team? Can I speak with the developer who will actually build this? If it is outsourced, is there a markup? A company that builds its own work answers in a sentence; a sales-first reseller gets vague or routes you back to an account manager. Offshore or outside teams are not the problem – many do excellent work. The problem is paying agency rates for a middleman layer you did not know was there. The cleanest arrangement is briefing the senior team that writes the code directly.
