Internal MyCarrier ICP Resource Page

A simple internal guide to understand key customer profiles by shipment volume, buying team, product usage, pain points, objections, and sales opportunities.

ICP Profile 1: Very Low-Volume Shippers

Annual LTL Spend< $20k
Shipment Band1 - 20/m
Avg Monthly Shipments5
Avg Monthly Quotes15-20

Company Demographics

Average employee count is not included because Sales notes it rarely correlates to LTL company size.

Mechanical EngineeringBuilding MaterialsRetailAutomotiveChemicalsConstructionFood & BevPrintingMachinery

Typical Tech Stack

Excel, QuickBooks, email, carrier portals

MyCarrier Usage

Avg Users2
Avg Carriers3-4
Platform Tenure~2 years
Locations1-2
Avg ARR$1390
Core takeaway: This profile needs MyCarrier to stay simple, fast, and effortless. They keep using it when it helps them handle occasional shipping without adding work.

Common Products Purchased

ProductShare
Free93% of shippers
Starter3%
Starter + Truckload + Unlimited Data History1%
Starter + Data1%
Starter + Other Combos<1%
Professional1%

Team + Decision-Making Unit

  • One or two departments are typically involved.
  • Departments: Owner / CEO / Book Keeper and Shipping Operations.
  • Buyer: Owner / Office Manager.
  • Champion: Buyer or User.
  • Users: Single Shipper or Admin Role.
Primary Persona: Single Shipper / Office Admin / Owner
Use Cases
  • Occasional rate check
  • Book a shipment when needed
  • Customer tracking inquiries
Buying Trigger
  • Jack-or-Jane of all trades, juggling multiple roles in one
Objection
  • Not enough volume to need
Journey

Before: Ad hoc, reactive shipping

During: Uses MyCarrier sporadically

After: Stays only if it remains effortless

Example AccountsNutraluxe (Professional), Vanhessen (Was Professional, now on Free), Carolina Narrow Fabric Co (Starter)

ICP Profile 2: Low-Volume Shippers

Annual LTL Spend~$130k
Shipment Band21 - 50/m
Avg Monthly Shipments~30
Avg ARR$1452

Company Demographics

Mechanical / Industrial EngineeringRetailAutomotiveConstruction

Typical Tech Stack

Excel, email, accounting software

MyCarrier Usage

Avg Users3-4
Avg Carriers7-8
Sales Estimate3-5 carriers
Platform Tenure~3 years
Locations~2
Core takeaway: This group is similar to ICP 1, but shipment volume makes manual work more painful and creates stronger motivation to compare rates, track shipments, and reduce back-and-forth.

Common Products Purchased

ProductShare
Free63%
Starter12%
Starter + Data5%
Starter + Data + Truckload6%
Starter + Other Combo2%
Professional10%
Professional + InvoiceHub1.5%
Professional Plus.5%

Team + Decision-Making Unit

  • Two or three main departments are typically involved: Owner / CEO, Book Keeper, Shipping Operations.
  • Sales feedback: often only one person is involved because they wear multiple hats.
  • Buyer: Owner / Office Manager.
  • Champion: Buyer or User.
  • Users: Single Shipper or Admin Role.
Persona: Single Shipper
Use Cases
  • Quote and book quickly without emailing carriers
  • Track shipment status in one place
Buying Triggers
  • Missed pickups or service issues from manual coordination
  • Booking without actually checking rates
Objections
  • Doesn’t want to change processes
  • Existing way is “good enough”
Journey

Before: Manual quotes and limited decision-making information

During: Experiences faster rate quotes and easy comparison

After: Makes more informed choices and ships more efficiently

Persona: Owner / Office Admin / Book Keeper
Use Cases
  • Manual review of rate quotes vs. invoices received
  • Customer tracking inquiries
Buying Trigger
  • Jack-or-Jane of all trades, juggling multiple roles in one
Objection
  • Not enough volume to need
Journey

Before: Ad hoc, reactive shipping

During: Uses MyCarrier sporadically

After: Stays only if it remains effortless

ICP Profile 3: Emerging Operational Complexity

Avg Employees500
Annual LTL Spend280k
Shipment Band51 - 100/m
Avg Monthly Shipments70
Avg Monthly Quotes130
Avg ARR$1901

Company Demographics

ManufacturingBuilding MaterialsAutomotiveChemicals

Typical Tech Stack

ERP + Accounting

MyCarrier Usage

Avg Users5
Avg Carriers8
Platform Tenure3 years
Locations2-3
Core takeaway: This profile is often ready for better workflows, but may still be comfortable on a basic plan. Growth, multiple locations, and data needs are the most common upgrade drivers.

Average Products Purchased

ProductShare
Free47%
Starter Only10%
Starter + Data7%
Starter + Data + Truckload2%
Starter + Other Combo2%
Professional29%
Professional Plus3%

Team + Decision-Making Unit

  • Departments: Shipping / Logistics, Finance / Accounting, Operations.
  • Buyer: VP of Ops.
  • Champion: Shipping Manager.
  • Users: Shipping Users / AP.
  • Sales feedback: often 2 layers of decision makers.
Persona: Shipping / Logistics
Use Cases
  • Quote and book quickly without emailing carriers
  • Reuse shipment and product details
  • Track status in one place
  • Reduce errors from inconsistent booking
Buying Triggers
  • Volume outgrows one person
  • Multiple users or locations
  • Frequent re-quoting of same lanes
  • Missed pickups or service issues
Objections
  • “Will this actually save us time?”
  • “I’ve been doing it fine for so long, will this actually help?”
Journey

Before: Manual quoting and booking through emails and portals

During: Centralizes quote, book, and track

After: Faster booking, fewer errors, consistent workflows

Persona: Finance / Accounting
Use Cases
  • Compare invoices against quoted rates
  • Identify overcharges without manual audits
  • Track monthly freight spend
  • Support accruals and budgeting
Buying Triggers
  • Increase in invoice volume
  • Repeated billing discrepancies
  • Leadership asks for clearer reporting
Objections
  • “Will this really catch billing issues?”
  • “Is the data accurate enough for finance?”
  • “Does this provide the same detail as a carrier portal?”
  • “What is the security of payments?”
Journey

Before: Manual invoice review in spreadsheets

During: Reviews invoices and flags discrepancies

After: Reduced invoice errors and faster month-end close

Persona: Operations
Use Cases
  • Standardize shipping processes
  • Ensure new hires follow workflows
  • Reduce dependency on power users
  • Monitor basic shipping performance
Buying Triggers
  • Growth exposes inconsistent processes
  • Shipping issues impact operations
  • Need for repeatable workflows
Objections
  • “Will teams actually adopt this?”
  • “How hard is it to roll out?”
Journey

Before: Inconsistent, person-dependent shipping

During: Uses MyCarrier to enforce a common process

After: Predictable, repeatable shipping operations

Sales NotesEven in larger volumes, many customers are comfortable with the basic plan. They may share logins and have 1-2 people handling shipping. The biggest upgrade drivers are 2 or more locations or the need for more data.

ICP Profile 4: Scaling Multi-Location Operations

Avg Employees~650
Annual LTL Spend~$570k
Shipment Band101 - 250/m
Avg Monthly Shipments150
Avg Monthly Quotes260
Avg ARR$2934

Company Demographics

ManufacturingAutomotiveIndustrial

Typical Tech Stack

ERP, BI tools, Accounting

MyCarrier Usage

Avg Users8
Avg Carriers9
Platform Tenure~3.5 years
Locations3-4
Core takeaway: This profile often knows it has a process problem. The choice is usually adding people to support the process or consolidating the process with better tooling.

Average Products Purchased

ProductShare
Free31%
Starter5%
Starter + Data7%
Starter + Data + Truckload1%
Starter + Other Combos4%
Professional32%
Professional Plus20%

Team + Decision-Making Unit

  • Departments: Shipping / Logistics, Finance, Operations, IT.
  • Buyer: Leadership / CEO.
  • Champion: Logistics / Operations Leader.
  • Users: Shipping Dept + Accounting Dept.
  • C-suite executives are often involved at this level.
Persona: Logistics / Shipping
Use Cases
  • Manage shipping across multiple locations
  • Scale department without scaling headcount
  • Improve visibility across teams
Buying Triggers
  • Expansion into new locations and/or acquisitions
  • Volume creates bottlenecks
  • Service issues from lack of oversight
Objections
  • “Can this support multi-location shipping?”
  • “Will it slow us down?”
Journey

Before: Fragmented processes by location

During: Centralizes booking and visibility

After: Consistent execution and improved reliability

Persona: Finance / Accounting
Use Cases
  • Process growing invoice volumes efficiently
  • Identify and dispute overcharges
  • Reduce reconciliation time
  • Deliver reliable reporting to leadership
Buying Triggers
  • Invoice volume overwhelms AP
  • Disputes consume too much time
  • Inconsistent freight data
Objections
  • “Will this integrate into our workflow?”
  • “Does it really reduce manual effort?”
Journey

Before: Manual invoice audits and reconciliation

During: Reviews invoices and manages disputes

After: Faster processing and fewer billing issues

Persona: Operations
Use Cases
  • Monitor performance trends
  • Reduce operational risk as volume grows
  • Support scale without adding headcount
Buying Triggers
  • Growth creates process breakdowns
  • Leadership pressure to control costs
  • Inconsistent execution across teams
Objections
  • “Will this limit flexibility?”
  • “Can it handle our pace of growth?”
Journey

Before: Reactive problem-solving

During: Standardizes and monitors shipping

After: Controlled, scalable operations

Persona: Leadership
Use Cases
  • Gain visibility into freight costs
  • Ensure shipping is not slowing growth
  • Reduce operational surprises
  • Justify investment in logistics tooling
Buying Triggers
  • Freight spend rising faster than revenue
  • Operational issues escalated to leadership
  • Need for accountability
Objections
  • “What’s the ROI?”
  • “Is this critical or just nice to have?”
Journey

Before: Limited visibility, reactive decisions

During: Reviews reporting for insight

After: Confidence in cost and operational control

Sales NotesThey may already have an ERP connection and view MyCarrier as the final puzzle piece. They may be manually entering ERP data into MyCarrier unless they have a large team. They are typically looking for something more robust.

ICP Profile 5: Enterprise-Lite Network Governance

Avg Employees~1,100
Annual LTL Spend~$1.2M
Shipment Band250 - 500/m
Avg Monthly Shipments340
Avg Monthly Quotes520
Avg ARR$4600

Company Demographics

ManufacturingDistributionRetail

Typical Tech Stack

ERP, BI tools, Accounting, procurement systems

MyCarrier Usage

Avg Users18
Avg Carriers11
Platform Tenure3.2 years
Locations6

Sales note: average users might be a tad high.

Core takeaway: This profile needs control across people, locations, carriers, and spend. The strongest message is centralized governance without disrupting existing workflows.

Average Products Purchased

ProductShare
Free29%
Starter2%
Starter + Data4%
Starter + Other Combos3%
Professional41%
Professional Plus21)%

Team + Decision-Making Unit

  • Departments: Shipping / Logistics, Finance, Operations, IT, Procurement.
  • Buyer: Leadership / Owner / CEO.
  • Champion: Logistics Leader + Finance Leader.
  • Users: Shipping, operations, procurement, warehousing, finance, etc.
Persona: Logistics / Transportation
Use Cases
  • Govern carrier usage across locations
  • Manage exceptions efficiently
  • Maintain service levels at scale
  • Balance local autonomy with centralized control
Buying Triggers
  • Volume creates operational risk
  • Carrier sprawl
  • Inconsistent performance across sites
Objections
  • “Can this support our complexity?”
  • “Will it disrupt existing workflows?”
Journey

Before: Fragmented tools and processes

During: Uses MyCarrier as the central operating system

After: Reliable, governed execution

Persona: Finance / Accounts Payable
Use Cases
  • Audit large invoice volumes
  • Identify freight leakage
  • Support forecasting and budgeting
  • Reduce reconciliation effort
Buying Triggers
  • Audit risk
  • Overpayment concerns
  • Executive scrutiny of spend
Objections
  • “Will this cover all scenarios?”
  • “Can we trust the data?”
Journey

Before: Manual audits and spot checks

During: Uses invoice review and disputes

After: Improved accuracy and reduced manual work

Persona: Operations
Use Cases
  • Track KPIs across the network
  • Identify inefficiencies
  • Enforce shipping policy compliance
  • Improve customer satisfaction
Buying Triggers
  • Inconsistent performance
  • Cost variability
  • Compliance concerns
Objections
  • “Is this another dashboard?”
  • “How actionable is the data?”
Journey

Before: Reactive oversight

During: Uses reporting for governance

After: Proactive operational management

Persona: Procurement
Use Cases
  • Analyze carrier utilization
  • Support negotiations with performance data
  • Align freight data with sourcing forecasts
Buying Triggers
  • Too many carriers
  • Poor leverage in negotiations
  • Lack of performance data
Objections
  • “Will this replace existing sourcing tools?”
  • “Is the data negotiation-ready?”
Journey

Before: Limited insight into carrier performance

During: Uses MyCarrier data to guide sourcing

After: Stronger vendor strategy and cost control

Persona: Leadership
Use Cases
  • Ensure cost governance
  • Reduce operational risk
  • Maintain predictability
  • Trust freight reporting
Buying Triggers
  • Rising spend
  • Audit exposure
  • Leadership / owner questions
Objections
  • “Is this scalable long-term?”
  • “What risk does this bring to my business if we rely on this and it fails?”
Journey

Before: Limited confidence in controls

During: Reviews MyCarrier insights

After: Confidence in governance

Sales NotesMulti-modal needs are common for this profile, including movement toward Freight View, Kuebix, or building their own solution.

ICP Profile 6: High-Volume, Mission-Critical Shipping

Avg Employees~1,000
Annual LTL Spend~$3.1M
Shipment Band500+ /m
Avg Monthly Shipments970
Avg Monthly Quotes1400
Avg ARR$15,907

Company Demographics

Building MaterialsAutomotive

Typical Tech Stack

ERP, BI tools, Accounting, procurement systems, internal custom tools

MyCarrier Usage

Avg Users28
Avg Carriers12
Platform Tenure~3.3 years
Locations10
Core takeaway: This profile is evaluating whether MyCarrier can support large, distributed, mission-critical shipping. Reliability, workflow fit, and ERP bridge value matter most.

Average Products Purchased

ProductShare
Free27%
Starter9%
Professional42%
Professional Plus22%

Team + Decision-Making Unit

  • Five or more departments are often involved: Shipping / Logistics, Finance / Accounts Payable, Operations, Procurement, IT / Systems, Executive Leadership.
  • Buyer: VP of Supply Chain / Operations.
  • Champion: Director of Logistics / Transportation.
  • Users: Large, distributed teams across logistics, finance, and operations.
Persona: Shipping / Logistics
Use Cases
  • Run shipping as mission-critical part of the organization
  • Manage large carrier networks efficiently
  • Support complex routing, accessorials, and exception handling
  • Maintain consistent execution across locations
Buying Triggers
  • Manual processes become impossible at volume
  • Service failures escalate to leadership
  • Lack of visibility across the network
Objections
  • Can this handle our volume without breaking?
  • Will this disrupt existing workflows?
  • Is this reliable?
  • Not adding 3PLs on our platform
  • They need a multi-modal solution
Journey

Before: Fragmented systems and manual oversight

During: Centralizes booking, tracking, and carrier management

After: Reliable, scalable shipping with fewer disruptions

Persona: Finance / Accounts Payable
Use Cases
  • Identify problematic invoices that require human attention while automation and AI handle the rest
  • Perform side-by-side invoice comparisons to catch discrepancies and overcharges
  • File disputes and manage resolutions in one system
  • Pay carrier vendors quickly and accurately from a centralized platform
  • Deliver trusted freight spend reporting to executive leadership
Buying Triggers
  • Extremely high invoice volume
  • Audit exposure or recurring billing discrepancies
  • Inefficient payment workflows
  • Executive pressure for cost transparency
Objections
  • “Can this handle all of our edge cases?”
  • “Will this actually eliminate the need to jump between carrier portals?”
Journey

Before: Manual data entry, fragmented invoice review, and portal hopping

During: Reviews invoices, flags discrepancies, disputes charges, and pays carriers in one place

After: Better data accuracy, faster processing, and dramatically reduced manual effort

Persona: Operations
Use Cases
  • Ensure shipping does not disrupt core operations
  • Monitor performance across locations
  • Identify inefficiencies and bottlenecks
  • Enforce standardized shipping processes
  • Visibility into customer tracking
Buying Triggers
  • Operational issues tied to freight execution
  • Inconsistent performance across facilities
  • Growth increasing operational risk
Objections
  • Will this actually improve operational consistency?
  • Is the data actionable or just reporting?
Journey

Before: Reactive oversight and firefighting

During: Monitors and manages shipping performance

After: Predictable, controlled operations at scale

Sales NotesThe main reason they are looking into MyCarrier is because other TMSs are not working properly. MyCarrier needs to bridge the gap between customers that already have ERP integrations and those that do not.