The people behind the work.

The problems we get called about are rarely new. A process has outgrown the spreadsheet that ran it. 2 systems that were supposed to share data do not. An automation somebody built has quietly stopped, and the work has gone back to being done by hand. A product does most of the job, and the team works around the rest. The tools to fix every one of these exist. What is usually missing is a person who will own the whole problem, from the first conversation to the day it runs on its own.

We started Mantelin to be that person. We have spent our careers on both sides of the work: building software for other people, and running the systems a business depends on, on-call included. So we build what we would be willing to run, and then we run it.

We keep the engagement small on purpose. You talk to the people doing the work, and we stay on after launch, because software is not finished the day it ships.