Design systems
Tokens, components and documentation that live in the same language as your codebase, so the colour in the design file and the colour in production are the same colour for longer than a week..
Landing pages
One page, built to load and built to convert.
Designed and built in hand-written HTML and CSS. No page builder, no forty plugins, no four-second load. You get files you can host anywhere and edit without a subscription.
The problem
The tooling is usually the problem.
Page builders are quick for the first page and expensive for every page after it. They load frameworks you are not using, they generate markup that search engines have to work to read, and they lock the output behind an account. When the person who built it leaves, the page becomes untouchable.
Hand-built pages take slightly longer to make and are then free. They load in under a second, they work with a screen reader because the markup means something, and they can be dropped on any host in a folder.
The second problem is structural. Pages fail to convert because the first screen does not say what the thing is and who it is for. That gets fixed with copy and hierarchy, not with animation.
“Our site takes six seconds to load on mobile and we pay a monthly fee for the privilege of not being able to change the header.”
A marketing lead, describing a common arrangement
What you get
Everything in the box.
Built as a folder of files. Host it on Netlify, Vercel, GitHub Pages or your own server; it does not care.
- Page structure and content hierarchy agreed before design, based on what the page has to prove.
- A designed page built to your brand system, or to decisions we make and document if you do not have one.
- Semantic, hand-written HTML with real landmarks, so assistive technology can navigate it.
- CSS with all tokens at the top of one file, so a colour change is one line rather than a search.
- Responsive behaviour checked at desktop, tablet and phone widths, and at large text settings.
- Accessibility pass: contrast ratios, visible focus states, labelled inputs and alt text that says something.
- Form handling wired to your endpoint, with client-side validation and a real error state.
- Meta tags, Open Graph cards, a favicon set, and analytics or tracking hooks where you want them.
How it runs
Four steps, start to handover.
Scope
What the page has to prove, to whom, and what happens after the button. Usually one call.
Structure
A section-by-section outline with the argument each section makes, signed off before visuals.
Build
Designed and built in the browser rather than mocked and then rebuilt, which removes a whole handover.
Ship
Deployed to your host, tested on real devices, with a short guide to editing the copy yourself.
Price
From ₹75,000
Two to four weeks for a single page, including build and deploy.
One page at the starting number. Additional pages sharing the same system are considerably cheaper, because the hard part is already done.
Questions
What teams ask before booking.
Do we need a CMS?
For one to five pages that change a few times a year, no. A CMS adds cost and a maintenance surface for a problem you do not have yet. If you are publishing weekly, that changes and we will say so.
Can our team edit the copy?
Yes. The HTML is readable and we include a guide showing exactly which lines are text. If you would rather not touch files at all, we can connect a lightweight editor, quoted separately.
What about SEO?
We handle the technical side: clean markup, heading structure, meta and Open Graph tags, fast load, sensible URLs. Keyword strategy and content production are somebody else's specialism, and we will say so rather than pretend.
Will it work with our existing site?
Usually. We can match the design of your current site and host the page on a subpath or subdomain. If your current site is the problem, we will tell you that instead.
Do you build the whole site?
Up to around eight pages, yes, and that is priced per page after the first. Beyond that you want a proper site build with a content model, which is a different conversation.
Also relevant
Two services that sit next to this one.
HTML email
Templates built and tested against the clients your list actually uses, including Outlook for Windows, which renders through Word and breaks everything designed for a browser..
Send us the page that is not converting.
We will tell you whether it is a structure problem, a speed problem or a copy problem before quoting anything. Often it is not the design.