Guide
What 'custom coded' actually means
Most people looking for a website assume the result will be WordPress, Shopify, or Squarespace with a new coat of paint, because that's what most of the industry actually ships. Here's what changes when a site is fully custom coded instead, and why every plan we offer, not just the top tier, is built this way.
Every Plan
Fully custom coded, from Basic to Custom
No page builder, no theme marketplace, no plugin stack holding it together. Every plan starts from the same place: code written for your project, not a template reconfigured for it.
- Hand-written code, not a page-builder template or
- , language, and chosen per project on the Custom plan
- No dependency stack to patch, break, or pay licensing fees for
- Full ownership, portable to any host or developer
- Performance and built into the code, not layered on with plugins
What 'custom coded' actually means
A custom coded website is one where the code itself, the , the components, the logic, is written from scratch for that specific business rather than assembled from a pre-built or ecosystem. On a WordPress, Shopify, or Squarespace site, what changes between businesses is the configuration layer: colors, logos, copy, content blocks arranged inside templates someone else engineered for thousands of unrelated sites. On a custom coded site, the code itself is the deliverable, built to that business's pages, features, and performance needs, with nothing running underneath that wasn't put there on purpose. This matters because the platform layer, not the design layer, is what actually governs page speed, how much a search engine can and understand, and how far the site can scale before it hits a wall. Two sites can look identical and still be fundamentally different products depending on which of these two categories they fall into.
A custom coded website is software written specifically for one business: every page, every component, every interaction exists because that project needs it, not because it shipped as part of a or someone else built for a different site.
The alternative, most of the web, is a template: a pre-built design and feature set (a WordPress , a Shopify theme, a Squarespace template) that gets configured, not written. The logo changes, the colors change, the copy changes. The underlying code, the part that actually determines how fast it loads and what it can do, stays the platform's.
Neither approach is inherently wrong. The problem is that most buyers don't know which one they're getting, because 'we'll build you a website' sounds the same regardless of which is actually happening underneath.
The assumption almost everyone makes
Most people assume that getting a website built means picking a WordPress , a Shopify template, or a Squarespace layout and customizing it, because that mental model matches what the overwhelming majority of the web actually runs on. That assumption is accurate about the market and inaccurate about what's required to get a professional result. Page builders exist to let someone without coding skills launch a working site quickly, which is a genuinely useful capability for many use cases, but ease of setup and long-term suitability are different questions. For a business site that needs to load fast, rank well in search, convert visitors, and scale as the business grows, defaulting to a because that's how websites get built skips over a real decision. The platform question is one of the first calls a business makes when commissioning a site, whether or not anyone frames it that way at the outset.
WordPress alone runs a large share of the web, and Shopify and Squarespace cover most of what's left for small business and e-commerce sites. So when someone imagines 'getting a website built,' the mental model is usually: pick a , customize it, launch.
That assumption isn't wrong about the market. It's wrong about what's necessary. Page builders exist because they let one person without coding ability launch something fast, and that's a genuinely useful tool. They are not the only way to get a professional website, and for a business that depends on the site to perform, rank, convert, scale, they're often not the right one.
Most agencies build on the same platforms, just with better design
Hiring a professional web design agency does not automatically mean the underlying platform question disappears, because a large share of agencies work by customizing the same WordPress themes and Shopify stores that are directly available to anyone for around twenty dollars a month. What that kind of agency actually sells is design judgment and setup time layered on top of an existing platform, not a different foundation of code underneath it. That's a legitimate, often reasonable way to work, especially for a straightforward brochure site or store built on a tight budget and timeline. But it means hiring an agency to build a site and getting a custom coded site are two separate claims that don't imply each other, and a buyer who assumes professional design equals custom code can end up with the same performance ceiling, limits, and dependencies as a DIY build, just wrapped in a nicer-looking .
Here's the part that surprises people: hiring 'a professional' doesn't automatically mean the platform question goes away. A large share of web design agencies work by customizing WordPress themes or building Shopify stores, the same platforms available directly to anyone for $20/month. What's being sold is design and setup time, not different underlying technology.
That's a legitimate way to work, and it's often the right fit for a straightforward brochure site or store on a tight timeline. But it means 'I hired an agency' and 'I got a custom coded site' aren't the same claim, and the difference shows up exactly where our DIY vs. professional website guide breaks it down: performance, ceiling, ownership, and what happens when you outgrow the platform.
How to tell if an agency is actually coding, or reselling a platform
- Ask what the site is built with. A real answer is specific: a and language (for example, Next.js and TypeScript), not a vague 'our proprietary ' with no detail behind it.
- Ask what happens if you want to leave. If the answer involves losing your design, your content structure, or paying to 'export' anything, you're inside a platform, not owning code.
- Check whether the quote includes or costs. Line items for a theme license or a page-builder subscription are a platform-based build wearing an agency's pricing.
- Ask if a performance problem gets fixed at the code level, or if the fix is 'install a caching .' The second answer means the bottleneck is the platform, and no plugin fully removes it.
- Look at whether every client's site runs on the same admin dashboard, login screen, and block editor. If it looks identical behind the scenes across completely different businesses, it's the same platform underneath.
What we build with
Every site we build starts as hand-written code rather than a or stack: React and Next.js on the for most projects, with the specific , language, and , meaning , authentication, and third-party integrations, chosen per project instead of defaulting to one stack for every client. There is no WordPress install running underneath, no Shopify theme being configured, no page-builder plugin doing the real work behind a customized front end. This holds across every plan we offer, not only the highest tier: Basic, Premium, and Pro differ in the number of pages, features, and overall complexity delivered, not in whether the underlying code is custom. The Custom plan is where the language, framework, and database themselves become an open decision shaped entirely around what that specific project needs, rather than a starting point every other plan also builds from.
Every site we ship starts as hand-written code: React and Next.js for the on most builds, with the specific , language, and (, authentication, integrations) chosen per project rather than fixed in advance. There's no WordPress install, no Shopify , no page-builder stack underneath any of it.
That's true for every plan, not only Custom. Basic, Premium, and Pro scale the number of pages, features, and complexity, not the underlying approach. The Custom plan is where the language, , and themselves become a decision made around what the project specifically needs, not a default we start every project from.
Why this applies to every plan, not just the top tier
Every plan we offer, including the entry-level one, is built on custom code rather than a , because the downsides of a template, a lower ceiling, slower load times, and locked-in platform dependency, don't scale down just because the budget does. It would be cheaper and simpler for us to build the cheapest plan on WordPress or Shopify and save custom code for whoever pays the most, but a small business running on a page-builder site loses just as much search visibility and page speed as a larger one would in the same position. Search engines don't apply a lower performance standard to a smaller budget, so building the entry plan on a platform that caps both means selling a worse outcome to the clients who can least afford to lose search traffic or conversions. That's the reasoning behind keeping every tier on the same custom-coded foundation and varying only scope and feature count between them.
It would be simpler, and cheaper for us, to build the entry-level plan on a and reserve custom code for whoever pays the most. We don't, because the , performance, and ownership problems a template creates don't wait for a bigger budget: a small business on a tight page-builder site loses just as much search visibility as a large one.
See what each plan includes in the pricing section above.
The trade-off, briefly
Custom code is not the better choice in every situation, and treating it that way would be dishonest. It typically costs more upfront than subscribing to a page-builder platform, and it takes longer to launch because the site is being built from scratch rather than assembled from existing templates and plugins. For a short-lived campaign landing page, a single-page portfolio, or a project with a genuinely minimal budget and no long-term ambitions for the site, a like WordPress, Shopify, or Squarespace can be the more sensible call, and recommending custom code there would be over-engineering. The trade-off flips for a business site that's expected to rank in search, convert visitors reliably, and still be running on the same platform three years from now without hitting a performance or scalability wall, where the upfront cost and longer build time typically pay for themselves well before that point.
Custom code is not automatically better in every situation. It typically costs more upfront than a template subscription, and it takes longer to launch because it's being built rather than configured. For a short-lived campaign page, a single-page portfolio, or a genuinely minimal budget, a can be the right call.
For a business site expected to rank, convert, and still be the same platform in three years, the calculation usually points the other way. We've laid out that full comparison, cost, performance, , maintenance, ownership, in our DIY vs. professional website guide. It applies whether you're weighing custom code against building it yourself, or against hiring an agency that still builds on a platform.
If your current site isn't custom coded, does that mean you need to rebuild
No, not automatically, and a well-built WordPress or Shopify site that is currently ranking well and converting visitors doesn't need to be torn out purely to make it custom. The decision should turn on whether the platform is actively costing the business something measurable right now: slow scores that are suppressing rankings or conversions, an ceiling the site has visibly hit and can't get past through content or optimization alone, recurring costs and breakage that keep eating time and budget, or a growth plan, new features, new markets, more complex integrations, that the platform genuinely can't support no matter how it's configured. If none of those conditions currently apply, the existing platform is doing its job and rebuilding would be solving a problem that doesn't exist yet. Once one of them does apply, moving to custom code stops being a nice-to-have and starts directly paying for itself.
Not automatically. A well-built WordPress or Shopify site that's ranking and converting doesn't need to be torn out just to be 'custom.' The question worth asking is whether the platform is actively costing you: slow scores, an ceiling you've hit, recurring costs and breakage, or a growth plan the platform genuinely can't support.
If none of that applies yet, the platform is doing its job. If it does apply, that's usually the point where moving to custom code stops being a nice-to-have and starts paying for itself.
Related guides
Frequently asked questions
Is my current website custom coded?
The clearest sign is in the admin login and URL structure: a wp-admin login, a name in the page source, or a myshopify.com subdomain (even behind a connected custom ) all point to a platform build. If you're not sure, ask whoever built it what it's written in; a specific answer means it's custom, a vague one usually means it isn't.
Do you ever build on WordPress, Shopify, or Squarespace?
No. Every plan we offer, Basic through Custom, is fully custom coded. If a project genuinely needs a platform's specific ecosystem, a large app marketplace, for example, we'll say so directly rather than force a custom build that isn't the right fit.
Isn't custom code always more expensive than a template?
Upfront, usually yes: a custom build costs more than a $20/month subscription. Over time it's closer, since a custom build has no recurring theme, , or transaction fees. See the pricing section above for exact numbers across all four plans.
Will building custom take longer than picking a WordPress theme?
Yes, a template can go live the same day; a custom build is designed and coded for the specific project, which takes longer upfront. What you get in exchange is a site built for what the business actually needs instead of what the happens to support.
Can I still edit content myself after launch on a custom site?
Yes. Custom code doesn't mean no editing interface. We build in an editable content layer scoped to what actually needs to change, text, images, blog posts, without shipping the full weight of a page-builder's editor to every visitor.
What happens if I want to switch developers later?
You own the outright, so it's a technical handoff, not a rebuild. That's the opposite of a page-builder platform, where leaving usually means starting over inside a new system.
Does custom coding actually help SEO, or is that just a sales pitch?
It's mechanical, not persuasive: custom code gives full control over , logic, and , the layer a 's panel doesn't expose. See our SEO guide and guide for the specifics.
Is the Basic plan also custom coded, or is that just the Custom plan?
Every plan is custom coded. Basic, Premium, and Pro scale pages, features, and scope; the Custom plan is where the language, , and themselves get chosen around the project instead of defaulting to our standard stack.
What if my project actually needs Shopify's app ecosystem?
Then Shopify may genuinely be the right call, and we'll tell you that rather than force a custom build where the platform's ecosystem is the actual point. It's a narrow case, mostly e-commerce businesses that depend on a specific marketplace app, but it's a real one.