MaintainTime: maintenance records that reach the machine.

The operational problem

Equipment maintenance is easy to postpone when the record is somewhere else. An owner wants a complete service history. A manager needs to know what is due. An operator needs a fast way to report a fact from the field. A mechanic needs the context behind the next service. If those people are working from separate notes, the operation finds out about a missed interval when a machine is already unavailable.

The product needed to be useful across that chain without becoming a generic enterprise fleet system. The record had to stay attached to the equipment, the workflow had to work on a phone, and the system had to make a preventive action visible before a failure.

The decisions that shaped the product

Service intervals are not all calendar reminders. MaintainTime supports intervals by hours, mileage, or calendar so the rule can follow the machine and the operation. Fuel tracking and full service history stay with the same asset record, creating context instead of a series of disconnected events.

QR codes make the field entry point physical. An operator can scan the machine rather than search a list or remember an internal identifier. The product runs as a web app on a phone, which means a twenty-person crew does not need an app-store installation. English and Spanish throughout the product make the workflow more usable across the people doing the work.

What shipped

MaintainTime gives operations a shared place for equipment records, service intervals, fuel, history, and alerts before something breaks. Owner, manager, and operator roles reflect who actually touches what, while the field entry point stays short enough to use in context.

The result is not just a maintenance calendar. It is an operational record that can answer which machine needs attention, what happened previously, and who is responsible for the next action.

• Service intervals by hours, mileage, or calendar.
• Fuel tracking and full service history.
• Automated alerts before a service issue becomes a breakdown.
• QR code access from the equipment in the field.
• English and Spanish support throughout the product.
• Owner, manager, and operator roles.

What it runs on

MaintainTime is a web product built with React, Express, PostgreSQL, and Stripe. The web approach keeps the product available on a phone without requiring an app-store install, while the database keeps the equipment record available to the roles that need it.

The technical choices serve the operating model. The important part is not the stack as a badge; it is that the product can support an asset record, role-aware workflows, notifications, and client-controlled data without asking the field crew to work like office staff.

Timeline and the lesson

Atlas AG plans focused production releases in a six-to-ten-week window after discovery defines the first release. The lesson from MaintainTime is that operational specificity compounds: a QR code, the right interval types, a useful alert, and a role model can make a small product feel like it belongs to the work.

That is the standard for a custom build. Start with the moment where a missed record costs the most, then design the system around the person who has to act.

Continue

• Visit MaintainTime
• Read the logging operations software guide
• Build a workflow around your equipment

Start a build

If you already know what you want built, describe it. If you only know what is broken, that works too.

Tell Atlas AG what needs to exist