Choosing a provider
Corporate website design services
Choosing a provider for a corporate website often involves procurement: written requirements, comparison of proposals and sign-off by several people. The risk is choosing on presentation rather than on how well a provider handles governance, security and the years after launch.
This page sets out what to require from corporate website providers and how to compare proposals fairly.
Illustrative diagram
- Overview — goals and audiences
- Mandatory requirement — for example accessibility level
- Detail — what exactly is required
- How it will be checked
- Desirable features — ranked, not mandatory
- Support after launch
Write requirements, not just a brief
A corporate brief describes goals; requirements describe what the site must do and meet. Separating mandatory requirements, such as accessibility level, security practices and editing roles, from desirable features makes proposals comparable and prevents essentials being traded away for visual polish.
Include how content will be migrated, who will write new content, how many people will edit the site and what support you expect after launch. These are the areas where proposals differ most.
Evaluation criteria to weigh
| Criterion | What to look for |
|---|---|
| Understanding of audiences | A proposal that addresses each audience's task |
| Governance approach | Roles, approvals and component-based publishing |
| Accessibility | Design and testing to a stated WCAG 2.2 level |
| Security | Updates, access control, backups and incident handling |
| Content migration | A plan for existing content and redirects |
| Support after launch | Clear arrangements and handover documentation |
Matching provider size to your needs
Large agencies bring teams and broad services; independent specialists bring direct communication and lower overheads. Neither is automatically better. The right fit depends on the size of the site, how much ongoing work is planned and how many people on your side need to be involved.
LetGetGrow is run by an independent specialist. That suits corporate sites with a focused scope and a clear decision-making group. For very large programmes needing many concurrent specialists, a larger team may suit better, and we will say so.
Questions for shortlisted providers
Delivery
- Who will work on the project day to day?
- How will feedback from several stakeholders be managed?
- How is accessibility tested before launch?
After launch
- What documentation will we receive?
- How are security updates handled?
- How could we move to another provider later?
Security expectations
Corporate websites are attractive targets simply because they are prominent. Expect a provider to explain how software is kept updated, how admin access is limited and protected, how backups are taken and restored, and who responds if something goes wrong.
Ask for these arrangements in writing. They matter more over the life of the site than any visual feature.
Warning signs in proposals
No accessibility commitment
Accessibility mentioned vaguely or not at all.
Content assumed
Proposals that ignore who writes and migrates content.
Proprietary lock-in
Platforms only the provider can maintain.
Reducing risk with a discovery phase
For larger corporate projects, a paid discovery phase before the main contract reduces risk on both sides. It produces the content inventory, audience routes, governance model and a refined estimate. If the relationship does not work, you keep the outputs and can take them to another provider.
Discovery also tests how well a provider understands your organisation, which is hard to judge from a proposal alone.
Checking a provider's track record
Ask to see live sites a provider has worked on, with their role on each stated clearly. Visit them on a phone, use the keyboard to move around and look at pages beyond the homepage, such as a careers listing or a long article. How these ordinary pages behave says more about quality than a polished homepage.
Questions about corporate website design services
What should a corporate website requirements document include?
Audiences, mandatory standards such as accessibility and security, editing roles, content migration, integrations and support expectations.
How should we weight proposals?
Give governance, accessibility, security and support real weight alongside design, because they decide the site's success over years.
Is an independent specialist suitable for a corporate site?
For focused scopes with a clear decision-making group, often yes. For very large programmes, a bigger team may suit better.
Can you respond to a formal tender?
Yes. Send the tender documents and we will respond to the requirements we can meet and say clearly where we cannot.
How is content migration usually handled?
With an inventory, decisions on what to keep, and redirects for pages that move or retire.
What support do corporate sites need after launch?
Security updates, monitoring, content support for editors and occasional improvements, agreed in writing.
Do you sign confidentiality agreements?
Yes, where a project requires one. Send it with your enquiry and we will review it.
Can you work with our internal IT team?
Yes. We agree responsibilities for hosting, security and integrations with them at the start.
How long does a corporate website project take?
It depends on scope, content readiness and approval speed. We give a timeline after discovery, with the review stages built in.
Sources referenced
Platform features, guidance and rules change. We check the current versions before committing to an approach. This page is general information, not legal advice.
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) — reviewed 2026-10-22
Request a Custom Quote
Ask about Corporate website design services
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.