Three ways to hire the designer behind a plant-management platform running in 40+ countries. For product teams shipping industrial and B2B software. For machine builders with an HMI people have to run a shift on. For studios that need a senior product designer under their own name.
SVC 01
Product design for industrial and B2B software
A senior product designer embedded with the team that ships a plant-management platform, an industrial IoT product, a production dashboard or a data-heavy B2B tool.
For
Product teams and their owners — the people responsible for a platform that plant managers, operators and service engineers open every morning, and who need design that keeps pace with a roadmap instead of arriving after it.
What you get
- The information architecture and the data model argued, not assumed: what the people on the floor, in the office and on the phone actually need to see, in what order.
- Screens with every state drawn — loading, empty, degraded, alarmed — so a developer never has to invent one.
- A design system the team keeps after I leave: tokens, components, the rules for extending it.
- Reviews inside the build, not after it. Handoff is the middle of the job.
- A mobile companion where the work leaves the office — designed as one system with the desktop, not a second product.
Shape
Embedded, by the month, on a fixed number of days a week; or a fixed-scope project when the problem is already framed.
Proof
SCM Digital Portal · Tescam
SVC 02
HMI and machine-interface design
The screen on the machine, designed with the people who run it: from a review of what you have to a full interface system your HMI developers can build without a meeting.
For
Machine builders — packaging, plastics, machine tools, automotive, medical, process equipment — with a screen that operators fight with, or a new machine that needs one, and a team that has designed for gloves, glare, noise and a €400,000 machine that must not stop.
What you get
- Discovery on the floor with the operators, the maintenance crew and the people who buy the machine — what each of them needs to see, and when.
- The operating model before the screens: states, alarms and their priority, recovery paths, who sees what.
- The screen system with every state drawn — running, degraded, alarmed, recovering — and a spec kit your HMI developers can build from.
- Review rounds after first build, on the machine.
- Or start smaller: a written review of the interface you have, with the fixes ranked by risk and effort, and an HMI guideline document your team designs against from then on.
Shape
Fixed scope, agreed after discovery; a review on its own is measured in weeks. One fence, stated plainly in the questions below.
Proof
Low level interfaces · Strato
SVC 03
Senior design capacity for studios
Product design and, where needed, production front-end for design and development studios — white-label, under your brand, inside your process.
For
Studios and agencies with an industrial, enterprise or data-heavy client and nobody senior on product design this quarter. Particularly Northern European studios whose clients build machines, plants and the software around them.
What you get
- A senior product designer on your client calls as your team — your name on the work.
- The same build kit your client would get from an in-house lead: flows, every state, specs, a design system your developers can extend.
- Production-ready front-end when the studio needs it: I build what I design.
- Reserved capacity once we have shipped together — days held for you each month, whether or not a project is live.
Shape
By the day for a first project; by the month once we know each other. Fully white-label; NDA as standard.
Proof
A development process from nothing · Strato