Summary: Pricing in an over-the-road truckload network is not simply the act of matching a market rate. It is the discipline of deciding which freight deserves scarce capacity, what the carrier must recover to serve it, and when a lane should be won, repriced, redesigned, or allowed to go elsewhere. BidRight supports this approach by helping pricing teams model costs, evaluate opportunities, and manage RFPs more effectively.

This article is part of The Network Playbook: Role-by-Role Strategies for Truckload Profitability and Risk, a 12-part series exploring how OTR truckload carriers can structure their networks, interpret data, and turn insights into profit.

Pricing Is a Network Decision

Pricing is often asked to solve for one piece of the puzzle, when the harder work is understanding what that piece does to the rest of the board. On paper, the lane looks contained: origin, destination, miles, and volume. The implied instruction is simple: Quote the number.

That framing is convenient, but it is incomplete. In an over-the-road network, no lane stands alone. A rate on one lane changes where a tractor ends up, what work is available to the driver next, how much trailer capacity is tied up, how much empty mileage the network absorbs, and whether operations has a realistic path to the next profitable move.

A lane can look properly priced against the market and still be wrong for the carrier. A lane can look thin in isolation and still be valuable because it puts capacity exactly where the network needs it. A customer can say the rate is “at market” while the carrier’s own cost to serve says the freight is quietly consuming more value than it creates.

That is the hard call for pricing: Do not price the lane only. Price the network the lane is joining.

The carrier’s own cost floor speaks first. Network fit speaks second. The market speaks third.

Start With the Cost Floor

The first pricing question is not, “What is the market paying?”

The first question is, “What must this freight recover for our network?”

That answer should include loaded miles, expected empty miles, transit, fuel, maintenance, insurance, overhead, load-specific costs, accessorial expectations, and the likely cost of getting into and out of the freight. If a lane requires live-load delay, drop capacity, unusual appointment work, expected weather disruption, or difficult recovery, those costs should be part of the pricing conversation before the bid is submitted.

At scale, no pricing team is going to build that picture one lane at a time on a 2,000-lane RFP. It has to be modeled. That is why the industry has been moving toward true activity-based costing at the lane level, and why a lane-level modeled operating ratio is becoming the default question a pricing team asks. If your model can produce a defensible modeled OR on every lane in the bid, not just the ones with rich history, you can start every rate conversation from a real cost floor instead of a rounded-off assumption. Lanes with thin data should not fall out of the picture. They should fall back through a cascade (zip-3, city-state, state) until the model finds a usable sample, so that every lane in the file has a signal.

Too often, the bid file is not wrong so much as incomplete. It captures the lane, miles, rate, and volume, but not the operating conditions that will determine whether the rate works. Pricing should treat the pre-bid window as a discovery period, not just a deadline. Many customers allow questions by email, portals, or formal RFQ sessions before the RFP is due. Pricing should use those openings to get more granular before the rate is built.

The file may show a clean pickup and delivery window. The dock takes six hours.

It may show inbound and outbound volume in the same customer package. In practice, the customer tenders more in one direction and leaves the carrier to solve the other.

It may show weekly volume. The freight shows up late Thursday and Friday.

It may show a destination market. Dispatch learns there are no usable reloads at a sustainable rate.

None of those misses are purely operational. They are pricing misses too, because the operating realities were never clarified, challenged, or converted into a required rate, a customer requirement, or a review trigger.

For new business, pricing should partner with sales to understand what the customer is really promising and where flexibility may exist. For existing business, pricing should partner with operations to confirm what actually happens with the incumbent freight.

Without those answers, the carrier is not pricing the freight. It is submitting a hope-driven rate.

Decide the Lane’s Role

Once the cost floor is known, pricing should decide what job the lane performs in the network.

Core lanes should be protected because they support the carrier’s strongest markets, drivers, customers, and operating rhythm. Connector and backhaul lanes may look ordinary or thin in isolation, but they can be valuable if they reduce empty miles, improve utilization, or position trucks for stronger freight. Growth lanes should be tested against the network the carrier wants to build, not just the first load awarded.

Bad-fit lanes should carry a premium. If the freight strands equipment, creates chronic dwell, damages driver experience, requires difficult recovery, or adds risk, the rate should reflect that burden. No-fit lanes should be declined or priced high enough that losing is acceptable.

That classification should happen before the final rate is built. Otherwise, the deadline arrives, sales wants the revenue, operations hopes it can make the freight work, and pricing trims the ask because the market looks competitive. That is how a carrier wins freight it should have been willing to lose.

The practical version of this is simple. Every lane in the file gets marked. Not just the ones you love. Not just the ones you want to walk from. All of them. And that mark should be visible and filterable as the rate work progresses, so pricing can look at only the pursue lanes when it is doing the pursue conversation, and only the decline lanes when it is deciding how high to price them. Interest and posture live at the lane, not in someone’s memory.

Build Bid Posture Before Bid Price

The most useful pricing discipline is a written bid posture.

Before an RFP is submitted, each meaningful lane should be classified: protect, pursue, price normally, price with premium, redesign, or decline.

Protect and pursue lanes strengthen the network through density, balance, customer fit, or strategic market position. Normal lanes are acceptable at the right margin. Premium-required lanes consume extra capacity, driver time, trailer availability, or operational tolerance and should pay for that burden. Redesign lanes need something besides rate to become desirable. Decline lanes do not fit the carrier’s network, risk posture, or capacity strategy.

This posture gives pricing and sales a shared backbone before the deadline pressure arrives. A carrier that cannot identify which lanes it is willing to lose will eventually behave as if every lane must be won.

That is not pricing strategy.

The posture also drives the math the other way. If pricing knows the target OR for a lane and the operating realities of the freight, the rate is a calculation, not a guess. You back-solve from the OR you need to a starting rate per mile and then let the tool cascade the adjustments (fuel structure, mileage source, accessorials, pay terms) into the number that actually goes on the bid sheet. A good pricing tool should handle that math consistently rather than forcing the team to reverse-engineer it on every lane.

Do Not Negotiate Against Yourself

One of the most expensive habits in trucking pricing happens before the customer ever says no.

The carrier discounts its own request.

The team knows a lane needs an increase but decides the customer “will never take that.” The model supports a meaningful correction, but the ask is reduced because “we do not want to upset them.” A lane is below the cost floor, but the carrier requests only half the needed increase because “something is better than nothing.”

Sometimes that caution is framed as relationship management. Often, it is negotiating against yourself.

A carrier should be thoughtful in how it approaches a customer. It should understand market context, relationship history, service performance, and competitive pressure. It should avoid reckless demands and poorly supported increases. But it should not weaken its own position before the customer has even responded.

That habit reveals a deeper problem: many carriers do not fully believe in the value of their own capacity.

They know reliable service has value. They know good drivers, clean execution, and committed capacity are not commodities. Yet when it is time to price that capacity, they often behave as if the customer is doing them a favor by accepting it.

The result is a handicapped negotiation. The carrier starts from a reduced ask, the customer negotiates from there, and the final answer lands below what the business actually needed. Nobody made a single dramatic mistake. The carrier simply gave away margin before the negotiations even began.

A better standard is this: make the full business case before deciding what concession is acceptable.

If the cost floor says the lane requires $2.50 per mile, do not open at $2.38 because the customer might object. Understand the $2.50. Prepare the explanation. Know the annual dollar impact. Know the operating drivers. Know the alternatives. Then approach the customer with a professional, specific, lane-level case.

Part of what quietly enables that discipline is standardization. A carrier that prices one lane with one fuel structure and another lane with a different fuel structure, one customer with one accessorial package and another with another, cannot compare its own asks to itself with any confidence. When every lane can be normalized to a comparable rate per mile, with fuel, mileage source, and pay terms handled underneath the number rather than mixed into it, the pricing team sees clearly. It knows exactly what it is asking for. It knows exactly what it is willing to accept. It stops shaving the ask by accident.

The customer may still say no. That is part of the work. But the carrier should at least make the customer say no to the real requirement before compromising away its own economics. If the team does not price its capacity like it has value, the customer has little reason to do it for them.

Make the Customer Conversation Specific

The strongest rate conversation is not a broad complaint about costs. It is a specific discussion about freight.

Current revenue. Required revenue. Annual dollar impact. Operating cause. Options for resolution.

A five-cent gap can sound small until it is annualized across 300 loads. A lane that appears only slightly underpriced may be one of the biggest opportunities in the network because the volume is meaningful and the issue repeats every week.

That is why dollars matter. Cents per mile help pricing calculate. Dollars help leadership and customers understand the business issue.

The strongest customer conversations are specific. If a customer has 12 lanes and three are structurally underpriced, the best conversation is usually about the three. A customer-wide increase may put good freight at risk and still fail to repair the actual problem.

A lane-specific request is more credible because it proves the carrier has done the work.

It can start with the relationship: “This account matters to us, and most of the freight is working.”

Then it can narrow the issue: “These lanes are the exception.”

Then it can explain the cause: “The challenge is not only linehaul rate. It is the cost of positioning, dwell, trailer use, and reload quality.”

Then it can present choices: “We can solve this through rate, volume balance, appointment changes, trailer support, delivery-day changes, or a different lane mix.”

That framing changes the conversation from “we need more money” to “this freight has to be redesigned or repriced if it is going to remain sustainable.”

The tool matters here more than people expect. If a pricing team cannot quickly pull up the three problem lanes, with the current rate, the required rate, the dollar gap, and the operating cause on one screen, the conversation devolves into generalities. Specificity is a workflow question, not just a discipline question.

Use Market Data the Right Way

Market data has a role. It shows what the customer may be hearing and helps frame the competitive environment.

But it cannot decide whether the freight belongs in this carrier’s network.

That decision starts inside the business. What does the lane cost to serve? What does it do to the next move? What capacity does it consume? What rate does the network need?

Only then should the benchmark enter the discussion. And when it does, one benchmark is rarely enough. DAT is one view. A shipper’s own historical paid rates are another. A public index is another. An internal benchmark built from prior awards is another. The right pricing view holds these side by side, so the team can see how much agreement there is between them and, more importantly, where they disagree. Disagreement between market signals is often the most useful data point in the file.

If the market supports the required rate, the carrier has a cleaner case. If it does not, the carrier has choices: Change the operating plan, ask for different customer requirements, limit the volume, accept the tradeoff intentionally, or walk away.

What it should not do is treat the benchmark as the answer.

A market number can show where freight is trading. It cannot show whether that freight deserves this carrier’s capacity.

Post-Award Review Is Part of Pricing

Pricing work is not finished when the award comes back.

A bid is a set of assumptions. Once the freight starts moving, those assumptions should be tested.

Thirty, 60, and 90 days after a meaningful award, the pricing team should compare actual performance to the bid file. Did the volume show up? Did the customer tender the lanes that made the package work? Did dwell match the expectation? Did reload quality hold? Did operations have to use workarounds the bid did not price?

This is not about proving the pricing team right or wrong. It is about building institutional memory.

A carrier should know which customers consistently tender differently than promised. It should know which markets look better in an RFP than they operate in practice. It should know which assumptions are routinely too optimistic.

Without post-award discipline, every bid season starts over. The same assumptions get made. The same discounts get offered. The same freight gets won and then explained away six months later.

The unlock here is being able to search across two data sets a carrier already owns. What did we bid? What did we actually run? Held side by side, in the same query, the same customer, the same lane, over the same window. That comparison is where the institutional memory lives. Most carriers have both data sets. Very few can pull them into the same view without significant manual Excel work.

A pricing organization gets stronger when it studies its own misses.

The Standard for Pricing

The pricing team does not need to win every lane. It needs to help the carrier win the right freight at a rate the system can sustain.

No benchmark before the cost floor.

No RFP submission without documented assumptions.

No below-floor bid without a clear business case and review trigger.

No customer-wide increase when the issue is lane-specific.

No self-discount before the customer has responded to the real business case.

No award should be trusted until actual performance has been compared to the bid.

These standards do not make pricing rigid. They make it intentional. They give sales a clearer story, operations a more realistic plan, finance a more credible forecast, and ownership a better view of what the network is choosing to become.

Key Takeaway

Pricing is not the act of matching the market. It is the act of deciding which freight deserves scarce capacity and what the carrier must recover to serve it well. The best pricing teams know the cost floor, understand the lane’s role in the network, use market data as context, refuse to negotiate against themselves, and review whether the freight performed the way the bid promised.

How BidRight Supports Smarter Pricing

Everything above is the pricing philosophy that BidRight is built around. A lane-level modeled OR on every lane in the bid, with a fallback cascade so nothing goes into the RFP without a real cost signal. A normalized rate per mile that lets a pricing team compare lanes across customers without the fuel, mileage, and pay-term noise. Lane-level interest and posture markings that are visible and filterable as the work progresses. Suggested rates that back-solve from the target OR to a starting RPM. Multiple market benchmarks held side by side, not one. And a Bid Warehouse that lets a carrier search its BidRight bid history and its FreightMath^™ order history in the same query, so post-award review takes minutes instead of weeks.

If any of this sounds like the way your team already thinks about pricing, we should talk. BidRight was built by carriers, for carriers, and the alpha group in the latest software release shapes the roadmap every week.

To learn how BidRight can help your team price the network instead of the lane, contact us via the form below.

Connect with us