Hiring an independent for enterprise work
Small studios do enterprise design at a fraction of consultancy cost. The risks are real, specific, and mostly manageable if you know what they are.
Deciding whether this tier fits at all
The three questions that settle it
Does the work need multi-market delivery? Simultaneous rollout across regions, languages, and regulatory regimes needs bench depth and programme management that small studios do not carry. If yes, stop here and go to a consultancy.
Does the work need organisational change management? If the design is one workstream inside a transformation programme, with training, comms, and process redesign alongside, you are buying consulting rather than design.
Will procurement accept them? Some enterprises have vendor requirements that eliminate small firms regardless of capability: minimum revenue thresholds, insurance levels, or established vendor status. Find this out before you fall in love with a portfolio.
If all three are no, this tier is not a compromise. It is the correct choice, and you will pay considerably less for the same design output.
The risks, and what actually mitigates them
Key person dependency
At a studio of twenty, one senior designer leaving mid-engagement is felt immediately. Consultancies absorb this. Independents may not.
Name the people in the contract. Agree what happens on departure, including notice and replacement standards. Ask what happened the last time someone left mid-project, since the answer tells you whether they have a process or a hope.
Capacity and continuity
Small studios run at or near capacity, and the phase after yours may not be available when you need it.
Ask about their pipeline for the next two quarters, not just the start date. If the work will need a second phase, secure the slot when you sign the first rather than assuming.
Security and procurement friction
The most common reason a small studio engagement fails before it starts. Questionnaires, insurance verification, penetration test evidence, and data processing agreements can take longer than the design work.
Ask on the first call whether they have completed enterprise security review before, and for which kind of client. Ask for their documentation upfront. Start vendor onboarding in parallel with selection rather than after it. If your security team requires SOC 2, ask directly rather than discovering it in week six.
Thin public proof
Enterprise work is often unpublishable, and small studios have fewer projects overall, so the public portfolio understates capability more here than anywhere else.
Ask for detail under a mutual NDA, which most will provide. Ask for references from clients in comparable sectors and actually call them. Weight what they can describe in conversation over what appears on the site.
No account layer
There is no project manager absorbing your stakeholder churn. Every internal contradiction you send lands directly on the people doing the design.
Consolidate feedback internally before sending, name a single point of contact on your side, and resist parallel threads. This is a demand this tier places on you, and it is the most common reason enterprise clients find small studios frustrating.
Business continuity
Small firms are more fragile than large ones. Uncommon, but real.
Staged payments tied to deliverables, files and source in your possession as work progresses rather than at handover, and repository access from day one.
Evaluating the studio
Test enterprise experience specifically
Consumer credentials do not transfer, and a single enterprise logo is not an enterprise practice.
Worth asking: Describe a project where a legacy system prevented the obvious solution. How do you handle a stakeholder who overturns an approved direction in week ten. What do you do when compliance rejects something users clearly need. Tell me about work you delivered that was never implemented.
That last question is the most useful available. Everyone with real enterprise history has one, and a candid answer tells you how they will behave when it happens to you.
Test domain acquisition, not domain knowledge
No studio will understand your domain on day one. What matters is a repeatable method for learning it fast.
Ask how they onboarded to an unfamiliar domain recently, and how long before they could argue with a subject matter expert rather than just take notes.
Ask what they will not do
Studios worth hiring at this tier are clear about their limits. A firm that claims comfort with multi-market rollout, change management, security clearance, and organisational design either is a consultancy or is overselling.
Check the trade-off against your situation
Every studio has a structural consequence of how it is built. A small senior team means limited capacity. An engineering-led firm means design sits inside a technical engagement. A young studio means a shorter track record.
Read those against your own constraints. A trade-off that is irrelevant to most buyers may be disqualifying for you.
Structuring the engagement
Start with a paid discovery phase
The highest-value risk reduction available. A four to six week discovery or audit, priced separately, tells you how the studio thinks, how they handle your stakeholders, and whether the working relationship functions, before you commit to a six-figure build.
Both sides benefit. They scope the main phase against reality rather than a brief, and you buy an exit that costs a fraction of the full engagement.
Phase with real decision points
Not milestone billing on a predetermined plan. Genuine points where you can stop, change direction, or continue with revised scope.
Secure user access before you sign
The strongest predictor of enterprise design success and entirely your responsibility. Get written commitment from department heads for a specific number of hours from named roles in the first six weeks.
Small studios have no capacity to spend months chasing internal access. Without it, they will interview stakeholders instead and you will get software designed around what management believes the job involves.
Agree the measures and the baseline
Task completion time, error rates, support volume, adoption against the system being replaced. Set them before the work starts. Retrofitting measurement produces numbers nobody trusts.
Contract points at this tier
- Named individuals and replacement terms.
- You selected people, not a logo. Say so in the contract.
- Staged payment against deliverables.
- Protects both sides and reduces exposure if either party needs to stop.
- Files and repository access throughout.
- Not at handover. Work in your possession as it is produced.
- Data handling and residency.
- Where research recordings and system access live, who can see them, and what happens at the end. Your security team will ask, so agree it early.
- Confidentiality and publication.
- If the work cannot be published, say so before signing. Studios at this size rely on portfolio rights and would rather know upfront than negotiate afterwards.
- Continuation terms.
- Enterprise design rarely finishes cleanly. Agree the rate and mechanism for extension before you need it.
- Environment access provisioning.
- Who sponsors it internally and how long it takes. Access delays are among the most common causes of slippage on enterprise projects.
Running it well
Give them a single decision-maker. Committee review degrades work at any tier and does more damage where there is no account layer to absorb it.
Do not skip discovery to save budget. It is the cheapest phase and the most expensive to cut. Work made without an agreed understanding of the domain gets relitigated for months.
Book their time for implementation. A specification handed to engineering under deadline gets interpreted, and interpretations accumulate. Even light-touch design review through the build keeps the shipped product close to the intent.
Separate preference from evidence in feedback. "I do not like this" and "three of five users could not complete the task" are different inputs. Mark which is which.
Plan the handover deliberately. Documentation, decision rationale, and a walkthrough with whoever maintains it next. Studios that treat this as an afterthought leave you dependent on them.
Common expensive mistakes
- Choosing this tier for a programme that genuinely needed a consultancy, then discovering in month four that nobody can staff the rollout.
- Choosing a consultancy for a single-product design problem, and paying three times the rate for the same design work delivered by people you did not meet at the pitch.
- Failing to arrange operator access, so research happens with stakeholders and the design addresses a job nobody actually does.
- Discovering security requirements after selection, then losing two months to onboarding a firm that had never been through it.
- Sending committee feedback to a studio with no account layer, and getting flatter work and a strained relationship.
- Treating delivery as completion, so implementation drifts from the design and nobody owns the difference.
Seven enterprise UX studios, ranked, profiled, and honest about the trade-offs.