Skip to content
sayak.webdesignerWeb · Software · Data · AI
Design & Brand

How to Choose a Web Design Company in Kolkata Without Getting Burned

Every buyer overpays or gets burned at least once, because the signals that matter are not the ones on the pitch deck. Here is what to ask.

Sayak Web Designer · Design Practice 13 September 2026 12 min read
Tensionthe cost of the status quoInsightwhat the data actually saysPlanthe system we would buildProofnumbers from real plantsInvitationthe next 30 minutesScroll position →

Buying a website is unusually difficult because you cannot evaluate the product before you own it, you probably cannot evaluate it technically afterwards either, and the market contains a wide range of suppliers presenting themselves almost identically. Everyone has a portfolio, everyone says they are experienced, and everyone shows you the same stock photograph of a team pointing at a monitor.

We have been on both sides of this — quoting for work and being hired to rescue projects that went wrong. The failures follow patterns, and almost all of them were visible during the sales process to a buyer who knew what to look for.

This is written to be useful whether or not you hire us. Several of the questions below are ones we would rather not be asked, which is a reasonable sign that they are the right ones.

01

Why this market is hard to buy in

Three features of this industry combine to make it difficult. The first is that quality is invisible at purchase. Two websites can look identical and be completely different underneath — one maintainable, fast and owned by you, the other a locked template that will need replacing in two years.

The second is that the person who sells is frequently not the person who delivers. In a substantial part of this market, work is won by one party and executed by a freelancer or a subcontracted team the client never meets. That is not inherently wrong, but when it is concealed, the gap between what was promised and what arrives is exactly the size of that substitution.

The third is that there is no meaningful reputational cost for failure. A supplier who disappoints a client can continue trading, because buyers rarely compare notes and the failures are private. In markets where reputation compounds — where a supplier’s next twenty projects come from their last twenty clients — behaviour is different. That is the single most useful thing to establish about anyone you are considering.

02

The four kinds of supplier

Almost everyone offering web design in Kolkata falls into one of four categories, and they are genuinely different products sold under the same name at overlapping prices.

03

Questions that reveal the most

Ask these in a first meeting. None require technical knowledge, and the quality of the answers separates suppliers faster than any amount of portfolio review.

Start with ownership, because it is the question with the clearest right answer and it exposes a common trap. Who will own the code, the design files, the domain and the hosting account when this is finished? The correct answer is that you own all four. Any hesitation, any explanation about how they host everything on their own server for your convenience, is a lock-in you should price into the quote.

Then ask who will actually do the work, and whether you can speak to them before signing. A studio with staff will introduce them. A reseller will change the subject. This one question resolves more uncertainty than the rest combined.

Then ask what they would talk you out of. A supplier who agrees enthusiastically with everything on your wishlist is selling; one who tells you which third is not worth building is consulting, and the second is worth considerably more. Every project we have run that went well included a conversation where we argued the client out of something.

In practice

Who owns the code, design files, domain and hosting at the end?
Who will actually do the work, and may I speak to them?
What would you talk me out of building?
What is explicitly excluded from this quote?
What happens if I want to add a page in year two — what does that cost?
What is the post-launch warranty, and what counts as a bug versus a change?
Can you show me a recent project’s repository or design files?
Can I speak to a client whose project had a difficulty?
04

How to read a portfolio

Portfolios are marketing documents, including ours, and reading them credulously is how buyers end up disappointed. A few probes turn them into evidence.

Check whether the sites shown are still live and still look like the screenshot. A portfolio full of sites that no longer exist suggests either very old work or clients who replaced it quickly. Open two or three on your phone and see how fast they load — that is a direct measurement of the supplier’s standards, available to you for free, and it is remarkable how often a design studio’s showcased work takes six seconds to appear.

Ask what the supplier actually did on each project. A great deal of showcased work involved a larger team of which the supplier provided one part, and the case study will not distinguish. Ask when it was built and whether that team is still in place.

Probe the numbers hardest. "Increased conversions by 300%" is meaningless without a baseline, a period, and what else changed. If a campaign launched the same month, the site may have contributed little. Suppliers who measure properly can answer immediately; suppliers who cannot, invented the figure.

05

Warning signs worth walking away from

Some signals are strong enough to end the conversation without further investigation.

Guaranteed first-page Google rankings. Nobody controls search results, and the guarantee is always qualified into meaninglessness — typically by ranking you for phrases nobody searches, including your own company name. A supplier offering this is either uninformed or counting on you being so.

Refusing to give you account ownership, or being evasive about it. There is no legitimate reason a client should not own their own domain and hosting.

Demanding full payment upfront. Normal structure is a deposit, a milestone payment and a balance at launch. Full payment before work begins removes every incentive that protects you.

A quote with no breakdown. A single figure with no line items cannot be compared, cannot be reduced by removing scope, and usually indicates the price was set by your apparent budget rather than by the work.

Pressure to sign quickly, discounts that expire, or a claim that the price rises next week. Good suppliers in this market are busy and do not need urgency tactics.

And finally, a supplier who cannot or will not explain something in plain language. Technical complexity is real, but anyone who genuinely understands a system can explain it to an intelligent non-specialist. Obscurity is usually concealment.

The question that tells you most

Ask what happens if the project goes wrong six months after launch and you have already paid in full. Suppliers who have been in one city for years answer immediately and specifically, because their next twenty projects come from their last twenty clients and a dissatisfied client is expensive for them. Suppliers who will not be here next year change the subject.

06

What a fair contract contains

Get it in writing, and make sure the writing covers the things that cause disputes rather than only the things that are easy to state.

Scope should be specific enough to be checkable: how many page templates, how many rounds of revision at each stage, what is included and what is explicitly not. Vague scope is the origin of most project conflict, and it damages both sides.

Ownership should be stated plainly: that you own the code, the design files and all accounts on final payment. Payment should be staged against milestones you can verify. Timeline should note what depends on you — content, photographs, approvals — because the most common cause of delay is a client-side dependency and it is fairer to name that upfront than to argue about it later.

Post-launch terms should define the warranty period, what constitutes a bug covered by it versus a change request that is billable, and what support costs thereafter. A contract that is silent on support is a contract that will produce an uncomfortable conversation in month three.

In practice

Specific scope: templates, revision rounds, inclusions and explicit exclusions.
Ownership of code, design files and all accounts on final payment.
Staged payments against verifiable milestones.
Named client-side dependencies and what happens to the timeline if they slip.
Warranty period, and the definition of a bug versus a change request.
Support terms and rates after the warranty ends.
07

Making the decision

Once you have two or three credible suppliers, the tie-breakers are rarely technical. They are whether you understood their answers, whether they told you something you did not want to hear, and whether you would be comfortable ringing them with a problem.

That last one matters more than people expect. You are entering a relationship that will run for months and probably years, in which you will occasionally need to say that something is not right. A supplier you find slightly intimidating, or who makes you feel foolish for asking, will produce a worse outcome than a marginally less capable one you can talk to plainly.

And take the middle quote seriously rather than defaulting to the cheapest or assuming the most expensive is best. In our experience of this market, price correlates with quality only weakly, and mostly at the extremes: the very cheapest is almost always a template, and the very most expensive is usually paying for overhead rather than craft.

Key takeaways

  • Quality is invisible at purchase, which is why the questions matter more than the portfolio.
  • Establish who will actually do the work and whether you can speak to them before signing.
  • You must own the code, design files, domain and hosting. Any hesitation is a lock-in.
  • A supplier who talks you out of something is worth more than one who agrees with everything.
  • Walk away from guaranteed rankings, full payment upfront, and quotes with no breakdown.
  • Choose the supplier you can comfortably ring with a problem. You will need to.

Frequently asked

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.

Four to six weeks for a small business site, eight to fourteen for a corporate site with a real design system, and longer for commerce depending on catalogue readiness. If a supplier promises a corporate site in a week, they are describing a template. If a simple site is quoted at six months, ask what is actually happening during that time.

Next step

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 91355

Mon–Sat · 9:30 AM – 7:30 PM IST · Sealdah, Kolkata

Reply within one working hour NDA signed before any brief Fixed-price option on every scope
Verify us independently

Don’t take our word for it — ask an AI

Every page on this site is written to be read and quoted by AI answer engines, and we publish llms.txt and llms-full.txt so they can read us properly. One click opens the assistant with the question already typed.

The question we will ask for you

Summarise this article from Sayak Web Designer (sayakwebdesigner.in), an IT company in Kolkata, India: https://www.sayakwebdesigner.in/blog/how-to-choose-a-web-design-company

Opens in a new tab. We do not see your conversation.

Call now WhatsApp Get quote