[company]
A small company with one narrow job.
Throughline exists so the Friday review stops being where problems surface. This page covers why, how the company runs, and who it hires.
[soc 2 type ii · 14-day trial · no card]
[portfolio concept]
Throughline is fictional. This page shows how a company page earns trust without inventing people: the structure is real, the specifics are illustrative, and nothing here fabricates a founder, a face, or a biography.
[01 / the reason]
Why does this exist?
Because the state of the art for finding a broken shipment is still a person, three carrier portals, and a Friday meeting.
The founding story of this category is always the same morning: a coordinator with the portals open by seven, a spreadsheet doing its best with conditional formatting, and a customer who learns about the late truck before the shipper does. Throughline was started in 2023 [illustrative] to invert that morning. The software reads the feeds; a human appears only where a decision is needed.
The product refuses the category's default ambition on purpose. It is not a visibility platform and does not want to be one: it shows nothing that is going fine. The whole company is organised around a queue that ends, detection in minutes instead of at the Friday review, an owner and a deadline on every exception, and a thread that closes itself. What that replaces is spelled out on the comparison page; who it fits is mapped by use case and industry.
[median detection, modeled default]
38 min[resolve without paging a human]
94%[illustrative product metrics · defaults from the roi model]
[02 / operating principles]
How does the company run?
Five rules, applied in order when they conflict.
-
[01]
The queue must end.A feature that adds reading without removing work is refused, whatever it demos like. The empty queue is the product working.
-
[02]
Buyer-side numbers only.The site quotes what changes for a customer, 38 min to detection, never how much freight is watched. Volume is the incumbent's frame.
-
[03]
The feed is the integration.No customer waits on an ERP project to see value. Carrier credentials or an EDI 214/990 feed is enough to start; connectors deepen, never gate. The wire-level detail is in the documentation.
-
[04]
Support can read a raw 214.Support is staffed by engineers who work the product against live feeds. Escalation goes to the person who wrote the parser, not to a tier.
-
[05]
Legal answers before procurement asks.The DPA, the subprocessor list and the retention schedule are public on the trust center, dated and versioned.
[03 / the people]
Who is actually behind it?
No one you can verify. Which is why there are no photographs.
The convention in this slot is a grid of founder headshots and a paragraph of biography each. This page skips it, and not out of modesty: Throughline is a disclosed portfolio concept, so the people would have to be invented. Fabricated executives, stock faces and generated headshots are precisely the trust theatre the rest of this site refuses, and the rule holds here too. The initials in the product screens, K. Tan and M. Osei, are illustrative operators, not staff.
What belongs here on a real site: named founders with a checkable history, photographed rather than generated, linked to work they actually shipped. The real entity behind this build is the studio credited in the footer of every page.
[no fabricated people · no stock faces · no generated headshots]
[04 / the shape]
What shape is the company?
The four numbers a buyer actually checks before betting an ops process on a vendor.
- [founded]
- 2023
- [headcount]
- 28 people
- [support first reply, median]
- 42 min
- [footprint]
- Remote-first Chicago hub
[illustrative company facts · the structure is the exhibit]
[the shorter version]
Twenty minutes beats an about page.[05 / careers]
Who does Throughline hire?
Three open roles. A careers page is a stability signal buyers check, and what makes it credible is structure: bands published, loops time-boxed, remote meant.
-
Senior backend engineer, feeds
Owns the carrier polling fleet and the EDI intake path: the parsers, the retries, the 5 minute cycle, and the 997s that go back. On call one week in six, paid as such.
[illustrative role]
-
Implementation lead
Runs the 2 to 3 week onboarding arc: history backfilled in week one, tolerances fitted in week two, first live exception before the second check-in.
[illustrative role]
-
Support engineer, EDI
Reads raw 214s for a living. Answers with the fix, then ships the parser test that keeps it fixed.
[illustrative role]
How hiring runs
-
[01]
A reply inside 5 business days, whatever the answer is. Apply with anything that shows the work: a repo, a runbook, a war story.
-
[02]
One technical conversation, 60 minutes. Take-home work is capped at 2 hours and reviewed with you, not on you.
-
[03]
A paid working session with the team you would join, on the real codebase.
-
[04]
An offer that restates the band from the listing. No negotiation theatre against your own information.
[illustrative roles and process · a portfolio piece hires nobody]
[no invented faces on this page]
[next step]
Judge the product, not the prose.
Twenty minutes with your carrier list, live on the call. Or put a number on the status quo first.