Why we built Haveri

We've worked in both software and manufacturing. We built Haveri because we kept seeing the same gap between the two.

On the software side, we've built and used structured incident management for years. On the manufacturing side, we've been on the factory floor at 3 AM when a line goes down. We've seen shift supervisors wake people up because nobody knew who else to call. We've watched teams scroll through hundreds of chat messages trying to reconstruct what happened on a shift they weren't on. We've seen the same equipment fail the same way, three months apart, because the fix was never written down anywhere anyone could find it.

This isn't unusual. It's standard operating procedure in manufacturing. When something breaks, the group chat explodes. Three people start troubleshooting in parallel, stepping on each other. Someone eventually fixes it — somehow. Nobody records what happened. The knowledge stays with the person who was on shift, and when they're not around next time, the whole cycle starts again.

The software world figured this out years ago

In software, structured incident management has been standard practice for years. When a service goes down, there's a clear process: declare the incident, assign a severity, notify the right people, work the problem in a dedicated channel, capture everything in a timeline, and write up what happened afterward. Tools like PagerDuty and incident.io made this possible.

The result isn't just faster resolution — it's organizational learning. Every incident becomes a record. Patterns emerge. Root causes get addressed. The team gets smarter.

Manufacturing teams deal with incidents that are equally complex — often more so, since they involve physical equipment, safety considerations, and people who aren't sitting at desks with laptops. But they're doing it with group chats and phone calls.

What if there was a tool built for them?

Not an enterprise platform that costs six figures and takes six months to implement. Not a CMMS with an incident module bolted on. Not a generic project management tool repurposed for incidents.

Something that lives where these teams already communicate — in Microsoft Teams, on their phones. Something that captures what happens during an incident automatically, just by the team talking. Something that surfaces what worked last time when the same thing breaks again.

That's what we're building. We named it Haveri — the Swedish word for a breakdown, a disaster, an incident. Because pretending incidents don't happen is what makes them catastrophic. Haveri says: incidents are normal. Let's get good at them.

Where we are now

We're in early access, working with a small number of manufacturing teams to validate and refine the product. If your team manages incidents through group chats and phone calls, and you're tired of losing fixes to chat history — we'd like to hear from you.

The fix your team figured out at 3 AM shouldn't disappear into a group chat.