Frequently asked questions

Yes. Every site ships with a content management system and a short handover walkthrough, so you can change text, images and pages without calling us.

We build with Next.js and React rather than page builders. The result is significantly faster, more secure, and does not slow down as you add plugins. If you specifically need WordPress, we will tell you honestly whether it is the better fit.

Your logo if you have one, any existing brand colours, and a rough idea of the pages you need. We handle the rest, including writing a first draft of the content if you would like.

Technical fixes can show movement within weeks. Competitive keywords realistically take three to six months. Anyone promising page one in 30 days is not being straight with you.

No, and neither should anyone else — search rankings are controlled by Google, not by us. What we guarantee is the work: the audit, the fixes, the content, and honest reporting of what moved.

Yes. A large part of our SEO work is on existing sites, including WordPress, Shopify and Wix.

Razorpay, Stripe, PayU, Cashfree and most major Indian and international gateways. We will recommend one based on your transaction volume and fee structure.

Yes. We migrate products, customers and order history from Shopify, WooCommerce and most other platforms, and set up redirects so you do not lose search rankings.

We set up hosting and can maintain the store on a monthly plan, or hand everything over documented so your team can run it.

Three distinct directions to start, then unlimited refinement on the one you choose until it is right.

Completely. You receive full rights and every source file on final payment.

Yes. A modernisation that keeps your recognition intact is often smarter than starting over.

Because you or your team want to publish frequently without a developer. WordPress earns its keep when content changes weekly. If your site is mostly static, a hand-coded build is faster and cheaper to run, and we will say so.

Usually, yes, and it is normally the cheaper answer. We audit what is loading, remove what is not needed, fix the images and the caching, and tell you honestly if the theme itself is the problem.

That risk is why we keep the plugin count low and set up a staging copy. Updates get tested there before they touch the live site.

Shopify if you want to run it yourself and stay out of maintenance — the monthly fee buys real convenience. Custom if you have unusual requirements, high volume, or want to avoid transaction fees at scale. We will tell you which you are.

Yes — products, variants, customers and order history from WooCommerce, Wix and most platforms, with redirects so your search rankings survive the move.

Rarely. A free theme customised properly looks better than a paid one used as-is, and it is one less thing to pay for.

A landing page removes everything that is not the one action — usually including the navigation. A normal page invites browsing; a landing page does not, because a visitor who wanders off is one you paid for and lost.

We write a first draft structured for conversion and you correct the facts. You know your customers' objections better than we do; we know the order to answer them in.

Yes, though it only pays once you have enough traffic for the result to mean anything. Below a few hundred conversions a month, testing tends to measure noise.

No. You pay Google directly from your own account and pay us a flat management fee. Marking up media gives an agency a reason to want your spend high, which is the wrong incentive to have in the room.

Enough for roughly 30 clicks a day in your market, or the data never becomes meaningful. For most local services that is ₹15,000–30,000 a month. Below that, SEO is usually the better use of the money and we will say so.

You do. We work inside your account, and if we part ways you keep the account, the history and the learning. Agencies that run ads from their own account are holding your data hostage.

Usually yes, and for the same reason it is worth it for anyone else: a link you control beats a PDF attachment. College projects are fine to show, as long as the page is honest about what they were and what you did on them.

Yes. The handover walkthrough covers exactly that, and adding an entry is editing one file. If you would rather we did it, ask and we will quote the change rather than put you on a retainer.

We draft them from what you tell us about each project, then you correct anything that is not right. You know what you built; we know what a reader needs to see first.

That is the part we spend the most time on. You get a walkthrough of every module and the questions examiners tend to ask about that kind of project. If you cannot explain it, the project has failed at the only thing it needed to do.

That depends on your college, and it is worth checking rather than assuming. Where the rules require the work to be your own, we scope it as guidance — we review your code, unblock you and prepare you for the viva, and you write it. We would rather lose the job than have you caught out.

Web stacks mostly: React and Next.js, Node and Express, PHP, MySQL and MongoDB. If your syllabus requires something we do not work in, we will say so rather than learn it on your deadline.

Two weeks is tight but workable for a mini project. For a final-year project, less than three weeks usually means cutting scope — and we will tell you what to cut rather than promise everything and miss.

You get a fixed price in writing after a scoping conversation, the same as every other job here. If the scope is genuinely unclear we will quote a small paid discovery first rather than guess a number we would have to revise later.

Usually, if that software has an API — accounting, payments, WhatsApp, calendars. Tell us what you use and we will check before quoting rather than after.

Small changes come out of a care plan if you have one, or are quoted individually. You hold the code either way, so you can hand it to another developer without asking us for anything.

Often not, and we will say so. An app has to be installed before it does anything, which is a real barrier, and it only pays off when people open it repeatedly or it needs something a browser cannot reach. If a faster website would serve you better we will tell you that instead of taking the larger job.

Both, from one codebase, which is why this costs what it does rather than double. If you only need Android to start — common in India, where it is the bulk of the market — we can ship that first and add iOS later without rewriting it.

You do. The apps are published under your own Play Store and App Store developer accounts, registered in your name. An agency that publishes your app under its own account is holding it hostage, and moving it later is painful.

Google is usually a few days, Apple anywhere from a day to a couple of weeks, and a rejection on the first submission is normal rather than alarming. The timeline above covers the build; store review sits on top of it and is not something anyone can promise a date for.