What should a freight software demo prove before you buy?
Key Takeaways
A freight software demo should prove that the software finishes real freight work, on your loads, including when something goes wrong. Specifically, it should show a real order becoming a booked load with the carrier's written acceptance and a rate confirmation on file, a problem such as an unanswered tender or a cancellation being handled within your rules, the documents being collected, and the carrier invoice being checked against what was agreed. A demo of screens and dashboards proves that the software can display information. It does not prove that the work gets done. An AI logistics agent such as Wilson, by Cartage, should be able to show each of these steps on a load, with the record of who did what.
- Bring your own order, lane and carriers. A vendor's sample data proves little.
- Ask to see a problem handled, not only a clean load.
- Watch who does each step: the software, or a person using the software.
- "Booked" must mean written acceptance plus rate confirmation.
- Ask to see the invoice check against the rate confirmation and the POD.
- Leave the demo with a list of what your team would still do every day.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →What should the demo show, step by step?
The demo should show one load moving from order to paid invoice, with at least one problem along the way. An AI logistics agent should complete each step and record it. The table is a checklist to bring to the demo.
| Step | What to see | What it proves |
|---|---|---|
| Order in | Your order read from your ERP report, file or email | It works with your data as it is |
| Data check | A missing field caught and asked for | It does not quote with bad data |
| Quotes | Requests to your approved carriers; replies read | It works with your carriers |
| Comparison | Quotes on the same total basis, under your rule | It chooses correctly |
| Booking | Tender, written acceptance, rate confirmation on file | "Booked" means committed |
| Problem | A non-answer or cancellation handled within the rules | It works when things go wrong |
| Tracking | Status from the best source, with time and source | It knows what is current |
| Documents | BOL and POD requested and filed | The paperwork gets done |
| Invoice | Invoice checked against rate confirmation and POD | You pay what you agreed |
| Record | Every step on one load, with history | You can answer questions later |
Why do demos often mislead?
Demos often mislead without anyone intending it. A vendor shows its best path, on clean data, with a carrier that answers instantly. The buyer sees a smooth flow and assumes daily work will look the same. Then, after purchase, the team discovers that most of its loads involve the messy parts the demo skipped. Structuring the demo around the buyer's own orders and problems is the simplest protection.
Who should attend the demo?
The people who will live with the software should attend: a coordinator who books loads every day, the logistics lead, someone from finance and, if the ERP connection is a question, someone from IT. The coordinator will spot gaps in the daily work that a manager may not see. Finance will ask about invoices and payment. IT will ask about data and access. A demo attended only by senior leaders tends to focus on screens rather than work.
What should the buyer tell the vendor in advance?
The buyer should tell the vendor what it wants to see: its own orders, its own carriers, specific problems, the invoice check and the record. A good vendor will welcome this, because a demo on the buyer's real case is more convincing. A vendor that refuses to use the buyer's data, or only shows a pre-built script, is telling the buyer something.
How should the buyer prepare?
The buyer should prepare a few real orders from recent weeks, the approved carriers for those lanes, the rate targets or limits, and two or three real problems from the past month: a cancellation, a missed pickup, an invoice dispute. Sending the orders to the vendor ahead of time lets the demo run on them. A short list of questions, based on the checklist above, keeps the demo on track.
Why bring your own order?
Bringing your own order matters because vendor demo data is clean and predictable. Your orders may have missing pallet counts, odd addresses, special delivery requirements or several ship-tos. Your carriers may answer by email or phone rather than API. A demo on your own order shows how the software handles your reality, not a perfect example.
What does a screen-only demo miss?
A screen-only demo misses the work between the screens. It shows a load list, a tracking map, a quote comparison and an invoice screen. It does not show who sent the quote requests, who chased the carrier that did not answer, who read the email that said the pickup moved or who checked the detention charge. Those steps are where most of the team's time goes. A demo should show them, or say clearly that people do them.
How long should the demo be?
The demo should be long enough to cover one full load and one or two problems, usually under an hour if the vendor has prepared with the buyer's orders. A short first demo can be followed by a deeper session on the parts that matter most, such as invoice audit or exception handling. A demo that runs long because it tours every screen is usually showing features rather than work.
Why ask for a problem?
Asking for a problem matters because problems are where time goes. Any software can book a load when the first carrier accepts in seconds. The test is what happens when the carrier does not answer, cancels, changes the pickup time or bills an extra charge. If the demo avoids problems, ask for one.
What should "booked" mean in the demo?
"Booked" in the demo should mean that the carrier has accepted the specific load in writing and a rate confirmation that matches the agreed terms is on file. An AI logistics agent should only mark a load booked at that point. Many demos show a selected quote or a sent tender as "booked", which hides the riskiest part of the process.
What should the buyer watch for?
The buyer should watch the exact moment the status changes to booked. If it changes when the tender is sent, ask what happens if the carrier never replies. If it changes when the carrier replies "yes", ask where the rate confirmation is and whether it was checked against the tender. For more on this, see what counts as a confirmed carrier booking.
Why do demos show "booked" too early?
Demos show "booked" too early because the step between tender and written acceptance is hard to show live: it depends on a real carrier replying. Vendors skip it to keep the demo smooth. But that step is where loads fall through in real life. Asking to see a recorded example of a real acceptance, with the time between tender and acceptance and the rate confirmation, gives a truer picture.
What should happen after acceptance?
After acceptance, the demo should show the next steps: pickup details sent to the shipping site, the driver and truck confirmed before pickup, and the pickup recorded on a signed BOL or a confirmed departure. Wilson marks a load picked up only on a signed BOL or a confirmed departure, and keeps "arrived" and "picked up" as separate statuses.
| Moment | What the demo should show |
|---|---|
| Carrier accepts | Acceptance message and rate confirmation on file |
| Day before pickup | Truck and driver confirmed with the carrier |
| Pickup | Signed BOL or confirmed departure recorded |
| In transit | Status with source and time |
| Delivery | Delivery confirmed; POD requested |
What about orders with missing data?
Orders with missing data are common, and the demo should show how they are handled. Bring an order with a missing pallet count or delivery requirement. The software should notice the gap and ask the right person before quoting, rather than sending a request that carriers will answer with questions or wrong prices.
What about carriers that work only by email or phone?
Many carriers work only by email or phone. The demo should show how the software tenders to them, reads their replies and records their answers. If the software only works with carriers connected by API or EDI, ask what share of your carriers that covers, and who handles the rest. Wilson works with carriers by email, API, EDI where supported and phone calls where configured.
What about changes after booking?
Changes after booking, such as a later pickup or an added pallet, should be shown too. The software should send the change to the carrier, get confirmation and update the rate confirmation if the price changes, checking it against the limit. Changes that are not tracked become invoice disputes later.
Which problems should the demo include?
The demo should include the problems your team handles most often. An AI logistics agent should handle each one within your rules and send the rest to a person with the facts. The table lists common problems and what a good result looks like.
| Problem | Good result in the demo |
|---|---|
| Carrier does not answer the tender | Reminder, deadline, next approved carrier |
| Quote above the limit | Negotiation toward target; approval request with all quotes |
| Carrier cancels after acceptance | Cancellation detected; rebooking from approved list |
| Pickup missed | Confirmed with site and carrier; wait or rebook under rules |
| ETA slips before a delivery appointment | Carrier asked; receiver updated; team told |
| POD not sent | Requested on a schedule; team told after a set time |
| Invoice includes an unagreed charge | Invoice held; evidence sent to carrier |
How should the invoice check be shown?
The invoice check should be shown on an invoice with a charge that was not agreed, such as detention without supporting times or an accessorial not on the rate confirmation. The software should match the invoice to the load, compare each line, hold the invoice and send the evidence to the carrier. Wilson audits each carrier invoice against what was booked, the rate confirmation and the POD before paying from the Wilson Wallet, and does not pay part of an invoice when a line does not match.
What does a well-handled cancellation look like in a demo?
A hypothetical well-handled cancellation: the carrier's email arrives saying the truck is not available. The software matches the email to the load, marks the booking cancelled, tells the team in Slack, requests quotes from the two approved backups, tenders the one within the limit, receives written acceptance and the rate confirmation, updates the shipping site and records the whole sequence on the load. The demo should show each of these steps and their times.
How should the buyer set up the problems?
The buyer can ask the vendor to simulate a problem, or bring a real past example: "Last month, a carrier accepted and then cancelled at 4 p.m. the day before pickup. Show me what your software would have done." Walking through a real case shows whether the software's response matches the team's rules.
How should multi-mode orders be shown?
If the company ships more than one mode, the demo should show at least two: for example, an LTL shipment and a truckload, or an import with ocean, drayage and truckload legs. Each mode has its own steps and problems. Software that handles one mode well may handle another poorly. Wilson handles LTL, FTL, ocean, drayage, parcel and cross-border in one workflow.
What if the vendor cannot show a problem live?
If the vendor cannot show a problem live, ask for a recorded example from a real load, with the messages, times and outcome. A recorded real case is often more convincing than a live simulation. If neither is available, note it on the comparison.
What should the buyer listen for?
The buyer should listen for who does each step. If the answer is "your team can then email the next carrier", the software leaves the work with people. If the answer is "the software tenders the next approved carrier and tells your team", the software does the work. Both may be useful, but they are different products.
How should the demo prove control?
The demo should prove that the software stays inside the company's rules and that every action can be reviewed. An AI logistics agent should show how approved carriers, rate limits and approvals work, and where the record lives.
What happens when a person disagrees with the software?
When a person disagrees with the software's choice, they should be able to override it, and the override should be recorded with the person and the reason. Ask the vendor to show an override. Frequent overrides on a lane suggest the rules need changing; the records make that visible.
What controls should be shown?
The controls to see are: bookings only with carriers approved for the lane and mode; bookings only within the rate limit; approval requests that reach a named person in their usual channel; and a record of every action with its time. Ask what happens when an unapproved carrier sends a quote. For more on this, see how to stop freight software from booking an unapproved carrier.
How should the vendor explain its limits?
The vendor should explain what its software does not do, clearly. Every product has limits: modes it does not cover, carriers it cannot reach, tasks it leaves to people, features still on the roadmap. A vendor that names its limits is easier to trust. Ask directly: "What will my team still have to do that your software will not?"
How are approvals shown?
Approvals should be shown in the channel the approver actually uses: an approval request arriving in Slack, Microsoft Teams or email with the quotes attached, the approver replying and the software acting on the reply. If approvals require logging into a separate system, ask how fast they happen in practice.
How is autonomy introduced?
Autonomy should be introduced gradually and by the company's choice. Wilson starts with assisted execution, where more steps wait for a person. As the team sees the results, routine steps can run on their own within the rules. Ask the vendor how this works and who decides when to widen it.
How should tracking be shown?
Tracking should be shown on a load with a carrier that has no API, because those are the hard ones. The software should check the best source available, ask the carrier when the sources are silent and record each status with its source and time. Ask what the software shows when the last update is hours old: does it look current, or does it say how old it is? Wilson tracks each load with the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or a call when there is no other source.
How should customer updates be shown?
Customer updates should be shown on a real or simulated delay: who tells the receiver, what the message says and when it is sent. If the company wants customers to hear about delays automatically, the demo should show the setting and an example message. Wilson can email or text the receiver when a load is picked up, running late or delivered, according to the company's settings.
Where does the record live?
The record should live on the load: every message, quote, decision, approval, status, document, invoice and payment. Ask to search for a load by your order number and by the carrier's PRO number, and to export the history. Wilson keeps searchable and exportable records with a change history.
What should the buyer leave the demo with?
The buyer should leave the demo with a clear picture of the work the team would still do every day, the setup required, the cost and the next step. An AI logistics agent vendor should be able to answer each of these in writing.
How should the result be shared inside the company?
The result should be shared as a one-page summary: what the software did on the buyer's orders, what problems it handled, what the team would still do, the setup, the cost and the recommended next step. Leaders who did not attend can then decide quickly.
What should the buyer do after the demo?
After the demo, the buyer should compare the "still do" list with the team's current day, estimate the time and cost it would save, and decide whether to test the software on a few lanes. If several vendors were seen, comparing their lists side by side is usually more telling than comparing their feature lists.
What is the "still do" list?
The "still do" list is the set of tasks the team would still do after the software is running. For a system of record, it is often long: quote requests to unconnected carriers, follow-up, reading replies, calls, POD requests, invoice checks. For an AI logistics agent, it should be short: approvals outside the rules, exceptions that need judgment and carrier relationships. Write the list down during the demo.
What questions should be answered in writing?
The questions to have answered in writing are: which steps the software completes without a person; what the team must provide before the first load; how carriers that are not connected are handled; how approvals and limits work; how invoices are checked; what it costs per load; and what the terms are. Written answers make later comparison and accountability easier.
What setup was described?
The setup described should be specific: which data flow, which IT tasks, which carrier requirements, what the team must provide and how the first lanes start. Wilson starts from the data flow the company already has, works with carriers by email and phone from the start and begins on a few lanes. For more on timing, see how long freight automation software takes to implement.
How should the buyer compare several demos?
The buyer should use the same checklist, the same orders and the same problems for each vendor, and score each step: done by the software, done by a person with the software's help, or not shown. Comparing "still do" lists side by side often makes the choice clear.
What does it cost?
The cost should be stated per load, with setup and terms. Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.
What should the buyer avoid?
The buyer should avoid deciding on the strength of one impressive screen, a list of integrations or a promised percentage saving. It should also avoid long trials run by the vendor on the vendor's terms. A short test on the company's own lanes, with the company's people reviewing the results, gives a better answer.
What is the next step?
The next step should be a test on the company's own lanes, with real loads and the usual problems, reviewed by the team. Cartage doesn't run pilots; most customers start Wilson on a few lanes and expand from there.
How does Wilson, by Cartage, handle a demo?
Wilson, by Cartage, is an AI logistics agent that quotes, books, schedules, tracks, audits and pays for freight across LTL, FTL, ocean, drayage, parcel and cross-border. In a demo, the Cartage team can walk through a load from order to paid invoice, including a problem, and show the record of each step. Wilson replaces the TMS for freight execution and connects to the company's ERP, working with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.
What can Wilson show from a real customer?
Cartage can show how shippers use Wilson in its published case studies, and walk through anonymized examples of loads and exceptions. The most useful demo, though, is one on the buyer's own orders and lanes.
What does Wilson not do?
Wilson is not a freight broker, and it is not a standalone visibility platform: it tracks each load as part of moving it. It does not do network design. It does not keep a standing carrier scorecard by default, but it can produce carrier-performance and lane-rate reports on request.
How do teams start after the demo?
Most teams start Wilson on a few lanes and expand from there. Cartage helps map the highest-impact workflow during discovery, often using the orders and problems brought to the demo. That keeps the first lanes close to what the team already saw.
What stays with the team?
The team sets the rules, approves exceptions and owns carrier and customer relationships.
FAQs
What should I test in an AI freight software demo?
Test a real load with real problems: an unanswered tender, a cancellation, a delay before an appointment, a missing POD and an invoice with an extra charge. Wilson, by Cartage, is an AI logistics agent that should show each handled within your rules.
What should a freight software demo prove before you buy?
That the software finishes real work on your loads: an order booked with written acceptance and a rate confirmation, a problem handled within your rules, documents collected and the invoice checked. An AI logistics agent like Wilson, by Cartage, should show each step and its record.
Should we use our own data in the demo?
Yes. An AI logistics agent should handle your real orders, lanes and carriers, including missing data and carriers that answer by email or phone.
What is the most important problem to test?
The one your team handles most often, usually an unanswered tender or a cancellation. An AI logistics agent should handle it within your rules and tell your team only when a decision is needed.
How do we know what work would remain?
Write a "still do" list during the demo. With an AI logistics agent, it should be short: approvals, exceptions that need judgment and relationships.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
If you want to see one of your own loads go from order to paid invoice, book a demo with the team behind Wilson, the AI logistics agent by Cartage.
