Partners

Build with thefreight workflow, not around it

Choose the partnership path that creates shared operating value, with clear data, product and go-⁠to-⁠market boundaries.

Choose the partnership model

The first choice changes the requirements, the proof and the owner, so each partner type gets its own conversation.


[01]

Shared workflow


Four answersbefore anything is built

A partnership that cannot answer these four is not scoped yet.

01

What comes in

The data or the action the partner brings, and in what shape.

02

What the product does with it

The step in the freight workflow it changes, named exactly.

03

What the customer gets

The outcome a dispatcher, driver or finance team can see.

04

Who holds the record

Which system keeps the record afterwards, and who owns it.


[02]

Technical fit


What to expectbefore the first call

We cover API and authentication, refresh cadence, sandbox, support, security and data rights before anything is built.

Covered in technical discovery

No public API is published

API and authentication
Agreed in discovery, including the interface you would use
Refresh cadence
Stated per source, with what happens when it is late
Sandbox
Before any production data moves
Support
Who owns it afterwards, written down during qualification
Security
Reviewed before anything is connected
Data rights
What is used, for what, and for how long

[03]

Governance and commercial


Governance ispart of the offer

Integration is not the whole partnership. The commitments and the commercial model are agreed in writing, not discovered afterwards.

Commitments

01
Attribution that survives the integration
02
Consent asked for rather than assumed
03
No more data than the workflow needs
04
A named owner for every status

Commercial models

Referral
You send carriers who need the product; the terms are agreed on a call.
Reseller
You sell LoadHunt alongside your own service, with support split in writing.
Co-marketing
A webinar, a guide or a launch together, scoped before anything is promised.

[04]

FAQ


Questions,answeredplainly

Load board, ELD, factoring, data and technology, which is the choice this page opens with. None is a running program with a list of members; each is a conversation that starts with a message through the contact page and is scoped before anything is connected.

Not published. Integration starts with a technical discovery conversation, which is also where the interface you would use is agreed.

We do not publish a range before scoping. The discovery conversation produces one for your case.

That is agreed during qualification and written down, so neither side discovers the answer during an incident.