HubSpot website rebuild and CRM setup

Goals

• A restaurant operator finds the right consulting service quickly, with a clear call to action for the next step.
• Your team can update pages without a developer, without worrying about breaking the layout.
• Search rankings carry over from the current site, with nothing lost in the move.
• A better sales funnel: clear calls to action for lead generation, with attribution, tracking, and reporting that show which pages and campaigns turn visitors into consultations.
• A foundation to grow on: new services, client case studies, and seasonal campaigns your team can add themselves, on a well-built custom theme any HubSpot developer can understand and extend.
• Faster publishing with AI: find where the client’s team can put new AI tools to work, in HubSpot and alongside it.

Where things stand

The current site is on an older HubSpot marketplace theme. The client’s team can edit text, but most layout changes need a developer, and three of the service pages have drifted out of date. Search traffic is steady, and most of it lands on the menu engineering and kitchen design pages. Consultation requests arrive by email, and there’s no record of where they came from.

A custom theme built for the client

As requested on the initial call, the client wants a custom theme. This gives the client:

• A design that fits the brand, with the client’s colors and typefaces applied as a system instead of overrides to a marketplace theme.
• Modules designed for the client’s content: services, case studies, and consultation requests.
• An editor built for the client’s team, with fields named in plain language and grouped the way the team thinks about each page.
• Everyday edits instead of developer requests for the layout changes that need a developer today.
• Guardrails: typical edits won’t break the layout, and HubSpot keeps a revision history on every page, so any change can be rolled back.

Approach

• Account review on day one. I check the things that can only be seen inside HubSpot first, and if anything changes the plan, I say so before going further.
• Build the theme first. Global styles, the header and footer, and the custom modules every page is made from, each with editor fields named in plain language. Pages are then built from those modules, so the site stays consistent as it grows.
• Launch in stages, like a soft opening. Core pages go live first, with the rest following in small batches, so real traffic surfaces problems while there’s still time to fix them.
• Redirects mapped before launch. Every current URL gets a home on the new site, so search rankings and old links carry over.
• A weekly status call. We review progress together, answer open questions, and keep the timeline on track.
• A page-building tool. It turns an approved build sheet into a draft page in HubSpot, and an AI assistant can run it, so new pages and copy changes arrive within hours. It creates drafts only; the client’s team reviews and publishes.
• Training as pages launch. We walk through editing each page together, and the client gets a short written guide.

Rough timeline

Some of this runs side by side, and pages move when their content is ready.

Weeks 1–2 · Setup

Account review, redirect map, and design review of a sample home page and service page

Weeks 3–6 · Build

Theme and modules, then the home, service, and contact pages, with the first pages live

Weeks 7–8 · Launch

Case studies and remaining content, redirects turned on, Search Console checked, and editing walkthroughs

Goals

• Every inquiry lands in HubSpot, with where it came from and the type of project (new opening, menu engineering, kitchen design, or operations review) recorded, and the right partner notified.
• A simple pipeline from first call to site visit, proposal, and signed engagement, so no lead gets eighty-sixed by accident.
• A clear view of what’s working: which pages and services bring in consultations.

Approach

• Planning session first. How inquiries come in, who follows up, and what the CRM needs to track, agreed before anything is built.
• Website forms connected. Lead source, service of interest, and number of locations recorded automatically, with a confirmation email so each person hears back right away.
• Pipeline set up with the partners. Stages agreed with the people who use them, then adjusted after the first few deals.
• A dashboard and team training. Inquiries by source and page, and a walkthrough of using the CRM day to day.
• Room to grow. Once the basics are running, we can look at tracking each client restaurant as its own record in the CRM.

What the estimate assumes

• Content for new pages is provided by the client’s team, or written together from the current site.
• A HubSpot subscription that supports the custom theme and the CRM work, confirmed during the account review.
• Two rounds of design review before the build starts.

Investment and timing

A fixed fee for each part, half to start and half on completion. Real proposals include the amount and a timeline with dates. Ongoing support afterward is optional, hourly or on a retainer, with a short note each month on what was finished and what’s next.

Next steps

• Reply to accept, and the first invoice goes out.
• A short kickoff call, where we set up the HubSpot access I need together.