Why the same word carries very different prices
A corporate website isn't a product with a part number. To one person it means seven pages describing services plus a contact form. To another it means a system with a partner login area, price lists synced from an accounting system, three languages, and an admin panel where a content manager assembles pages block by block.
The gap between those two isn't double. It's closer to tenfold. Until the brief says what's included, any figure is an answer to a question you didn't ask.
The second source of spread is who does the work. A freelancer builds on a ready-made template and bills their hours. A small studio designs from scratch, builds the front end by hand, tests across devices, and stands behind the result as a team. A large agency adds an account manager, analytics, and process on top. All three are honest models. You're simply buying different things.
What actually goes into the estimate
It helps to see the price not as one number but as a sum of work items. Then it's clear where you can trim and where you can't.
- Research and structure: who your customers are, which pages you need, what belongs on each one. You can skip it, but redoing things later costs more.
- Design. Priced by unique layouts, not by pages. Ten service pages on the same grid are one layout, not ten.
- Responsive work for phones and tablets. That's separate effort, not something that adjusts on its own.
- Front-end build and development: assembling pages, forms, integrations.
- The admin panel. An off-the-shelf CMS is cheaper; a custom one costs more but bends to non-standard content.
- Integrations: CRM, accounting systems, payments, email, analytics. Each one is its own line item.
- Content. Text and photos are either yours, or they're an addition to the estimate, and a noticeable one.
- Testing and launch: browser checks, speed, tracking, domain, hosting, SSL.
Where money quietly leaks
The most common gap is content. The client assumed the text would somehow get written, and a month later the project is stalled because nobody produced the service descriptions. Design is done, the build isn't, payment is stuck. Easy fix: before you start, agree who writes the copy and by what date, and put it in writing.
The second gap is integrations. "Leads should land in our CRM" sounds like one line, but if your CRM is homegrown with no proper API, it can cost more than the rest of the site. Ask before signing: has the contractor worked with your CRM, or will they figure it out on your budget?
The third is revisions after delivery. Clarify how many rounds are included and what counts as a revision versus a new task. Rewording a headline and adding a careers section are different things, and it's good when the contract treats them differently too.
How to read an estimate and what to ask
A good estimate is a list of work items with hours or prices against each one. A bad estimate is a single line that says "website development". With the second kind you can neither compare offers nor remove anything.
Ask for the estimate broken down by block. If the contractor refuses, that's not confidentiality. That's the absence of a calculation.
- How many unique design layouts are included, and what happens to the remaining pages.
- Who writes the copy and takes the photos. If that's you, by what date.
- What happens to the site after launch: who hosts it, who updates it, what it costs per month.
- Who owns the source files and the access credentials. "We keep the access" means moving to another contractor will hurt.
- What support covers and what gets billed separately.
- How the timeline is calculated, and whether the delivery date shifts if your content is late.
When you don't need a corporate website
If the goal is to test demand for one service and collect enquiries, you need a landing page, not a twelve-section site. It costs a fraction, launches faster, and tells you right away whether the offer works at all.
If you sell through messaging apps and you're drowning in the same questions over and over, put the money into a Telegram bot or automation and leave the site for later. A multi-page site with no internal process behind it doesn't generate enquiries by itself.
And if you have no content - no text, no photos, no clear sense of how you differ from competitors - it's too early to start with design. A beautiful empty storefront costs the same as a full one and sells nothing.
How to make sense of the numbers
Look at the starting-from range a contractor publishes openly. Ours is on the site for every service: landing pages, corporate sites, online stores, Telegram bots, web services, and support. It isn't a final price, it's a reference point. Below the lower bound, the work usually can't be done without losing quality.
The exact figure appears only after a brief, once the page count, the set of integrations, and content ownership are clear. If someone gives you a final price after five minutes on the phone, they'll either raise it later or cut the scope.
The wide range isn't market chaos. It reflects how many different volumes of work hide behind the phrase corporate website. Ask for an estimate broken into blocks, pin down who owns the content, and compare offers by what's in them rather than by the final number.
Frequently asked
Why can't you quote a price right away over the phone?
We can give you a range, and that's the honest answer. The exact figure depends on the number of unique layouts, the integrations, and who prepares the content. Until that's known, any number is either padded for safety or set low with add-ons waiting.
Is a cheap template site always a bad idea?
No. If the goal is a basic online presence with your services and contact details, a template handles it fine. Trouble starts when you need non-standard functionality, your own visual style, or integrations: at that point reworking the template costs more than building from scratch.
What does it cost to keep a site running after launch?
There are fixed technical costs: domain, hosting, SSL, and those are small annual amounts. Support is separate: updates, content edits, responding to outages. We publish a starting-from range for support too, and the format depends on how often you plan to change the site.
What if my budget is below the lower bound?
Cut scope, not quality. Five pages instead of fifteen, integrations postponed, an off-the-shelf CMS, more sections added later. That works. What doesn't work is asking for the same scope at half price: the savings come out of testing and responsive work, and you find out after launch.