DRD Liquid Handling: Turning a Patented Mechanism into a Site Three Audiences Can Act On
DRD Liquid Handling sells a mechanical breakthrough — two pistons of slightly different diameters in one chamber, delivering nanoliter resolution with clean, contact-free release, protected by three U.S. patents. The design problem: the value is invisible, three audiences want three different kinds of proof, and buyers search the symptom, not the product. Envion designed and built drdliquidhandling.com as a single linear argument — claim, six named failure modes, mechanism, SLAS 2026 evidence, applications — that splits into Labs, OEM, and investor journeys only at the end. UX strategy, information architecture, content design, UI system, and the WordPress/Elementor build.
The client’s website
From the client’s archive to the live site
The challenge
DRD sells a mechanical breakthrough: two pistons of slightly different diameters inside one chamber, giving fine nanoliter resolution while keeping enough flow force to blow a sample off the tip cleanly, contact-free — protected by three U.S. patents.
That's a genuinely hard thing to sell on a webpage, for three reasons. The value is invisible — a photo of a pipettor looks like every other pipettor, while the differentiator happens inside a sealed chamber at volumes a person can't see. Three audiences want three definitions of proof — a bench scientist wants assay specs, an OEM engineer wants module-level integration detail, an investor wants market size, patent position, and momentum; the same page must serve all three without becoming a brochure that serves none. And the buyer often doesn't search the product name — they search the symptom: "how do I reduce pipetting error in 384-well plates," "why does liquid stick to my pipette tip." Increasingly, they ask an AI assistant rather than Google.
Decision path
Discovery ran in three tracks. Symptom-first keyword mapping: instead of building IA around the product catalogue, the work mapped the failure modes labs actually complain about — failed aspirations, hanging drops, touch-off variability, cross-contamination, reagent waste, poor reproducibility. Six named failures became the site's second section. Audience path modelling: running the three buyer types through a jobs-to-be-done exercise showed their paths diverge exactly once — after they accept the mechanism works — so the page keeps one linear narrative at the top and splits only at the bottom. Answer-engine audit: testing how LLM assistants described DRD and its competitors showed they summarise whichever page structures content as direct question → direct answer, which shaped the FAQ layer.
The homepage became a single argument, in order: claim — "Precision nano- and micro-volume liquid handling without touch-off"; problem — six named failure modes a visitor can self-identify with in under three seconds; mechanism — "Two pistons, one clean release," with the patent numbers inline as instant credibility; evidence — four hard figures from the SLAS 2026 run; fit — eight application contexts; the fork — "Two Journeys," For Labs vs For OEMs & Manufacturers, side by side; an investor lane deliberately placed after the technical proof; and eight plain-language FAQs. The deliberate call: problem before product.
Envion contribution
Envion owned the work end to end: UX strategy, information architecture, content design, the UI system, and the WordPress/Elementor build.
Key UI decisions: a CONVENTIONAL | DRD DIFFERENTIAL™ split comparison in the hero — "hanging drop, incomplete delivery" against "clean, contact-free release" — making the invisible visible above the fold; a six-card failure-mode grid, scannable at F-pattern speed, each card a search-intent landing target; a stat block with an honesty line — 0.25–10 µL, ±0.02 µL, 384 wells, 0 missed wells, scoped in small text to DRD's SLAS 2026 highlight data, converting a scientist's default skepticism into credibility; a two-column fork with equal-weight Labs and OEM paths and their own CTAs; FAQs written as self-contained, quotable answer surfaces; and a triple-CTA system where the three calls to action never appear at equal weight in the same viewport.
Delivery
Accessibility and performance were design requirements, not afterthoughts: every product image ships descriptive alt text tied to the claim it supports, so the argument survives with images off or a screen reader on; the µ character, superscripts, and patent numbers are real text — searchable, translatable, selectable; and Elementor's default section stacking was overridden on the two-column fork so the OEM path isn't buried below three screens of Labs content on mobile.
The build runs on WordPress + Elementor, structured so the DRD team can extend product pages — µL Magic 96, DPDD 1000, Titan, Little Squirt — without breaking the argument's architecture.
Outcome and evidence
The site is live at drdliquidhandling.com, carrying the full argument from symptom to mechanism to evidence to fork. Outcome instrumentation — organic sessions, demo and investor-deck requests, scroll depth — is measured by the client against GA4 rather than asserted here.
The named next steps: instrument the two-journey fork with click tracking to see the real Labs/OEM/investor split and reorder the page per segment; and add a short looping video of the clean blow-off in the hero — the still comparison works, but motion closes the argument in one second instead of three.
Client feedback
What the client says about this engagement
“Amazing. I have never seen my old stuff introduced in a digital format — nice and clean. I like it. They heard me, and they took me not to the earth but to the moon. A lot above my expectations.”
Evidence gate. This page publishes only what Envion's project records and client disclosure permissions support. Outcomes are added once verified against a baseline, a measurement period, and an approved source.
FAQ
Questions about this case
Facing a similar challenge?
Selling a breakthrough nobody can see? Envion designs the argument that makes the invisible visible — symptom-first, evidence-led, one fork per audience.
Discuss a Similar ChallengeKeep exploring
Similar case studies
Executive Technology Leadership
Support for high-stakes product and AI decisions
Bring senior technology leadership into the business when the roadmap is unclear, delivery is at risk, an AI initiative needs stronger ownership, or the company needs an experienced technical voice before hiring a permanent CTO.
Discuss Interim CTO SupportCore responsibilities
- Align product and technology priorities with business goals and measurable outcomes.
- Review architecture, delivery risks, data foundations, security needs, and AI readiness.
- Lead internal teams and external partners through a practical execution plan.
- Clarify team structure, ownership, decision rights, and delivery cadence.
- Support investor, board, partner, and due-diligence conversations with credible technical judgment.
New experience
Prompt-to-Page — try it right here
Describe the landing page you want, in your own words. We turn it into a finished page and email you a private link in 5–10 minutes — no briefs, no calls, $0 to see the result.
- Describe what you want to create.
- We structure, write, and compose the page.
- You receive a private link when it is ready.
Start with a sentence — the interactive builder takes it from there.
Generate My PageSafe, respectful content only. No obligation.