Home How we build
How a project
actually runs.
Most agency pages describe an outcome and leave the middle vague. This describes the middle: what happens at each stage, who owes what to whom, where the money moves, and exactly what transfers to you at the end. It is written down so you can compare it against anyone else's process — and hold us to ours.
The shape of it
Five stages, and two that matter most.
Money moves at stage two. Ownership moves at stage five. Those are the two most projects leave undefined.
Stage by stage
What happens, and who owes what.
The brief — free, and genuinely free
You describe what the thing has to do and who it is for. We reply within one business day, usually with a direction or an existing template to react to rather than a questionnaire. Two of the questions we ask are the ones that decide whether the project runs late: who writes the copy, and what has to connect to what. Nobody is charged at this stage and there is nothing to sign.
Sometimes the honest answer here is that you should not buy anything yet — that the site converts fine and the problem is traffic, or that the offer is the thing that needs work. We would rather say that now than three weeks in.
You get — a direction, free
Scope — a fixed number, and the exclusions
You get a written scope with a fixed price for a defined piece of work. It lists deliverables, the number of templates, revision rounds with a definition of what counts as a round, the schedule, and what you are responsible for supplying.
It also lists what is not included. That section is the one that prevents the argument in week five, and its absence is the single most reliable warning sign in someone else's proposal. Payment is staged — part here, the rest at completion. Never all of it up front.
Exclusions — listed explicitly
Build — why this takes days, not a quarter
A project does not start from a blank page. We maintain our own library of production templates and a generator that takes a niche and a source and produces a complete, animated, deployed site — structure, content scaffolding, imagery, hosting and all. That is most of the reason a first version is days rather than months.
What that buys is not speed for its own sake. It is that the boring, repeatable parts — layout, responsiveness, performance, SEO scaffolding, redirects — are already solved and consistent across projects, so the time we spend on yours goes to the part that is actually yours: the offer, the structure, and what the site has to make happen.
Time goes to — your problem
Review — defined rounds, not an open loop
Two rounds, and a round is defined in the scope so neither side is guessing. Small requests get absorbed — but they get logged, so that at the point the accumulated small requests have become a second project, that is a conversation rather than a surprise.
On a redesign, the redirect map is produced and reviewed before the launch date. Skipping it is the most common way a redesign loses the search traffic the old site spent years earning.
Handover — the part most people never write down
On final payment, everything transfers. Not a licence to use it while you keep paying us — ownership. The table below is the actual list.
Hosting and the domain are in your name from the start, registered to you as registrant rather than as an administrative contact on an account of ours. Renewals happen directly with the provider at their published rates. There is nothing you have to keep buying from us to keep using what you paid for.
The handover
Exactly what transfers to you.
| What | Who holds it afterwards | Why it is on this list |
|---|---|---|
| The domain name | You, as registrant | Registrant — not admin contact — is the field that decides control |
| Hosting account | You, in your own name | So leaving us costs nothing and needs no migration |
| The site itself | You, assigned in writing | Assigned on final payment, not merely licensed |
| All credentials | You | A handover without logins is not a handover |
| Search Console property | You, verified | Your traffic data belongs to you from day one |
| Any automation built | You, exportable | Workflows are files; you should be able to take them |
| A written walkthrough | You | So the next person can pick it up without us |
The clause-by-clause version of the paperwork behind this is in what to include in a web design contract, and the questions worth asking any agency — us included — are in how to choose a web design agency.
Limits
What we say no to.
A process is only meaningful if some things fall outside it.
Ranking guarantees. Nobody controls Google's index. Any guarantee is either meaningless or a misunderstanding of what SEO is, and we will not write one into a scope.
Open-ended retainers before results. A monthly fee starting before there is something working is a subscription, not a service. Care plans exist after a build, not instead of one.
A redesign as a fix for no traffic. A better-looking page with nobody on it converts nobody. If the problem is demand, a build is the wrong purchase and we will say so.
Automation for its own sake. Complexity has to be earned by a task that genuinely repeats. Adding a workflow because the tool supports one is cost with no return.
Rule — results before retainers
Questions
Before you get in touch.
How long does a project take?
A first working version is usually days rather than months, because the build starts from an existing template library and generator rather than a blank page. The variable that actually moves the date is content — if you are supplying the copy, the schedule waits on you, which is why the brief asks who writes it before anything is quoted.
When do I pay, and how much up front?
Payment is staged — part at scope, the rest at completion. Never the full amount up front, because that puts all the risk on you and removes any reason for us to finish promptly. The brief stage is free and carries no obligation.
What exactly do I own at the end?
The domain registered in your name, the hosting account, the site itself assigned to you in writing, every credential, the Search Console property, any automation built for you, and a written walkthrough. Assignment happens on final payment rather than on delivery — that is deliberate, and it is stated in the scope.
What happens if I want changes after handover?
You can make them yourself, hand the work to anyone else, or come back to us. Because you hold the code, the credentials and the hosting, none of those options require our permission — which is the point of transferring ownership rather than licensing it.
Do you work with clients outside India?
Yes — we work remotely with businesses in the US, UK, Canada, Australia and the UAE. Briefs get a reply within one business day regardless of time zone, and calls are scheduled around yours rather than ours.
Can you take over a site someone else built?
Usually, provided you actually control the domain and hosting — that is the first thing to check, and it is where these conversations most often stall. If the previous agency holds the registrant record, resolving that comes before any work can be scoped.
Start with the brief.
It costs nothing.
Describe what it has to do. You get a reply within one business day, and a direction to react to before any money moves.
Fixed price · exclusions in writing · you own everything on final payment