Back to Main PageThe product site and storefront for a boutique instrument maker — a bilingual launch page for the UDS-16 Soviet drum synthesizer, with the plugin catalogue, audio demos, learning material, a blog, and the purchase flow.
This case study focuses on the delivery constraints, product choices, and workflow decisions that shaped the build.
Product site and storefront
English and Russian
UDS-16 drum synthesizer
Sell a niche instrument to musicians who buy on sound. The site has to carry the character of the product — rare Soviet drum circuits, rebuilt as a synthesizer — and then get out of the way of the purchase.
A launch page that has to do three jobs at once: convince on aesthetics, explain an unusual synthesis approach to people who know the subject, and run a time-limited launch offer without looking like a discount store.
A bilingual product site where the instrument, the demos, the story behind the circuits, and the buy button live on one page — with the catalogue, learning material, and blog behind it.
Tapechild makes drum synthesizers modelled on rare Soviet hardware — the UDS-16 is built from two original circuits plus one of the company's own, and it synthesizes every hit as you play rather than triggering samples.
Selling that to producers is not a specification problem. They already understand plugins; what they are deciding is whether this one has a character worth having. The site is built around that decision.
The landing page opens on the instrument itself, in a dark, photographic treatment that puts the hardware ancestry in front of the visitor before a single feature is named. The headline states the proposition — the machine is rare, the signature is yours — and the interface of the plugin is shown directly underneath it, knobs and all.
The launch offer is carried in a slim bar at the very top and repeated once under the buy button, with the original price struck through and the end date stated. It is present at both decision points and absent everywhere else, which keeps a limited-time price from reading as a permanent discount.
Behind the launch page sits the rest of the argument, arranged as a sequence rather than a menu: the instruments the company makes, an audio section to hear them before reading anything, an explanation of where the sound comes from, and the account of how a hardware study became a record.
The technical claims live in that sequence — four synthesis models drawn from two rare Soviet circuits and one of the company's own, sixteen-voice polyphony, twenty presets, kicks, snares, hats, toms and metallic percussion, no samples anywhere in the signal path.
For a plugin purchase, compatibility is the last blocking question, and it is answered on the page rather than in a support article: VST3, AU, and standalone, on macOS and Windows.
Stating it plainly at the point of sale removes the most common reason a producer abandons a checkout — uncertainty about whether the thing will open in their session at all.
The site runs in English and Russian from a switcher in the header, reflecting an audience split between an international plugin market and the region the original hardware came from.
The two languages are the same site rather than two sites: the catalogue, the offer, and the blog are shared, so a launch does not have to be executed twice or fall out of sync between them.
Beyond the storefront, the site carries a learning section and a blog. For an instrument built on unusual circuits, that material is not marketing filler — it is how a buyer learns what the machine does and why it behaves the way it does.
It is also how the site earns search traffic between launches, which for a small catalogue is the difference between a page that only works during a campaign and one that keeps selling afterwards.
A content-led storefront: a marketing site with a product catalogue, audio demos, editorial sections, and a purchase flow, served in two languages from one content model. The visual weight sits on the launch page, where photography, the instrument interface, and the offer have to hold together on both desktop and mobile.
If you are scoping a marketplace, customer portal, or workflow-heavy MVP, start with the smallest transaction that proves the business works. Then estimate the cost, compare custom code against no-code, and decide which features belong in version one.
A marketplace listing sells on category and price. An instrument with a distinct character sells on story, sound, and the reason it exists — none of which fit a listing template. Owning the page is what makes the argument possible, and the direct sale keeps the margin.
By bounding it. The price appears at the two moments it is relevant — before the visitor starts reading and again at the buy button — with the end date stated, and nowhere else on the site. A discount that follows the visitor around reads as the real price.
Only if it is built as two sites. Sharing one content model means the catalogue, pricing, and posts exist once and are presented in either language, so a launch is executed once rather than twice and the versions cannot drift apart.
Yes. Digital products — plugins, templates, courses, licences — share a shape: a landing page that has to convince, a catalogue, a checkout, and editorial content that keeps the page alive between launches. The fastest next step is to estimate the scope.
Book a free founder call. We'll help you figure out what to build first, what it'll cost, and how fast we can launch it.
Limited availability — email alex@shipkit.us or use the contact page to start the conversation.
