If your team edits content more than once a month, yes, and it's included in the Scale tier. If the copy changes twice a year, a CMS adds cost and a moving part for no benefit — I'll tell you that rather than sell you one.

What happens if the scope changes mid-build?

We price the change and you decide before anything is built. Small changes usually absorb into the existing timeline; larger ones become a written addendum with their own price and date. Nothing gets silently added to the bill.

You do, completely, from the first commit. The repository lives in your organisation, and every third-party account is created in your name with you as owner.

All services

01 — Web Products

Full-stack websites & web apps

Production-grade websites and web applications, designed and built end to end.

Most web projects lose their quality in the gaps — the designer hands off to a developer who reinterprets the layout, the developer hands off to an agency that never reads the code, and three months later nobody can explain why the checkout is slow. I remove the gaps by owning the whole thing: interface, backend, database, deployment and monitoring. You get one person who can answer any question about the system, and a codebase your next developer will thank you for.

Next.jsTypeScriptPostgreSQLTailwind CSSVercel

Discuss a project

See related work

2–6 weeksTypical timeline

₹65,000Starting from

95+ LighthousePerformance target

30–60 daysPost-launch support

What you get

Next.js 16 App Router + TypeScript codebase, strict mode on
Custom design system and responsive UI — no purchased template
Auth with httpOnly session cookies and role-based access control
Razorpay or Stripe checkout with server-side payment verification
PostgreSQL schema with migrations, constraints and real indexes
CMS layer so your team edits content without touching code
Vercel deployment with preview environments and domain wiring
CI running type-checks, tests and Lighthouse on every pull request

Outcomes you can expect

LCP under 1.5s on production for content-heavy pages
95+ Lighthouse across performance, accessibility, SEO and best practices
WCAG 2.2 AA on every revenue-carrying flow
A documented codebase your team — or your next developer — can extend
Content edits ship without a deploy or a developer
Search-ready at launch: server-rendered HTML, sitemap, structured data

In practice

What those actually mean

Every item above is something you can check for yourself after launch — not a promise that only becomes measurable once the invoice is paid. Here is the reasoning behind the ones that matter most.

A site that is genuinely fast on a mid-range phone

Core Web Vitals in the green on 4G, measured on real device profiles rather than a desktop dev machine. Performance is treated as a budget enforced every week, not an optimisation pass at the end that never happens.

Interfaces built around one clear action per screen

Every screen is designed with an explicit primary action, and the loading, empty and error states are designed too. The states nobody specifies are the ones your customers eventually meet.

A database you can actually query

A normalised PostgreSQL schema with real constraints and indexes, documented so that pulling a business answer out of it later is a five-minute job rather than a project.

Deployment and infrastructure you own

Everything runs on accounts in your name — hosting, domain, database, analytics. If we stop working together, nothing about your business stops working.

Accessibility to WCAG 2.2 AA on the paths that matter

Keyboard navigation, focus management, colour contrast and screen-reader labelling on the flows that carry your revenue. Tested with an actual screen reader, not just an automated scanner.

SEO wired in at build time

Server-rendered HTML, semantic headings, canonical URLs, structured data, sitemap and Open Graph cards — all generated by the codebase, so new pages inherit them automatically.

How we work

The engagement, phase by phase

This is the actual sequence, including how long each phase takes and what is expected from you at each point.

01
Scope & architecture
2–4 days
Before quoting, I map what actually needs to exist. You end up with a document precise enough that we could hand it to a third party and get the same result.
- Kickoff call covering users, current pain points and business goals
- Route-by-route inventory of every page and its states
- Data model sketch and integration list — payments, email, CRM
- Fixed price, delivery date, and a written list of what is out of scope
02
Interface design
3–7 days
Design happens against real content and real constraints. No lorem ipsum, because layouts that only work with placeholder text are not designs, they are decorations.
- Two directions on the highest-stakes screen, then we converge
- Full responsive treatment — mobile layout designed first, not derived
- Component inventory so nothing gets designed or built twice
- One consolidated round of feedback, turned around inside 48 hours
03
Build
2–6 weeks
A live preview URL exists from the first day and updates on every push. You are never waiting for a status report to know where the project is.
- Trunk-based development with a deploy preview on every pull request
- Weekly 20-minute demo of working software plus a written changelog
- Automated tests on revenue-critical paths — auth, payments, data writes
- Continuous Lighthouse and accessibility checks in CI, not at the end
04
Launch
2–5 days
Going live is a checklist run against a staging environment that already mirrors production. Uneventful launches are the goal.
- DNS, SSL, environment variables and automated database backups
- Error tracking, uptime monitoring and performance alerts wired first
- Redirects mapped from every old URL so existing rankings survive
- Rollback rehearsed before launch, not improvised during an incident
05
Support & handover
30–60 days
The support window covers anything not behaving as specified, at no extra cost, while your team gets comfortable owning the system.
- Same-day triage on anything blocking users
- A walkthrough session recorded for whoever maintains it next
- Day-14 analytics review against the metrics agreed in scoping
- Optional retainer — offered, never assumed

Is this a fit?

Where this works — and where it doesn't

Turning down the wrong project is cheaper for both of us than discovering the mismatch in week four.

A good fit for

Businesses whose current site gets traffic but loses people before the enquiry form
Teams running operations in spreadsheets that have clearly outgrown them
Founders who need a working product in front of customers, not another deck
Companies replacing a slow, unmaintainable template or page-builder site

Not what I do

Brand identity or logo design with no build attached
Ongoing content-marketing or link-building retainers on their own
Native iOS or Android apps — I build for the web, including installable PWAs
Rescuing a codebase without a scoped audit first

Handover

What you own at the end

Everything below transfers to you on completion. There is no proprietary layer you have to keep paying me for, and no account that stays in my name.

Full Git repository with readable commit history and no vendor lock-in
README covering local setup, environment variables and the deploy process
Database schema documentation and migration history
Design source files and the component inventory
Admin access to every account created for the project
A recorded walkthrough of the architecture and the deploy pipeline

Questions