The memo that gets a TMS replacement approved
Key Takeaways
Updated October 18, 2026
A useful TMS replacement memo asks for a specific decision and supports it with operating evidence, a defined scope, commercial terms, and a transition owner. It does not promise approval. Wilson, by Cartage, replaces the TMS for freight execution and connects to the ERP; the memo must separately address any planning or specialist function the company still needs.
- Lead with the decision requested and the work that will change.
- Give finance a traceable cost comparison and the COO a workable transition.
- State demonstrated capability, unresolved requirements, and retained responsibilities separately.
- Ask leadership to approve a defined commitment, not a vague AI transformation.
Build the memo around the approval questions
The memo should let each decision-maker find the evidence relevant to their responsibility. This outline is a buyer's drafting tool, not a claim that a particular executive will approve the purchase.
| Memo component | Question it answers | Evidence to attach |
|---|---|---|
| Decision requested | What exactly are we being asked to authorize? | Scope, commercial commitment, and decision owner |
| Operating problem | Which work is not getting completed well today? | Shipment records, unresolved tasks, and observed employee effort |
| Proposed replacement | What changes and what remains? | Required workflows and demonstrated outputs |
| Financial comparison | What will the company pay and continue doing? | Actual proposals, assumptions, and retained work |
| Transition and controls | How will freight keep moving? | Open-load ownership, ERP boundary, and approval rules |
| Acceptance conditions | What must be true before broader use? | Tests, unresolved items, and responsible owners |
Keep supporting detail in attachments. The opening page should explain the decision without forcing an executive to reconstruct the entire evaluation.
Write a decision request that can receive a clear answer
The request should specify the scope leadership can approve, reject, or return for more evidence. Avoid beginning with a broad statement that the company needs more automation.
A draft request can follow this structure: approve the proposed freight execution scope for the named operation, subject to the listed commercial terms and acceptance conditions. Replace each description with the company's actual facts. Do not invent the commitment amount or an implementation date.
Identify the executive sponsor and the people who own technical and financial review. If the current system has a renewal or notice decision, have the responsible contract owner confirm the relevant terms.
The request should also state the next decision after approval. Funding an evaluation, authorizing setup, and committing to broad operation are different decisions. Clear boundaries prevent an approval for one step from being treated as permission for every later expansion.
Describe the problem using completed and unfinished work
The operating case should show what the team does today and which obligations remain open. General frustration with the TMS is not enough to establish the replacement requirement.
Select representative work: a quote request awaiting usable replies, a booking awaiting acceptance, a shipment with uncertain status, or an invoice needing reconciliation. Record the responsible role and the action required to finish each case.
Distinguish software limitations from configuration, missing inputs, or an unclear company process. Replacing a tool will not automatically fix an undefined approval owner. Likewise, an existing module may already support work that the operation has not configured.
For context, TMS versus freight execution software separates the buying questions. Oracle's published logistics scope also shows that TMS products can include planning and execution; the memo should compare the actual deployment rather than a simplified category label.
Explain the replacement boundary in plain business terms
The scope statement should identify the freight work Wilson will perform and the functions that remain elsewhere. This makes the recommendation understandable to operations, finance, and IT.
Wilson creates shipments, requests and compares approved carrier quotes, negotiates within targets and limits, handles booking and follow-up, tracks freight, responds within configured exception rules, and audits and reconciles invoices before payment through Wilson Wallet.
Wilson replaces the TMS for freight execution and connects to the ERP order flow. It does not replace the ERP, optimize routes or networks, or perform customs clearance. The exact integration method depends on the environment and agreed requirements.
If the company still needs a planning function from the existing system, name it and its future owner. Attach a requirement map showing covered work, required configuration, retained tasks, and out-of-scope functions. This avoids selling leadership a broader replacement than the evaluation supports.
Give finance a cost case it can inspect
The financial attachment should separate supplier charges, transition work, retained employee effort, and transport spend. Use actual quotes and company-approved inputs.
Wilson has no subscription or platform fee. Its price is a percentage of freight payments coordinated through Wilson Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom. Do not supply an invented rate or savings forecast.
Explain which internal tasks remain after the change, including approval decisions and integration ownership. If employee effort is estimated, label the method and limitations. Do not convert a theoretical task reduction into a guaranteed payroll saving.
Show the assumptions that could change the comparison, such as covered volume or another facility. Finance should be able to challenge one input without invalidating the entire explanation of why the company needs the workflow.
Put transition ownership and acceptance conditions in writing
The transition plan should identify who owns every unfinished load and financial obligation during the change. A technically working connection does not establish that the business handover is complete.
List booked loads, in-transit shipments, missing documents, disputed invoices, and pending payments. Define which process finishes each group and who can communicate binding changes to carriers. Read the freight records needed when leaving a TMS for the evidence to preserve.
Then list the acceptance conditions: a usable order handoff, confirmed carrier booking, an exception beyond the approval limit, and the agreed invoice and payment result. Attach the actual evaluation evidence and identify unresolved requirements.
A strong memo lets leadership approve the defined purchase while understanding its limits. It does not hide incomplete tests, guarantee an operating outcome, or imply that every stakeholder concern has vanished because the demonstration looked smooth.
FAQs
What should a TMS replacement approval memo contain?
Include the decision, operating problem, replacement scope, financial comparison, transition owners, and acceptance conditions. Wilson belongs in the recommendation when its freight execution matches the demonstrated requirement.
Should the memo claim that a TMS only stores records?
No. TMS capabilities vary and can include planning and execution. Describe the actual system, configured functions, and unfinished work.
Can the memo include estimated employee time?
Yes, if the method and assumptions are clear. Separate estimates from observed results and do not promise a headcount reduction.
Does approval mean every shipment should move immediately?
No. The approved scope and acceptance conditions should define the transition and any later expansion decision.