Data points to consider when evaluating customization
Availability of public vs private APIs and rate limits
Data schema and field mappings for loads, routes, equipment, and customers
Customizable business rules for: pricing, bidding, notifications, escalations
Ability to create custom dashboards and KPIs
Localization, currency, time zone handling
Change management support and versioning of custom configurations
Practical considerations
Customizations can increase implementation time and cost
Some customizations might be better handled via configuration rather than code
Ensure upgrade compatibility; confirm how DAT handles updates with your customizations
Additional Costs
Setup/implementation fees
One-time onboarding/implementation fee to cover discovery, configuration, integrations, data migration, and training
Typical range: broadly from a few thousand dollars up to tens of thousands, depending on scope and whether integrations are included
Licensing and subscription costs
Per-user or per-seat pricing (e.g., for brokers, dispatchers, admins)
Tiered pricing based on features, load volume, or modules (e.g., standard load board vs. advanced analytics)
Annual or multi-year contracts often provide discounts
Maintenance and support
Ongoing support fees, usually as a percentage of annual software cost or a fixed annual fee
Service levels (SLA) may affect response times for critical issues
Some plans include standard updates; premium support may include 24/7 access, dedicated account manager
Add-ons and modules
Additional modules such as enhanced analytics, mobile apps, advanced reporting, or premium data feeds
Integrations marketplace fees if using third-party connectors
Data processing and usage fees
Some vendors charge for high volumes of data, API calls, or post-load processing beyond included limits
Training and enablement
Optional onboarding sessions, advanced training, or certification for users
Documentation and knowledge-base access often included but dedicated training may incur fees
Training
Onboarding and admin training
Guided onboarding sessions for admins to configure roles, permissions, branding, and initial integrations.
Admin-led training on security, access control, and governance.
End-user training
Role-based training for drivers, dispatchers, brokers, and shippers covering core workflows: post/load creation, search, bid/accept, messaging, rating, and escalation.
Quick-start guides, in-app help, and step-by-step tutorials within the platform.
Use-case specific training (e.g., setting up saved searches, alerts, and automation rules).
Training formats
Live virtual training sessions or in-person workshops (depending on region and contract).
Self-service resources: knowledge base, video tutorials, FAQs, and printable guides.
Practice/sandbox environment (if available) to safely explore features before going live.
Certification and enablement
Optional user certifications or competency checks for key roles, often part of enterprise engagements.
Regular refresher courses or update trainings when new features are released.
Training timing and rollout
Training typically occurs during onboarding (2–6 weeks, depending on scope).
Ongoing training for new hires and feature updates as part of customer success programs.
Security Measures
Access and identity
Role-based access control (RBAC) to limit data visibility by user, group, or region.
Single sign-on (SSO) support (SAML/OAuth) for enterprise customers.
Strong password policies and optional MFA (multi-factor authentication).
Data protection
Data encryption at rest and in transit (TLS for data in transit; encryption for stored data).
Regular security assessments and vulnerability management.
Data segregation for multi-tenant environments.
Data governance and privacy
Audit logs documenting user activity, data access, and configuration changes.
Data retention policies and controls for deletion or anonymization where applicable.
Compliance considerations (regions may align with GDPR, CCPA, or local data protection laws as relevant).
Incident response
Defined incident response process with notification timelines for security incidents.
Security containment, investigation, and remediation protocols.
Third-party risk management
Vendor risk assessments for integrations and data sharing with TMS, ERP, or telematics providers.
Compliance/security updates: patches addressing vulnerabilities or regulatory requirements.
Update packaging and delivery
In-app notification of new features and changes.
Changelog or release notes detailing what’s new, what’s fixed, and any configuration impacts.
Potentially a sandbox/test environment or test notes to validate changes before broad rollout.
Deployment and change management
Rolling deployments to minimize disruption, with staged pilots for enterprise customers.
Optional maintenance windows for larger changes, with communication in advance.
Compatibility guidance to help you plan for any required configuration adjustments.
Data Ownership and Portability
Data ownership
User-created data ownership: Loads, carriers, equipment profiles, customers, saved searches, quotes, and messages are typically owned by the customer who created or uploaded them.
Platform rights: DAT usually retains rights to anonymized usage data and aggregate analytics to improve services, subject to privacy and contractual constraints.
Data usage rights: Confirm that your organization retains the right to export or extract your own data at any time.
Data portability and export
Data export options: Availability of bulk export (CSV, Excel, or API-accessible formats) for core data sets (loads, carriers, customers, rates, messages).
Schedule and cadence: On-demand exports vs. scheduled data dumps (e.g., nightly, weekly).
Data format compatibility: Standardized schemas for easy migration to your own systems or another platform.
Data deletion: Procedures for securely deleting data upon contract termination, including timelines and confirmation receipts.
Scaling Up / Down
Flexible licensing and seats
Additions: Process, lead time, and cost for adding users, modules, or tiers mid-term.
Reductions: Process and penalties (if any) for reducing seats or downgrading modules before term end.
Pro-rated adjustments: How adjustments are calculated within a billing period.
Usage-based scalability
Volume-based pricing: Whether pricing scales with load volume, number of searches, API calls, or posting volume.
Peak vs off-peak: Any different pricing or limits for high-demand periods.
Module and feature scalability
Modular expansion: Ability to start with core Load Board and add modules (Powerload, Duo, analytics, mobile app) as needs grow.
Feature gating: How feature availability changes with plan tier and how upgrades are executed.
Service levels during scale changes
Implementation windows: Lead times for enabling new modules or deactivating others.
Data handling during scale changes: Ensuring no data loss when increasing/decreasing capabilities.
The terms & conditions for contract renewal and cancellation
Renewal structur
Term length: Common terms are annual or multi-year; auto-renewal language and notification requirements.
Price changes at renewal: How price increases are communicated, cap limits, and any grandfathering provisions for existing features.
Termination for convenience
Termination rights: Notice period (e.g., 60–90 days) and any early termination penalties.
Non-renewal: Process to opt out at contract end and any required transition support.
Data return/deletion post-termination: Timelines for data export and data deletion after contract ends.
Termination for cause
Causes recognized: Non-payment, repeated SLA breaches, data security incidents, breach of material obligations.
Cure periods: Any grace period to remedy identified breaches before termination.
Migration and transition assistance
Post-termination support: Availability and duration of transitional access to data, APIs, or export tools to facilitate migration.
Knowledge transfer: Access to documentation, configurations, and support during transition.
Fees and refunds
Unused prepaid fees: Policies on refunds for prepaid periods or credits for unused capacity.
Termination charges: Any liquidated damages or penalties for early termination beyond standard notice.
Compliance and audits
Audit rights: Whether customers have rights to audit or verify compliance during renewal discussions.
Renewal negotiations: Process and timelines for negotiating terms at renewal.
Compliance
General data protection and privacy
Data sovereignty: Where data is stored (data center regions, cloud provider locations) and controls over cross-border data transfer.
Data processing agreements (DPAs): Availability of a DPA that aligns with GDPR, CCPA, or other regional privacy laws.
Data subject rights: How customer requests (access, correction, deletion) are handled.
Security certifications and controls
SOC 2 / SOC 3: Presence of independent security audits and the latest report availability (Type II often preferred).
ISO/IEC 27001: Certification status if applicable.
PCI DSS: Relevance if payment processing or handling cardholder data is involved (usually not for core load board data, but relevant for billing systems).
NIST/CSA frameworks: Any alignment or mapping to recognized security frameworks.
Regulatory compliance by region
GDPR/CCPA/CPRA: How personal data of drivers, brokers, shippers, or customers is protected; data subject rights handling.
Local data protection laws: Any regional considerations (e.g., E.U., U.S. state laws, UK GDPR).
Incident reporting and response
Notification timelines: Timefraes for confirming and reporting security incidents or data breaches.
Containment and remediation: Expected actions and customer communication during incidents.
Data retention and deletion compliance
Retention schedules for logs and analytics data; deletion upon request where applicable.
Data retention alignment with legal or contract requirements.
