FleetGo
← Back to home

Features

Five honest capabilities. Zero feature pile-on.

Capture, remind, flag, see, maintain. That's the product. Everything in the $9-per-item core — including photo-of-meter logging and repair flagging — is built to be used by every role on a job site.

5:00
●●●4G▮▮

FleetGo · 5:00 PM

Log today's hours?

CAT 320 #104 · Last: 4,812.6

Pinned

CAT 320 #104✓ logged
Skid #09needs
Lowboy 48'needs

End-of-day push → one-tap log

01 · Capture

Capture

The two-second daily habit: log hours by typing or by photographing the dash. Trailers and no-meter equipment use a status check-in instead.

  • One-tap asset picker — favorites pinned to the top
  • Photo of the dash with on-device OCR (Tesseract local-first; Gemini fallback)
  • Multi-meter: HOURS for yellow iron, ODOMETER for trucks, status-only for trailers
  • Suggested last reading; jump-detection if it looks unrealistic
  • Quick chips: Fuel · Grease · Issue · All good
5:00
●●●4G▮▮

CAT 320 #104 · Photo log

Engine hrs

4,851.2

REC

Detected reading

4,851.2

Last reading 4,812.6 · Δ +38.6 hrs

Photo of dash → confirm reading → done

02 · Remind without nagging

Remind without nagging

Push reminders that respect the crew. End of day by default; configurable per fleet.

  • End-of-day push at 5 PM or your shift end
  • Optional start-of-shift opening reading
  • Gentle nudge for assets still missing a reading
  • Per-driver mute window for vacation / weekends

Reminder copy (samples)

Defaults: end-of-day at 5 PM or your shift end; optional start-of-shift prompt. Copy stays short — operators decide in a glance.

End of day (default)

Log today's hours?

5:00 PM

CAT 320 #104 · Last reading 4,812.6 — tap to update before you roll out.

Start of shift (optional)

Start shift — opening reading

6:45 AM

Select the unit you're running today and confirm start hours.

Gentle nudge (if enabled)

Still open: 2 assets

8:15 PM

Lowboy 48' and skid #09 need a reading for today. Takes ~20 seconds.

Manager / Mechanic alert

🔴 Urgent: skid #09 flagged out of service

2:13 PM

Driver M. Ortiz — “hydraulic line leaking, parked at south yard.” Tap to view photo.

Auto-flag (hour-based PM)

🟡 PM due: Excavator 320 #104

Auto

Hit 5,000 hrs — service interval reached. Mechanic dashboard updated.

03 · Repair flagging & alerts

Repair flagging & alerts

Anyone in the field can flag an asset in seconds. Red flags page managers and mechanics on the spot.

  • Yellow = needs repair (routine), Red = urgent / out of service
  • Optional photo + voice-to-text note attached to the flag
  • Push alerts on red flags; SMS fallback if push fails
  • Auto-flag at hour-based PM intervals (no CMMS project)
  • Mechanics resolve with notes + photos — works offline

Mechanic · Queue

Sorted by urgency

  • Skid #09

    Hyd line leaking — flagged 2:13 PM by M. Ortiz

    Photo attached · 2,167 hrs

  • CAT 320 #104

    PM due — passed 5,000 hr interval

    Auto-flag · 4,851 hrs

  • Light tower #03

    Approaching 250 hr filter change

    Auto-flag · 612 hrs

  • F-450 #211

    On schedule

    Last service 1,200 mi ago

04 · Visibility

Visibility

One honest view of utilization and hours — without a TMS science project.

  • Manager dashboard: fleet list with current hours + utilization %
  • Mechanic dashboard sorted by urgency and hours-to-service
  • Week / month rollups per asset and per yard
  • CSV / PDF export for the spreadsheet your office already runs

Fleet · Today

5 units · 2 active flags

Logged today

92%

Urgent flags

1

Hrs this week

1,240

CAT 320 #104
4,851.2
Skid #09
2,167.4
Lowboy 48'
1,022.0
F-450 #211
78,431 mi
Light tower #03
612.5

05 · Maintenance

Maintenance

Service intervals tied to real meter hours, not someone's calendar guess.

  • Set a service interval once per asset type (e.g. every 250 hrs)
  • Auto-flag yellow when an asset crosses the threshold
  • Hour history visible to mechanics — no lookups across systems
  • Photo on flag is searchable later if a dispute pops up
5:00
●●●4G▮▮

FleetGo · 5:00 PM

Log today's hours?

CAT 320 #104 · Last: 4,812.6

Pinned

CAT 320 #104✓ logged
Skid #09needs
Lowboy 48'needs

End-of-day push → one-tap log

Vs. the alternatives

Why fleets pick this over the spreadsheet — or the enterprise TMS

FeatureSpreadsheet / clipboardEnterprise TMSFleetGO Hours
Cost on a 25-truck fleet
Free (and chaotic)
$1,200–3,000/mo + onboarding
$225/mo
Time to first log
Whenever someone opens the file
8–12 weeks of rollout
Same day
Drivers / operators included
Unlimited (and unmanaged)
$ per seat
Unlimited, no charge
Offline logging
If they remember to write it
Sometimes (varies)
100% offline, syncs later
Repair flagging from the field
Texts to mechanic
Workflow rollout required
3 taps, push to manager + mechanic
Hour-based PM alerts
Manual calendar reminders
Available, configuration-heavy
Set once, auto-flags forever
Photo of dashboard / meter
Rare
Built in to the log step
Cancel / export your data
It's already yours
Contract-dependent
Anytime, CSV + PDF

Pricing — without the seat math

Per tracked asset. Unlimited users. That's it.

$9 per item per month annually, $7 at 50+ items, $12 month-to-month. Drivers, mechanics, and managers don't add to the bill — the truck or loader does.

FAQ

Feature questions, answered

What about trailers and other equipment without an hour meter?

Trailers, attachments, and no-meter vehicles get a status check-in instead of a numeric reading: In use / Idle / Out of service, with optional photo + note. Same flag flow, same dashboard, same map. Service intervals for these fall back to date-based PM.

Hours, miles, both — how does the app handle a mixed fleet?

Each asset has a meter type: HOURS (yellow iron, gensets), ODOMETER (pickups, vans — miles or km), or NONE (trailers, attachments). Drivers see the right input automatically; managers see units labeled correctly across the dashboard, exports, and PM alerts.

Is photo-of-dashboard logging really part of the base plan?

Yes — and it now reads the meter for you. Local OCR runs on-device (Tesseract.js, free) and detects the reading; the driver confirms or edits before save. If local OCR struggles, a server-side Gemini call covers the gap. Both paths included in the base plan.

What stays out of the core product?

Full TMS, deep warehouse workflows, advanced analytics, and video integrations stay paid add-ons. We keep the core minimal so it actually gets used.

How does offline-first work?

Hours, photos, flags, and repair logs all save to the device first. The instant a driver hits a bar of signal — driving back to the yard, walking past the office wifi — everything queues up to Postgres in the background.

Do you need OCR / AI to read the meter from the photo?

Not at launch. Drivers confirm or edit the number themselves with big buttons — no AI needed for accuracy. We can layer optional OCR later without changing the price.

Can a driver see another driver's logs?

No. Drivers see their own logs and the assets they touched. Mechanics see flagged + recently-logged assets. Fleet managers see everything for their organization. Tenant data is isolated at the database level — never mingled across companies.

Beta cohort

First 50 fleets lock $9 / item / month for life.

Hands-on onboarding, white-glove import of historic data, direct line to the team. Cancel anytime, take your data with you.