Melrose

Name: Melrose
Brand: Melrose

AI Native

AI automation, purpose built for truckers and carriers.

Est 2024|Valuation $116.5M|Raised $39M

LinkedIn 375|Website|Web traffic 4K|FTEs 18|HQ San Francisco, California, US

MarketsSupply Chain Visibility Freight Management

Published Sep 20, 2026

01Common complaints

- If you require a full TMS replacement (dispatch, accounting, settlement) as your primary system of record - If you require publicly documented compliance attestations (SOC 2 Type II, ISO 27001) and are unwilling to proceed without them - If your operation has very low volume where automation ROI would not justify subscription and implementation costs - If your primary need is carrier-network real-time visibility at scale; a specialist visibility provider may be a better fit - If your documentation is highly variable and exception-heavy, making automated extraction difficult and likely to require substantial manual correction

Deal disqualifiers

Requirements for publicly available SOC 2 Type II or ISO 27001 attestations where the buyer will not accept documentation provided only under NDA
Highly customized legacy workflows with low standardization and resistance to SOP changes
A primary requirement to replace a full TMS (Melrose positions itself as an overlay)

Current limitations acknowledged by the vendor

No explicit public limitations or a known-issues log was found in the accessible site excerpts; a site navigation element indicates a changelog, but details were not captured for this research.

Roadmap / future features

Not publicly documented in the materials reviewed.

Scale limitations

Not publicly documented. Buyers should test:

Peak quote volumes (e.g., 1,000+ requests/week) and associated processing latency
Document parsing accuracy across diverse templates and suppliers
EDI partner variability and transaction failure handling at scale

Security / compliance gaps

No publicly documented SOC 2 or ISO 27001 certifications were found for the product in accessible sources.

API limitations / integration constraints

The vendor states integration capability with various TMS APIs and EDI workflows. Buyers should verify:

Depth of supported API capabilities and specific TMS adapters
Rate limits, retries, and observability for integrations
How partial failures and exception states are surfaced and handled

02Why they buy

Unique selling points supported by available evidence

Consistent messaging around automating the quote-to-delivery workflow and reducing manual document handling
An EDI offering that the vendor describes as enabling faster onboarding through AI-assisted mapping and monitoring
A vendor-authored case study with specific baseline metrics for quote volume and time-per-quote that illustrates an intended use case and ROI pathway (vendor-provided and not independently verified)

Where competitors have clearer advantages

Pricing transparency: some competitors publish starting prices or entry tiers, while Melrose’s pricing is not publicly confirmed in the sources reviewed
Independent review footprint: some competing products appear on public review platforms and analyst sites; Melrose’s presence was not located on major review sites during this research session

03Field reports

Important limitation: review source ambiguity / name collisions

The brand name “Melrose” is used by multiple unrelated companies (retail, healthcare, staffing, etc.). Many third-party review sources returned entries for other organizations named Melrose. To avoid misleading conclusions, this report: - Treats testimonials on the Melrose website as vendor-published endorsements (these are useful but inherently biased). - Treats third-party review platforms with caution when listings do not clearly reference the vendor’s official domain. - Did not locate verifiable product pages for Melrose on G2, TrustRadius, or Capterra during the research session.

Vendor-published testimonials (vendor-provided)

The vendor site includes several customer quotes and case-study summaries. Examples (paraphrased): - A named trucking customer stated the vendor adapted the software to the customer’s workflows and reported measurable efficiency gains shortly after deployment. - A second customer described improved flexibility for automating operational tasks and receiving timely updates. - A third customer characterized the vendor as operationally effective and responsive to business needs. - A fourth customer described faster access to consolidated data through a single integration. These items are vendor-published and selectively presented; they do not include contract scope, baseline metrics, or independent verification.

Case-study claims (vendor-authored)

A Melrose case study for Gulf Winds International (published in 2026) reports the following baseline and changes: - Before: nontrivial per-quote processing time, high inbound quote volume, and only a minority of quotes being answered due to capacity constraints. - With Melrose: integration with rate sheets, automatic replies bounded by configured rules, a human-approval workflow for complex quotes, and storage of quote data for accounting/CRM. The case study provides a plausible ROI pathway (increased quote coverage), but it is vendor-authored and does not provide independently verified outcomes such as net revenue uplift, win-rate change, or error-rate impacts.

Third-party review platforms (attempted)

Gartner Peer Insights: No Melrose product listing was located in accessible searches during this research session.
G2 / TrustRadius / Capterra: No attributable product pages for Melrose as a B2B AI logistics automation product were found in verifiable searches; results were often for other organizations named Melrose.

Community and social proof (attempted)

Reddit and Hacker News searches did not return product-specific discussions that could be attributed to the vendor during this research session.

Implication: The independent user-review footprint for the vendor appears limited or difficult to locate publicly as of the time of research.

Case study: Gulf Winds International (quoting automation)

Source: Melrose case study page (Mar 9, 2026). Reported baseline (before Melrose) - A non-trivial time required per quote (on the order of minutes) - A high weekly volume of inbound quote requests - Only a minority of inbound requests were answered weekly due to capacity constraints Described solution (with Melrose) - Integration into rate sheets with lane coverage - Automatic replies for quotations that fall within configured boundaries - Human approval workflow for complex quotes - Storage of quote data into accounting/CRM systems - Mileage computations via third‑party routing/mileage services (e.g., PC Miler or Google Trucks API) Critical evaluation - The baseline descriptions are plausible and indicate a capacity bottleneck, but the case study does not provide independently verified metrics for changes in quote volume handled, win-rate, revenue, or margin impact. - The described controls (bounded automatic replies and human approvals) are sensible; buyers should request details on how boundaries are configured, audited, and updated. - External dependencies (e.g., PC Miler or Google Trucks API) can introduce additional costs and integration complexity.

04Best fit

Company sizes

Likely best fit: mid-market freight operators (roughly several dozen to several hundred employees) or high-volume operations teams where small time savings per transaction compound into material labor-cost reductions. Enterprise deployments are possible but may require more detailed security and compliance documentation and references.

Industries / verticals

Trucking carriers and drayage operators
Freight brokerages with high inbound quoting volume
Forwarders and NVOCCs with heavy document workflows

Roles and personas

Decision makers: COO/VP Operations, CIO/CTO (in tech-forward carriers/brokers), Head of Pricing/Quoting, Head of EDI/Integrations
End users: dispatch, customer service representatives, pricing analysts, EDI analysts, operations coordinators

Pain points the product addresses

Manual re-entry of shipment and document data
Low quoting throughput and missed opportunities
Slow EDI onboarding and high EDI maintenance overhead
Fragmented tooling across portals, email, and TMS systems

05The pitch

What the product does (core value proposition)

Melrose is a logistics automation platform that uses artificial intelligence and machine learning to extract data from documents, synchronize information with an existing TMS, and automate recurring operational workflows (e.g., quoting, delivery order processing, and shipment/status updates). Vendor messaging emphasizes reducing manual paperwork and automating processes across the quote-to-delivery lifecycle while integrating with a customer’s TMS rather than replacing it. Key product areas described by Melrose include: - Quote automation: ingest inbound quote requests (often via email), prepare replies, store quote data, and support a human-approval workflow for exceptions and complex pricing. Vendor materials reference integration with rate sheets and guardrails for automated responses. - Document / delivery order (D.O.) parsing: extract data from unstructured documents and map fields to shipments, quotes, and customer records. - Container / load updates: track containers from vessel to pickup and provide operational visibility and notifications. - EDI platform: an EDI offering that is described by the vendor as modern; features noted include direct TMS integration, monitoring/alerting, and AI-assisted mapping. (Primary vendor sources: product overview and EDI product page.)

Target market and positioning

Melrose is positioned for logistics operators that already use a TMS (carriers, drayage operators, brokers, forwarders, and logistics teams) and that seek to: - Reduce back-office labor requirements or scale capacity with existing staff - Increase speed and coverage for quoting - Reduce manual data-entry errors and the effort required for EDI onboarding Site content and case examples emphasize trucking and drayage workflows and list common TMS integrations (e.g., McLeod, PCS, TMW, Turvo, Rose Rocket), indicating an overlay approach designed to work with existing TMS platforms rather than replace them.

Get a comprehensive analysis of Melrose including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Sep 20, 2026

01Common complaints

If you require a full TMS replacement (dispatch, accounting, settlement) as your primary system of record
If you require publicly documented compliance attestations (SOC 2 Type II, ISO 27001) and are unwilling to proceed without them
If your operation has very low volume where automation ROI would not justify subscription and implementation costs
If your primary need is carrier-network real-time visibility at scale; a specialist visibility provider may be a better fit
If your documentation is highly variable and exception-heavy, making automated extraction difficult and likely to require substantial manual correction

Deal disqualifiers

Requirements for publicly available SOC 2 Type II or ISO 27001 attestations where the buyer will not accept documentation provided only under NDA
Highly customized legacy workflows with low standardization and resistance to SOP changes
A primary requirement to replace a full TMS (Melrose positions itself as an overlay)

Current limitations acknowledged by the vendor

No explicit public limitations or a known-issues log was found in the accessible site excerpts; a site navigation element indicates a changelog, but details were not captured for this research.

Roadmap / future features

Not publicly documented in the materials reviewed.

Scale limitations

Not publicly documented. Buyers should test:

Peak quote volumes (e.g., 1,000+ requests/week) and associated processing latency
Document parsing accuracy across diverse templates and suppliers
EDI partner variability and transaction failure handling at scale

Security / compliance gaps

No publicly documented SOC 2 or ISO 27001 certifications were found for the product in accessible sources.

API limitations / integration constraints

The vendor states integration capability with various TMS APIs and EDI workflows. Buyers should verify:

Depth of supported API capabilities and specific TMS adapters
Rate limits, retries, and observability for integrations
How partial failures and exception states are surfaced and handled

02Why they buy

Unique selling points supported by available evidence

Consistent messaging around automating the quote-to-delivery workflow and reducing manual document handling
An EDI offering that the vendor describes as enabling faster onboarding through AI-assisted mapping and monitoring
A vendor-authored case study with specific baseline metrics for quote volume and time-per-quote that illustrates an intended use case and ROI pathway (vendor-provided and not independently verified)

Where competitors have clearer advantages

Pricing transparency: some competitors publish starting prices or entry tiers, while Melrose’s pricing is not publicly confirmed in the sources reviewed
Independent review footprint: some competing products appear on public review platforms and analyst sites; Melrose’s presence was not located on major review sites during this research session

03Field reports

Important limitation: review source ambiguity / name collisions

Treats testimonials on the Melrose website as vendor-published endorsements (these are useful but inherently biased).
Treats third-party review platforms with caution when listings do not clearly reference the vendor’s official domain.
Did not locate verifiable product pages for Melrose on G2, TrustRadius, or Capterra during the research session.

Vendor-published testimonials (vendor-provided)

The vendor site includes several customer quotes and case-study summaries. Examples (paraphrased):

A named trucking customer stated the vendor adapted the software to the customer’s workflows and reported measurable efficiency gains shortly after deployment.
A second customer described improved flexibility for automating operational tasks and receiving timely updates.
A third customer characterized the vendor as operationally effective and responsive to business needs.
A fourth customer described faster access to consolidated data through a single integration.

These items are vendor-published and selectively presented; they do not include contract scope, baseline metrics, or independent verification.

Case-study claims (vendor-authored)

A Melrose case study for Gulf Winds International (published in 2026) reports the following baseline and changes:

Before: nontrivial per-quote processing time, high inbound quote volume, and only a minority of quotes being answered due to capacity constraints.
With Melrose: integration with rate sheets, automatic replies bounded by configured rules, a human-approval workflow for complex quotes, and storage of quote data for accounting/CRM.

The case study provides a plausible ROI pathway (increased quote coverage), but it is vendor-authored and does not provide independently verified outcomes such as net revenue uplift, win-rate change, or error-rate impacts.

Third-party review platforms (attempted)

Gartner Peer Insights: No Melrose product listing was located in accessible searches during this research session.
G2 / TrustRadius / Capterra: No attributable product pages for Melrose as a B2B AI logistics automation product were found in verifiable searches; results were often for other organizations named Melrose.

Community and social proof (attempted)

Reddit and Hacker News searches did not return product-specific discussions that could be attributed to the vendor during this research session.

Implication: The independent user-review footprint for the vendor appears limited or difficult to locate publicly as of the time of research.

Case study: Gulf Winds International (quoting automation)

Source: Melrose case study page (Mar 9, 2026).

Reported baseline (before Melrose)

A non-trivial time required per quote (on the order of minutes)
A high weekly volume of inbound quote requests
Only a minority of inbound requests were answered weekly due to capacity constraints

Described solution (with Melrose)

Integration into rate sheets with lane coverage
Automatic replies for quotations that fall within configured boundaries
Human approval workflow for complex quotes
Storage of quote data into accounting/CRM systems
Mileage computations via third‑party routing/mileage services (e.g., PC Miler or Google Trucks API)

Critical evaluation

The baseline descriptions are plausible and indicate a capacity bottleneck, but the case study does not provide independently verified metrics for changes in quote volume handled, win-rate, revenue, or margin impact.
The described controls (bounded automatic replies and human approvals) are sensible; buyers should request details on how boundaries are configured, audited, and updated.
External dependencies (e.g., PC Miler or Google Trucks API) can introduce additional costs and integration complexity.

04Best fit

Company sizes

Industries / verticals

Trucking carriers and drayage operators
Freight brokerages with high inbound quoting volume
Forwarders and NVOCCs with heavy document workflows

Roles and personas

Decision makers: COO/VP Operations, CIO/CTO (in tech-forward carriers/brokers), Head of Pricing/Quoting, Head of EDI/Integrations
End users: dispatch, customer service representatives, pricing analysts, EDI analysts, operations coordinators

Pain points the product addresses

Manual re-entry of shipment and document data
Low quoting throughput and missed opportunities
Slow EDI onboarding and high EDI maintenance overhead
Fragmented tooling across portals, email, and TMS systems

05The pitch

What the product does (core value proposition)

Key product areas described by Melrose include:

Quote automation: ingest inbound quote requests (often via email), prepare replies, store quote data, and support a human-approval workflow for exceptions and complex pricing. Vendor materials reference integration with rate sheets and guardrails for automated responses.
Document / delivery order (D.O.) parsing: extract data from unstructured documents and map fields to shipments, quotes, and customer records.
Container / load updates: track containers from vessel to pickup and provide operational visibility and notifications.
EDI platform: an EDI offering that is described by the vendor as modern; features noted include direct TMS integration, monitoring/alerting, and AI-assisted mapping.

(Primary vendor sources: product overview and EDI product page.)

Target market and positioning

Melrose is positioned for logistics operators that already use a TMS (carriers, drayage operators, brokers, forwarders, and logistics teams) and that seek to:

Reduce back-office labor requirements or scale capacity with existing staff
Increase speed and coverage for quoting
Reduce manual data-entry errors and the effort required for EDI onboarding

Site content and case examples emphasize trucking and drayage workflows and list common TMS integrations (e.g., McLeod, PCS, TMW, Turvo, Rose Rocket), indicating an overlay approach designed to work with existing TMS platforms rather than replace them.

Get a comprehensive analysis of Melrose including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →