Customers and prospects
Capability by capability, in the language the buyer uses, with proof and a route to a named contact. This is where commercial value sits.
Website Design · Delhi NCR & remote
Not technically. Structurally. Six divisions, four audiences and nine people with an opinion produce a site that says everything to everyone, which is the same as saying nothing to anyone.
Short answer
Corporate website design is for organisations serving several audiences at once — customers, partners, investors, job applicants and press — usually across multiple divisions. The hard part is not visual. It is deciding the structure, agreeing who owns which section, and building a system that stays coherent after fifty people have edited it.
Four details. A real reply the same day, from me.
01 The premise
A corporate website has to serve audiences whose needs actively conflict. A prospective customer wants a specific capability explained. A job applicant wants to know what it is like to work there. A partner wants technical detail. A journalist wants a fact and a contact within thirty seconds. Designing one homepage that serves all four equally produces a homepage that serves none.
The second structural problem is ownership. In a company of any size, sections are written by the people who run them, and every one of those people believes their section deserves the homepage. Without an agreed hierarchy the site becomes a negotiated compromise, and compromise sites are the ones that get redesigned again in three years.
So most of the value I add on a corporate project happens before any visual work: settling the audience hierarchy, agreeing what each division owns, and building a component system strict enough that a page added in eighteen months by somebody I have never met still looks like it belongs.
02 Audiences
Each needs its own route. Trying to serve them from one page is the failure mode.
Capability by capability, in the language the buyer uses, with proof and a route to a named contact. This is where commercial value sits.
Careers is often the second-most-visited section of a corporate site and usually the worst maintained. It needs real roles, real people and a working application route.
Technical detail, documentation, compliance and credentials. Deep, unglamorous pages that a small number of high-value people read carefully.
Facts, figures, leadership, contact. Judged entirely on speed of access, and quietly damaging when out of date.
03 Governance
A corporate site is not finished at launch. It is a system that will be edited by people who were not in the original meetings.
Free structure review
Send me the URL. I will tell you whose needs the current structure actually serves — and in most corporate sites the honest answer is the internal org chart, not the customer.
Four details, and a real reply today.
04 Decisions
05 Process
Who must be consulted, who must approve, and who only needs telling. Agreed in writing before design, because this is what determines the timeline.
Audience hierarchy, sitemap, URL structure and navigation. Reviewed and signed off as a document while it is still cheap to change.
Tokens, components and page templates. Approval happens at component level, so page ninety does not need a meeting.
Development, content migration and redirect mapping. Losing rankings in a corporate migration is common, avoidable and expensive.
CMS training per section, documentation, and the publishing checklist. The site has to be operable without me.
— Website Design
These sit next to a corporate website and are usually bought with it. Same person doing the work in each case.
Layouts built to convert.
Read moreFor companies that sell offline.
Read moreOne page, one action.
Read moreNo themes, no templates.
Read moreDesigned at 360px first.
Read moreFix what is losing you enquiries.
Read more— Questions
Straight answers, including the ones that cost me work. If yours is not here, ask it — I reply the same day.
Longer than the build. Development is rarely the constraint — approval cycles and content from multiple divisions are. Projects that agree a single approver and a content deadline in week one finish months earlier than those that do not.
Usually not. Separate microsites divide your search authority, multiply maintenance and confuse customers who deal with more than one division. One site with clearly owned sections is almost always stronger. The exception is a genuinely separate brand with a separate audience.
Yes, and for a site this size you must. Editing is granted per section, so each team maintains its own area without being able to disturb anyone else’s. That restriction is a feature; it is what stops the site drifting.
Yes, with correct hreflang so the language versions support rather than compete with each other in search. I will also ask who is going to maintain each language, because an out-of-date translation damages more trust than not offering it.
Not if the migration is planned. Every existing URL gets mapped to its new address with a 301 before launch, and the old structure is crawled first so nothing is missed. Ranking loss in migrations is almost always caused by skipping that step.
Yes, and it is normal on projects this size. I work to your brand guidelines and your hosting or security requirements. What I will ask for is one named decision-maker on each side, because that is what keeps a multi-stakeholder project moving.
Free consultation · No obligation
One call about how the organisation is actually arranged and who the site has to serve. You will get an honest view of whether this is a redesign or a restructure — they are very different budgets.
Name, number, email, what you need.