
A genomics application, a laboratory instrument, and a biotech marketing website call for different design experiences. If you are hiring a partner for scientific software, the useful question is whether that team has worked through problems resembling yours: unfamiliar terminology, complex data, specialist users, and workflows that must preserve scientific meaning.
This shortlist compares five design agencies with publicly described work on scientific software or instrument-related digital experiences. It focuses on the products researchers and laboratory teams use.
Publisher disclosure: This article is written for Dworkz and includes Dworkz. It is a publisher-authored shortlist, not an independent ranking. Agencies appear alphabetically by the names shown below. Dworkz receives the same evidence requirements and qualification questions as the other firms.
Research date: October 23, 2026.
How we selected these agencies
We searched for agencies working on life-sciences UX, scientific software, laboratory interfaces, and bioinformatics, then reviewed relevant pages on the agencies’ own websites. Searches included “UX design agencies scientific software life sciences” and targeted searches for named scientific projects.
An agency qualified when its public material identified a relevant software or instrument-interface project and described a design contribution. A life-sciences industry page, a client logo, or a marketing website alone was insufficient. Named self-initiated scientific tools qualified alongside client projects.
For each agency, we compared:
The scientific product or workflow described.
The agency’s stated contribution to research, interface design, visualization, prototyping, or implementation.
The type of engagement that evidence suggests exploring.
A specific question buyers should resolve before hiring.
The fit assessments below are our editorial judgments based on those sources. They are not measured performance ratings. We did not interview the agencies or their clients, audit delivered software, or obtain comparable proposals. Availability, current staffing, fees, and minimum engagements remain unverified.
This is a selective shortlist, not a census. Older projects establish relevant history but should prompt questions about recent work and team continuity. We make no claim that this is the only list in the niche or that these are the only qualified agencies.
Comparison at a glance
Agency | Public project evidence | Fit suggested by that evidence | What to verify |
|---|---|---|---|
BioDesign at Science Practice | Sequence Bundles, a bioinformatics visualization tool | Scientific data exploration and research prototypes | Recent comparable work and production support |
Dworkz | Cellanome collaboration, described in its design and development article | Scientific workflows needing close design and engineering collaboration | Exact project ownership, artifacts, and validation scope |
Guidea | Biological-data applications needing UX research and testing | Relevant product scope and assigned specialists | |
Indicius | Columbia University’s ACGEN, a genomic-analysis platform | Research software redesign and reusable interface components | Recent scientific work and implementation responsibilities |
Native | Cellanome platform, spanning physical and digital design | Instruments where hardware and software interactions are closely connected | Boundaries between interface design, engineering, and software delivery |
BioDesign at Science Practice
BioDesign is Science Practice’s team focused on life-science digital tools. Its stated services include user research, interface design, prototyping, information architecture, and data visualization.
Its Sequence Bundles project provides a concrete example. Science Practice describes designing and developing a web application for visualizing biological sequence alignments, working with researchers at the European Bioinformatics Institute and testing with bioinformatics researchers.
Why consider it: The work is relevant when the central challenge is helping scientists explore and interpret complex data. It offers a useful example of scientific inquiry informing the visualization itself.
What to verify: The linked project account dates to 2015. Ask for a recent comparable engagement, who would conduct the scientific research, and how a prototype would become a maintained production application.
Dworkz
Dworkz focuses on design and development for data-driven B2B products. In its published account of the Cellanome collaboration, it describes designers and engineers working together on software involving complex assays and dynamic cell biology.
Why consider it: This experience suggests a fit for scientific product teams that need interface decisions and engineering constraints resolved together. It is particularly relevant to a brief centered on translating specialist workflows into usable software.
What to verify: The public article is a process account, with less project detail than a dedicated case study. Ask Dworkz to show its precise contribution, representative workflows, and the research or testing behind key decisions. Establish the required validation and documentation responsibilities in the scope.
Dworkz should meet the same evidence threshold as every other agency on this list. Inclusion here does not establish suitability for every scientific or regulated product.
Guidea
Guidea’s health portfolio identifies Genedata work involving web application design and testing for genetics and biosafety. It also identifies UX research and design for Pattern.bio in clinical diagnostics.
Why consider it: Those examples make Guidea worth discussing with teams whose scientific applications require research and testing alongside interface design. Its portfolio connects scientific software with a broader range of health-product experiences.
What to verify: The portfolio summaries do not establish the complete scope of each engagement. Ask which Genedata product and workflows the team worked on, what testing it performed, and which specialists would join your project. Define any human-factors or validation work explicitly rather than assuming it follows from the agency’s broader portfolio.
Indicius
Indicius documents its work on ACGEN, Columbia University’s genomic-analysis platform. The case study describes expert interviews, analysis of an existing prototype, interface redesign, and a documented design system intended to support Columbia’s internal developers. The project is dated 2019.
Why consider it: This is a useful example for research teams moving from a functional prototype toward an interface that can grow and be maintained internally. The case study connects the design work to a specific scientific application.
What to verify: Ask for recent scientific projects and examples of how design decisions were tested with researchers. Clarify the division of front-end work between the agency and your developers. A design system is valuable only if the implementation team can use and maintain it.
Native
Native’s Cellanome case study describes an engagement spanning instrument design, consumables, and digital experience. Its reported deliverables include production-grade CAD models, material and finish specifications, appearance prototypes, and detailed UX/UI flows.
Why consider it: Native is a relevant candidate when the product includes tightly connected physical and digital interactions. An instrument team may need to consider loading consumables, operating hardware, and navigating software as one continuous experience.
What to verify: Ask which software deliverables Native would own and which would sit with your internal team or another partner. Distinguish interface flows from production software implementation, and request examples close to your instrument’s operating context.
Both Native and Dworkz publicly describe Cellanome work. Their inclusion reflects their separately reported contributions; it does not establish shared scope, a subcontracting relationship, or sole ownership by either firm.
How to choose a scientific software design partner
Start with one difficult workflow. “Improve our scientific platform” leaves too much room for agencies to propose different problems. “Help researchers compare experimental runs while retaining sample context” gives them something concrete to investigate.
Include the users, inputs, outputs, known failure points, and technical constraints in your brief. Explain which decisions the interface supports and which information must remain visible throughout the workflow.
Then ask each shortlisted agency the same questions:
What similar work did your proposed team personally deliver? Request a walkthrough of decisions and artifacts, including contributions made by the client or other partners.
How will you learn the science? Look for a plan involving domain experts and representative users, with time to resolve unfamiliar concepts.
How will you evaluate the design? Ask which tasks users will attempt, what will count as a successful outcome, and how findings will change the interface.
What happens when the workflow fails? Discuss incomplete data, interrupted operations, ambiguous results, recovery, and handoffs between people.
Who owns implementation and maintenance? Clarify responsibility for components, documentation, accessibility, testing, and changes after launch.
What does the proposal actually include? Compare the same deliverables and assumptions, including research recruitment, review cycles, engineering support, and any required validation activities.
A small paid discovery engagement can make the comparison more concrete. Useful outputs include a workflow map, a prototype of one difficult interaction, findings from representative users, and a delivery plan with explicit responsibilities. Agree on what that phase must answer before commissioning it.
Choosing by project fit
For a new scientific visualization, BioDesign’s published work offers a relevant starting point. For a research application and reusable interface system, examine Indicius’s ACGEN example. Guidea’s portfolio merits discussion when biological-data interfaces and testing are central to the brief. Dworkz is worth evaluating where scientific workflows require close design and engineering collaboration. Native’s Cellanome work is relevant when instrument and software design need to progress together.
Use those distinctions to choose whom to interview. Make the final decision on the proposed team, comparable work, a credible research plan, and a clear scope.
If Dworkz fits your brief, share the workflow you need to improve. Ask us to demonstrate the relevant experience and explain where our responsibilities would begin and end.


