You've been through a CMMS rollout that died. So has the founder — that's why this page exists before you ever book a call. Below is the plan in writing: what happens in each 30 days, who does what, and how many hours it costs your team. The numbers are what we plan around at a 5–25 tech site — targets, not guarantees. Anyone who guarantees an implementation timeline hasn't run one.
The founder works from your exports. Send spreadsheets, a Maximo dump, paper PM sheets — whatever exists. Two CSVs carry the load: the asset registry and the PM library (templates below, downloadable today). Then the dedupe pass, done together on a call: you know which of the three "Conveyor 4" entries is real. We don't. That call is where most rollouts quietly die, so we put it on the calendar in week one.
One crew, one line. Operators on that line get the report-a-problem link. The old system stays warm — nothing gets burned in month two. A weekly 30-minute check-in fixes what the floor finds, while it's small.
Remaining crews come on. PM schedules cut over with a parallel-run week — both systems generate, we reconcile the lists. Compliance-tagged PMs move last and get verified one by one. A Title V PM never falls in a gap between systems.
Hour estimates are typical for a 5–25 tech site. This is the founder-led onboarding on the pricing page — $2,500 one-time, waived on a 2-year term.
Day 1: a login and your queue. Nothing else — no training binder, no module tour. You close your first work order at the machine, and that's the whole onboarding. If it takes longer than a smoke break to learn, we built it wrong.
Days 2–5: we load the PM library together — your frequencies, your crafts, your compliance tags. By the end of the week you're looking at the week view with your PMs on it, not demo data.
Your dashboard starts nearly empty, and that's correct — a dashboard full of numbers on day one is showing you fiction. Blocked-work counts appear the first time a tech hits a missing part. PM compliance populates as the first cycles complete, around week six.
These two files are the entire data ask. Start filling them out now if you want — or don't, and we'll map your existing exports instead.
Required: asset_id, asset_name, area. Everything else — manufacturer, serial, criticality, install year — is optional and can come later.
Download template ↓Required: pm_id, pm_name, asset_id, frequency. Craft, estimated hours, and compliance program are optional — but tag your Title V and OSHA PMs if you can, because those move last and get verified one by one.
Download template ↓Coming from Maximo, SAP PM, eMaint, or UpKeep? Send us a raw export — mapping is our job, not yours.
Our implementation includes historical import: closed work orders load as read-only history records, linked to the right assets. The history that proves a pump is a lemon shouldn't die in the old system.
The walkthrough covers this plan against your facility — your equipment list, your PM count, your crews. If the timeline above doesn't fit your plant, we'll say so on the call.