Redesigning an enterprise website is not a design project. It’s a business decision that happens to involve design. The organizations that get it right — and there are fewer of them than you’d think — treat the brief as the hardest part of the job, not the launch.
Most Philippine enterprises approach a redesign the way they approach a fit-out: pick a contractor, agree on a scope, wait for delivery. What they don’t account for is everything that has to be true before the contractor can do anything useful. The sitemap that hasn’t been agreed on. The brand refresh that’s still in legal review. The three departments that all want homepage real estate. The IT team that discovers, halfway through development, that the hosting environment doesn’t support the CMS the agency recommended.
This checklist won’t eliminate those problems. But it will surface them early — before they become delays, scope creep, or worse, a finished website that nobody inside the organization actually owns.
Phase 1: Audit What You Have Before You Decide What You Want
The biggest mistake in any enterprise redesign is beginning with a vision board instead of an honest assessment of the existing site. Before you open a single brief or talk to an agency, audit your current website across four dimensions.
Start with traffic and behavior. Where are visitors coming from, and what are they doing when they get there? Which pages have high exit rates? Which are generating actual leads or conversions? Google Analytics or equivalent will tell you this. If you don’t have this data — or if it hasn’t been properly configured — that’s the first problem to fix, not the last.
From there, look at technical health alongside content quality. Site speed, mobile responsiveness, Core Web Vitals, and crawl errors on one side; accuracy, relevance, and content age on the other. Most enterprise sites carry significant content debt — pages published years ago, never updated, now either misleading visitors or quietly dragging down the site’s search authority. Both technical issues and content issues will shape what kind of redesign you actually need, and how long it will take. Finally, hold the site against your current brand identity. If your organization has evolved visually or strategically since the last redesign, the gap between what the website says and what the business now stands for is often the clearest signal that a rebuild is overdue.
Phase 2: Align Internally Before You Brief Externally
Enterprise redesigns fail in the middle more often than they fail at the start. The agency does good work, then hits a wall of internal disagreement that nobody anticipated. The way to prevent this is to do the alignment work before the brief goes out.
Define the business objective.
Not “we want a modern website.” Specifically: what should the new site do that the current one doesn’t? More qualified leads? Lower bounce rate on key service pages? A better experience for a specific audience segment — investors, corporate clients, graduate recruits? If you can’t write a one-sentence answer to this question, you’re not ready to brief an agency.
Identify your decision-makers.
Who has final approval on the homepage? On the navigation structure? On photography and imagery? On copy? These are four separate decisions in most organizations, and they often involve four separate people or teams. Map them before you start.
Confirm your content ownership.
Who writes the copy? Who approves it? Who owns the product or service descriptions? Who has authority to retire outdated content? If these questions don’t have clear answers, the project will stall in content development — which is the single most common source of timeline overruns in Philippine enterprise web projects.
Get IT in the room early.
Hosting environment, security requirements, integration dependencies (CRM, ERP, single sign-on, payment gateways) — these need to be on the table before an agency recommends a platform. The projects that ran smoothest at Designblue were almost always the ones where the client’s IT lead was looped in from the first briefing call, not introduced two months later as a gatekeeper.
Phase 3: Define Scope Before You Compare Agencies
The temptation is to send a vague brief to four agencies and see what they come back with. The problem is that you’ll get four wildly different proposals — different scopes, different platforms, different assumptions — and no meaningful basis for comparison. Define scope first, then go to market.
Page count and site structure.
You don’t need a final sitemap at this stage, but you should know the rough scale: is this a 20-page brand site or a 200-page enterprise platform? That distinction alone changes the nature of the engagement, the team required, and the timeline.
Platform decision.
WordPress, Laravel, Shopify — these aren’t interchangeable options that an agency will simply choose for you. They reflect fundamentally different decisions about flexibility, scalability, maintenance burden, and long-term cost of ownership. One pattern we see repeatedly with Philippine enterprise clients: organizations that deferred the platform decision to the agency ended up rebuilding sooner than they needed to, because the platform selected was optimized for delivery speed rather than the client’s actual operational requirements. Know which direction you’re heading before the brief goes out, or at least know what questions to ask.
Third-party integrations.
List every system the website needs to connect to. Every integration adds complexity, timeline, and cost. Surprises here are expensive.
Accessibility and compliance requirements.
Does your organization serve international audiences or have public-sector relationships that require WCAG compliance? ADB, for instance, requires WCAG 2.1 AA on all public-facing digital assets — a standard Designblue has delivered for their annual reports and web properties for four consecutive years. Not all agencies have the capability to build to that standard. Know your requirements before you shortlist.
Phase 4: Set Realistic Timelines and Launch Criteria
A well-scoped enterprise website in the Philippines takes between three and six months to build properly. Projects that launch in six weeks either cut corners or had most of the work done before the agency got involved.
Build your timeline backward from your target launch date, accounting for: discovery and strategy (two to four weeks), design (four to six weeks), development (six to ten weeks), content population and QA (two to four weeks), and a buffer of two weeks minimum for stakeholder review cycles.
Define what “done” means before you start. List your launch criteria explicitly: which pages must be live, which integrations must be functional, which browsers and devices must be tested. Ambiguous definitions of “done” are how projects drag on past their launch date indefinitely.
Frequently Asked Questions
How do I know if I need a redesign or just a refresh?
A refresh updates visuals and copy while keeping the existing structure and platform intact. A redesign rethinks the structure, the platform, or both. If your current site has fundamental navigation problems, platform limitations, or is built on a deprecated CMS, that’s a redesign. If it works well but looks dated and the content is stale, start with a refresh and see how far it gets you.
Should we hire an agency before completing the internal audit?
No. Bring an agency in after you’ve done the audit and the internal alignment work. The brief you bring to the table will be sharper, the scope will be more defined, and you’ll spend less of the engagement resolving internal disagreements on the agency’s clock.
How much does an enterprise website redesign cost in the Philippines?
Ballpark: a properly scoped enterprise website — custom design, bespoke development, third-party integrations, QA — typically ranges from ₱500,000 to ₱2,000,000 depending on complexity and scale. Template-based builds cost significantly less but carry corresponding limitations.
What’s the most common reason enterprise redesigns go over budget?
Content. Organizations consistently underestimate how much effort goes into writing, editing, approving, and populating content. Design and development proceed on schedule; content review cycles don’t. Build a content plan and a content owner into the project from day one.
Conclusion
A website redesign is a significant organizational commitment — not just a visual one. The enterprises that get the most out of the process are the ones that treat the planning phase with the same rigor they’d give any major business project: clear objectives, defined ownership, honest audits, and a scope that reflects what they’re actually trying to accomplish.
The checklist above won’t design your website for you. But if you work through it honestly, you’ll know exactly what you’re building, why you’re building it, and whether your organization is actually ready to see it through.
