---
title: Do You Still Need a HubSpot Theme Developer in 2026?
description: AI now builds about 95% of a HubSpot website overnight. Here is what a developer still does, what the build costs now, and the trap to avoid.
---

[Skip to content](https://themespot.app/blog/do-you-still-need-a-hubspot-developer#main-content)

[![themespot](https://themespot.app/hubfs/themespot-1.svg)](https://themespot.app/)

- Product
  
    - [Build themes/theme-development](https://themespot.app/theme-development)
    - [Manage content/content-management](https://themespot.app/content-management)
    - [Roadmap/roadmap](https://themespot.app/roadmap)
- [Pricing](https://themespot.app/pricing)

[Connect your portal](https://themespot.app/join-the-waitlist)

[← All posts](https://themespot.app/blog)

[Development](https://themespot.app/blog/tag/development)

# Do you still need a developer to build a HubSpot website?

By [Reece Sim](https://themespot.app/blog/author/reece-sim)·October 13, 2026·7 min read

Short answer: not for the build. You still need one for the review.

On my last client site, AI did roughly 95% of the HubSpot build overnight. A senior person then spent one to two hours on the 5% that matters: spotting what is off, tuning the interactions, and setting up the parts of HubSpot that no tool can reach. The site went live fully editable, with reusable sections and Core Web Vitals scores above 90.

I have built HubSpot themes for six years, mostly the slow way. This is what changed, what it now costs, and the one mistake I would stop any client making.

## What a HubSpot website build used to involve

Take a small site. My latest client project took more than 30 hours of design and revisions before anyone wrote a line of code. That part has not changed, and it should not.

The build is where the hours went. To do it properly, a developer would spend around another 50 hours turning the design into a HubSpot theme:

- page templates for every layout in the design
- blog post, blog listing, tag and author pages
- search results, 404 and 500 pages
- a library of saved sections marketers can drop into any page
- every heading, image and button made editable in the page editor, with sensible defaults
- testing on desktop and phone, then fixing what broke

None of that is glamorous, and most of it is the same on every project. It is also why a HubSpot specialist with HubL experience charges $150 an hour and why their calendar is full.

## What changed: the overnight first draft

Now an AI agent does the build while I sleep.

It runs for hours. It writes the templates, the sections and the editable fields. Crucially, it checks its own work: it renders each page on a HubSpot-compatible engine, compares the result with the design, and fixes the differences before it moves on. It holds itself to a strict set of standards for accessibility, editability and HubSpot's own build rules, so problems are caught before HubSpot ever sees the theme.

By morning there is a first draft of the whole site. Not a mock-up, a working theme.

## What a human still does

This is the part the "AI replaces developers" headlines leave out. Implementation is solved. Judgement is not.

**The review (one to two hours).** A senior person goes through the draft against the design and points out every discrepancy: spacing that is technically right but feels wrong, a hover state that should be softer, a mobile menu that needs to behave differently. Interactions and motion get refined here. The agent makes the fixes; the human decides what good looks like.

**The parts of HubSpot an API cannot reach.** Some settings still need hands in the portal:

- the brand kit
- blog settings
- complex menus
- domains

That is the list. Upload the theme, set those up, and the site is live.

**Approval.** Nothing should reach a client's live site because an agent decided it was finished. A named person approves the deploy. That is the job a developer does now: reviewer and approver, not typist.

## HubSpot website development cost: before and after

Here is the same small project, priced two years ago and priced now.

|  | Two years ago | Now |
| --- | --- | --- |
| Design | $2k | $3-5k (higher quality) |
| Development | $10k+ | $200 |
| Content population and HubSpot setup | $2k | $300 |

Two things stand out. Development has collapsed from the biggest line to a rounding error. And design has gone up, because that is now where the quality of the site is decided. The money moved from typing HubL to getting the design right.

For an agency, that changes the margin on every project. For a marketing lead, it changes what you should expect to pay and how long you should expect to wait.

## The trap: the "AI native" site only one person can edit

Not every AI-built HubSpot site is a good one. A prospect recently asked me whether they should migrate to an "AI native" website. This was the description, word for word:

> "The rebuild is 100% AI-generated custom HTML (via Claude Design and Claude Code), deployed to HubSpot via the API by one developer, from their laptop. Only that one developer can currently edit the site."

That last sentence is the red flag.

The question to ask of any build like this is simple: is it built in HubSpot's native theme and module system, or is it custom code that happens to be hosted on HubSpot? If it is the second, you are about to lose the things you pay Content Hub for:

- **Drag and drop editing.** Marketers cannot add a section, swap an image or reorder a page without a developer.
- **Dynamic content.** HubDB tables, the blog and custom objects all expect a real theme.
- **HubSpot's own AI features.** Anything HubSpot ships for Content Hub works on native themes and modules, not on pasted HTML.
- **Anyone but one person.** The whole site depends on one laptop and one set of credentials.

At that point, why pay for the subscription at all?

This is the old agency problem in a new coat. Custom-code sites have always been easy to hold hostage, and a good developer's job has always been to make themselves unnecessary once the site is live. AI speed with a one-person bottleneck is not progress. It is the same lock-in, built faster.

You do not have to choose between AI speed and a site marketers can safely edit. You can have both, on HubSpot. Your marketers do not need to learn a coding tool. You do not need to give up drag and drop. And the site does not need to be a black box: the theme can be inspected, checked and exported like any other.

## Why build on HubSpot at all?

Because the boring parts are already solved. SEO settings, multiple languages, dynamic content, blogs, forms, workflows and memberships all come with the platform, and the site sits inside the CRM your sales team already uses. The editor gives marketers visual control inside guardrails, so they can change a page without breaking the brand.

That split between the theme (owned by developers, designers and now AI) and the content (owned by marketers) is exactly what makes AI building safe. The agent works on the theme, behind checks and approval. Marketers work on pages, in the editor they already know.

## What to ask your agency or developer now

If you are about to commission or renew a HubSpot build, these questions will tell you quickly whether you are paying for 2024 or 2026:

1. **How many hours are build, and how many are design and review?** If build is still the biggest line, ask why.
2. **Is it a native HubSpot theme with editable modules and saved sections?** Ask to see a page edited in the drag and drop editor.
3. **Who can edit the site after launch?** The answer should be "your marketing team", not a name.
4. **How is the build checked?** Ask for evidence: rendered pages compared with the design, on desktop and phone, and Core Web Vitals scores.
5. **Who approves what goes live?** There should be a named person, and it should not be the AI.
6. **Can I take the code with me?** If the answer is anything other than yes, walk away.

## How I do it now

I built ThemeSpot because I was doing this by hand on every client site. It turns a design into an editable HubSpot theme, renders and checks every page against the design, and deploys nothing until a named person approves. Marketers keep the page editor. The theme stays yours.

If you want to try the design-to-theme part on your own machine, there is a free Claude Code plugin, Theme Dev Tools for HubSpot, that does it locally. If you want the whole loop on your portal, connect it at [themespot.app](https://themespot.app).

So here is my question for agency owners and heads of delivery: if the build is now 5% of the hours, what are you going to do with the other 95%?

## FAQ

**Do you need a developer to build a HubSpot website in 2026?**  
Not for most of the build. AI can now produce a full, editable HubSpot theme overnight, including templates, blog pages and saved sections. You still need an experienced person to review the result against the design, refine interactions, configure the brand kit, blog, menus and domains, and approve what goes live.

**How much does a HubSpot website cost to build now?**  
On a recent small site, development dropped from over $10,000 to around $200, and content population and setup from $2,000 to around $300. Design went up to $3,000 to $5,000, because that is now where quality is decided. Your numbers will depend on the size of the site and the agency.

**Is an AI-built website on HubSpot as good as a hand-coded one?**  
It can be, if it is built as a native HubSpot theme with editable modules, checked against the design on desktop and phone, and reviewed by a senior person before launch. It is not, if it is custom HTML pushed to HubSpot that only one developer can edit.

**What can AI still not do on a HubSpot site?**  
It cannot set up things HubSpot does not expose to its API, such as the brand kit, blog settings, complex menus and domains. It also should not decide on its own what good looks like or push changes live without a person approving them.

---

*HubSpot is a trademark of HubSpot, Inc. ThemeSpot is not affiliated with or endorsed by HubSpot.*

Filed under

- [Development](https://themespot.app/blog/tag/development)

![](https://themespot.app/hs-fs/hubfs/fsdf%20(1).png?width=64&height=64&name=fsdf%20(1).png)

Written by

Reece Sim

[More from this author →](https://themespot.app/blog/author/reece-sim)

[← Back to all posts](https://themespot.app/blog)

[![themespot](https://themespot.app/hubfs/themespot-1.svg)](https://themespot.app/)

Runs alongside HubSpot. Never replaces it.

Your site is yours, forever. ThemeSpot is the bonus.

All systems normal

- Legal
  
    - [Privacy](https://themespot.app/privacy)
    - [Terms](https://themespot.app/terms)

© 2026 ThemeSpot

HubSpot is a trademark of HubSpot, Inc. ThemeSpot is not affiliated with or endorsed by HubSpot.

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Reece Sim",
    "url" : "https://themespot.app/blog/author/reece-sim"
  },
  "dateModified" : "2026-10-13T07:35:22.320Z",
  "datePublished" : "2026-10-13T07:35:22.000Z",
  "headline" : "Do You Still Need a HubSpot Theme Developer in 2026?",
  "mainEntityOfPage" : {
    "@id" : "https://themespot.app/blog/do-you-still-need-a-hubspot-developer",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://themespot.app/hubfs/themespot.svg"
    }
  }
}
```