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 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
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
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 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
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 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
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.