Question 1

How long does a typical project take?

Accepted Answer

Most projects ship within 14 days; complex custom applications take 4–6 weeks. You'll get a detailed timeline with your quote — and weekly drops so you always see progress.

Question 2

Do you offer revisions?

Accepted Answer

Yes. Every project includes structured revision rounds at design and pre-launch. We keep iterating until it matches the brief we agreed on — it is included, not an add-on.

Question 3

What happens after launch?

Accepted Answer

30 days of free support comes standard — bug fixes, tweaks and monitoring. After that, iteration sprints or care plans keep you improving.

Question 4

Can you work with our existing brand?

Accepted Answer

Absolutely. We build on your guidelines, and if your identity needs a refresh first, we can scope that as phase one.

Question 5

How do payments work?

Accepted Answer

Credit cards, UPI and bank transfers. Smaller projects run 50/50 — half to start, half at handover. Larger ones are milestone-based, so you never pay for work you have not seen.

Question 6

Who owns the code once the project is paid for?

Accepted Answer

You do, on full payment. The deliverables we create specifically for you — your content, your designs, your codebase — are yours. We keep ownership of our pre-existing tools, components and internal libraries, and license those to you for use inside the delivered work. That carve-out is deliberate: they are the parts of our stack that are already built when you arrive, not work produced for you.

Question 7

Do you sign an NDA?

Accepted Answer

Confidentiality is mutual and already in our terms, so an NDA is not something you have to ask for separately. Each side keeps the other’s non-public information confidential and uses it only for the project. The two carve-outs are standard: information that is already public, and anything either side is legally required to disclose. If your legal team wants a bespoke agreement on top, we will sign it.

Question 8

Can we take the project in-house later?

Accepted Answer

Yes, and the build is written for that rather than against it. Handover documentation and a walkthrough come with every project. If yours needs a CMS, an admin surface, or a documented handover, that is scoped in from the start — because a site nobody can edit is a liability, not an asset. We do not build to make ourselves indispensable.

Question 9

Will you use our project in your portfolio?

Accepted Answer

By default yes — unless you ask us not to, we may show the work and describe it publicly. That is the one clause worth reading before you approve a design. If something is under embargo, an unreleased product, or client-confidential, tell us and we will keep it out of the portfolio and off the case-study page.

Question 10

Which countries do you work with?

Accepted Answer

Worldwide. GrowMyStore is a studio in Kolkata, India, and we build for businesses across time zones — the wording on our own service pages is "serving clients worldwide from its Kolkata studio". For most projects that means calls scheduled against your working hours rather than ours, and payment by card, UPI or bank transfer regardless of where you are.

Question 11

What do you need from us to get started?

Accepted Answer

Four things, and they are the difference between a project that lands on time and one that does not: accurate information, timely feedback, access to the systems and accounts we need, and content you have the right to hand over. Keep your own backups of anything you send us. Scoping is part of the job rather than a billable extra, so a rough description is enough to begin — and you will have a scoped quote within 48 hours.

Question 12

Our database is slow. Do we need a rewrite?

Accepted Answer

Often, no. Most database slowness is missing indexes and N+1 queries rather than a wrong underlying choice, so we measure first and tune second — and only propose structural changes once tuning has genuinely run out. That is also why we plan migrations as reversible steps with backfill and verification at each stage, scheduled around your quiet hours, instead of a big-bang rewrite over a weekend.

Question 13

Will the site actually rank on Google?

Accepted Answer

We ship the technical foundations that rankings need — semantic markup, metadata, sitemaps, and Core Web Vitals budgets — but we will not promise a position. Rankings compound from content and links over months, and no build partner controls either one. Anyone who guarantees page one for a new domain is guessing. What we can commit to is that nothing on your site is quietly holding it back.

Question 14

Who will we actually be working with?

Accepted Answer

There is no account manager layer between you and the people writing the code. The person who scopes your project is the person who delivers it, so nothing gets re-explained at a handover. Scoping and pricing, engineering and delivery quality, and building the apps are all covered by the same people, on the same project, from the first conversation to the last deploy.

Everything we get asked.

Questions, answered.