← All case studies

Construction · Modular Homebuilding

Rebuilding the quote: configurator pricing in the CRM.

How Sector Growth moved Corey's Construction, a builder of modular and turnkey homes across several states, from a spreadsheet configurator toward a HubSpot product catalog, with a clear path to branded, signable proposals.

Industry
Residential Construction: Modular & Turnkey Homes
Client
Corey's Construction
HubSpot Products
Sales Hub (with a PandaDoc CPQ path)
Migrations
Customer records from the Wix website system
Scope
Onboarding, product catalog architecture & quoting fit-gap, June to July 2025
4
Pricing variables per home: state, zone, foundation, size
1
Product per home model per pricing zone
3
Stages: clean data, the catalog, an honest fit-gap
1
Catalog in HubSpot, whichever tool fronts the quote

01 · The challenge

A home priced like a configuration, sent as a spreadsheet link.

Each named home model is priced differently by state, by pricing zone within the state, by foundation type and by square footage, before a buyer adds any upgrades. The sales team had built a capable Google Sheets configurator to handle it, but it created three problems the business wanted to solve.

  • A poor buyer experience

    • The output sent to buyers was a link to a spreadsheet.
    • For a purchase like a home, the proposal is part of the sale.
  • Pricing outside the CRM

    • Deals, contacts and quotes were disconnected.
    • Leadership wanted pricing and proposals with the rest of the customer record.
  • Fragmented customer data

    • Customer records sat in the company's Wix website system.
    • They needed cleaning and migrating before anything could be built on them.

“I don't love what's getting sent to the client.”

Mike, Corey's Construction

02 · The solution

Build what HubSpot does well, and a clean path for the rest.

We ran a weekly onboarding cadence focused on the deal, the pricing and the presentation to the client, in three stages: a clean data foundation, a catalog that could represent configurable pricing, and an honest test of how far native quoting could go.

  1. 01

    A clean data foundation

    HubSpot tracking on the Wix site; customer records exported and cleaned to HubSpot's structure, with names split, emails consolidated and addresses standardized; unused fields removed, dropdown options documented and seats set up for the sales lead and the owners.

  2. 02

    A catalog built for configurable pricing

    One product per model per pricing zone, so the right base price is one selection away. SKUs encode state and zone (MD1, PA1, PA2) for instant filtering, unit descriptions read clearly on proposals, and unit cost sits apart from unit price so margin is visible internally only.

  3. 03

    Quotes configured for a home sale

    Proposal-style templates without irrelevant columns, multiple buyers on one quote, e-signature and countersignature, expiration dates, percentage-based payment schedules for deposits and staged payments, and a tax-rate library.

  4. 04

    An honest fit-gap

    We walked the configurator line by line against native quoting and told the client plainly that it could not reproduce the conditional pricing, the upgrade quantities calculated from each model, or a layout that separates the base model from its upgrades.

  5. 05

    A CPQ path through PandaDoc

    As a PandaDoc partner, we briefed PandaDoc's solutions team on state and zone pricing, upgrades and a branded document generated from the HubSpot deal, and arranged a discovery session and tailored demo, with products still loaded into HubSpot as the single source of truth.

03 · The outcome

HubSpot owns the customer, the deal and the catalog; a CPQ layer owns the proposal.

  • Pricing moved toward the CRM

    Home models and pricing zones began moving into a structured catalog in HubSpot instead of living only in a spreadsheet.

  • A clear decision instead of a forced fit

    Learning early which requirements native quoting could and could not meet avoided months of workarounds.

  • A future-proof foundation

    Because the catalog lives in HubSpot, a CPQ front end can generate proposals from the same products and deals without rebuilding pricing.

  • Clean customer data

    Customer records from the Wix website system were cleaned and structured for HubSpot before anything was built on them.

“I want it to be centralized in the CRM and I want it to come through like this with all this other nice pretty information… Whatever you guys think we should go, I'm good with it.”

Mike, Corey's Construction

04 · Stack

Products & integrations used.

Products & integrations used.
HubSpot Sales HubProduct library, quote templates, e-signature, payment schedules and tax rates.
Product catalogOne product per model per pricing zone, with an SKU convention, unit descriptions and internal margin.
PandaDoc CPQRecommended layer for conditional pricing and the buyer-facing proposal, briefed with PandaDoc's solutions team.
WixWebsite tracking installed; customer records exported, cleaned and migrated.
Google Sheets configuratorMapped line by line in the fit-gap review.

Pricing too complex for out-of-the-box quotes?

We test honestly what HubSpot can do, build that part well and design the connection for the rest.

Ask the team

Tell us what you are working on. Someone from the team replies by email.