How a rider with three bikes stopped losing money to missed servicing

Rezaul rides. He also lends. Between himself, his brother and a cousin who borrows it most weekends, he runs three motorcycles: a commuter he uses daily, a larger bike for highway trips, and an older one that mostly sits and occasionally saves the day.

Service records lived in a shoebox. Not metaphorically — an actual shoebox, with thermal receipts that had faded to blank in about eighteen months.

The moment it became a real problem

He sold the older bike. The buyer asked a reasonable question — when was the chain last replaced? — and Rezaul genuinely did not know. He guessed "maybe a year ago". The buyer heard uncertainty and negotiated accordingly, and the sale closed about eight thousand taka below where it started.

Eight thousand taka is not a catastrophe. But it was entirely a documentation problem, and that stung more than the number.

What he tried before an app

• A notebook in the toolbox. Lasted three months. It was never present at the workshop, which is the only moment the entry could realistically be made.
• Photos of receipts in the gallery. Better, and still useless — a thousand photos with no structure means you can't answer "when was the chain done" without scrolling for ten minutes.
• A spreadsheet. Lasted two entries. Spreadsheets on a phone, standing in a workshop with oily hands, are a fantasy.

The pattern is consistent: the record has to be created at the workshop, in under thirty seconds, one-handed. Anything that requires "I'll enter it properly later" produces no records at all.

What changed with a structured log

The odometer field is the whole point

Rezaul's instinct was to record dates. Service intervals are not date-based, they are distance-based, and a log without odometer readings can tell you what happened but never what is due. Once every entry carried a reading, the app could tell him the highway bike was 900 km past its oil change — something no shoebox could have said.

Shared bikes need per-vehicle, not per-person, records

Because his cousin rides the highway bike most weekends, distance accumulates without Rezaul noticing. Tying the log to the vehicle rather than to a rider is what made the reminders correct. This is obvious in retrospect and was not obvious at the time.

The fuel log found a fault before the bike did

Six weeks in, the commuter's kilometres-per-litre drifted down across four consecutive fill-ups. Nothing felt wrong to ride. It was a clogged air filter, caught in the fuel numbers well before it would have been caught by feel. That single catch paid for the habit.

The reminders are what you install it for. The fuel trend is what makes you keep it.

The resale conversation, second time round

He sold the commuter eighteen months later. This time the buyer got a printed history: every service, dated, with odometer readings and costs. The chain question was answered in four seconds.

The bike sold at asking price. We would not claim the log added value in any measurable way — what it removed was the buyer's leverage. Uncertainty is the discount, and documentation is what deletes it.

What we'd tell the next owner

1. Record at the workshop or not at all. If the entry takes more than thirty seconds one-handed, it will not happen. Optimise for that moment specifically.
2. Always capture the odometer. Skipping it turns a maintenance log into a diary, which is pleasant and useless.
3. Track the vehicle, not the rider. Especially if anyone else ever borrows it.
4. Watch the fuel trend, ignore the fuel number. Absolute mileage means little; four consecutive fill-ups trending down means something.
5. Back it up. A phone lost with two years of history is worse than the shoebox, because you'd stopped keeping the paper.