HUGO by Stippd

Your TMS records the work. Hugo does it.

HUGO is a TMS where Hugo does the routine and your planners steer. Start on the TMS you run today, and grow into ours when you are ready.

Planners are hard to find.

A fleet can only grow as fast as its planning desk.

Your best people do the admin.

Completing one order by hand takes 8 to 15 minutes, one fleet told us.

What customers say gets lost.

The real order is in a mail, a call or a WhatsApp. Little of it reaches the TMS.

The rules live in people's heads.

The usual place, the trailer after yeast, the driver who refuses a site. They leave when a planner does.

Built for what you already run

  • Your TMS
  • Telematics
  • Mailbox and PDF
  • EDI
  • Retailer portals
  • Teams
  • WhatsApp

Meet Hugo. Ask it anything, or tell it what to do.

Hugo works in every screen, in Teams and in your mailbox. It answers with its sources. When you tell it to change something, the change waits for you to keep it, like a drag on the planning board.

Behind Hugo, a team of desks

  • Intake
  • Master data
  • Capacity
  • Next-day
  • Same-day
  • Timeslots
  • Charter
  • Customer
  • Proof
  • Charges

Each desk has its own permissions, playbooks, track record and off switch. More desks join as you switch on more of HUGO.

HugoExample fleet

Where is order 48133, and why is it not planned?

Still at the depot. It came in by mail at 06:40 without a slot, and the wholesaler in Aalst has no room before 14:00 today.

MailPortalToday's plan

Move it to tomorrow's first wave.

Your change, not kept yet

Order 48133 to Thursday, wave 1, truck 4.

Window, trailer and driving time checked.

A day with Hugo. Eight moments, from the first order to tomorrow's plan.

06:10Intake desk

The orders come in.

Hugo reads the mail and the PDF, builds the order, and drafts a question about what is missing.

OutlookInbox

Supermarket planningOrder for today

Same as last week. 12 pal frozen, usual place, today.

Order_Wednesday.pdf

Hugo works it out

  • SiteMemorySupermarket DC Mechelen
  • TrailerMailReefer at -20 °C
  • LoadPDF12 pallets, 4.8 loading metres
  • ArrivalMailToday, Wednesday
  • PO numberMissingNot in the mail or the PDF

OutlookReply to Supermarket planningDraft

Order 48122 has no PO number. Can you send it before we lock the board?

Order built. The question needs you.

07:45Capacity desk

A rush order asks too much.

Hugo checks trucks, rules and price before anyone says yes, and drafts a counter-offer for your planner.

OutlookInbox

Discounter transportRush order

Can you take 8 pallets to Genk tomorrow at 07:00?

Hugo works it out

  • Genk at 07:00PlanEvery reefer is on another run until 09:00
  • Truck 9TelematicsFree from 09:15, reaches Genk at 10:30
  • PriceContractThe tariff still covers a 10:30 delivery

OutlookReply to Discounter transportDraft

We can deliver at 10:30 tomorrow. Shall we book it?

Needs you. Approve the reply.

08:12Timeslots desk

The dock gets booked.

Hugo adds the PO, picks a portal slot that fits the truck's route, and books it.

OutlookInbox

Supermarket planningRe: Order 48122

PO 4500812. Any time before noon is fine.

Hugo works it out

  • PO numberMail4500812, added to order 48122
  • WindowMailBefore 12:00
  • Truck 12TelematicsReaches Mechelen at 11:10
  • SlotPortal11:30 is free and fits the route

Retailer portal, DC Mechelen

09:00 10:00 11:30 Dock 4 12:30

Booked. Reference on order 48122

09:20Timeslots and Customer desks

A truck runs late.

Hugo finds the next legal window, moves the slot, and drafts the message so the customer knows before they call.

Telematics

Truck 12R0 at Groot-Bijgaarden

Wholesaler Aalst, window09:40

Arrival10:05, 25 min late

Hugo works it out

  • Window 09:40TelematicsMissed by 25 minutes
  • Next windowRules10:25 is legal, and Mechelen 11:30 still fits
  • ChannelMemoryThis customer answers on WhatsApp

WhatsAppWholesaler, AalstDraft

Truck 12 arrives at 10:25 instead of 09:40. The new slot is booked.

Slot moved. The message needs you.

10:20Same-day desk

Two promises collide.

When no legal move keeps both, Hugo lays out what each option costs and your planner decides. Try it.

Today's plan

11:00Chocolate makerTrailer 3

11:30Supermarket, frozenTrailer 7

Trailer 3 carried yeast this morning

Hugo works it out

  • Trailer 3RulesYeast, then chocolate needs a wash. No time before 11:00
  • Trailer 7PlanClean, but booked for the supermarket at 11:30
  • ResultRulesOne promise has to move

Needs you

12:00Charter desk

No own truck can take it.

Hugo picks a subcontractor you already use, inside your own price limit, and drafts the request for you to send.

Orders

Thu 08:0014 pallets ADR to AntwerpNo truck

Hugo works it out

  • Own fleetPlanBoth ADR drivers are off on Thursday
  • Regular carrierMemoryADR certified, used 11 times this year
  • €410RulesBelow your €450 limit for this lane

OutlookTo your regular ADR carrierDraft

Thursday 08:00, 14 pallets ADR to Antwerp. Can you take it for €410?

Needs you. Send the request.

13:40Charges desk

The work gets paid.

Hugo matches the POD to the order and proposes the waiting time, with the evidence, before the invoice run.

Driver app, truck 12

Delivered. Signed at dock 4.

Hugo works it out

  • PODPhotoMatches order 48122, 12 pallets
  • Dock 4Telematics11:28 to 13:31, 2 hours at the dock
  • WaitingContract1 hour free, so 1 hour billed at €45

InvoicingProposed

48122Supermarket, frozenReady

+€45Waiting time, 1 hourEvidence

POD and dock times attached

15:00Next-day desk

Tomorrow gets ready.

Hugo proposes the plan with your cleaning, ADR and driver rules, and flags what only a person can fix.

Planning board, Thursday

38Orders to planOpen

22Trucks, 26 trailers, 24 driversFree

Hugo works it out

  • Trailer 14RulesCarried yeast. Wash before the chocolate run
  • Genk DCRulesYour rule: one driver never goes there
  • Truck 7PlanThe driver's ADR certificate expires tonight

Plan for ThursdayProposed

37Orders on 21 tripsChecked

05:30Trailer 14 to the washRule

Needs you. An ADR driver for truck 7.

Bring Hugo in like a new planner. You decide how much it does.

  1. Shadow

    Hugo works out what it would do and changes nothing. You see how often you would have agreed.

  2. Approve

    Hugo prepares each change and waits for a planner to keep, edit or reject it.

  3. Auto

    Hugo acts inside the limits you set. A desk only gets there on its track record, and drops back to Approve when that slips.

Each desk moves on its own, and you can hold one customer back. You set a rule by saying it and confirming what Hugo understood.

Hugo's team at an example fleet, a few months in

2 of 8 desks run on their own

  • IntakeOrders from mail and PDFAuto
  • CapacityTake it or push backApprove
  • TimeslotsDock appointmentsAuto
  • Next-dayTomorrow's planShadow
  • Same-daySave today's promisesApprove
  • CustomerETAs and delays, as draftsApprove
  • ChargesWaiting time and extrasShadow
  • CharterSubcontractorsOff

"Trailer 14: never chocolate after yeast without a wash."

Confirmed by you. Every plan checks it, by people and by Hugo

  • Every change shows its reasons.

    In kilometres, minutes and euros, with the mail, scan or rule it came from.

  • Engines do the exact work.

    Plans, driving times, tariffs and invoices are calculated, the same way every time. Hugo explains the result. It never guesses a number.

  • Some things stay yours.

    Hugo never signs a consignment note. Messages to customers and subcontractors, and invoices, wait for a person at every fleet. Only you can change that.

Start next to the TMS you have. Grow into ours, one step at a time.

Each step goes live on its own, and you decide when the next one opens. Your TMS keeps running until you switch it off. Try it.

  1. Base

    One view of every load.

    Always on
    • Every order, trip and message from your systems in one place.
    • Addresses cleaned, also where a town has a French and a Dutch name.
    • Your rules learned from your own history.
  2. Plan and communicate

    Customers know before they ask.

    • Orders read and completed.
    • Tomorrow's plan proposed, today's repaired.
    • ETAs and messages before the phone rings.

    Prove and document

    No more paper.

    • A driver app with scans and e-POD.
    • Electronic consignment notes.
    • Waiting time and extras charged with evidence.
  3. Run operations

    Trips live in HUGO.

    • Orders, trips, drivers and driving time.
    • Cross-dock, yard and containers.
    • Vehicle maintenance and Mobility Package checks.

    Needs the two steps above

    Full TMS

    Your old TMS can go.

    • Contracts, tariffs and quotes.
    • The invoice run, with Peppol and self-billing.
    • Margin per trip and per customer.

    Needs Run operations

  • Keep your TMS

    Hugo works on the TMS you run today and writes every change back. You can stay this way.

  • Grow into HUGO

    Switch on one step at a time. Before a step moves, HUGO is compared with your TMS until both agree. For two weeks after the move you can still switch back.

  • Replace your TMS

    Is your TMS reaching its end? Move in one migration. HUGO is compared with your old TMS first, and for two weeks after you can still go back.

Ask your own AI. It answers from your real operation.

Connect Claude, Copilot or ChatGPT to HUGO. It reads your orders, trips and times with the same rights you have in HUGO. Changes stay with Hugo and your planners, and every read is logged.

Your assistant, connected to HUGORead-only

Which customer did we deliver late most often last week, and why?

The wholesaler in Aalst. 3 of 14 drops were late, all on Tuesday morning. Dock 2 was closed and the trucks waited for dock 5.

Stop timesSite notesExample fleet

Built for carriers that run their own trucks. Whether your TMS stays or is on its way out.

Every desk runs a little differently. If yours spends its day in mail, portals and phone calls, or you are choosing your next TMS, we would like to hear how it works.

See Hugo at work.

A 30-minute demo of what Hugo takes off your desk, and how a fleet grows into HUGO.

Book a demo

Questions

Do we have to replace our TMS?

No. Hugo starts on the TMS you run today and writes every change back to it. You can stay that way. If you want to move, HUGO takes over one step at a time, or in one migration when your TMS reaches its end.

How does a step move from our TMS to HUGO?

First Hugo works on your data while your TMS keeps the record. Before a step moves, we reconcile the data and compare HUGO with your TMS day by day, until both agree. After the move your old TMS keeps getting copies, and for two weeks you can switch back in one step.

Does Hugo message customers on its own?

Not unless you decide so. Every message to a customer is a draft that a planner sends. Later you can let routine messages go out on their own, once the desk has earned it on its track record and two of your people sign off. Messages to key accounts stay with a person.

Which TMS does it work with?

Tell us which one you run. The connection is built per TMS, from real use on that system. We tell you plainly where yours stands: what Hugo can read, and what it can write back.

Is this a planning optimiser?

No. An optimiser sits behind tomorrow's plan, and engines calculate driving times, tariffs and invoices. Hugo does the work around them, from the order coming in to the invoice going out, and explains every result.

When can we start?

We are choosing the first fleets to start with in 2027. Hugo starts on your current TMS. The steps follow one by one, and the full TMS comes last. Each step is switched on when it is ready for your fleet, and not before.

What happens to our data?

Orders, customers and prices stay yours, hosted in the EU. Every change records who made it and why. With your consent, site facts such as real dock times may later be pooled across fleets. Prices and volumes never are.