Built for Logistics and 3PL Companies

The CRM freight brokers and 3PLs run their book out of.

Logistics operators juggle shippers, carriers, warehouse accounts, and a TMS or WMS that was never designed to answer "which shipper is at risk of churn." A good CRM for a 3PL is the one that holds the shipper relationship, the carrier scorecard, the active RFP, and the quote-to-signed-MSA motion in one place. Strkr is that one place.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Logistics is a relationship business running on a razor margin. Freight brokerages win and lose shippers on response time, pricing judgment, and the carrier bench they can mobilise in a four-hour window. 3PL fulfillment operators win and lose shipper contracts on the SKU-level fit between the shipper catalog and the warehouse network. Warehousing specialists win on the facility footprint and the long-term lease pricing judgment. Every one of those motions needs a CRM, and the CRM most 3PLs land on is either a TMS add-on that treats shippers as freight records, a WMS add-on that treats shippers as billing codes, or Salesforce bent into a shape that costs more than the margin on the account. The five pains below show up on every call we have with 3PL and freight-brokerage operators. If any of them look familiar, the rest of this page shows how Strkr collapses the shipper acquisition, carrier scorecard, RFP, and warehouse account motion into one workspace that the sales team, the operations team, and the carrier manager can all run out of without the Monday morning spreadsheet dance.

TMS is not a CRM

Our TMS treats shippers like freight records, not relationships.

The TMS is built around loads, lanes, and dispatch, not around the shipper relationship. Shipper contact history, procurement cadence, RFP timing, pricing judgment notes, carrier preference, and the last four quarters of volume trend live in six places or in nobody head. Strkr sits on top of the TMS with a native two-way integration and holds the shipper record, the account team, the pricing judgment, the RFP calendar, and the renewal risk in one place so the account manager spends the day on the relationship instead of digging through TMS reports.

Carrier scorecard scatter

Our carrier bench lives in a spreadsheet nobody updates.

The carrier manager keeps a mental model of which carriers to call for a reefer out of Fresno at 2 PM on a Thursday. When the carrier manager is on vacation, that mental model goes with them. Strkr carrier records hold the scorecard (on-time percentage, claim rate, insurance expiry, lane coverage, equipment type, driver pool size, last-paid date, dispatcher response time) with a lane-and-equipment filter so any brokerage rep can run the match in 30 seconds without the senior carrier manager on the line.

RFP response chaos

A shipper RFP drops and we lose a week on spreadsheet gymnastics.

Shippers run annual RFPs with 40 to 400 lanes and expect responses in a 7 to 14 day window. Most 3PLs run the response out of email threads, three Excel files, and a pricing meeting that ends at midnight the day before submission. Strkr RFP flows ingest the shipper lane sheet, auto-map lanes to the carrier bench, surface target buy rates by lane, pull the pricing-committee workflow onto the record, and generate the response pack with the margin cover sheet attached. The RFP is a tracked workstream, not an email fire.

Shipper churn silence

We lose a shipper and find out from the quarterly volume report.

Shipper volume quietly declines across three months and nobody raises the flag until the quarterly report shows the account at half of last year. By then the shipper is already running two more brokerages against you. Strkr churn signals flag shippers whose weekly volume dropped more than the per-account threshold, whose load acceptance ratio slipped, whose last-touch is past the account cadence, or whose contract renewal is inside the 90-day window. The account manager sees the three accounts to call this week instead of staring at a 400-shipper book.

Quote-to-signed scatter

A quote wins and the MSA sits in Legal for six weeks.

The brokerage reps a quote, the shipper verbally agrees, and the MSA, carrier liability certs, broker authority, SCAC verification, and payment terms sit in Legal while the shipper calls the next brokerage on the list. Strkr contract flows fire the DocuSign or PandaDoc draft on quote-accepted, loop Legal in with a review task, store the signed MSA on the record, and bump the account to Active with the TMS record provisioned by the Flow. The quote-to-signed window shrinks from six weeks to five business days without a Legal headcount add.

Multi-mode confusion

Shippers want van plus reefer plus intermodal plus air plus warehouse and the CRM only knows loads.

The shipper wants a quote on 30 van loads a week, 8 reefer loads a week, a drayage leg out of Long Beach, a flatbed for an oversized machine, 2,000 pallet positions of warehousing, and air freight for the high-value sub-assembly. Most CRMs tracks one mode and five product rows. Strkr handles multi-mode shippers natively with mode-specific product lines, mode-specific pricing, mode-specific carrier benches, and a consolidated shipper record so the account manager pitches the full service portfolio instead of fragmenting the relationship across three systems.

How Strkr fits the 3PL motion

The daily primitives logistics operators actually use.

Strkr for logistics is not a different product than Strkr for SaaS or Strkr for construction. It is the same CRM with industry-specific objects, flows, and views tuned for the 3PL and freight-brokerage motion. Everything below ships on every paid tier with no premium module or logistics-specific SKU gate. The primitives are shaped around what a 3PL repeats every day: shipper outreach, carrier capacity planning, RFP response, pricing judgment, contract execution, and renewal defence. When those six motions happen in one workspace with one record of truth, the account manager stops stitching the picture together across the TMS, the WMS, three spreadsheets, and an email thread, and starts working the three accounts that actually matter this week.

Shipper pipeline

The pipeline I actually run shippers out of.

Column-per-stage board grouped by owner, mode mix, lane region, estimated monthly volume, or current freight spend. Drag a shipper between stages (Prospect, Qualified, RFP Issued, Pricing, Quote Delivered, MSA Pending, Onboarded, Active) and the Flow checks the entry criteria, requires the missing artifact (shipper insurance, SCAC verification, carrier liability cert, broker authority), and surfaces the next-step prompt. Density toggle, color-by mode, group-by region live on the board so the brokerage director sees the book the way they need to run it today.

Shipper record

One record holds the whole shipper relationship.

The shipper record pulls in the primary contact, logistics manager, procurement lead, AP contact, operations manager, lane history, mode mix, equipment preferences, carrier approval list, insurance requirements, payment terms, last four quarters of volume, RFP calendar, and the current pricing judgment notes. A sidebar renders role-aware so the account manager sees relationship fields and the pricing analyst sees margin fields on the same record without a tab switch.

Carrier scorecard

The carrier bench on a scorecard, not in a spreadsheet.

Every carrier record holds the scorecard (on-time pickup percentage, on-time delivery percentage, claim rate, tender acceptance, insurance effective date, broker authority verification date, lane coverage map, equipment pool, driver roster size, dispatcher response time, 30 day paid status). A lane-and-equipment filter lets any brokerage rep find the top 10 carriers for a 53-foot dry van on the LAX to DFW lane in 30 seconds, scored by the metrics the shipper cares about.

Lane pricing panel

Target buy, target sell, margin cover on every lane.

A lane pricing side panel lives on every shipper quote and RFP with the target buy rate (pulled from the lane history and the market index), the target sell rate (pulled from the account margin target), the margin cover, and the comparable recent moves. The pricing analyst approves non-standard discounts inline, and the pricing committee audit trail lives on the record so the CFO review on margin erosion is a report pull instead of a six-hour excavation.

Load context

TMS loads threaded on the shipper record.

The TMS integration pulls recent and active loads onto the shipper record with pickup, delivery, carrier, revenue, cost, and margin visible per load. The account manager walks into a QBR with the last 90 days of lane performance, carrier mix, service failures, and margin profile on one screen without a BI tool and a prebuilt dashboard. The TMS stays the system of record for the load; Strkr stays the system of record for the relationship.

Warehouse account view

Pallet positions, SKU-level fit, dock scheduling on one record.

For 3PLs with a fulfillment or warehousing arm, the shipper record holds pallet positions in use, SKU count, SKU-level velocity, dock door assignment, picking method (each-pick, case-pick, pallet-pick), VAS requirements, and the WMS billing line items. The account manager pitches the warehousing expansion to an existing freight shipper from the same record they run the brokerage account out of.

Mobile for the yard

Edit the shipper record on the way across the warehouse floor.

Strkr mobile is first-class with offline queue, voice-note capture, pipeline edit, task completion, and SMS. The operations manager walking the warehouse floor after a shipper walkthrough opens the account on the phone, bumps the stage, drops a voice-note next-step, and the whole thing syncs when they get back to Wi-Fi. The brokerage rep standing at a carrier yard logs the dispatcher conversation from the parking lot.

The RFP response workstream

The one process that eats a week every time it drops.

Shipper RFPs are the single highest-stakes workstream in a brokerage or 3PL and the single most-often broken one. A mid-sized shipper RFP covers 40 to 400 lanes, asks for primary and secondary pricing, requires carrier liability certs, broker authority, insurance evidence, SCAC verification, references, and a pricing-committee sign-off on the margin spread. Most brokerages run the response out of three Excel files, four email threads, and a pricing meeting that runs past midnight the night before the response is due. Strkr RFP flows make the RFP a tracked workstream with an owner, a timeline, pricing judgment captured inline, and a response pack generated from the record. The RFP is a workflow, not a fire drill, and the brokerage director sees every live RFP across the book on one view.

RFP intake

Shipper lane sheet in, Strkr record out.

Upload the shipper RFP template and Strkr parses the lane sheet into structured records: origin region, destination region, equipment type, volume commitment, special handling, pickup window, delivery window, accessorial requirements. The parser handles the five formats most mid-market shippers send (CSV, Excel, PDF with tables, Project44 export, SMC3 export) so the brokerage team spends zero minutes retyping lanes.

Carrier match

Lane rows auto-matched to the carrier bench.

Each lane row in the RFP auto-matches to the top 10 carriers from the carrier bench based on lane coverage, equipment type, scorecard rating, and recent-week capacity signals. The pricing analyst reviews the match, bumps or drops carriers per lane, and the response pricing anchors on the matched carriers rather than on a market-index guess. Carrier conversations fire from the lane row with one click to request a buy-rate commitment on the specific lane.

Pricing analyst

Target buy, target sell, margin cover on every lane row.

Every lane row surfaces the suggested buy rate from the carrier bench, the target sell rate from the shipper margin target, the margin cover percent, and the comparable recent moves on the lane. The pricing analyst approves outliers, rejects margin-eroding lanes, and the final response pack carries the pricing judgment with the margin cover sheet attached for the pricing-committee sign-off.

Pricing committee

Non-standard pricing routed to committee with audit trail.

Any lane where the proposed margin falls below the account-tier threshold fires an approval task to the pricing committee. The committee reviews, approves or rejects with reason code, and the audit trail lives on the RFP record. The CFO review on margin erosion is a report pull instead of a Monday night fire drill, and the brokerage director knows which lanes the team should walk away from before the response goes out.

Response pack

The shipper response bundle, generated.

Response pack generates from the record: lane-by-lane pricing in the shipper template, carrier liability certs, broker authority, insurance evidence, SCAC verification, references matched to shipper segment, service capability narrative, and the executive summary. The account manager reviews, edits where needed, and sends the pack from Strkr with a tracking link. The one-week scramble shrinks to a two-hour review.

Award tracking

Won, lost, split-award rolled up on the record.

When the shipper awards the RFP, enter the awards per lane and Strkr rolls up the won volume, the lost volume, the split-award volume, the primary versus secondary coverage, and the committed revenue. The RFP record becomes the baseline for the account onboarding, the TMS lane configuration, and the quarterly volume comparison against commitment. Patterns across RFPs surface the lanes the brokerage wins and the lanes it loses on.

Mini RFP motion

Spot RFPs and quarterly re-prices on the same rails.

The same RFP rails handle the mini-RFP motion (a shipper refreshes 20 lanes quarterly) and the spot-RFP motion (a shipper rounds a one-time project up for bid). The brokerage team does not run three parallel processes for annual, quarterly, and spot RFPs; one record shape, one workflow, one set of pricing-committee rules handle all three with a type tag.

Carrier management

The carrier side of the book, treated as first-class.

Freight brokerage is a two-sided business and most CRMs only build for the shipper side. Strkr treats the carrier bench as first-class with carrier records, scorecards, lane coverage maps, insurance tracking, and the capacity planning workflow that keeps the right carrier in the right truck on the right lane at the right time. The brokerage carrier manager runs the bench out of Strkr instead of a spreadsheet, and when the carrier manager is on vacation the bench is still legible to the next person on the desk. 3PLs with asset-based carriers run the same patterns against their own driver roster. Warehousing operators run the same patterns against the drayage carrier and the final-mile carrier bench supporting the facility.

Carrier record

One record holds the whole carrier relationship.

Carrier record holds MC number, DOT number, SCAC, insurance effective and expiry dates, broker authority verification, equipment pool (dry van, reefer, flatbed, step-deck, Conestoga, chassis, drayage, final-mile), driver roster size, dispatcher contacts, dispatcher response time, lane coverage map, scorecard, 30 day paid status, dispute history, factoring arrangement, and the primary brokerage rep. The record is the system of record for the carrier relationship on the brokerage side.

Insurance watch

Expiring insurance surfaces before the load is tendered.

A daily Flow surfaces carriers whose insurance expires in the next 30 days, whose broker authority is unverified, whose SAFER inspection is overdue, or whose SCAC verification is stale. The carrier manager clears the queue daily and the brokerage never tenders a load to a carrier whose insurance lapsed last week. Compliance exposure drops to near zero without a dedicated carrier-compliance headcount.

Capacity signals

Which carriers have capacity on which lanes this week.

Carriers submit weekly capacity through a Strkr intake form (next 7 days capacity by lane and equipment type) or through an API push from their dispatch system. The intake rolls up on the capacity view by lane and equipment, so the brokerage rep sourcing a Fresno-to-Dallas reefer out at 2 PM sees the top 10 carriers with signalled capacity in the window. The carrier call takes 30 seconds, not 20 minutes of cold calls.

Scorecard calibration

The scorecard that reflects what the brokerage cares about.

The default scorecard (on-time pickup, on-time delivery, claim rate, tender acceptance, dispatcher response time) covers the brokerage case out of the box. Custom scorecards per shipper segment (temperature-controlled, HAZMAT, drayage, oversized) weight the metrics the segment cares about. The pricing analyst matching a reefer shipper filters on the reefer-weighted scorecard and sees the right carriers at the top.

Carrier development

The onboarding pipeline for new carriers.

A separate pipeline tracks carrier onboarding (Prospect, Packet Issued, Insurance Received, Broker Authority Verified, SAFER Clear, Approved, Active). Flows automate the insurance verification, the SAFER inspection pull, the W-9 collection, and the mutual non-disclosure. The carrier manager grows the bench without the week-long paperwork drag that most brokerages carry.

Dispute track

Claims, OS&D, and detention on the record.

When a load generates a dispute (damage claim, OS&D, detention, chargeback), the dispute lives on the carrier record with the shipper reference, the load reference from the TMS, the amount in dispute, the resolution status, and the aging. The carrier manager sees the pattern of claim-heavy carriers before the next tender and the shipper account manager sees the pattern of claim-heavy shippers before the next margin re-negotiation.

Payments and factoring

Quick-pay, factoring, standard-term tracked on the record.

Carrier record carries the preferred payment arrangement: quick-pay percentage, factoring company, factoring release approval, standard net terms. AP pulls the record when cutting the check and the brokerage never factors a load twice or releases to the wrong factoring company. Carrier payment disputes resolve from the record instead of a three-way phone call with AP and the factoring company.

Flows for the 3PL motion

Automations that cover the full logistics day.

The best 3PLs are not the ones that grind the longest; they are the ones that automate the quiet administrative drag and spend the day on judgment calls that actually move margin. Strkr Flows handle the dozen automations every 3PL should run, and each one ships as a native trigger with no webhook plumbing or glue code. The patterns below show up in week two of every deployment, and they compound into a cleaner shipper book, a cleaner carrier bench, a faster quote-to-signed window, and less dropped followup on the shippers at renewal risk.

New shipper lead

Website lead becomes a qualified shipper record.

A shipper form submission on the website lands in Strkr with the mode mix, estimated monthly volume, current spend, incumbent brokerage, and pain narrative captured. The Flow checks volume thresholds, enriches with FreightWaves or a similar provider for shipper credit and legitimacy, assigns to the right rep by territory and mode, and schedules the discovery call within the SLA window. The brokerage rep walks into the discovery call with a prepared shipper summary instead of a cold form submission.

Quote accepted

Verbal yes fires MSA and provisioning.

The brokerage rep moves the stage to Quote Accepted and the Flow drafts the MSA in DocuSign or PandaDoc with the shipper terms, pricing, and liability framework pulled from the shipper record. Legal review task fires in parallel. Carrier liability certs, broker authority, and insurance evidence attach from the record. Once signed, the shipper flips to Onboarded, the TMS record provisions, and the account team pulls into the kickoff thread.

Shipper churn signal

Volume slip triggers an account-manager review.

A weekly Flow computes shipper volume versus trailing-12 average. Shippers whose volume dropped more than the per-tier threshold (25 percent for strategic, 40 percent for commercial, 50 percent for transactional) land on the account-manager review view with the trend chart, the recent-load mix, the carrier mix, and the last-touch date. The account manager calls the three shippers at risk this week instead of staring at a 400-shipper book and hoping.

Renewal window

MSA renewal inside 90 days hits the account manager queue.

Flows read the MSA renewal date and surface shippers inside the 90, 60, and 30 day windows. The 90 day touch fires an executive-sponsor check-in task. The 60 day touch fires a QBR task with the account summary pack. The 30 day touch fires the renewal pricing request to the pricing committee. The brokerage does not lose shippers because the MSA quietly expired on an unmanned calendar.

Insurance expiry

Carrier insurance lapse pulls the carrier out of load matching.

A daily Flow pulls carrier insurance effective-and-expiry dates. Carriers whose insurance expires in 30 days get a notice task to the carrier manager with the carrier contact prepopulated. Carriers whose insurance expired get flagged as ineligible for new tenders in the TMS via the integration, so the brokerage never tenders a load to a carrier whose insurance lapsed last week. Compliance exposure drops without a compliance-manager headcount.

OS&D and claim

A claim fires the resolution workflow.

A damage claim or OS&D event logged on the load lands on the shipper record and the carrier record with the dispute amount, the incident date, and the required documentation. The Flow fires the resolution tasks to the claims specialist, the carrier manager, and the shipper account manager with the SLA clock on. Claims resolve in days instead of weeks and the aging report is on the record instead of in a claims-specialist spreadsheet.

RFP calendar

Shipper RFP cycle date fires the pre-RFP workstream.

Each shipper record carries the expected annual RFP cycle date (October through November for the 2024 planning cycle, for example). 90 days before the expected cycle a Flow fires the pre-RFP workstream: refresh the account summary, pull the trailing-12 lane data, request current carrier bench health per lane, and schedule the pre-RFP executive touch. The brokerage walks into the shipper RFP as the incumbent with the current data, not as the vendor who shows up when the lane sheet lands.

Multi-mode and the service portfolio

For 3PLs that sell more than one mode out of the same account.

Most mid-market shippers want a 3PL that handles more than one mode. The brokerage selling 30 van loads a week is also the one the shipper asks about reefer, drayage, warehousing, final-mile, and the oversized flatbed. The CRM that only tracks one mode fragments the relationship across three systems and the brokerage misses the full-service portfolio pitch. Strkr handles multi-mode and multi-service shippers natively, with mode-specific product lines, mode-specific pricing, mode-specific carrier benches, and a consolidated shipper record so the account manager pitches the full portfolio from one surface and sees the full revenue picture across modes.

Mode-specific products

Van, reefer, flatbed, drayage, intermodal, air, warehousing on one shipper.

The product catalog ships with the standard logistics modes: full truckload (van, reefer, flatbed, step-deck, Conestoga), LTL, intermodal, drayage, ocean (FCL, LCL), air freight (domestic, international), expedited, white-glove final-mile, warehousing (per pallet position, per SKU, per activity), VAS (pick, pack, label, kit, FBA prep). Products carry mode-specific pricing primitives (per mile, per load, per CWT, per pallet, per activity) so the quote reflects the real mode without wedging it into a one-size SKU.

Mode-specific carrier

Carrier bench filters by mode and equipment.

Carriers list the modes and equipment types they cover. A reefer-shipper quote filters the bench to reefer carriers only. A drayage quote filters to drayage carriers with the right port approval. A final-mile quote filters to white-glove-capable carriers. The pricing analyst matches the right bench to the right mode without the manual mental filter the brokerage used to run through.

Mode-specific scorecard

Weighted scorecards per mode and segment.

The default scorecard works for the brokerage general case. Mode-specific scorecards weight the metrics the mode cares about: reefer weights temperature-compliance, drayage weights port-dwell-time, final-mile weights appointment compliance and consumer-reported damage. The pricing analyst filters the bench on the right scorecard for the right mode and the right carrier floats to the top for the right quote.

Warehouse and 3PL fulfillment

Pallet positions, SKU-level fit, activity-based pricing.

For 3PLs with a fulfillment arm, the shipper record carries pallet positions in use, SKU count, SKU velocity distribution, inbound receipt method, outbound ship method, VAS requirements, dock scheduling policy, EDI setup, and the WMS billing primitives. The warehouse account manager runs the same account the brokerage account manager runs and the shipper sees one 3PL instead of three vendors.

Portfolio quote

One quote covers the full service portfolio.

A portfolio quote covers van freight plus reefer plus warehousing plus VAS on one document with the pricing anchored on the mode-specific primitives. The shipper sees the all-in picture, the brokerage captures the cross-mode margin profile, and the quote does not splinter into three documents the shipper negotiates in isolation.

Cross-mode QBR

QBR pack carries the full-portfolio revenue picture.

The quarterly business review pack generates from the shipper record with the mode-mix revenue, trailing-12 trend per mode, service failures per mode, carrier mix per mode, warehouse utilization, VAS volume, and the cross-sell opportunity sized per mode. The account manager walks into the QBR with the full picture instead of pulling three dashboards from three systems the night before.

TMS and WMS bridge

Two-way sync with the systems of record.

Strkr integrates with McLeod, Mercury Gate, MercuryGate TMS, Turvo, Revenova, Project44, FourKites, SAP TM, Oracle OTM, Blue Yonder, Manhattan Associates, Highjump, Softeon, 3PL Central, and most modern TMS and WMS stacks. The TMS stays the system of record for the load. The WMS stays the system of record for the inventory. Strkr stays the system of record for the relationship, the pricing judgment, and the pipeline.

What the brokerage director sees

Views that make the Monday pipeline review fast.

A good brokerage director coaches on three specific accounts a week, not on all 400 in the book. Strkr surfaces the data the director needs to run a short, specific pipeline review without the rep feeling surveilled, because the same views are available to the rep and the director with the same filters. The views below ship as default saved views for the brokerage-director role on every tenant and can be duplicated and personalised without an admin ticket.

Rep roll

Each brokerage rep on one row with pipeline, won, at risk.

The Monday pipeline view puts every rep on one row with their active pipeline, won-this-month, at-risk shippers, open RFPs, and quota attainment. The director sees the full roll in one scroll and drills into the specific accounts behind any cell. Reviewing 15 reps takes 10 minutes, not an hour.

Top shippers

Top 20 by projected ARR with next-touch date.

A top-shippers view sorts by projected annualized revenue with next-touch date, last-touch date, and churn-risk score as columns. The director spots the biggest shipper with the stalest cadence in seconds and coaches that one, instead of asking the rep to walk through all 20 in the 1:1.

At-risk map

Shippers whose volume slipped this month.

The at-risk saved view surfaces every shipper whose volume dropped more than the per-tier threshold with the trend chart, the recent-load mix, the carrier mix, and the last-touch date. One click to assign a save task, one click to escalate, one click to clear the flag. The thresholds are tunable per tier so strategic, commercial, and transactional accounts calibrate against the right pattern.

RFP map

Live RFPs across the book with pricing-committee status.

A live-RFPs view shows every open RFP with the shipper, the lane count, the response-due date, the pricing-committee status, and the margin cover forecast. The director sees the two RFPs where the response is tomorrow and the margin cover is thin before the Monday fire drill starts.

Carrier health

Insurance, authority, SAFER status on one view.

A carrier-compliance view surfaces every carrier whose insurance expires in 30 days, whose broker authority is unverified, whose SAFER inspection is overdue, or whose SCAC verification is stale. The carrier manager clears the queue daily and the compliance exposure stays at near zero.

Lane margin

Lanes whose margin cover slipped this quarter.

A margin-erosion view surfaces lanes whose average margin cover slipped more than the per-tier threshold versus the trailing-12. The pricing analyst sees the pattern of margin erosion before the quarterly CFO review and the brokerage team either re-prices the lane, swaps the carrier mix, or walks the shipper from the lane with a documented pricing judgment.

Head-to-head

Strkr for 3PL vs TMS add-on plus Salesforce plus spreadsheets.

A typical mid-market 3PL stack runs a TMS (McLeod, MercuryGate, Turvo, Revenova) for the load side, Salesforce or a TMS-bundled CRM for the shipper side, a shared drive of carrier insurance PDFs, an Excel pricing analyst workbook, a DocuSign subscription for contracts, and a Slack channel for RFP response coordination. Strkr collapses the relationship side of that stack into one workspace with one bill, one admin surface, and one record of truth for every shipper and carrier. The TMS stays. The WMS stays. The glue goes away.

Feature Strkr TMS add-on + Salesforce + spreadsheets
Number of tools account manager opens daily 1 (Strkr) + TMS for load ops 4 to 7
Shipper record shape Native with mode-mix, RFP cycle, pricing judgment, churn signals TMS freight record, or Salesforce bent into a shipper shape
Carrier scorecard Native with lane-and-equipment filter and insurance watch Spreadsheet owned by the senior carrier manager
RFP response workstream Native with lane parsing, carrier match, pricing panel, response pack Three Excel files and a midnight pricing meeting
Pricing committee Native approval flow with reason codes and audit trail Email thread and a verbal pricing-director sign-off
Insurance and authority watch Daily Flow pulls expiry, flags ineligible carriers in TMS Carrier manager chases the shared drive quarterly
Shipper churn signals Weekly Flow computes volume slip and surfaces at-risk accounts Quarterly report reveals the churn after it is final
Multi-mode Van, reefer, flatbed, drayage, intermodal, air, warehouse, VAS native Single-mode CRM, warehouse billed from a separate WMS
TMS and WMS integration Two-way sync with McLeod, MercuryGate, Turvo, 3PL Central, and more CSV export and a manual match once a week
Contracts and MSA DocuSign and PandaDoc native, stage auto-advances on signature DocuSign separate, manual stage update, no audit on the record
Admin changes Self-serve for brokerage director and RevOps, in-app 2-week Salesforce admin review queue
Mobile for the yard and warehouse floor First-class with offline queue and voice notes Thin wrapper over web, no offline
How teams use Strkr

How logistics teams run Strkr.

The patterns below show up across brokerages, asset-light 3PLs, asset-based carriers, warehousing operators, and multi-mode logistics firms. The common thread: collapse the shipper, the carrier, the RFP, the pricing judgment, and the warehouse account into one surface so the account manager spends time on relationships and judgment instead of stitching the picture back together across six systems. Each playbook is a real motion a logistics operator runs today, not a hypothetical configuration from a demo script.

25-rep freight brokerage

Shipper pipeline with RFP flows and carrier scorecards.

A 25-rep freight brokerage running van, reefer, and flatbed across the lower 48 moved off a TMS-bundled CRM plus Salesforce. The shipper pipeline flipped onto Strkr with mode-mix and RFP cycle tracking. RFP flows parsed shipper lane sheets, auto-matched to the carrier bench, and generated response packs. Carrier scorecards replaced the senior carrier manager spreadsheet and the bench stayed legible when the senior manager took a two-week vacation. Quote-to-signed window dropped from 32 days to 7, and the brokerage director reports 11 hours a week back across the team.

3PL with warehousing arm

Multi-mode portfolio quote and cross-sell to brokerage shippers.

A 3PL with a brokerage arm and a 180,000-square-foot warehousing arm runs both lines of business on one Strkr tenant. The brokerage team sees the warehousing opportunity on existing shipper records and the warehousing team sees the brokerage freight on new warehouse prospects. Portfolio quotes bundle freight plus warehousing plus VAS on one document. Cross-sell revenue grew 23 percent in two quarters because the account manager finally saw the full-portfolio picture on one surface.

Asset-based carrier

Driver roster plus shipper pipeline on one tenant.

A 60-truck asset-based carrier running regional dry van and refrigerated runs the shipper pipeline, the driver roster, the equipment maintenance calendar, and the owner-operator onboarding pipeline on Strkr. The dispatcher sees shipper preferences on the load match. The owner-operator onboarding Flow handles the W-9, insurance, drug screen, and road-test tracking without the paperwork drag. Driver retention improved and the shipper book doubled over 18 months.

Warehousing specialist

Pallet-position accounts with activity-based pricing.

A warehousing specialist with three facilities (240,000 pallet positions total) runs shipper acquisition on Strkr with pallet-position records, SKU-level fit scoring, dock-door assignment, VAS pricing, and WMS billing primitives on the shipper record. The sales team pitches the fit between the shipper SKU catalog and the facility network with a repeatable scoring model instead of ad-hoc guesswork. Facility utilization rose from 71 percent to 89 percent across the three sites in a year.

Multi-mode mid-market 3PL

Shipper acquisition across van, reefer, drayage, air, warehousing.

A mid-market 3PL with 85 operators across six branches runs the shipper acquisition motion across all modes on Strkr. The RFP workflow handles 300-lane annual RFPs with pricing-committee sign-off and margin-cover reports. Churn signals surface shippers at renewal risk 90 days ahead. Insurance watch flags carrier compliance exposure daily. The brokerage director reports the Monday pipeline review dropped from 90 minutes to 25 minutes across the six branches, and net revenue retention improved by 8 points year over year.

See the CRM 3PLs actually run their book out of.

Start a 14-day trial with the full logistics stack enabled: shipper pipeline, carrier scorecards, RFP response flows, pricing-committee workflow, insurance watch, churn signals, multi-mode products, portfolio quotes, DocuSign and PandaDoc contracts, and TMS and WMS two-way integrations. One bill, one workspace, one record of truth across brokerage and warehousing. The pricing page lays out the per-seat line in full so there is no mystery before the trial starts, and the features index shows the surfaces in detail if that is the piece you want to pressure-test first.

See pricing Explore features
Common questions

What buyers in this bucket ask most.

Can Strkr replace our existing TMS?

No, and it does not try to. The TMS (McLeod, MercuryGate, Turvo, Revenova, SAP TM, Oracle OTM) is the system of record for the load: dispatch, tendering, tracking, invoicing, driver settlement, EDI, carrier payments. Strkr sits on top of the TMS with a two-way integration and holds the shipper relationship, the carrier scorecard, the RFP workstream, the pricing judgment, the pipeline, and the renewal risk. The TMS stays. The CRM comes to Strkr. The two systems stay in two-way sync so the shipper record sees the recent load activity and the TMS sees the shipper and carrier records Strkr owns.

How does the RFP response workflow work for a 200-lane shipper RFP?

Upload the shipper RFP template (CSV, Excel, PDF with tables, Project44 export, SMC3 export) and Strkr parses the lane sheet into structured records with origin region, destination region, equipment type, volume commitment, special handling, pickup and delivery windows, and accessorials. Each lane row auto-matches to the top 10 carriers from the carrier bench based on lane coverage, equipment type, scorecard rating, and recent capacity signals. The pricing analyst reviews the match, bumps or drops carriers per lane, approves non-standard pricing through the committee flow, and generates the response pack. The one-week scramble shrinks to a two-hour review for the account manager plus the committee sign-off window.

How does the carrier scorecard handle multi-mode carriers?

Each carrier record carries the modes and equipment types they cover (dry van, reefer, flatbed, step-deck, Conestoga, drayage, chassis, final-mile, white-glove). The default scorecard (on-time pickup, on-time delivery, claim rate, tender acceptance, dispatcher response time) covers the general case. Mode-specific scorecards weight the metrics each mode cares about: reefer weights temperature-compliance, drayage weights port-dwell-time, final-mile weights appointment compliance and consumer-reported damage. The pricing analyst filters the bench on the right scorecard for the right mode and the right carrier floats to the top. Lane-coverage maps per carrier let the brokerage filter the bench to the carriers that actually run the lane the shipper is asking about.

Does Strkr handle warehousing and fulfillment accounts alongside freight brokerage?

Yes. For 3PLs with a warehousing or fulfillment arm, the shipper record carries pallet positions in use, SKU count, SKU velocity distribution, inbound receipt method, outbound ship method, VAS requirements, dock scheduling policy, EDI setup, and the WMS billing primitives. Portfolio quotes bundle freight plus warehousing plus VAS on one document. The account manager pitches the full service portfolio from one surface and the cross-sell between brokerage and warehousing stops fragmenting across two systems. Strkr integrates with 3PL Central, Softeon, Highjump, Manhattan Associates, Blue Yonder, and most modern WMS stacks.

How does the shipper churn signal work?

A weekly Flow computes shipper volume versus the trailing-12 average and tier-specific thresholds (default: 25 percent slip for strategic, 40 percent for commercial, 50 percent for transactional). Shippers whose volume dropped past the threshold land on the account-manager review view with the trend chart, the recent-load mix, the carrier mix, the service-failure count, and the last-touch date. The account manager calls the three shippers at risk this week instead of staring at a 400-shipper book and hoping. Patterns across the book inform the brokerage director coaching: are losses concentrated by mode, by lane, by rep, by carrier mix, or by service-failure pattern.

What TMS and WMS integrations ship native?

Native two-way integrations ship for McLeod LoadMaster, MercuryGate, Turvo, Revenova, SAP TM, Oracle Transportation Management, Blue Yonder TMS and WMS, Manhattan Associates TMS and WMS, Highjump, Softeon, 3PL Central (Extensiv), and the common visibility platforms (Project44, FourKites, Trucker Tools, MacroPoint). The integration pattern pulls recent and active loads onto the shipper record, pushes shipper and carrier record updates back to the TMS, and keeps the two systems in two-way sync without a webhook plumbing project. Custom integrations with regional TMS stacks ship through the Strkr REST API without a Strkr-side engineering ticket.

How does Strkr handle insurance and broker-authority compliance?

Carrier records hold insurance effective and expiry dates, broker authority verification date, SAFER inspection status, SCAC verification, and the W-9 on file. A daily Flow surfaces carriers whose insurance expires in 30 days, whose broker authority is unverified, whose SAFER inspection is overdue, or whose SCAC verification is stale. Carriers whose insurance expired flag as ineligible for new tenders in the TMS via the integration. The carrier manager clears the compliance queue daily and the brokerage never tenders a load to a carrier whose insurance lapsed last week. Compliance exposure drops to near zero without a dedicated carrier-compliance headcount.

Can brokerage directors and RevOps make admin changes without a two-week queue?

Yes, within the permission matrix. Custom fields, Layouts, saved views, pipeline stages, stage entry criteria, Flows, scorecard definitions, and dashboard widgets are self-serve for the role the admin has granted the permission to. Most 3PLs give the brokerage director full self-serve on their own pipeline and saved views, and route tenant-wide changes (new object, cross-tenant automation, data model migrations) through RevOps or the admin role. The change ships the hour it is needed, with an audit trail on who changed what, so the quarterly release freeze that Salesforce admins impose on the brokerage team does not exist.

Also built for

Related audiences.

For Manufacturing For Ecommerce For Construction For Professional Services For Mid-Market For Enterprise

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing