The gap between template work and custom development is enormous. The price difference is often small. The reason this works is that most clients can’t tell the difference from the outside — and many agencies have learned to use that gap profitably.
This is not a guess. Template-to-custom misrepresentation is one of the most consistent complaints in post-project agency reviews, and the pattern is recognizable once you know what to look for.
What “Custom” Actually Means
Custom development means code written specifically for your project, from scratch. No pre-built theme. No page builder drag-and-drop. No premium template purchased from ThemeForest and renamed with your colors.
The output of real custom work is a codebase that only exists for you — written to your specifications, structured for your content, and not shared across the agency’s other clients.
Template work means an existing design framework was purchased or reused, then populated with your content and adjusted for your brand. This is faster, cheaper to produce, and often looks nearly identical to custom work in screenshots. The differences show up in the code, the performance, and the maintainability.
Neither is inherently wrong. The problem is billing template work at custom rates without disclosure.
The Browser Checks Anyone Can Run
You don’t need to know how to code to verify this. These checks take under ten minutes.
BuiltWith or WhatRuns (browser extensions): Install either extension, then visit the agency’s portfolio sites. The extension shows you the technology stack. If Elementor, Divi, WPBakery, or Beaver Builder shows up, the site was built with a page builder — not hand-coded. If a premium ThemeForest theme name appears, it’s a modified template.
Google PageSpeed Insights (pagespeed.web.dev): Enter a portfolio site URL and check the mobile score. Hand-coded custom sites from competent developers consistently score 80+. Page builder sites and template-based sites average 38–55. One or two outliers don’t mean much — look at five or six sites for the pattern.
View Source (right-click → View Page Source): Look at the first 30–50 lines of HTML. Custom-coded sites have clean, minimal markup. Template sites often show generator meta tags like <meta name="generator" content="Elementor"> or theme purchase IDs in the code comments. You don’t need to understand the code — you’re looking for names you recognize.
Google Fonts or ThemeForest signatures: Search the page source for “themeforest” or the theme name. Some agencies buy premium templates from ThemeForest at $40–$90 and resell the customized result as “custom development” at $6,000+. The template name often appears in the source code comments.
What to Ask the Agency Directly
These questions have clear answers. Evasion is itself useful information.
“Is this built with a page builder? Which one?” — A yes-or-no answer is appropriate. Deflection to “we use industry-standard tools” or “our proprietary framework” means yes.
“Is the theme custom-coded or based on a premium template?” — The right answer: “We write our themes from scratch.” Any variation that mentions purchased themes, starter themes, or “heavy customization of an existing theme” means it’s template-based.
“Can I see the GitHub repository or source files from a completed project?” — An agency doing real custom development has source files and version control. An agency assembling templates won’t be able to show you a meaningful repository because there isn’t one.
“What’s the PageSpeed score on your most recent completed project?” — Ask them to pull it up during the call or meeting. If they have to check, that’s fine. If the number is below 70 on mobile, follow up with: “Why?” Their answer will tell you a lot.
Alex ran a SaaS company and hired an agency for a $12,000 website. The proposal mentioned “custom design and development.” After launch, he asked a developer friend to review the code. The friend found a ThemeForest theme ($79), Elementor installed with the page builder plan, and a codebase that was almost entirely the theme’s original files. Alex paid $12,000 for what amounted to $300 in tools and a few hours of configuration. The agency had done this on dozens of projects.
How Agencies Disguise Template Work
The language shifts are subtle but consistent:
- “Custom design” means they designed the look, not the code. Custom design on a template is still a template site.
- “Built on WordPress” — accurate, but says nothing about custom vs. template.
- “Our proprietary framework” — sometimes legitimate; often a repackaged page builder or premium theme with an agency watermark.
- “Hand-crafted for your brand” — refers to brand application, not code architecture.
- “Modern, responsive design” — responsiveness is a feature of templates too. Completely uninformative.
None of these phrases confirm custom development. The only confirming language is specific: “We write all code from scratch. No templates. No page builders. You can see the source files.”
What the Performance Gap Means for Your Business
This isn’t just a technical complaint. The performance difference between template work and custom development has a direct business impact.
A custom-coded site that scores 90 on mobile PageSpeed loads in roughly 1.2–1.8 seconds on a median mobile connection. A page builder template site scoring 38 loads in 4–6+ seconds. Google’s research shows that as mobile load time goes from 1 second to 5 seconds, the probability of a bounce increases by 90%.
If your site is bouncing 90% more visitors than it could be, that’s a conversion problem, a ranking problem, and a revenue problem — disguised as a website.
The Referral Chain Problem
Some agencies build template sites and then refer clients to “SEO agencies” when rankings don’t improve. The SEO agency adds content and builds links, but never touches the technical foundation — which is the root cause. The client keeps paying, results stay poor, and neither agency is accountable for the full picture.
If your site isn’t ranking despite consistent content investment, run a technical audit before spending more on content. A slow, template-based site can undermine otherwise strong content strategy.
Our custom WordPress development is built hand-coded from scratch — no page builders, no templates, full PageSpeed 90+ floor. That’s what makes the content work matter.
If you’re not sure where your current site stands technically, Honest runs an independent audit on speed, SEO, and technical quality. Worth knowing before committing to more content spend on a weak foundation.
What to Do If You’ve Already Paid for Template Work at Custom Prices
First, confirm the situation with the checks above. If the technical evidence is clear — page builder signatures, template IDs in source code, PageSpeed scores below 60 — document it.
Then decide: is the site performing well enough for your needs? A template site with a score of 65 on mobile, maintained well, might be serving you adequately. If it’s under 50 and you’re investing in SEO or paid traffic, the math on a rebuild likely works.
If you want to have a direct conversation with the agency, lead with the evidence, not the accusation. “I found these things in the code and have some questions” gets further than “you lied about custom development” — even if the latter is what happened.
See our fixed-price packages if you want a clean starting point with documented architecture, published pricing, and no ambiguity about what “custom” means.
FAQ
Is there a way to find out if my current site was built with a template without telling my agency? Yes. Use BuiltWith or WhatRuns on your own site URL. Check your site’s source code for generator tags and theme IDs. Run Google PageSpeed Insights. None of these require your agency’s involvement or knowledge.
Can a template site be converted to a custom site without rebuilding? Not meaningfully. The performance overhead of a page builder is architectural — it’s baked into how the site is structured, not something that can be removed without rebuilding the theme. Content can be migrated, but the underlying architecture needs to be replaced.
Are all ThemeForest themes bad? No. Some are well-coded and perform acceptably. The problem isn’t the tool — it’s the misrepresentation. A premium theme installed and customized, delivered at template pricing with transparent disclosure, is a legitimate service. The same theme sold as “custom development” at custom prices is fraud.
What’s the PageSpeed score I should expect from genuinely custom work? 90+ on mobile as a consistent floor. Individual results vary based on images, third-party scripts, and hosting. But well-written hand-coded themes consistently reach 90+ without heroic optimization effort. If an agency promises “custom development” and their portfolio sites average 55, they’re not writing custom code.
How common is template work being sold as custom? Extremely common. A 2022 survey by WP Loop found that over 60% of agencies they surveyed used page builders on projects they described to clients as “custom WordPress development.” Disclosure rates were low. This isn’t a fringe practice — it’s a standard operating model at a large portion of the market.
If I suspect misrepresentation, do I have legal recourse? Potentially, depending on the contract language. If the contract explicitly states “custom development” and the work is demonstrably template-based, that could be a breach of contract claim. The first step is consulting a contracts attorney — one with experience in service agreements. The evidence from technical audits is usually sufficient to establish the factual basis.