YOUR IMPACT AT UMH
Hi, this is team UMH.
Who we are. 8 years ago, we were frustrated with the state of data infrastructure in manufacturing. Companies paid millions per year for outdated software from the 90s. They still do. There is much better technology out there, built on open source, and we’ve spent the last 8 years building it.
What we build. We build a data platform for manufacturing. It connects machines across all major industrial protocols, models data to industry standards like ISA-95, and feeds it into systems where users can build applications and automations on top. The whole thing is open source, which matters for partners. A partner can evaluate UMH, build a demo for a customer, and make a recommendation before any commercial agreement with us exists. They can prove value before a contract is signed. That changes the onboarding conversation.
Where we are. We’ve gone from a GitHub project to an enterprise platform trusted by Böllhoff, Hipp, and Edeka. The incumbents in industrial data management are slow. We’re not.
The partner opportunity. System integrators are finding us through the community. OEMs are reaching out. The partners who are already on-site at manufacturers, running OT projects, integrating ERP, maintaining SCADA, are the ones who spot a UMH-shaped problem and make a warm introduction. We’re not capitalising on that at all.
This role. You build the partner program from zero, but go deep enough on each partner that it looks like an alliance, not a contact list. You recruit and activate a focused set of high-potential partners, invest in each relationship with the rigour of a joint business plan, and simultaneously think about the bigger picture: which partners complement each other, which segments are uncovered, and how the open-source community connects to the commercial side.
You’ll love this if you want to:
Who we are. 8 years ago, we were frustrated with the state of data infrastructure in manufacturing. Companies paid millions per year for outdated software from the 90s. They still do. There is much better technology out there, built on open source, and we’ve spent the last 8 years building it.
What we build. We build a data platform for manufacturing. It connects machines across all major industrial protocols, models data to industry standards like ISA-95, and feeds it into systems where users can build applications and automations on top. The whole thing is open source, which matters for partners. A partner can evaluate UMH, build a demo for a customer, and make a recommendation before any commercial agreement with us exists. They can prove value before a contract is signed. That changes the onboarding conversation.
Where we are. We’ve gone from a GitHub project to an enterprise platform trusted by Böllhoff, Hipp, and Edeka. The incumbents in industrial data management are slow. We’re not.
The partner opportunity. System integrators are finding us through the community. OEMs are reaching out. The partners who are already on-site at manufacturers, running OT projects, integrating ERP, maintaining SCADA, are the ones who spot a UMH-shaped problem and make a warm introduction. We’re not capitalising on that at all.
This role. You build the partner program from zero, but go deep enough on each partner that it looks like an alliance, not a contact list. You recruit and activate a focused set of high-potential partners, invest in each relationship with the rigour of a joint business plan, and simultaneously think about the bigger picture: which partners complement each other, which segments are uncovered, and how the open-source community connects to the commercial side.
You’ll love this if you want to:
- Build the relationships that create inbound pull. The best partners refer deals without being asked, because they trust you, understand the product, and know how to pitch it. Getting there takes consistent relationship work, real investment in the partner’s success, and the patience to build before you harvest. You’re energised by that kind of long-game work.
- Enable partners to spot and introduce, not just to know you exist. A partner who can walk a shop floor, recognise a problem we solve, and make the introduction: that’s your output. You build the enablement that gets them there. Opportunity spotting frameworks, ICP education, warm introduction mechanics, reference material that makes the conversation easy.
- Design the commercial model, not just run it. What do partners earn for a warm introduction when they can’t bill implementation hours? How do you structure referral economics that actually change partner behaviour? How do you build attribution mechanics your own sales team trusts? These are unsolved problems. You solve them.
- Build the program with the precision of someone who has done it before. You know what to build in month one and what to defer. You know which parts of a partner program create real leverage and which are theatre. You bring a tested methodology and apply it with discipline, not enthusiasm.
- Run partner relationships like a pipeline. You have a framework for partner health that goes beyond “are we talking.” Activation rates, deal registration cadence, pipeline contribution, QBR outcomes. You track all of it. Within 90 days of signing a partner you know whether they’ll contribute. You make the call on where to invest more and where to disengage, and you back it with data.
- Put UMH in rooms we wouldn’t otherwise be in. The partners in your network are already inside manufacturing companies. They see problems before a budget exists and before a vendor has been invited. When they spot something we can solve, they should think of us first and know how to make the introduction.
- Make sales easy. You’re successful when an AE picks up a warm introduction from a partner and closes it faster than they would have cold. Getting AEs to trust, prioritise, and work within the partner motion, especially at a company where direct sales is the default, is one of the hardest parts of this role. You know how to build that trust without authority.
- Lay the foundation for what comes next. Today’s motion is referral-based. The next phase is delivery partners who implement UMH independently at scale. You’re building toward that from day one: identifying which partners have the technical depth to get there, running early enablement, designing a program that grows with us.