Which enterprise product design agency can work at Fortune 500 scale?
Compare nine enterprise product design agencies by named work, scale evidence, and implementation scope, then see how large companies shortlist, pilot, and contract a design partner.
An enterprise redesign can look like a screen problem until the team opens the workflow. The person requesting a change cannot approve it. The data arrives from another system. A branch office follows different rules. Meanwhile, the old product still has to work.
At Fortune 500 scale, the same problem repeats across teams, markets, and approval layers. Blink UX, Elsewhen, frog, Huge, Humbleteam, IDEO, Thoughtworks, ustwo, and Work & Co all publish relevant product work. The evidence differs in kind: research and internal systems, a focused interface assignment, a multi-year design program, or design combined with engineering. Start with the part of the project your own team cannot cover.
Humbleteam publishes this comparison and is one of the agencies included. The agencies appear alphabetically, without a ranking. The assessments use public evidence re-checked on October 19, 2026; they are editorial judgments about fit. A past case establishes experience, while the proposed team and scope still need checking.
What qualifies an agency for this shortlist?
Every agency below has a named enterprise client example involving a digital product, operational workflow, or shared interface system. Its published material identifies a design contribution beyond a client logo. The same threshold applies to Humbleteam.
The comparison asks four questions: what was designed, how the work handled complexity, who handled implementation, and what kind of engagement the evidence supports. A portfolio description supports a narrower claim than a detailed account of research, components, and rollout.
What does Fortune 500 scale look like in public evidence?
“Scale” is not a headcount. A buyer can look for five signals in a case:
- A named large client. American Express, McDonald’s, and Qualcomm appear on the 2026 Fortune 500, as does BlackRock, whose iShares business is a ustwo client.
- Breadth: one program covers many products, teams, or markets.
- Adoption: other teams kept using the shared system after the first release.
- Research across roles, reaching employees, field staff, and administrators as well as customers.
- Engineering capacity, or a stated boundary that says who builds.
Public pages rarely show all five. A client list is not a case, and every agency-sourced number below is that agency’s own. Where evidence is thin, the section says so, Humbleteam’s included.
The short answer: the strongest public evidence of large-program work comes from Blink UX (design systems across hundreds or thousands of products), frog (a multi-business program, though an old one), Huge (a global consumer app and shared system), ustwo (a long-running shared system), and Work & Co (IKEA across several touchpoints). Elsewhen and Humbleteam publish narrower assignments that sit next to a client’s engineers. Thoughtworks shows a delivery-led operational app. IDEO’s evidence centers on research and concepts.
| Agency | Public example to examine | Scale signal in the source | Published base or studios |
|---|---|---|---|
| Blink UX | Qualcomm and ORNL design systems; Avangrid service journeys | Thousands of products (Qualcomm); 400+ internal applications (ORNL) | Seattle HQ and five other studios |
| Elsewhen | Inmarsat’s Invison satellite-services platform | One platform; core engineering stayed in-house at Inmarsat | London and Europe |
| frog | GE UX Center of Excellence and design system | Several GE business units, about 2010 to 2015 | Studios in North America, Europe, and Asia |
| Huge | McDonald’s global app and design system; Google partnership | Global markets; 100+ Google products, brands, and teams | New York HQ, with offices in London, Chicago, and elsewhere |
| Humbleteam | Logitech’s Logi Dock Flex interface; ING small-business banking prototypes | One product’s app, on-desk screen, and admin tools | Prague and Dubai |
| IDEO | American Express Pay It Plan It; GE Healthcare CT console | Amex feature rolled out to 21 million customers in 30 days | Cambridge, Chicago, London, San Francisco, and Shanghai |
| Thoughtworks | Morrisons’ employee ordering application | 505 UK stores in 24 weeks | Chicago corporate base; global delivery |
| ustwo | iShares design system; HSBC’s Klir | Global iShares sites; a 22-month product build | London, Malmö, New York, and Lisbon |
| Work & Co | IKEA app, in-store tools, and Skapa design system | App, website, internal tools, and stores for one retailer | Brooklyn; part of Accenture Song |
What does each agency’s work establish?
Blink UX: research and consistency across internal products
Blink’s enterprise design-system page describes Qualcomm moving from fragmented experiences across thousands of engineer-supported products toward one system. Deliverables include a UI kit, component library, reference site, adoption frameworks, and a long-term release plan. The same page describes ORNL work covering more than 400 internal applications, with accessibility reviews, coded components, and a Storybook reference site.
Its Avangrid case shows the research side: customer interviews, process mapping, and field-crew ride-alongs informed service journeys and an outage dashboard for a utility with more than 3.3 million customers. Consider Blink when understanding the work across roles is a large part of the assignment. Ask which researchers and designers will join, and where implementation responsibility ends.
Elsewhen: complex journeys with a clear engineering boundary
Elsewhen’s Inmarsat case describes UX, UI, and customer journeys for procuring and managing satellite services. Its team narrowed a long feature list into an MVP and supplied prototypes, journey boards, and Jira requirements for Inmarsat’s engineers. The case places core platform development with Inmarsat.
That suits a B2B platform whose technical owners are in place but need help resolving the user journey. It is one platform, so the page shows design depth rather than program size. Its about page now leads with enterprise AI alongside product design and build; a proposal should say which services you need.
frog: a multi-business design program, with dated evidence
frog’s GE case is the most direct public example here of design across business units. frog describes a UX vision for GE’s software, a UX Center of Excellence with a playbook, pilots such as myEngines for GE Aviation and myFleet for GE Energy, and the Industrial Internet Design System. It credits that system with a 100% productivity increase and $30 million in first-year savings.
The work ran from roughly 2010 to 2015, and the page dates from 2020, so treat it as history. Ask for a current comparable case and the named studio and designers. frog’s DesignOps page matters when governance after launch is part of the brief.
Huge: a global consumer program on a shared system
Huge’s McDonald’s case describes a reinvented global mobile app, website, and self-service kiosks, with a centralized design system meant to give each market a common base. Huge reports the app became the most downloaded in its category; that figure is the agency’s. Its Google page reports work across more than 100 Google products, brands, and teams.
Huge describes its model as strategy through engineering, so ask which engineers are Huge’s and which are yours. Both cases are consumer-facing; ask for an internal or B2B example if your redesign is operational software.
Humbleteam: a focused product and design-system engagement
Humbleteam’s Logitech case describes the interface layer of Logi Dock Flex, a desk-booking system for hybrid offices: the booking app, the on-desk experience, and the admin tools IT uses. Its design-system service also cites the Logitech design system and covers audits, components, behavior documentation, and handoff planning. A fintech page adds a prototype-stage example: Humbleteam says it supported ING’s team on small-business banking and user-tested the prototypes.
Consider Humbleteam when an internal product and engineering team needs a design partner for a bounded assignment. Engineering remains separate: Humbleteam does not deliver production code. The public pages describe single products, not a program across many teams, so they do not establish capacity for a company-wide migration. Ask for a walkthrough of comparable roles, exceptions, and handoff material first.
IDEO: research-led work on products and services
IDEO’s GE Healthcare case describes a CT scanner console redesign that had to serve junior and senior technicians in one interface. Its American Express write-up covers Pay It Plan It, a payment-plan feature launched in 2017 and rolled out to 21 million customers in 30 days.
Both lean on research and concepts. The Amex case describes a feature, not a full product redesign, and neither page details engineering. Confirm the implementation boundary and the proposed team before assuming IDEO fits a delivery-heavy program.
Thoughtworks: operational redesign tied to software delivery
Thoughtworks’ Morrisons case concerns an employee reordering process that relied on printed product documents of up to 800 pages. Thoughtworks says a mobile web application reached all 505 UK stores in 24 weeks.
The case fits a redesign that depends on changing how software and operations work together. It is undated and says little about the design process. Request a current comparable case and confirm the team’s design responsibilities alongside its engineering scope.
ustwo: shared systems and products built with engineers
For iShares, ustwo describes a design kit, documentation site, and front-end library for global teams, still reviewed four years on and recently extended with regional type styles and accessibility work. It fits when the hard part is keeping several teams consistent after launch.
Its HSBC Klir case shows another engagement: over 22 months, ustwo led design and research and built the full-stack product with machine-learning insights. Klir’s learnings and technology later entered HSBC Kinetic. A system migration and a new AI product need different teams, even within one studio.
Work & Co: several connected products in one program
Work & Co’s IKEA case spans an ecommerce app, a website, internal tools, and in-store experiences. It also describes Skapa, a shared design system with a React Storybook library, training, and a dedicated team to maintain it.
Its company page lists research, product design, full-stack development, and architecture, says Work & Co joined Accenture Song in 2024, and names clients such as American Express, Goldman Sachs, and Target. Ask for case evidence at that scale, how its team will divide delivery with yours, and which product ships first.
How do large companies choose a product design agency?
A large buyer rarely picks from a portfolio alone. These steps turn the evidence above into a process a procurement team can run.
| Step | What the buyer asks for | What it prevents |
|---|---|---|
| Scope the program | One written problem, the user roles involved, and who owns design, research, the system, and engineering | Proposals priced against different assumptions |
| Shortlist by comparable scope | Two cases of similar size and complexity, and a call with a client contact | Choosing on a client logo |
| Paid discovery or pilot | A short paid phase on one real workflow, with deliverables and a go or stop decision | A large contract signed before the team’s working style is visible |
| Name the team | Lead designer, researcher, and engineering lead by name, with a notice period for changes | The pitch team disappearing after signature |
| Set the implementation boundary | Who builds, who accepts, and which handoff files and reviews are included | Approved designs that nobody builds |
| Start security and legal review early | Master services agreement, data handling, intellectual property, and accessibility terms, reviewed during discovery | A start date lost to paperwork |
| Agree governance after launch | A system owner, a contribution process, and a metrics review date | A shared system that decays |
Published cases show parts of this. ustwo says it helped HSBC recruit the leads, engineers, and designers who continued Klir. Work & Co describes shared design and development work with IKEA’s internal teams. Blink lists adoption frameworks among its Qualcomm deliverables. Elsewhen handed Inmarsat’s engineers Figma boards and Jira tickets. None of these pages publishes a contract term, so security reviews and agreements need direct questions.
Use one troublesome workflow in every conversation. For example, an employee submits a change, an approver rejects part of it, and a downstream system has already accepted another part. This is an illustrative exercise. Ask candidates how they would investigate it, which roles they need to meet, and what they would test before designing a replacement.
Keep a decision record for each finalist: the closest case, the agency’s actual contribution, the proposed team, the first deliverable, and the unresolved dependency. If a critical responsibility has no owner, resolve it before comparing price. Before comparing agencies, decide whether one lead, a lead with specialist studios, or several studios coordinated by your own team fits the program; the guide to setting up design partners for a major redesign covers the trade-offs.
What if the redesign includes AI?
Add evidence for the specific AI task to the criteria. ustwo’s Klir case describes an implemented product with machine-learning insights. Elsewhen and Work & Co publish broader AI engineering capabilities. Those facts answer different questions and should stay separate.
Ask who owns data access, model behavior, security review, and recovery from a failed action. Use the AI product agency comparison for a more specific shortlist, and define the permission boundaries before commissioning a prototype.
The outcome should be a named team and a first assignment both sides can describe precisely: which workflow will improve, what evidence will show it works, and who maintains the result afterward.
