Fenichey LLC is a freight brokerage that coordinates hundreds of shipments a month through a mix of contracted agents and in-house staff — a model where speed and clear communication aren't nice-to-haves, they're the product. When you're moving 1,200 to 1,500 loads a month, your systems need to pull their weight. Fenichey's HubSpot portal was doing the opposite: a fully-licensed, $1,800-per-month investment that most of the team had quietly stopped using. Cartographer Consulting rebuilt it from the ground up — and in doing so, turned a growing operational liability into the backbone of how Fenichey works.
Fenichey had been paying for HubSpot's Sales, Marketing, and Service Hubs at the Pro tier for some time, but the portal had never been configured to match how the business actually runs. Over 57,000 contacts and 54,000 companies sat in the system — most unqualified or dormant, accumulated without any consistent management process. Workflows had been built and broken. Pipelines overlapped. 13 users held active HubSpot seats, but adoption was low — key members of the operations team had defaulted back to Gmail because HubSpot simply asked more of them than it gave back.
No pipeline visibility. Over 800 active deals sat in the system with no systematic follow-up logic and no reliable win/loss tracking — meaning there was no way to know how the sales operation was actually performing.
Manual work at every stage. The integration between Fenichey's TMS and HubSpot required manual intervention to sync shipment data — so agents faced a choice between double entry or skipping HubSpot entirely.
Volume without automation. Over 10,000 tickets had been processed through Service Hub, nearly all requiring manual handling. The accounting pipeline alone was managing 1,200 to 1,500 billing inquiries per month with no automated routing.
Agent friction by design. Fenichey's business depends on contracted agents who operate independently. The existing HubSpot setup asked too much of them — complexity and duplicate entry concerns had made adoption a losing battle before it started.
The team wasn't resisting HubSpot out of habit. The system hadn't been built for what Fenichey does, and no amount of training was going to change that.
Cartographer began with a full audit of the portal — not to document what was broken, but to understand exactly how Fenichey moves freight, manages agents, and handles the financial back-office before designing anything. That discovery shaped everything that followed.
Six purpose-built pipelines. Rather than patching the existing structure, Cartographer designed six distinct pipelines matched to Fenichey's actual workflows: Quoting, Logistics, Agent Sales, Accounting, Claims, and a master Operations router that directs inbound to the right place automatically. Each pipeline has defined stage criteria, exit requirements, and clear ownership.
Automated accounting routing. The accounting pipeline — which handles over a thousand billing inquiries a month — was redesigned around automation. Routine requests like payment status queries and rate verifications now receive auto-replies pointing customers to the appropriate portal, without touching a human queue. Manual review is reserved for inquiries that actually require it.
Logistics approval handling. A new approval routing workflow in the logistics pipeline handles the two scenarios where a shipment needs to pause for confirmation — customers who skip the quoting process and vendor shipments requiring client sign-off — without creating bottlenecks for every other load moving through.
A single intake point for everything. Cartographer built a multi-step Master Ingest Form that conditionally routes submissions to the correct pipeline based on the nature of the request. Quote requests, billing questions, and general inquiries each follow a different path from the same entry point — no manual triage required.
Documentation built to last. The engagement closed with a full documentation package: property references, pipeline SOPs, workflow documentation, and a process map tying everything together. The goal was a system the team could run, train from, and hand off — not one that required Cartographer to stay on the phone.
Fenichey came into this engagement paying $1,800 a month for a platform that wasn't doing much. The math on that is straightforward: over $21,000 a year in subscription fees, almost none of it generating operational return. What changed wasn't the subscription cost — it was what that investment now does.
The team has, for the first time, a complete picture of how freight moves through the business: from the moment a quote request arrives to the moment a shipment closes. Win and loss rates are now trackable. Accounting inquiries route automatically to the right handling path without anyone sorting them manually. New shipments that skip the quoting process no longer fall into a gray area — the logistics pipeline catches and routes them correctly. And when something comes in through the general inquiry channel, it gets directed to the right pipeline rather than sitting in a catch-all inbox.
Perhaps more practically: the system is documented. New team members and agents have SOPs to follow. Managers have a reference point when something breaks or needs to change. The dependency on institutional memory — on a specific person knowing how a specific workflow was supposed to run — has been replaced with something the whole organization can read and operate from.
The HubSpot portal at Fenichey is no longer a cost to be justified. It's an operational layer that does actual work.