Enterprise website design is not consumer web design with a bigger invoice. What makes a project enterprise is rarely the visual ambition. It is the number of people who can say no, the systems the site has to talk to, the regulatory and accessibility obligations attached to it, and the fact that something already exists and cannot be switched off. A design agency that is brilliant at brand work and inexperienced at governance and migration will produce beautiful comps and a painful launch. This page sets out the constraints that actually decide the outcome and the questions that reveal whether an agency has met them before.
What actually makes a project enterprise
Five things, none of them aesthetic. First, stakeholder count: when marketing, product, legal, security, accessibility, IT and several business units all hold a veto, the design process has to include a decision structure or it will stall in round three of revisions. Second, integration surface: a site that reads from a product information system, writes to a customer relationship platform, authenticates against single sign on and serves localised content in a dozen markets is an engineering project wearing a design brief. Third, content operations: thousands of existing pages, an owner for each, and a content model that has to work for authors who are not web specialists. Fourth, compliance: accessibility obligations, privacy notices, consent tooling and record keeping. Fifth, the existing site, which has traffic, links, bookmarks and integrations that all have to survive. Ask a candidate agency which of those five they have handled before, with a named example. An agency that answers the question in terms of design systems and component libraries has heard only the first half of the brief.
Migration is where enterprise projects actually fail
The single largest avoidable risk in a large replatform is losing search visibility at launch. Google documents crawl budget management for large sites and is explicit that crawl capacity and demand determine how much of a big site gets crawled, which means a redesign that changes every URL asks search engines to rediscover an entire estate at once. The mitigations are unglamorous and well known: a complete inventory of existing URLs, a mapped redirect for every one that has traffic or links, preservation of the internal linking that gave important pages their prominence, and a plan for the pages that will not carry over. None of that happens by accident, and it is frequently absent from a design agency's scope because it is not design work. Ask directly who owns the redirect map, who validates it before launch and who watches the logs for the first month after. If the answer is that SEO will be handled later or by another supplier, then make that supplier part of the design process from the beginning, since retrofitting search requirements after the information architecture is signed off is the expensive order. Buyers hiring separately here should evaluate an enterprise SEO company on the same evidence basis, and involve them during design rather than after.
Accessibility and performance are requirements, not enhancements
Accessibility is a legal question in the United States, not only a quality one. The Department of Justice publishes guidance on web accessibility and the Americans with Disabilities Act, explaining how the ADA's requirements apply to web content and pointing to the technical standards commonly used to meet them. In an enterprise buy that means accessibility belongs in the acceptance criteria and in the design system itself, because retrofitting colour contrast, focus states and keyboard navigation across a component library after launch costs far more than building them in. Performance sits in the same category. Core Web Vitals are documented publicly by the Chrome team as measures of loading, interactivity and visual stability, and Google's page experience documentation explains how those signals relate to search. On a large site, performance is decided by architecture: image handling, third party tags, personalisation logic and how much runs on the client. Put both accessibility and performance budgets into the contract as testable criteria with named tools, and require them at each milestone rather than as a pre launch scramble.
The questions that sort agencies quickly
Ask for a named enterprise client and a live site you can inspect, then check it yourself with a keyboard and a slow connection. Ask who the technical lead is and whether they are an employee or a contractor. Ask how they handle stakeholder review, specifically how many rounds are in scope and what happens on round four, because that clause governs the second half of the project. Ask what the content migration plan is, including who writes any new content and who audits what should be retired, since content is usually the schedule's critical path and rarely the design agency's job. Ask what the site will be built on and who maintains it afterwards, including whether you are buying a proprietary platform you cannot leave. Ask for the accessibility conformance approach in writing. Then ask what has gone wrong on a previous enterprise launch and what they changed afterwards. An agency with genuine enterprise experience answers that one immediately and in detail, because everyone who has done this has a launch weekend story. An agency that has never done it says their process prevents problems.
Questions people ask about enterprise website design
Should design and build come from the same agency?
Often yes for coherence, but insist on seeing the engineering credentials separately. Many design firms subcontract build, which is workable when disclosed and problematic when discovered. If they are split, name one accountable party for launch and put the integration testing in one scope rather than between two.
How long does an enterprise redesign realistically take?
Months rather than weeks once discovery, stakeholder review, content migration, integration testing and accessibility remediation are counted, and the content work is usually the longest pole. Treat any schedule that does not name a content owner and a redirect owner as incomplete rather than fast.
How do we protect search traffic through a replatform?
Inventory every existing URL, map redirects for everything with traffic or inbound links, keep important pages linked internally as they were, and monitor logs and Search Console closely after launch. Agree who is accountable for each of those steps before design begins, not after the staging site is approved.
What should be in the contract that usually is not?
Accessibility acceptance criteria with a named testing approach, performance budgets, the number of review rounds, ownership of design files and code, and what happens to the redirect map and the analytics configuration if the relationship ends. Those five clauses prevent most enterprise disputes.