The Shmøergh Moduleur is an open-source analog synthesiser designed and built in Hungary. It launched as an MVP — a single YouTube video — and the response was immediate. More than 2,200 people joined the waitlist. The community understood exactly what Shmøergh was doing: honest design, open schematics, no mass-production pretence.
Demand proved the concept, not the product. A waitlist struggles to convert if the build experience breaks down in the hands of a stranger. The gap between a working prototype and a buildable, global DIY product was the real problem to solve.
I came to the project as an early adopter — saw the launch video, understood what it was trying to be, and reached out. What followed was an ongoing collaboration with the Shmøergh team throughout an end-to-end build of the first-ever DIY unit.
This wasn't a document review. It was real-world stress testing: sourcing components, following the build guide cold, hitting edge cases the team hadn't anticipated, and feeding every friction point back in real time. Circuit queries, parts substitutions, ambiguous documentation — all surfaced through doing, not theorising.
The outcome was concrete: component changes that reduced build cost and sourcing complexity, process changes that lowered the skill barrier, and a build guide rewritten to hold up for anyone, anywhere, with a soldering iron and determination.
The Moduleur shipped its first completed DIY unit — built by someone with no prior relationship to the team, on the other side of the planet. That's not a milestone for the builder. It's proof of concept for the product.
The build guide now reflects real-world conditions, not ideal lab conditions. Component choices are more globally accessible and cost-effective. The assembly sequence is tighter. The path from "waitlist signup" to "working synth" is shorter and more reliable than it was before.
A 2,200-person waitlist is a strong signal. A product that converts that signal — repeatably, globally, without hand-holding — is what Shmøergh is now positioned to deliver.
The most reliable way to find what's broken in a product experience is to be the user. Reading a build guide and building from a build guide are completely different activities. Real friction only surfaces under real conditions.
For an open-source hardware product, the build guide is the UX. Ambiguous steps, missing context, and assumed knowledge are bugs — not oversights. Treating documentation with the same rigour as circuit design is what separates a prototype from a product.
Every component that's hard to source globally, every step that requires specialist knowledge, every cost that prices someone out — these are product decisions with real user impact. Lowering the barrier to entry isn't a compromise. It's what makes the design philosophy real.
The Moduleur's waitlist didn't come from advertising. It came from a single piece of authentic content that found the right people. These are builders who've been burned before by products that promise openness and deliver complexity. They can read a schematic. They know what a BOM is. They're not looking to be sold to — they're looking to be trusted.
They watch, research, and commit before they buy. Community reputation travels fast in these circles — a bad build experience gets shared as readily as a good one. The build guide is read before a single component is ordered. Every ambiguous step is a potential dropout point, a forum complaint, or a negative signal to the next person considering the build.
The MVP YouTube video that generated 2,200 waitlist signups and proved the concept worth building on.