Bhaumik Pathak — why the same client got two different websites

The challenge

The second website was for the same client, and almost everything about the brief was different. Where the engineering site had to make a company look established, this one had to make a person feel approachable — and those pull in opposite directions.

The easy decision would have been to reuse the first build. One client, two websites, one template: it is faster, it is cheaper, and it is what most agencies would have proposed. We did not, and the reason is worth stating plainly, because it was the central decision of the project.

A company website earns trust through scale — product range, capability, years in business. A personal professional website earns it through the opposite: a real face, a clear name, and the sense that a specific person is answerable for the work. Run the engineering layout for a personal site and the result reads as a small company pretending to be a large one, which is worse than either.

There was also an audience difference that changed the structure. Someone visiting a personal professional site has usually been given the name directly — by a referral, a card, or a conversation. They arrive knowing who they are looking for and wanting two things fast: confirmation they have the right person, and a way to make contact. That is a shorter journey than a buyer browsing an engineering catalogue, and a site built for browsing gets in its way.

The mobile constraint was sharper here than on the engineering site. A referral is shared by phone — a message, a saved contact, a link passed on — so the overwhelming majority of first visits arrive on a small screen. A personal site that is merely responsive rather than designed for the phone fails the exact visitor it exists to serve.

Our approach

The site was built separately from the ground up rather than branched from the engineering build. Shared code would have meant shared layout assumptions, and the two sites needed opposite ones.

The structure was kept deliberately short: who this is, what they do, and how to get in touch. A visitor arriving from a referral should not have to navigate to confirm they are in the right place — the answer is on the first screen, and the contact route is never more than one action away.

The profile leads with the person rather than a service list. On a personal professional site the name and the face are the credibility, so they carry the top of the page, with the services supporting them rather than the other way round.

Contact details are plain text and tappable, not buried in a form. Someone who has been referred usually wants to call or message directly — forcing that through a contact form adds a step and loses the people who were ready to act immediately. The form exists for those who prefer it; the direct route exists for those who do not.

The layout was designed at phone width first, then expanded to desktop, because that is the order in which real visitors arrive. It was tested on actual devices rather than resized in a desktop browser, which is where most "responsive" sites quietly fail.

Page weight was kept small. A referral link gets opened on mobile data, often mid-conversation, and a site that takes several seconds to appear has already lost the moment it was shared for.

On-page SEO targets the person's own name as the primary term, which is the realistic search for a personal professional site — alongside the service and location terms. Titles, meta descriptions, heading structure and Person schema markup are all in place, with the sitemap submitted and Search Console verified.

Domain, hosting and SSL were configured and verified on delivery, so a shared link opens clean with no security warning in front of the first impression.

The result

Bhaumik Pathak now has a personal professional website that confirms who he is and makes contact immediate — built separately from the engineering site rather than stretched from the same template.

The structure is short by design: identity, services and contact, with the contact route never more than one action away from any point on the page.

Contact details are plain and tappable alongside the form, so a referred visitor who wants to call or message directly can do so without filling anything in.

The layout was designed at phone width first and tested on real devices — which matters most here, because referral links are opened on phones.

Page weight is small, so a link shared mid-conversation opens immediately rather than several seconds later.

Titles, meta descriptions, heading structure and Person schema are in place, with the sitemap submitted and Search Console verified.

Both of this client's websites were delivered end to end — and the client recorded a video testimonial about the experience, which is on this page and on our YouTube channel.