You Move Me’s National Sales Center runs out of Kansas City, Missouri. It’s the sales engine for a 30+ location franchise network spread across the United States and Canada. Agents in Kansas City handle inbound calls, quotes, and booking for franchises in both countries. The software that runs the NSC — MoveRight — has to handle ZIP codes and postal codes, USD and CAD, US and Canadian document templates, and franchise-specific pricing rules for both sides of the border.

We’re relocating the Kansas City NSC to a new location. The process of moving a 42-workstation sales center across town taught us things about moving software that we couldn’t have learned any other way — because the software isn’t an abstract tool. It’s the thing the agents use every minute of every day, and when you move it, you find out real fast what it’s built for and what it isn’t.

The Setup: 42 Workstations, Two Countries, One Sales Center

The NSC has 42 workstations. Each workstation is a desk, a phone, and a browser. The agents log into MoveRight, see their zone (the NSC zone), and work leads, quotes, and bookings for franchises across the network.

A typical NSC agent handles calls from three or four franchises in a shift. A call comes in from a customer in Vancouver. The agent looks up the customer’s postal code, routes the lead to the Vancouver franchise zone, builds a quote using the Vancouver calculator, and books the move. The next call is from a customer in Charlotte. The agent switches to the Charlotte franchise zone, looks up the ZIP code, builds a quote using the NSC calculator (which handles North and South Carolina elevator logic), and books the move. The next call is from Calgary. Different zone, different calculator, different document templates, different tax rules.

All of this happens in one app. The agent doesn’t log out and log back in. They switch zones. The zone determines what calculator, what document templates, what pricing rules, what tax jurisdiction, and what currency apply.

This is what “purpose-built for moving” means. Not a generic CRM with a moving template. A system where the zone — the franchise territory — is the organizing principle, and everything downstream (calculator, documents, pricing, tax, currency) follows from it.

The Network Buildout: Managed IT Cross-Border

The NSC relocation involves a network buildout: firewall, switches, access points, ISP circuit coordination, and cutover planning. We evaluated managed IT providers and selected Epic Networks (a Bell MTS company) at $100 CAD per device per month for 42 devices — $4,200/month, $50,400/year. No onboarding fee. 12-month minimum term.

The cross-border reality: Epic is a Canadian company. The NSC is in the United States. ~95% of support is handled remotely from Winnipeg. The remaining 5% — onsite hardware deployment, network cutover, physical installation — is handled by a US-based field-services partner at $175 USD/hour. The network infrastructure project (firewall, switches, access points, staging, configuration, cutover) is estimated at $15,000-$40,000 for hardware plus $10,000 in professional services.

This is the reality of running a cross-border operation. You don’t just need software that works in both countries. You need IT, telecom, and support infrastructure that spans both countries. The software is one piece. The network is another. The people are a third.

What the Software Needs to Do When You Operate Across Borders

The relocation forced us to articulate what MoveRight does that generic CRM software can’t. Here’s the list:

Zone-Aware Permissions

When Charlotte sales moves to the NSC (which happened on August 28, 2026), the agents who were in the Charlotte zone need to be recontexted to the NSC zone. Their autodials, their OBE (outbound estimate) form, and their lead routing should behave like the NSC automatically — not require a configuration change.

In a generic CRM, “moving a team from one territory to another” means reconfiguring pipelines, reassigning record ownership, updating routing rules, and praying nothing breaks. In MoveRight, it means changing the zone. The zone carries the permissions, the pricing, the documents, and the routing. One change. Everything follows.

Postal Codes and ZIP Codes

Canadian postal codes are six characters, alphanumeric, format A1A 1A1. US ZIP codes are five digits (or nine with ZIP+4). Software built in the US for US markets handles ZIP codes fine. Postal codes break lead routing, distance calculations, and territory assignment in software that wasn’t designed for them.

We fixed a specific bug in August 2026 (Changelog_2608.md !2227): Vancouver OBE leads were being misrouted to Lehigh Valley because area-code casing wasn’t normalized before the service-area lookup. Area codes are now lower-cased, and address parsing for Canadian postal codes, US ZIP codes, highways, and civic numbers is improved. This is the kind of bug that generic CRM software doesn’t even know it has — because it was never built to handle Canadian postal codes in the first place.

MoveRight was built in Canada. Postal codes are first-class. The NSC handles both formats every day.

Multi-Currency Payments

The NSC books moves for US franchises (USD) and Canadian franchises (CAD). The same payment system — BlueSage — handles both currencies. The crew takes a card payment on a terminal at the door, in the currency of the franchise zone. The job financials panel shows the amount in the job’s currency. The settlement, reconciliation, and unmatched-payment review queue all work in the job’s currency.

A generic CRM doesn’t have a payment system. It integrates with Stripe or Square. The integration handles one currency natively and the other as an afterthought. MoveRight’s BlueSage integration handles both because it was built for a network that operates in both.

Cross-Border Documents

YMM’s bills of lading for interstate US moves come in three variants: Full Value Protection (FVP), Released Value Plus (RVP), and Released Value (PVP). Each has different liability coverage, different declared shipment value calculations, and different signature requirements. We ported all three to Aegis in August 2026 (Changelog_2608.md !2256, !2296) — auditing each one field-by-field against its PandaDoc original and fixing a PVP bug that understated declared shipment value by half.

On the Canadian side, the Vancouver Island estimate template handles GST, provincial tax breakout, and the DBA (doing-business-as) naming convention that Canadian franchises use. The Calgary estimate, the Kitchener-Waterloo estimate, and the Charlotte estimate each preserve their franchise-specific branding, pricing, tax, inventory, terms, signer roles, and promotional content.

The same Aegis engine renders all of them. Different templates, different jurisdictions, one document system. A generic CRM doesn’t have document templates — it has a “document builder” that produces the same PDF for every customer regardless of jurisdiction.

Screen Pop and Escalate Email Links

When a call comes in, a screen pop opens the job in MoveRight. When a job escalates, an email link opens the job. In August 2026 (Changelog_2608.md !2299), we fixed a bug where multi-zone users (e.g. NSC agents with roles in several franchises) who opened a job from a screen-pop or escalate-email link were recontexted to their first zone alphabetically and got a “Cannot find job in any zone” error. The frontend now passes the URL ?zone= param through to authentication, job URLs carry the franchise zone directly, and all notification templates include the zone in their job links.

This is a cross-border bug. A single-zone user never hits it. A multi-zone user — which is every NSC agent — hits it every time. Generic CRM software doesn’t have this problem because it doesn’t have zones. It also doesn’t have the solution.

What Generic CRM Software Can’t Do

A generic CRM (HubSpot, Salesforce, Zoho) is built for a sales pipeline. It has contacts, deals, stages, and reports. It doesn’t have:

Zones. There’s no concept of a franchise territory. You’d simulate it with record ownership and custom fields. But the calculator, the documents, the pricing, and the routing don’t follow the zone — because there is no zone.
Franchise-specific document templates. You’d build a document in a third-party tool (PandaDoc, DocuSign) and trigger it from the CRM. Each franchise needs its own template. Each jurisdiction needs its own tax logic. You’d maintain 30+ templates in a third-party builder, each with per-envelope fees.
Postal-code-aware lead routing. You’d build a custom integration with a geocoding service. It would break on Canadian postal codes because the geocoder was trained on US addresses.
A crew navigator. Generic CRMs don’t have crew management. You’d bolt on a third-party field service app.
OTR Ops Readiness. Generic CRMs don’t have a per-day checklist for long-distance moves with auto-resolved document signing columns. You’d build a custom dashboard in a BI tool.
Moving-specific calculators. Generic CRMs don’t have calculators. You’d build a spreadsheet and copy the numbers in.

You’d bolt on three or four integrations, maintain them, pay for them, and still have gaps. The total cost of a generic CRM + PandaDoc + a field service app + a BI tool + a geocoding integration is higher than MoveRight — and the result is worse, because the integrations don’t share a data model.

The Lesson

When you operate across borders, your software needs to be built by people who operate across borders.

MoveRight was built in Canada. It runs a US sales center in Kansas City. It handles both sides natively — postal codes and ZIP codes, USD and CAD, US and Canadian document templates, franchise-specific pricing for both countries. That’s not a feature. It’s an architecture.

The relocation forced us to articulate this because the relocation exposed every seam. The network buildout is an IT project. The managed IT contract is a cross-border vendor relationship. The zone migration is a software operation. The document templates are a jurisdictional compliance exercise. The payment system is a currency problem. None of these are “features” you check off in a buying guide. They’re the difference between software that works for a cross-border moving company and software that doesn’t.

We’re a Canadian company that runs a US sales center with software we built for both sides. That’s the pitch. Not “we have a moving template.” That’s not the same thing.

MoveRight is the moving company CRM that was built in Canada, runs a US sales center, and handles both sides of the border natively — because the people who built it operate on both sides of the border.

See how MoveRight handles multi-location operations

References:

What Relocating Our Kansas City HQ Taught Us About Moving Software