Launch HN: Terusama (YC W20) – We help warehouses schedule trucks

Launch HN: Terusama (YC W20) – We help warehouses schedule trucks

Hi HN, Andrew and Chris here. We’re building Terusama (https://www.terusama.com), a truck appointment system for logistics teams at warehouses and distribution centers. We automate the labor-intensive process of coordinating arrival times with a trucking company, checking a truck in at a facility, and keeping track of everything. Oh, and we have a theme song: https://www.youtube.com/watch?v=fyp4O4s5tk4

The status quo here is really antiquated software that is really hard to use. Not only is the current way of doing things inefficient for logistics folks, it has a big impact. The inefficiency created by poor supply-chain coordination costs $30B a year in the U.S. and generates billions of tons of C02, mostly from trucks idling in parking lots. On top of that, it has a huge impact on the lives of truck drivers, who are legally limited to 11 hours of driving time each day. Waiting at warehouses often eats up 3-4 of those. Those wasted hours really add up, making the job unsustainable for many and contributing to another problem in the industry - driver turnover, which is over 90%.

Most of this inefficiency is caused by the high level of friction in communication between the people who manage trucks, the drivers, and the people who the drivers are delivering to. The freight industry has made a ton of progress with software to help manage their fleets, but warehouse logistics software hasn’t caught up.

Chris and I were students together at Indiana University. We became really interested in this space at our later jobs. I was working at Uber Freight (formerly Otto), and Chris was consulting for companies in the industry. We were constantly amazed at how big and complex an issue it was, and surprised that nobody was thinking about it in the same way we were. We started talking to as many people in the industry as possbile to figure a better way to manage logistics. The result was the version of Terusama we launched with in the beginning of the year. We have been since iterating on the product with a core group of customers.

We streamline or automate most of the repetitive and administrative processes needed to keep trucks flowing smoothly in and out of a facility. We provide dispatchers at trucking companies and brokerages a way to search through facilities, and schedule directly with these facilities. When a truck driver arrives at a warehouse, we check them in at a kiosk. Our customers get a dashboard where they can track and manage loads coming to their facility. Logistics teams get visibility into their incoming trucks, the ability to communicate with drivers and carriers, and to track a load through its lifecycle (from staging through completion). Everyone involved is kept in the loop with smart notifications. In the future, an API will make it easy for anyone with a brokerage or trucking company to get facility availability (to feed into truck routing optimization), and schedule appointments. We’ll also offer services to help carriers reduce the risk of missing truck appointments.

One of the most important things we’ve learned in this time is how important reliability is for a mission-critical app. It's obvious in retrospect, but it definitely changes your approach when building an application - requiring heavier testing, redundancy, and support as a form of redundancy.

These days you hear a lot about things like autonomy and AI in the freight industry. We believe that to get the value promised by these things, we first have to upgrade the outdated technology infrastructure that currently runs the industry. Our goal is to build that infrastructure, while solving today’s pressing problems.

We’re excited to see what HN thinks of our platform. We’re eager to hear about HN users’ experiences, ideas, and know there is a ton of expertise among the community to learn from. And if you’re in the industry, we’d love to hear about your experiences with truck scheduling!

Discussion 26 comments · 69 points · adenta · 2020-03-11
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.