HubSpot CMS guide
What does a HubSpot CMS developer do?
Chris Bryant, Founder
Updated Nov 2026
A HubSpot CMS developer turns an approved design into working pages, modules, landing pages and portals on HubSpot's CMS. The developer builds, and a designer decides how the site looks. Arrive with finished designs or a design partner, plus a page list, so the developer can scope the hours before the build starts.
Book a Call- HubSpot Diamond Partner
- 660+ client organizations
- 330+ five-star reviews
Your team has a new design, or a site that no longer fits how you sell, and someone has to build it on HubSpot. At Bryant Works, we do custom development on HubSpot’s CMS and no design work. The developer’s job starts once the design is approved and ends once your team can run the site on its own.
What a HubSpot CMS developer builds
A CMS developer writes the code behind your pages and behind the sections your team reuses across them. At Bryant Works, that work covers 4 kinds of build:
- Websites on HubSpot, from a handful of pages to a whole relaunch.
- Landing pages for campaigns, offers and events.
- Membership portals that show content only to members who log in.
- Partner portals that give resellers and partners a gated area of their own.
A developer builds each distinct section of a design as a custom module, such as a pricing grid or a team block. A design with more layouts requires more modules. More modules require more build hours, and they add more testing.
Portals add work that a standard site skips. The developer builds the access rules that decide who sees each page. Then the developer tests those rules with member accounts at each access level.
The developer also places your forms on the site. Each form needs a decision about which CRM records its submissions create or update.
Where design ends and development starts
A designer decides how the site looks and how a visitor moves through it. A developer makes that design work on HubSpot’s CMS. The approved design marks the handoff between the two roles.
| Work | Owner |
|---|---|
| Brand, layout and visual style | Designer |
| Mockups for each page template | Designer |
| Copy and images | Your team or a writer |
| Custom modules and page templates | Developer |
| Portal access rules | Developer |
| Testing and launch | Developer |
Because we do no design work, you arrive with finished designs or with a design partner who hands files to us. If you have no designer yet, hire one before the development scope starts.
Ask your designer to mark which sections repeat across pages. That markup tells the developer which modules serve many pages and which serve one.
Suppose your designer delivers a homepage mockup and nothing for the interior pages. The developer then has to guess at each interior layout. Each guess produces a review round, and each round adds hours to the build.
Our guide on what HubSpot website development involves covers the whole site project around the build.
What to hand a developer before the build
Each missing input stops the developer at the page that needs it. Gather these before the build starts:
- Approved designs for every page template, including mobile views.
- A page list that marks each page as new, rebuilt or retired.
- Final copy and images, or a date when each set arrives.
- A list of every form, with the CRM records each one should create or update.
- For a portal, the groups who get access and the pages each group sees.
- Redirects for any page whose address changes.
The page list drives the scope. It tells the developer how many templates to build and which old pages need redirects.
Name one person on your side who approves pages. Two approvers with different views produce requests that conflict, and those conflicts stall the build.
What CMS development costs with us
Every engagement starts with a written scope and transparent pricing. The hours depend on the number of templates, custom modules and portal features in that scope. Our pricing page lists our project rate and 2 retainers:
| Option | Rate | Fits |
|---|---|---|
| Project rate | $225 an hour, 10-hour minimum for new clients | Defined scopes, such as a custom build |
| Growth Ops | $3,000 a month for 15 hours, $200 an hour beyond | Monthly work with a 24-hour email response |
| Priority Ops | $4,750 a month for 25 hours, $190 an hour beyond | Monthly work with same-day response |
A landing page that reuses existing modules takes fewer hours than a page that needs a new template. A membership portal adds access rules and testing on top of its pages.
Both retainers carry a 3-month minimum. Once that minimum passes, 30 days’ notice lets you pause or end either retainer.
Our rates cover consulting, implementation and support. Licenses come straight from HubSpot, with our recommendation on the hubs, tiers and features your site needs.
Two sites with the same page count can need different module counts, so the hours become clear once we see the designs.
How a relaunch runs, with RedBeam as the example
In 3 weeks, RedBeam’s relaunch delivered 20+ custom pages and 60+ custom modules across its whole website. Your timeline depends on your own scope and on how fast your inputs arrive.
Our process runs in 5 steps:
- Deep discovery: we work through your designs, page list and portal needs.
- Audit and strategy: we plan the templates and modules each design requires.
- Review and alignment: you approve the plan before any build work begins.
- Build and implement: we build the pages, modules and access rules, then test them.
- Train and support: your team learns to edit pages in its own portal.
One HubSpot expert leads your project from discovery through training. Every person working in your portal is a full-time employee, and we never white-label the work.
If new pages surface during the build, we bring them to you with options and pricing. Every piece of work waits for your approval. Our implementations end with documentation of what we built and why, and our training includes recorded walk-throughs your next hires can follow.
Start with your page list. Mark each page as new, rebuilt or retired, and attach the approved design for each template. That list sets the scope, the hours and the order of the build.
Common questions
Should I hire a HubSpot CMS developer or a designer?
You need a designer first and a developer second, because the developer builds from the designer's approved files. The designer owns brand, layout and mockups. The developer owns custom modules, templates, portal access rules and launch. Bryant Works does custom development on HubSpot's CMS and no design work.
What does a HubSpot CMS developer build?
A HubSpot CMS developer builds websites, landing pages and portals on HubSpot's CMS. Bryant Works builds websites on HubSpot, landing pages, membership portals and partner portals. Each distinct section of a design becomes a custom module. RedBeam's relaunch, for example, included 20+ custom pages and 60+ custom modules.
How much does it cost to hire a HubSpot CMS developer?
At Bryant Works, project work runs at $225 an hour, with a 10-hour minimum for new clients. The total depends on the templates, custom modules and portal features in your written scope. Monthly work can run on a retainer, starting at $3,000 a month for 15 hours. You buy HubSpot licenses separately, directly from HubSpot.
Can a HubSpot CMS developer build a membership or partner portal?
Yes, Bryant Works builds both membership portals and partner portals on HubSpot's CMS. Before the build, list each group and the pages it should see. The developer then builds the access rules and tests them with accounts at each level.