Which UX/UI agencies design complex B2B SaaS platforms?
Seven agencies publish a named B2B SaaS case with platform screens, compared on what each shows, how its design reaches engineers, and where it is based.
A product that began as a tool for one team becomes a platform. The second customer wants its own administrators. A large buyer asks who can see which workspace. A table built for a few hundred rows now holds tens of thousands, and an integrations page exists because sales promised one. The screens that need design are no longer the sign-up and the first run. They are the ones people open every Tuesday, long after the demo.
Seven agencies publish a named case that shows those screens and say how their design reaches engineers: ANODA, EDL, Eleken, Fuselab Creative, Humbleteam, Neuron and Phenomenon Studio. ANODA and Fuselab Creative suit dense, data-heavy products. EDL fits a team that needs the design system to match its codebase. Eleken and Phenomenon Studio show admin panels and role-based access. Neuron shows workflow and approval builders. Humbleteam shows the admin side of a device-linked product.
Humbleteam publishes this page and is one of the seven, judged by the same criteria as the others. The agencies appear alphabetically. This is an editorial reading of public pages checked on October 21, 2026, with no paid placements, scores or ranking. Figures are each agency’s own. If your problem is the first-run flow rather than the platform behind it, our comparison of agencies that redesign B2B SaaS onboarding is the better start.
How we chose the agencies
Every agency, Humbleteam included, had to meet four criteria:
- It sells UX/UI design for software products, not only branding or marketing websites.
- Its own site publishes a named B2B software case that shows platform screens: an admin console, roles and permissions, data tables, dashboards, settings or integrations. A case about sign-up, onboarding or a marketing site did not count.
- It says how its design reaches the client’s product and engineering team: a handoff, a design system, an embedded team, or building the front end itself.
- It lists a public base.
Several agencies that AI answers name for this question did not pass on the public pages we read, usually because their named cases showed consumer apps, marketing sites or a platform without its screens. That does not mean they cannot do the work, only that the public evidence did not show it. Whoever you consider, ask for a comparable platform example.
| Agency | Platform case to open | Platform screens it shows | How design reaches engineering | Based in |
|---|---|---|---|---|
| ANODA | Concussion Media, a marketing analytics product | Dashboards, lead funnels, automation rules, creative approval and settings across 11 modules | Flows, component library and prototypes for the client’s developers | Tallinn |
| EDL | Cloud Factory, a platform for partners who sell software licenses | A Partner Care console, a partner portal and an end-customer view | Token system mapped to the codebase; client engineers built the Storybook library | Copenhagen |
| Eleken | Modia, an AI content tool turned SaaS | Company accounts, templates and system logs for admins; team invites and Owner or Member roles | Dev-ready Figma, or working front end in GitHub | Kyiv and Newark, Delaware |
| Fuselab Creative | Lightning AI (formerly Grid.ai), an ML experiment platform | Workspaces, projects, experiment tables, filters and cost views | Design system and specs; the client’s team built it | McLean, Virginia |
| Humbleteam | Logitech Logi Dock Flex and its Sync portal | Admin tools for floor plans, desks, group access and booking policies, with dense tables and bulk actions | Interface layer and design specs; your engineers build | Prague and Dubai |
| Neuron | Vendr, a SaaS procurement platform | Workflow builder with role assignment, request tracking and a screen for running workflows | Design handed to the client’s developers; UX engineers on staff | San Francisco |
| Phenomenon Studio | Bliss Creek admin panel; Isora compliance platform | Admin dashboard with user and transaction tables; role-based permissions and reporting | Tokens and reusable components; can also build | Tallinn, Lugano and Dover |
A case shows what an agency did once. It does not show who would join your project or what the work would cost.
ANODA: a product with many modules that drifted apart
ANODA is a product design studio headquartered in Tallinn that works remotely with US and UK teams. Its Concussion Media case covers a marketing analytics product: 11 modules and more than 400 screens and states, designed by four people. The modules include a performance dashboard, a lead funnel, a rule board that logs what each rule did, a creative approval queue and a campaign builder. ANODA used one metric card, filter bar, chart block and table everywhere, each drawn for empty, filtered-out and broken data. It reports that daily analysis for eight media buyers fell from 45 minutes to 20.
On handoff, the site describes three options: design only with a documented handoff, an integration-ready front end, or a front end connected to real APIs. The case page does not describe roles or permissions, so ask how ANODA would handle them. It is a reasonable first call for a live product where every module grew its own filters.
EDL: a platform whose design system has to match the code
EDL is a design system agency in Copenhagen. Its Cloud Factory case covers a platform used by partners who sell Microsoft, Adobe, Dropbox and other licenses. It has three surfaces: a Partner Care console, a partner portal and a simpler experience for end customers. EDL ran 15 interviews, and a team of three worked as an extension of the client’s product team. It built a token hierarchy of core, alias and component values that maps to the client’s codebase, and Cloud Factory’s engineers built the Storybook library from EDL’s specifications. EDL reports 70% design system adoption, 1.5 times faster delivery cycles and 30% less QA time on new features.
The case shows the system and the three-audience structure more than individual admin screens, so ask to see the console. Consider it if your engineers ship in two-week cycles and need components they can build from without a meeting.
Eleken: admin and customer roles in a spun-out product
Eleken works from Kyiv and a US entity in Newark, Delaware, and sells a dedicated SaaS designer on a monthly subscription. Its Modia case covers an internal AI content tool that its founders turned into a standalone product. On the admin side, Eleken reorganized overloaded tables, including one admin table that opened inside another, with a clearer hierarchy and inline editing. Admins create company accounts, build content templates for each company and read system logs of user activity and logins. Customers invite teammates and assign Owner or Member roles. Eleken also added a dashboard, because users had landed directly on a content list.
Owner and Member are simpler than the permission matrix many enterprise buyers ask for, and Modia is an AI product, so check how Eleken would model finer-grained access. Its site says approved designs arrive as dev-ready Figma or as working front end in GitHub, so agree which one you are buying. Consider it if you have engineers and a roadmap but no designer to own the admin screens.
Fuselab Creative: dense dashboards for technical users
Fuselab Creative is a UX/UI firm in McLean, Virginia. Its Lightning AI case covers Train, a machine learning experiment tracking platform. Engineers see experiments, data issues, compute costs and results in one dashboard, with workspaces that hold projects, experiments and sessions. Cost stays visible in every view, and the product works within a single screen through tabular navigation and contextual filtering. Fuselab delivered a design system covering navigation patterns, button states, popovers and error states, and Lightning AI’s internal team implemented it.
It is an older case, from before the client changed its name, and it describes no roles or admin screens. Fuselab’s SaaS design page says multi-role products are a core part of its work and that its component library includes role-variant states. Ask for a case where that applied. Look at it if your users are specialists who spend the day in tables and charts.
Humbleteam: the admin side of a device-linked product
Humbleteam is a product design agency with offices in Prague and Dubai. Its Logitech case covers Logi Dock Flex, a desk booking system for hybrid offices. Humbleteam designed the interface layer: the booking app, the on-desk experience and the admin tools IT uses to run it. In the Sync portal, admins draw floor plans, define desks and their equipment, set access for user groups, and decide policies such as how long a desk is held and how far ahead people can book. The case says that side of the work needed dense tables, bulk actions and settings that are safe to change in a busy office.
Three limits matter. The product is a device and software system, not a subscription SaaS platform. The case reports no outcome metric. Its role depth is access for user groups, not a full permission model. Humbleteam does not deliver production code. Its design system service agrees foundations and naming with engineering and prepares specifications for your engineers to build. It matches an internal product team that needs a design partner for the admin and data screens of one product.
Neuron: workflow and approval builders
Neuron is a UX/UI agency for enterprise software, headquartered in San Francisco. Its Vendr case covers a workflow builder for SaaS procurement. Builders arrange approval, notification and conditional steps on a canvas, and each step has a panel for assigning people, teams or roles. The case also shows an intake form builder, a My Requests page for requesters, a task viewer for approvers, and a Manage Workflows page with tabs for workflows and running instances, where opening a step depends on permissions. The first engagement took four months; Neuron staged the design around Vendr’s alpha release and handed it to Vendr’s developers to build. Its AcuityMD case covers a medical device sales platform with pipeline, filtering and global search, and describes Neuron as an embedded design team.
Neither page reports a product metric. The Vendr page touches permissions only in passing and does not cover admin settings, so ask for a case that does. Look at it if your product is adding a builder, approvals or rules.
Phenomenon Studio: admin panels from a team that also builds
Phenomenon Studio lists offices in Tallinn, Lugano and Dover and offers design, development and team extension. Its Bliss Creek case is an admin panel for a New Jersey client: a dashboard of total value and earnings, tables of users, cycles and transactions with filtering and sorting, and storage for user documents. Phenomenon reports about twice as fast user onboarding and a 60% drop in time on routine admin tasks. It also refactored the inherited codebase and built the panel in React. The Isora case, a governance and compliance platform, includes role-based permissions for survey collaboration, report comparisons across organizational units and a design system mirrored in Storybook. There, backend changes were mostly off the table and the API documentation was outdated.
The two cases do not show roles and dashboards together. Phenomenon also builds, so decide up front who owns the code. It works for a team that wants design and front-end work from one vendor.
How to choose: match your platform problem to the evidence
Start from the screen that hurts.
| If your platform has | Look first at | Ask them |
|---|---|---|
| Many modules with their own filters and tables | ANODA, Fuselab Creative | Which empty, error and filtered-out states do you draw before the first dashboard? |
| Customer admins who invite people and assign roles | Eleken, Phenomenon Studio | How many roles can your model hold before the screen becomes a matrix? |
| Partners, resellers or several audiences on one platform | EDL | Show the console, not only the system. Who builds the components? |
| A builder, approvals or rules | Neuron, ANODA | How does a user see what a workflow or rule did, and who can open it? |
| Admin tools tied to a device or a physical site | Humbleteam | Which settings are safe to change at scale, and what does the handoff contain? |
A test that fits platform work
Send every shortlisted agency the same scenario. This one is illustrative, not a case from any agency here. A customer’s administrator runs two workspaces, Sales and Finance. A contractor must edit reports in Sales and see nothing in Finance. The administrator then opens a reports table with about 30,000 rows, filters to last quarter and exports the matches. The export stops halfway because an integration token has expired.
Ask which screens the agency would draw, which roles it needs to interview, and what it would test. Nielsen Norman Group’s guide to data tables names four tasks a table must support: finding records, comparing values, working with one record, and acting on several. Use them to judge whether the answer covers the table and not only the permissions.
| Part of the scenario | A strong answer | A weak answer |
|---|---|---|
| Contractor access | Shows the role where the administrator grants it, and what the contractor sees where access ends | Hides the Finance menu and stops there |
| The 30,000-row table | Says whether select-all means the visible page or every match, and keeps filters when the user returns from a record | Treats the table as a styled grid |
| The failed export | Keeps the filters, says what finished, and sends the administrator to the expired token | Shows a generic error and a retry button |
| Who decides | Names which answers need your engineers or security owner | Treats every answer as a design decision |
Before the call, check your own side. Audit what exists, using our guide to auditing an enterprise dashboard, so the brief names the roles, the tables and the states you already know are broken. Then ask each agency for a reference at a product of similar size. Agree in writing who writes the front end and who owns the design system after handoff. Call back the agencies whose answers come with questions about your roles and your data.
