Raft

• If procurement requires abundant third-party reviews for validation: When an organization’s procurement policy depends on extensive coverage on Gartner Peer Insights/TrustRadius/G2, Raft’s public review footprint may be insufficient.
• If formal, public security attestations are mandatory: If SOC 2 Type II or ISO 27001 must be publicly available and cannot be provided under NDA, an alternative vendor with published compliance documentation may be more appropriate.
• If a full forwarding system-of-record replacement is required: Raft functions primarily as an automation/intelligence layer rather than a full end-to-end forwarding platform; incumbents offering complete operating systems may better meet this need.
• If the organization cannot invest in integration and change management: Automation value frequently depends on integration quality and process redesign.
• If document and transaction volumes are too small: For lower-volume forwarders/brokers, lighter-weight IDP/RPA tools or targeted AP automation may provide a better cost-to-value ratio.

• Gartner Peer Insights: No clearly accessible Gartner Peer Insights product page for Raft was found in accessible results (potentially absent listing, naming mismatch, or blocked access).
• G2 / TrustRadius: No strong evidence of a widely reviewed listing for Raft on G2 or TrustRadius was found in accessible results.

Practical takeaway: Buyers should not expect abundant third-party star ratings for this vendor; validation may rely on reference calls, pilots, and customer case studies.

Raft publishes multiple case studies with direct quotes. Examples include:

• Navia Freight case study (Raft resources):

  "AI now takes care of tasks our staff did not enjoy, and the automation required us to optimize our processes, revealing areas for improvement." (Attributed to Rob Ardesi, COO)

• Navia Freight (Navia’s own website):

  "The automation provided by Raft also required us to have our processes optimized, which helped identify areas for improvement which otherwise would have gone unnoticed."

• Raft "Intelligent Document Processing" landing page (gated download):

  "It would take several additional people to replicate what we have with Raft"

Because mainstream product review pages were not found/accessible in the research, public end-user complaints about the Raft platform itself are limited in available sources.

However, employee reviews (Glassdoor) provide mixed signals that could correlate with delivery/support consistency:

• Glassdoor summaries show both positive culture/mission comments and negative claims about leadership, politics, and internal issues.

Interpretation caution: Employee review sentiment may not map directly to product quality, but it can be a risk indicator for enterprise buyers concerned about support responsiveness, implementation stability, and account management continuity.

Claimed results (Raft-published):

• "several thousand minutes of manual document processing time saved per month" (note: units appear inconsistent across the case study between weekly and monthly statements)
• "a portion of documents processed per month with zero user intervention"
• "a large portion of invoices were processed automatically"

Customer quote (Raft-published):

• "AI now takes care of tasks our staff did not enjoy…" (COO)

Critical evaluation:

• Metrics are vendor-published; no independent audit of baseline vs post-automation was provided.
• Internal inconsistency in time-savings phrasing (monthly vs weekly) suggests the buyer should request the underlying measurement method.
• Navia’s own site corroborates qualitative impacts, which increases credibility but does not substitute for independent validation.

Claimed benefits (Raft-published):

• Improved efficiency reported as very high in best-case scenarios and "saving substantial labor hours monthly" (as surfaced on Raft homepage excerpts)
• Case study notes Raft’s integration with CargoWise as a highlighted capability.

Critical evaluation:

• "Up to" claims should be treated as best-case results; procurement teams should ask for distributions (median, p90) and definitions used.
• The CargoWise integration claim is operationally significant and should be validated in a proof-of-concept using the prospective customer's CargoWise configuration and document set.

Claimed results (landing page):

• "Process a large volume of documents per month"
• "Save several minutes per document"
• "A majority of viable documents processed"
• "Time savings equivalent to many full-time employees"
• Quote: "It would take several additional people to replicate what we have with Raft"

Critical evaluation:

• The customer name is not on the landing page (gated), limiting independent verification.
• "Viable documents" is a key caveat; procurement teams should clarify what percentage are non-viable and why (format variability, handwriting, missing reference data, language issues, etc.).

Raft is a B2B logistics automation platform focused on freight forwarders, customs brokers, and related logistics service providers. The product is presented as applying machine learning to reduce manual intervention in shipment execution and back-office workflows—particularly extracting and standardizing data from unstructured inputs (documents, invoices, emails) and automating workflows across functions such as finance (AP invoice processing), customs, and operations. Raft also offers customer-facing capabilities (e.g., shipment portal, visibility, emissions reporting, quote-to-book) and describes the offering as an "operating platform" rather than a narrowly scoped point solution.