For fleets — not a freight quote
AI-native TMS.Hosted Hermes in Slack.
The same stack we run daily on a live Houston fleet — dispatch, docs, billing, and an ops agent that answers in Slack. Built for regional fleets that run drayage and OTR. No Mac mini. No “run AI on your office computer.”
MCP-compatible (Claude / OpenClaw) for builders — secondary to the hosted product.
What ships in the pilot
Hermes = product
Hosted Slack ops agent. Ask load status, capacity, gaps. Tier 0 read-only to start.
Runs on our platform
Agent runtime, tools, and audit stay in your private workspace — not on a desk Mac.
OpenClaw = optional
Connect Claude or OpenClaw via MCP with a fail-closed allowlist. Marketing reach, not the SKU.
Hermes in Slack
Real usage pattern from our fleet: @mention Hermes, get an answer with TMS deep links. Writes stay behind confirm cards — not in this pilot’s default.
Demo video landing soon
We’re recording a 60–90s clip from live Slack usage. Until NEXT_PUBLIC_HERMES_DEMO_VIDEO_URL is set, here’s what the demo covers:
- Ask Hermes for status on a real load — reply + deep link.
- Ask who’s open / capacity for a window.
- Ask about gaps (missing appointments / open empties).
- Close: hosted on our platform, MCP-compatible for builders.
Recording checklist: docs/gtm/hermes-demo-script.md
Hosted Hermes pilot
Four weeks. Read-only in your Slack. We score success on asks/week, unique askers, and whether you’d pay for hosted Hermes — even before a full TMS switch.
- · Target: 30–150 truck peer fleets that already live in Slack
- · Gate: ≥20 asks/week in weeks 3–4, ≥3 unique askers, “would pay” signal
- · Not included: local OpenClaw box, write tools, Safety Council as a product demo
Looking for container drayage out of Houston instead? That’s our carrier site.
Get a freight quote