Customer-Facing Calculator in HubSpot CMS | Freightzy Case Study | Digifianz

Every logistics business runs the same calculation a hundred times a week. What class is this shipment? What will it cost to move? Usually that calculation happens in someone's head, in a spreadsheet, or in an email thread that takes a day to close. The question worth asking is not whether you could put it on your website. It is whether your CMS can carry a real tool that customers use, or whether you need to build it somewhere else and bolt it on. Freightzy is our answer to that.

The problem: a slow quote is a lost quote

Freightzy delivers shipping solutions for clients throughout North America. Two of the questions their customers ask most often are the two that gate everything else: what freight class does this shipment fall into, and what will it cost to move.

Both are answerable. Neither is fast when a person has to answer them. Freight class depends on density, which depends on dimensions and weight, which means someone has to collect the numbers before the calculation can even start. A rate depends on carriers, lanes, and current conditions. When each of those answers takes a phone call and a wait, two things happen. The customer who was ready to book cools off, and the salesperson spends the day quoting instead of selling.

Freightzy already had tools for both jobs. The project was not to invent them. It was to redesign and rebuild them so they worked better, and, just as importantly, so they stopped being a dead end. A calculator that gives a visitor a number and leaves no trace on your side is a utility. The goal here was to make them a source of leads.

What we built

Two separate tools, each aimed at a different moment in the buyer's thinking.

1. The Freight Class Calculator

The visitor enters the shipment's dimensions and weight. The tool works out the density and estimates the freight class in seconds, with no registration and no account. This is the early-stage question, asked by someone working out what they are dealing with before they are ready to talk to anyone. Asking them to sign up at that moment would lose most of them, so we did not.

2. The Shipping Calculator

The second tool returns instant, real-time freight quotes from North America's most trusted carriers. This is the later question, asked by someone who knows what they are shipping and now wants to know what it costs. It is also the one with the harder engineering behind it, because a real-time quote means reaching live carrier data while the visitor waits.

Both are live on Freightzy's site: the Freight Class Calculator and the Shipping Calculator.

Why build it inside HubSpot CMS instead of a separate app

This is the part worth reading if you are weighing the same decision, so here is the honest version of it.

A calculator built as a standalone app is a perfectly reasonable thing to do. It is also four separate problems you now own: it has to be deployed and maintained somewhere; it has to be styled to match a site it does not live in; its analytics sit apart from your site analytics; and the one that actually costs real money: whatever the visitor typed into it lives in that app, not in your CRM.

Building inside the CMS removes those four problems by default. The calculator is a page on the site, so it inherits the domain, the navigation, and the design system. In Freightzy's case that last point mattered more than usual: the brand kit and the website designs already existed from the earlier brand manual and web development project, which is why the design phase here was the predictable part of the schedule.

But the real argument is the last one. We connected both calculators to Freightzy's sales process through three HubSpot mechanisms:

• Ticket creation: the query becomes a record. Someone asked about this shipment, on this date, with these numbers.
• Workflows: the record gets routed. What happens next is a decision the business made in advance, not one a salesperson has to remember.
• Internal email automation: a named person is told there is something to act on.

None of those three is exotic. That is the point. Because the tool was built where the CRM already is, connecting it to the sales process was configuration rather than integration work. A separate app can do all of this too, through an API, a sync, and a contract about what happens when the sync fails. Inside the CMS, there is no sync to fail.

What changed

The calculators improved on several fronts at once: design, optimization, automation, and running results smoothly without errors, with all of it integrated into HubSpot rather than sitting beside it. The structural change is the one to focus on, though. Before, a visitor could get a number. After, the business also got a record, a route, and a notification.

When this pattern fits, and when it does not

A custom calculator inside your CMS is not the right answer to every problem. It earns its cost when several of these are true:

• The calculation is specific to your industry, so a generic widget cannot do it.
• Your customers are already doing it somewhere else, or by asking you.
• The answer is a natural opening to a sales conversation rather than the end of one.
• You want the query recorded and routed, not just displayed.

It is the wrong call when the calculation is generic enough that an off-the-shelf embed would do, when the inputs depend on data you cannot reach in real time, or, most common of all, when nobody owns the follow-up. If no one acts on the ticket, you have built a toy with a maintenance bill. The mechanism only pays for itself if someone is waiting at the other end of it.

If you are costing this kind of work out, read HubSpot implementation cost for what drives the price of custom build work. For a different shape of the same idea, where a full program runs inside one portal rather than a single tool, read the DHL LATAM bootcamps case study. And if you want to work out what this would take on your own portal, that conversation starts with HubSpot implementation and onboarding.

Frequently asked questions

Can you build a freight calculator inside HubSpot?

Yes. For Freightzy we redesigned and built two: a freight class calculator that estimates class from the shipment's density in seconds without registration, and a shipping calculator that returns real-time quotes from North American carriers. Both run as pages inside HubSpot CMS. The part that creates commercial value is not the arithmetic. It is that each query is connected to the sales process through ticket creation, workflows, and internal email automation, so it is recorded and actionable inside the CRM.

Does a custom calculator work with HubSpot's CRM and forms?

That connection is what turns a calculator into a source of opportunities. Because the tool is built where the CRM already lives, wiring it up is configuration rather than integration: a ticket records the query, a workflow decides what happens to it, and internal email tells the right person to act. Without that connection, a calculator hands a number to the visitor and leaves no record on the business side.

Is HubSpot CMS a reasonable place to run a customer-facing tool?

For a tool of this kind, yes, and there are practical reasons to prefer it. The calculator lives on your domain, inside your navigation, and inherits your existing design system, so it does not have to be separately hosted, separately styled, or separately measured. The stronger reason is data: what the visitor enters lands in the CRM directly, with no synchronization between a standalone app and your customer records to build and maintain.

How long does a project like this take?

It depends on factors that can be named even when the schedule cannot be promised in advance. In this project the design phase moved quickly because the brand kit and the site designs already existed. Development was the variable part, and it went through many iterations as the team found better solutions to earlier roadblocks. The things that move the timeline most are how many variables enter the calculation, which live data sources it has to reach, and how quickly requirements can be settled in working sessions.