About kitwheel

Every facilities platform wants to be your system of record. None of them wants to talk to the others. So the actual integration layer of this industry is a person with two monitors, retyping work orders from one portal into another.

If you're a service provider, you live in your clients' systems, not your own: five portals, five logins, five places a status can go stale. If you're a multi-site operator, switching platforms means abandoning years of history, so you don't switch, and your vendor knows it.

Even when systems technically integrate, the data doesn't mean the same thing on both sides. One platform's "Completed" is another's "Pending Invoice." Every tenant has its own trade codes, its own priority scheme, its own dialect. Mapping that is the real work, and today it's done in spreadsheets, memory, and tribal knowledge.

We're building kitwheel to be the hub in the middle: it speaks each platform's dialect, translates statuses and vocabularies both ways, and keeps every connected system telling the same story about the same work order. Not another system of record. The layer every other system has to agree with once it's running.

Where we are

kitwheel is pre-launch. We're a small team building the first version now, working directly with early users to get the vocabulary mapping right, because that's the hard part and it's the part everyone else skips.

What kitwheel is not

kitwheel isn't another CMMS, and it's not one more portal your techs have to log into. We're not asking anyone to rip and replace what already works. We sit underneath the systems you already run and become the thing they depend on to agree with each other.

Want in early? Join the beta list.