Frequently asked
A clear road to your new TMS.
The questions brokers and carriers ask before moving their operation into a custom system.
Foundation TMS
How does Foundation TMS work?
Foundation TMS is a custom transportation management platform with two systems: Foundation Broker for freight brokers and 3PLs, and Foundation Carrier for asset-based carriers. Each is a working core that we customize around your business.
No. Every broker or carrier gets its own fresh install of the system. There is no shared data between systems.
There is no cap. Workflows, statuses, screens, documents, reports, roles and integrations can all be shaped around how you operate.
We can scope a hybrid build that combines broker and carrier workflows in your own install. Tell us about both sides of the business in your consult.
Foundation Broker
Will it fit our brokerage?
Command deck, comms deck and dispatch, carrier sales and coverage, track & trace, carrier management and compliance, carrier pay, carrier audit, customer billing, and reports with sales commissions.
Foundation Broker includes a carrier directory, a compliance center for insurance and safety, and dispatch blocks for carriers that fall out of compliance. A Highway onboarding integration is available, built on request. Exact provider connections depend on your accounts and scope.
Yes. Track & trace flags shipments needing attention, the driver app or an ELD link provides position, and shippers can receive public tracking links.
Carrier invoices are compared to the agreed rate and accessorials, exceptions and missing PODs are flagged, and approved bills move into the carrier pay queue with quick-pay fees and QuickBooks sync.
Yes. Reports break down revenue, carrier cost and margin by customer, carrier and lane, and sales commissions can be calculated from margin.
Foundation Carrier
Will it fit the way our fleet runs?
A working carrier TMS that becomes the starting point for your custom build. Its core includes dispatch, loads, assets, drivers, HOS visibility, customer billing, driver pay, maintenance, fuel and reporting. Your finished system is shaped around your operation—not sold as a fixed feature list.
The carrier core distinguishes company drivers from owner operators and supports operator company records, pay plans and driver or unit assignments. We scope your exact settlement rules, deductions and company structure during discovery.
Yes. Bring your equipment requirements, stop workflows, permits, customer rules and paperwork. Specialized workflows are custom build scope; they are not implied to be included in the base carrier template.
That is the point of a custom build. We map your statuses, dispatch process, roles, approvals and documents, then decide what to keep, reshape or add.
Foundation Broker covers brokerage workflows. For a company running both, we can scope a hybrid install combining broker and carrier modules.
Implementation & timeline
How do we get from here to go-live?
Concept to delivery can be as little as 60 days. The actual schedule depends on your scope, integrations, data migration and review process. We agree on a timeline for your build before delivery work begins.
People who understand dispatch, equipment, driver pay and billing; examples of the documents and reports you use; your integration requirements; and someone who can make decisions about the workflow.
The process includes discovery, a written blueprint, working build reviews, a pilot and go-live. Review the screens and workflows with the people who will use them before the cutover.
Yes. We can define a first phase around your essential workflow, then scope additional modules and connections separately.
Data & migration
What happens to our existing records?
We scope migration from the exports available in your current system: loads, customers, drivers, units, documents and financial history. What can be imported depends on the format, completeness and access you can provide.
Bring representative files. We map the fields, identify missing values and duplicates, and agree on the cleanup and validation needed before go-live.
Validation should include sample record checks and reconciliation of the totals your operations and finance teams rely on. The migration plan defines the records and history to bring forward.
Integrations & driver experience
Will our tools work with the new system?
The carrier system includes connection workflows for Samsara, QuickBooks Online and RingCentral, along with mapping. They need the appropriate provider accounts, access and configuration. Additional integrations are scoped individually.
These are potential custom connections, not claims that the carrier template already connects to every provider. We review API access, available data, costs and the depth of the required workflow during scoping.
The source system includes a mobile driver experience for trip sheets, status updates, location tracking and POD capture, with iOS and Android packaging. Your app branding, distribution and exact workflow are part of your build scope.
The source system includes public load tracking links. We configure what a customer can see, how links are issued and how tracking is populated for your operation.
Bring the partner specifications. EDI, scheduled files or import/export may be appropriate. Access, testing requirements and ongoing provider charges are part of the integration conversation.
Pricing & ownership
What does it cost—and what do we own?
Setup ranges from $2,500 to $7,500 and the monthly fee from $500 to $1,500, both based on complexity and integrations. There are no per-user, per-truck or per-load fees. Exclusive feature buildouts are priced by project.
Custom workflows, integrations, data migration, driver and customer experiences, pay rules and the complexity of your operation. Third-party provider costs and access requirements are also discussed during scoping.
Yes, on the ownership track. You pay a higher monthly fee during the term (roughly two years) and the IP transfers to you at the end. The agreement defines exactly what transfers and any third-party licensing obligations.
No. You pay a setup fee and a monthly fee. Adding users, trucks or loads does not change your bill.
White-label systems are available. We scope your name, logo, domain, documents and driver-facing experience as part of the project.
Support & training
What happens after the first dispatch?
The monthly fee ($500 to $1,500 by complexity and integrations) covers hosting, updates, support and training. The services, support arrangements and capacity required for your build are defined in your quote and agreement.
Training should follow each team’s workflow: dispatch, billing, driver pay, equipment management and drivers. We agree on the sessions and materials as part of delivery.
Yes. The system can be extended. New workflows or integrations are reviewed and scoped; your agreement determines what changes are included in ongoing service.
Security & control
How do we protect the operation?
The source system includes roles and a permissions matrix, plus an activity log. Your build defines which teams can view or change operational, financial and administrative information.
Hosting, backup, recovery and response requirements need to be agreed for your deployment. We do not advertise an uptime guarantee or a round-the-clock response promise without an agreement that provides it.
Ownership, source-code delivery, data export and hosting transition terms are defined in the agreement. Discuss these before signing so the exit path is clear.