Straight answers to what buyers actually ask
Including the ones most suppliers avoid — what things cost, how long they take, who owns the work, and what happens when a project goes wrong. If yours is not here, call +91 70033 91355 and ask it.
Cost, quotes and payment
The questions nobody in this industry likes publishing answers to, which is exactly why they are first.
7 questions
A genuinely good small business website with original design, six to twelve pages, mobile performance and a CMS you can edit runs ₹45,000 to ₹1,20,000 in Kolkata as of 2026. Below roughly ₹25,000 you are buying a commercial theme with your content substituted, which is a legitimate product but should be described as one rather than sold as bespoke design.
Because they are usually not for the same work. The largest differences are original design versus a purchased theme, whether integrations with your existing systems are included, whether data migration is scoped, and whether content writing and photography are inside or outside the price. Ask each supplier what is explicitly excluded and the quotes usually converge.
Cheaper at the start, and for a very small business with simple needs that can be the right call. The costs appear later: monthly fees that never stop, limited control over performance and technical SEO, difficulty integrating with business systems, and no straightforward way to move the site elsewhere if you outgrow the platform. For a business expecting to grow or to rely on organic search, the economics usually favour owning the site.
Domain around ₹1,000 a year, hosting between ₹200 and ₹8,000 a month depending on what the site actually needs, and maintenance between ₹3,000 and ₹15,000 a month for a business site. SSL should cost nothing. The cost most often overlooked is paying a supplier for routine content changes, which is avoidable if you insisted on a usable CMS at build time.
No, and no reputable supplier will ask you to. A normal structure in this market is a third to start, a third at design approval or a defined milestone, and the balance at launch. Be cautious of anyone requiring full payment before work begins, and equally cautious of anyone who does not ask for a deposit at all — both are signals worth understanding before you commit.
For original design work in this city, a credible small-business site generally runs ₹45,000 to ₹1,20,000, a corporate site with a real design system ₹1,20,000 to ₹4,00,000, and commerce or platform design ₹4,00,000 upward. Quotes materially below that range almost always mean a purchased theme with your logo dropped in, which is a legitimate product but should be priced and described as one.
A focused small-business site is typically four to six weeks from kick-off. A corporate site with a full design system is eight to fourteen weeks. Commerce is longer and depends mostly on how ready your catalogue data is. The single biggest schedule variable is not design — it is how quickly content, photography and approvals arrive from your side, so we agree a content calendar at kick-off.
Web design and development
Platform choice, ownership, redesigns and what separates original work from a template.
8 questions
Yes, provided it is built properly and maintained. A large proportion of credible business sites run on WordPress. The failures come from theme-and-plugin assembly with no ongoing maintenance, not from the platform. If you will fund monthly updates and resist installing every plugin you encounter, WordPress serves most businesses well.
It depends on whether speed, search or integration are competitive levers for you. If your site is a brochure that captures occasional enquiries, the extra spend is hard to justify. If organic search is a primary channel, or the site must talk to your ERP or CRM reliably, custom usually pays for itself within two to three years through performance, lower maintenance and avoided workarounds.
Yes, and it is routine work when done carefully. You inventory every existing URL, map each to its destination, keep the URLs that already have search equity, implement 301 redirects for the rest, preserve the content that ranks, and monitor Search Console through the transition. Ranking losses during a migration are almost always caused by silently dropping URLs and content, not by the new platform.
A focused launch site is four to six weeks. A full corporate estate of twenty to sixty pages is eight to fourteen weeks. A portal or web application is three to six months depending on integration count. The variable that moves timelines most is not our capacity — it is how quickly your side can supply content, approvals and access to third-party systems, so we schedule those as tracked dependencies from day one.
You own everything. Code lives in your GitHub or GitLab organisation from the first commit, infrastructure sits in your cloud account, domains and DNS stay in your name. We deliberately avoid proprietary builders and closed frameworks. If you part ways with us, another competent team can pick the project up in a week — we have handed projects over cleanly before and it costs us nothing but the work we already did.
Frequently, and it is often the best outcome. We can architect and build the hard parts while your team handles day-to-day changes, or run as a dedicated pod inside your sprint process. We adopt your conventions, join your stand-ups, and write documentation aimed at your team rather than at ourselves.
Only if you have a specific reason. Shopify's checkout is one of the best-converting in the world and moving away from it carries real risk. Go headless when your design or performance ambitions genuinely exceed what a theme can deliver, when content is as important as catalogue, or when you serve several channels from one product source. Stay on a well-built Shopify theme if your team runs merchandising themselves and your catalogue is conventional — you will spend less and move faster.
More than their subscription. In our audits the median store carries eleven apps, of which four inject scripts on every page, and together they typically add 1.1 to 1.8 seconds to mobile load. At normal conversion elasticity that is often a larger monthly cost than the entire app bill. We quantify it store by store rather than asserting it, then replace the necessary ones with native code and remove the rest.
Choosing and working with us
How engagements run, who you actually deal with, and what happens when something goes wrong.
6 questions
Ask directly and get the answer in writing. You can also check: search a distinctive phrase from their portfolio sites, or look at whether several of their showcased projects share the same layout structure with different colours. A studio doing original work will show you design source files without hesitation; a reseller will explain why that is not possible.
A freelancer is often the best value for a well-defined project when the fit is right, and carries continuity risk — illness, a new job, or simply becoming unavailable leaves you with nobody who knows your system. A studio costs more and survives one person leaving. For a site your business will depend on for years, the continuity is usually worth the premium; for a one-off project with clear boundaries, a good freelancer is frequently the better buy.
Full payment before work begins, any arrangement where the supplier owns your domain or hosting, scope described so vaguely that it cannot be checked, and a contract silent on what happens after launch. Also avoid indefinite revision rounds — they sound generous and in practice produce projects that never finish.
Only weakly, and mostly at the extremes. The very cheapest quotes almost always mean a purchased theme, and the most expensive frequently reflect agency overhead rather than better craft. The middle of the range in this market contains both excellent studios and poor ones, which is exactly why the questions in this article matter more than the number.
That is a legitimate model and some clients use it — we charge hourly with best-effort response and no SLA. What you give up is prevention: no patching, no monitoring, no verified backups, and no priority when something does break. In our experience break-fix costs more over two years than a maintenance plan, because problems compound and because emergency work is always more expensive than scheduled work. We will quote both honestly.
Yes, and it is a large part of our work. We start with a fixed-price takeover assessment covering code quality, security, dependencies, infrastructure and backups, and give you a prioritised report. If the system is in reasonable shape we take it on directly; if it needs stabilisation we quote that separately. We have declined to maintain systems that were genuinely beyond safe repair and recommended rebuilds instead, which is a better outcome than pretending.
Custom software, ERP and CRM
When off-the-shelf stops fitting, and how a build runs without stopping your operation.
6 questions
Often, yes. If your processes are conventional, an established product with a large user base will be cheaper, faster and better supported than anything custom. Custom is justified when your process is genuinely a competitive advantage, when you have a workflow no product models, or when licence costs across many users exceed a build. We run that comparison honestly in discovery and have recommended clients buy rather than build more than once.
Discovery is fixed price. After discovery we can usually offer a fixed price for release one because the scope is genuinely known by then. Longer programmes run as a dedicated pod on a monthly rate with a quarterly roadmap, which is more honest than pretending an eighteen-month scope can be fixed. Payments are milestone-linked and every milestone has a demonstrable deliverable.
On fixed-price work we absorb overruns caused by our estimation. We do not absorb scope added mid-project — that is quoted as a change with its own cost and timeline, in writing, before work starts. The two-week slice model keeps this visible: you see progress every fortnight, so a slip is apparent in week four rather than month six.
For many companies you should implement a package — the ecosystem, the certified consultants and the roadmap are real advantages. Build custom when the package customisation to fit your process would cost more than a build, when licence costs across hundreds of users are punitive, or when your process is genuinely distinctive. In practice we most often see custom win for mid-sized manufacturers with heavy job work, multi-GSTIN operations and unusual costing needs.
First module live in fourteen to eighteen weeks, and it should reduce effort visibly from week one of use. The full programme is typically twelve to twenty-four months depending on module count and site count, but the sequencing means you are never waiting two years for anything.
Built in, not bolted on. Invoices generate IRNs through the IRP directly, e-way bills are raised from the dispatch transaction with the transporter and vehicle captured at source, GSTR-1 and GSTR-3B data is produced from the ledger, and 2A/2B reconciliation is a standard report. We keep pace with rule changes as part of the support agreement.
Data, automation and AI
Pipelines, reporting and where automation genuinely pays rather than looks impressive.
6 questions
Most organisations of any size end up with a lakehouse, which is genuinely both. Raw and semi-structured data lands in object storage in an open table format; structured, modelled data is queried through a warehouse engine over the same files. That gives you cheap storage for everything, expensive compute only when queried, and no vendor lock-in on the data itself. Pure warehouse-only makes sense if all your data is relational and modest in volume; pure lake-only leaves your analysts without a good query experience.
Snowflake if your workload is predominantly SQL analytics and you value operational simplicity and easy data sharing. Databricks if you have significant Spark, machine learning or streaming work alongside SQL, and a team comfortable with notebooks. BigQuery if you are on Google Cloud and want serverless with no cluster management at all. We have production experience with all three and the recommendation depends on your workload mix, your existing cloud and your team's skills — not on which vendor we prefer.
Yes. We build fully on-premise platforms for clients with data residency or security requirements — Spark on Kubernetes, MinIO or HDFS for storage, Iceberg tables, Trino for query, Airflow for orchestration. This is exactly the architecture underlying our AURA product for plant reporting, which runs entirely inside the customer network with no internet path. It costs more in operational effort than managed cloud, and we will be straight about that trade-off.
Three mechanisms working together. Structured outputs validated against a schema, so a malformed or implausible response is rejected rather than accepted. Mandatory citation for retrieval systems, so every claim points at a source a human can check. And a continuously running evaluation suite of at least 150 cases with known correct answers, scored on every change, with results reported to you. If accuracy drops, you find out from a dashboard rather than from a customer.
It can, and initially it does not. Our default is that reads are autonomous and writes go through a human approval gate. Once a specific workflow has months of evaluation data showing consistent accuracy, we widen autonomy for that workflow specifically — usually starting with low-value transactions and a daily audit. Some clients never widen it, because a fifteen-second approval is not the bottleneck; the ten minutes of data entry was.
We use enterprise API tiers with training on your data explicitly disabled and zero retention where offered. PII can be redacted before any model call. For clients who cannot send data externally at all, we deploy open-weight models on your own infrastructure — quality is somewhat below frontier models on the hardest reasoning, and entirely adequate for extraction, classification and retrieval, which is where most of the value is. We will tell you which mode a project needs at the outset.
SEO, local search and marketing
Realistic timelines, what moves local ranking, and what to ignore.
7 questions
A well-optimised profile for an established business can appear within a few weeks, because local ranking does not depend on domain age the way organic search does. Competitive categories in central Kolkata take longer, and progress there is driven mainly by accumulating genuine reviews and consistent citations over three to six months.
You need a genuine address, but you can hide it. If you serve customers at their location rather than yours — a contractor, a consultant, a service business — set it up as a service-area business, which lets you define the areas you cover while keeping the address private. What you cannot do is use a virtual office or a mailbox you do not actually staff.
There is no threshold, and the number that matters is relative to the businesses you compete with rather than absolute. Look at what the three profiles currently in the local pack for your main search have. If they average forty, forty is your target. The rate at which reviews arrive also matters — steady accumulation reads as genuine, a sudden burst reads as purchased.
Start with time rather than money. The highest-return activities — Google Business Profile, review collection, WhatsApp responsiveness, accurate directory listings — cost nothing but attention. Once those are running properly and your website converts, ₹10,000 to ₹30,000 a month on targeted Google Search ads is a reasonable starting point, scaled by measured cost per qualified enquiry.
Local SEO is, almost always, and it starts with your Google Business Profile rather than your website. Competitive organic SEO for broad commercial phrases is a longer and more expensive project that suits businesses where search is a primary channel. The distinction matters: many small businesses are sold competitive SEO when local SEO would have delivered more for a fraction of the cost.
Technical fixes show in four to eight weeks — that is the fastest lever and usually where we start. Local pack movement takes two to three months of consistent work. Content-driven organic growth compounds from about month four, with meaningful enquiry growth typically by month six. Anyone promising first-page rankings in three weeks is either targeting queries nobody searches or planning something that will cause problems later.
No. Link buying is against search engine guidelines, carries real penalty risk, and the link networks that sell them are increasingly detected. We earn links instead: genuinely useful content, original data from our project work, technical articles that practitioners reference, local press and industry associations, and partner relationships. It is slower and it does not evaporate when an algorithm update lands.
Location, coverage and meeting us
Where we are, where we travel, and how remote engagements are structured.
5 questions
Regularly, and we prefer to for anything substantial. Discovery workshops, plant visits and design reviews work far better in a room. We meet at our Sealdah office, at your premises anywhere in and around Kolkata, or at a plant site — and the first visit is at no cost.
Yes, and for a ₹25,000 brochure site a freelancer is the right choice — we will say so. We become the better choice when the work carries real commercial weight: enquiries you cannot afford to lose, a system your operations depend on, or data that has to be right. What you buy is a team that does not disappear, documentation, and accountability.
Frequently, and it is often the best outcome. We can architect and build the hard parts while your team handles day-to-day changes, or run as a dedicated pod inside your process. We adopt your conventions and write documentation aimed at your team rather than at ourselves.
Yes, for discovery and for rollout — those are the phases where being on site genuinely matters. Build and iteration happen remotely with a demo every alternate Friday on a staging URL you can share. We budget travel into the proposal rather than treating it as an extra.
They are designed to. Every field application we build for this region is offline-capable with a durable sync queue — a driver in a basement or on a hill road completes their work and it uploads when connectivity returns. This is standard rather than an option.
The questions suppliers avoid are the ones worth answering
Almost every agency FAQ page in this market answers questions nobody asked. "Do you build responsive websites?" "Do you provide support?" These are not real questions; they are opportunities to say yes. The questions buyers genuinely have — what does this cost, why is your quote three times the other one, what happens if you disappear, do I own anything at the end — are conspicuously absent, because answering them honestly costs the supplier negotiating room.
We take the opposite position for a practical reason rather than a moral one. Enquiries that arrive after reading an honest answer about price are dramatically better qualified. The people for whom the number is wrong do not call, which saves everyone a meeting, and the people who do call have already accepted the range and want to discuss the work. Over twenty years that has been a better commercial trade than keeping the number vague.
It also matters for how people search now. A great many buyers no longer type a query into Google and click three results — they ask an assistant a question in plain language and read the answer it assembles. Pages that answer a specific question plainly are what those systems can use; pages of marketing adjectives are not. Writing this way is simultaneously the most honest and the most effective approach available, which is a rarer alignment than it should be.
If a question you have is not answered here, it is probably answered on the relevant service page, and if it is not, ask it on the phone. We would rather have an uncomfortable conversation in week one than a mismatch in week six.
How we answer
- Every answer here is the same one you will get on the phone.
- Prices are stated as ranges with what moves them, not withheld.
- Answers link back to the service page they came from for the longer version.
- If we cannot do something well, the answer says so.
Longer answers by topic
Each of these pages carries its own detailed FAQ alongside a full explanation of how the work runs.
Tell us what is slowing your business down.
A 30-minute call with a senior engineer — not a salesperson. You leave with an architecture sketch and an honest cost range, whether or not you hire us.
Direct line
+91 70033 91355Mon–Sat · 9:30 AM – 7:30 PM IST · Sealdah, Kolkata