How the pieces fit together
Read in isolation, each guide looks like a separate subject. In play they are one loop, and most early mistakes come from treating a link in it as independent.
It starts at the contracts board. A job names a pickup, a destination and a load, and the load is the first constraint: weight and volume decide which of your vehicles can take it at all, and some categories refuse anything but the right kind of van. Choosing the contract is really choosing the vehicle, and choosing the vehicle is committing to that vehicle's appetite for fuel and its tolerance for a long day.
Then somebody has to drive. You can do it yourself, or hand the job to a driver — and that choice is not only about your time. A hired driver takes their share, brings their own habits to the road, and will not always pick the line you would have picked. Skill shows up as speed and as steadiness, and both feed straight into the next link.
The route is where the trade-off becomes visible. The same delivery can be run three ways, and the fast line is not free: hurry raises the odds of something going wrong, and something going wrong lands on the cargo. Fragile loads arriving shaken are worth less than the same loads arriving intact, which is why a route decision is really a risk decision.
What survives all of that is your margin — and the road has already taken a bite out of it. Fuel is gone, components are a little more worn than they were this morning, and the vehicle is now parked wherever the job ended rather than where you would like it to start. That last detail matters more than it sounds: the next contract begins with the drive to its pickup point, and you pay for that leg too.
Whatever is left is what you reinvest — in a bigger vehicle, in another driver, or in the company licence that makes hiring properly possible. Then the loop runs again, with more moving parts.
Where to start
You have never played. Read your first delivery and stop there. It covers the first twenty minutes end to end — the starting car, reading the board, getting a load to its destination — and nothing beyond what you need for that. The How to Play page is its companion.
You are about to hire someone. Read hiring and managing drivers first, then contracts and payouts. The order matters: what a driver costs you only makes sense once you know how a job pays. Hiring before that is how people end up delegating work that was never worth delegating.
You are losing money and cannot see where. Fuel, wear and repairs is the honest answer most of the time — running costs are quiet and cumulative. If losses arrive in sudden lumps instead, the culprit is on the road: read cargo integrity, accidents and breakdowns and then reconsider your route strategy.
You are choosing what to buy next. Vehicles and the Showroom alongside cargo types. A vehicle is only as good as the contracts it unlocks, and the contracts you see depend on what you can already carry.
What these guides deliberately leave out
You will not find payout tables here, or a spreadsheet of what each cargo class is worth, or a formula for calculating a job's profit before you accept it.
That is a choice, not an omission. A tycoon game where the optimal move can be looked up stops being a game about judgement and becomes a game about reading the manual correctly. We would rather you learn the economy the way you would learn a real one — by running it, noticing which jobs left you better off, and building a feel for what a route is worth before you commit a vehicle to it.
So the guides explain what depends on what: why a heavier vehicle is not automatically a better one, why the fastest route is not automatically the most profitable, what a driver's skill is actually buying you. The numbers behind those relationships live in the game, and they move as we balance it.
Keeping the guides honest
Everything here is written against the build that is live right now, not against a design document. When a mechanic changes, the guide describing it changes with it — and if you find a page that no longer matches what you see in game, that is a bug in the page, and we would like to hear about it through the contact page.
The devlog records what changed and when, in the developers' own words. If a guide surprises you, the devlog is usually where the surprise came from.