01 · Service

Website design

A website is how a stranger decides whether you are worth a call. We do not drop a template on a logo. We write the sitemap, the copy, and the interface as one piece — then we engineer it so it stays fast on a mid-range Android in Indian traffic, ranks for what you actually sell, and can be edited by your team without a developer on every comma.

Companies that have outgrown a brochure PDF, a stale WordPress theme, or a single scrolling page that pretends to be a firm. If you need five to fifty pages that convert, this is the work.

When this is not the work. If you need a logo animation and nothing else, or a one-page “coming soon” with no sitemap, we are the wrong studio. If you need an Android app, that is a different practice — we will say so.

Start this work

A website layout on a monitor, with the HTML beside it and a phone on the desk

What this usually fixes

The brand is sharp. The site is not.

Visitors cannot tell what you sell, who it is for, or what to do next. The first screen is a slideshow. Enquiry is buried. We rebuild structure and writing until a stranger can decide in one sitting.

Nobody on the team can edit it.

Every comma is a developer ticket. The CMS is either missing or so general that staff are afraid of it. We ship a model that matches how you think — pages, people, products — and train the people who will type into it.

Google cannot find you, and the phone is slow.

The site was built on a designer’s laptop. On a mid-range Android in Indian traffic it takes four seconds to paint. There is no sitemap, no redirects from the old URLs, no analytics. That is architecture, not a plugin.

Paid traffic lands in a different company.

Campaign pages look like a third vendor. We make landing systems that share type, colour, and the same CMS as the main site, so AdWords does not invent a second brand.

Pages and screens

What a buyer actually walks through — not a capability matrix.

Home

Who you are, who it is for, what to do next — in one screen. Not a hero that takes eight seconds to load.

Work / products / programmes

The pages a buyer actually compares. Structured, filterable, honest about what exists.

Services and approach

What you do, how you work, what it costs in time if not in rupees. Written like a human, not a capability matrix.

About, people, careers

Enough to trust you. Not a CIN dump. Not a stock photograph of a handshake.

Contact, enquiry, booking

Forms that ask only what you will read. WhatsApp as a channel. Confirmation that does not vanish.

Insights, legal, the rest

A publishing model if you write. Privacy, terms, and the pages Google expects. Redirects when URLs move.

What we build

Marketing and brand sites

The public face: Home, work, services, about, contact, careers, insights. Structured so a first-time visitor knows who you are in one screen and what to do in the next.

Product and documentation sites

Feature pages, API docs, changelogs, and comparison tables — the pages engineers and buyers actually read before they sign.

Landing systems

Campaign pages that share a design system with the main site, so paid traffic does not land in a different company.

CMS-backed publishing

Editors update pages, blogs, and case studies without waiting on a sprint. We pick the CMS to the team, not to a vendor brochure.

Careers and hiring sites

Roles, culture, and a form that reaches the right inbox. Written so a candidate can decide whether to apply — not a “join us” paragraph under a stock photograph.

Multilingual company sites

English plus Hindi or regional copy when the buyer actually needs it. Routes, hreflang, and a CMS a translator can use — not a plugin that breaks the layout.

How deep this goes

Front-end engineering, not a theme

We ship production React and Next.js: server rendering, streaming, image pipelines, and routes that search engines can crawl. TypeScript so the next developer is not guessing. CSS that holds at 320px and at 1440px.

Core Web Vitals treated as a launch gate, not a later audit
Accessible markup: keyboard, contrast, names that screen readers can use
Motion that earns its keep and does not tank a 4G connection

SEO that is architecture, not a plugin

Titles, canonicals, sitemaps, redirects, schema, internal links, and content that answers the query. Rankings follow a site Google can parse. We do not sell “page one in 30 days.”

JSON-LD for organisation, services, and articles where it is honest
Redirect maps when you are leaving an old domain or CMS
Analytics and Search Console from day one

Content you can live with

We write, or we sit with your writer. No lorem ipsum at launch. Headlines that sound like the business. Forms that ask only what you will actually read.

Sitemap and page briefs before pixels lock
CMS models that match how you think (pages, products, people)
Handover: who edits what, and how not to break the layout

Hosting, forms, and the week after launch

The site lives in accounts you own. Forms hit email, a CRM, or a sheet you already use — not a black hole. DNS, SSL, previews, and a rollback if a deploy goes wrong. The first broken form and the first “can we add a page” are part of the job.

Vercel, AWS, or the stack your IT already runs — named in the brief
Spam-resistant enquiry, file uploads when you actually need them
Staging URL you can share with legal before it is public

Photography, type, and what “premium” actually is

A world-class site is not more decoration. It is type that is set, images that belong to the business, and motion that earns a second of attention. We write photography rules so every page is not a different shoot. We crop for the phone. We refuse stock that looks like another continent.

Image pipeline: sizes, lazy load, alt text a human wrote
Type scale that holds a fifty-page site without inventing a new headline each time
A first screen a stranger can finish on a train

Accessibility and measurement

Keyboard, contrast, names screen readers can use. Forms that announce errors. Then: Analytics, Search Console, and the events that match how you sell — enquiry, call, WhatsApp — not vanity sessions. If a page cannot be used by a person who cannot see the colour, it is not done.

WCAG as a constraint from the first template, not a retrofit audit
Conversion events named in the brief, wired at launch
A short report after go-live: what people actually did

Languages, platforms, tools

The names people search for belong on a service page, not in a footer buzzword strip. This is what we actually ship in.

Languages

TypeScript
JavaScript
HTML
CSS
SQL

Frameworks

React
Next.js
Node.js
Tailwind CSS

CMS & content

Headless CMS
Sanity
Contentful
WordPress (when it is the right tool)

Quality

Lighthouse
Playwright
Schema.org
Open Graph

What you walk away with

Sitemap and writing

What exists, in what order, and what each page is for. Headlines and body copy that sound like the business.

Art direction and UI

Type, colour, photography rules, and components that scale to twenty pages without twenty experiments.

Production build

Deployed front-end, metadata, sitemap, analytics, forms, and a CMS your team can open on Monday.

Handover

Credentials, a short edit guide, and the first week of nits included — not a surprise invoice.

How the work runs

A named owner, a written brief, and something you can click early. The longer studio sequence is on Approach.

01
Brief and map
How you sell today, who the visitor is, what “done” means. A sitemap before a visual is locked.
02
Design in the browser
You review live pages, not a sixty-slide deck. Structure is still cheap to change.
03
Build, content, launch
Engineering, final copy, redirects, a quiet launch with a checklist.

Questions we hear

Can you work from our existing brand?+

Yes. We inherit a strong identity. If there is none, we set a tight visual system before we multiply pages.

Do you also write the copy?+

Yes, unless you have a writer you already trust. We will not ship placeholder text and call it a launch.

WordPress or Next.js?+

Whichever the team can actually run. Marketing sites that need speed and structure usually land on Next.js. Some editorial teams still need WordPress. We say which, in writing, before we start.

How many pages, and how long does it take?+

A serious company site is rarely three pages. Five to fifty is the usual range once the sitemap is honest. Timeline is weeks, not a weekend — copy and reviews are what stretch it, not the build. We will not quote “a website in seven days” and then hide the writing.

Will it work on a phone?+

We design for the phone first and check on real mid-range Android, not only a studio Mac. If a page is unusable with a thumb, it is not done.

What about SEO and Google Business?+

Structure, titles, canonicals, sitemap, redirects, schema that is true, and Analytics plus Search Console from day one. We do not sell “page one in 30 days.” If you have a Google Business listing, the site should agree with it — NAP, services, the city you actually work from.

Can our team edit after launch?+

Yes. A CMS modelled on how you work, a short edit guide, and the first week of nits included. You should not need us to change a comma.

Will we own the site?+

Yes. Domain, hosting, repository, CMS, and analytics sit with you.

What does a website like this cost, and what is not included?+

The quote is the sitemap, writing, design, build, launch, and the first week of nits. Photography you do not have, paid ads, and ongoing SEO retainers are named separately. We will not hide writing in a cheap “design only” number.

Do you maintain the site after launch?+

Yes, if you want a care arrangement: updates, new pages, the odd campaign landing. If you only need handover, we still leave a guide. You should not be locked to us to change a headline.

Can the site be in more than one language?+

Yes, when the buyer actually needs it. We plan routes and the CMS so a translator is not fighting the layout. We will not bolt on a widget that machine-translates the brand into nonsense.

Other capabilities

If this is the work, send the brief.

Contact