Planning guide / Estimates
Website cost factors in Sri Lanka.
A transparent way to understand what shapes an estimate, what continues after launch and how to compare proposals that may look similar at first glance.
Direct answer
What determines website cost in Sri Lanka?
A website estimate is shaped by the outcome and scope, number and variety of templates, content readiness, design originality, responsive behaviour, workflows, integrations, data migration, administration, accessibility, SEO foundations, security, quality assurance, launch responsibility and post-launch support. Hosting, domains, licences, payment or messaging services and maintenance may be separate recurring costs. Location affects commercial context, currency and local dependencies, but a responsible estimate still needs a specific brief; page count or a generic price band cannot describe every website.
01 / Estimate logic
A quote prices a defined responsibility.
The same phrase—"business website" or "online store"—can hide very different journeys, content, systems and launch obligations.
An estimate becomes more reliable when it describes what will be delivered, what evidence will confirm completion, which inputs the client provides and which uncertainties remain. A discovery phase may be appropriate when the important workflow, integration or content model is not yet understood well enough to commit to a build scope.
Four components behind an estimate
Scope
Pages, templates, states, roles, workflows, content, languages, integrations and environments included in the work.
Effort
Research, strategy, writing, design, development, configuration, migration, review, testing, training and release work.
Risk
Incomplete data, unfamiliar external systems, approval dependencies, changing requirements or hard-to-test operating conditions.
Responsibility
Hosting, licences, monitoring, updates, support, content operations, account ownership and change after launch.
This guide does not publish a made-up price bracket or promise a universal timeline. Two projects with the same number of pages can require very different work. A useful figure follows a useful scope.
02 / Main cost drivers
Identify variety, behaviour and responsibility.
Raw page count is less informative than the number of unique layouts, content types, rules, user states and systems involved.
| Driver | What changes the work | What to define for an estimate |
|---|---|---|
| Purpose and scope | A public information site, catalogue, booking journey, online store and customer portal carry different obligations. | Priority outcomes, included journeys, launch boundary and explicit exclusions. |
| Page and template variety | Many pages using a stable system differ from a few pages with unique interactions and layouts. | Content types, reusable templates, special landing pages, states and responsive rules. |
| Content | Strategy, research, writing, translation, product entry, photography, illustration and migration require different contributors. | Content inventory, source quality, creator, approver, formats and readiness dates. |
| Design | Adapting an established system differs from creating a new visual direction and custom interaction language. | Brand inputs, accessibility targets, prototype depth, component system and review rounds. |
| Features and workflows | Forms, search, bookings, pricing rules, accounts, approvals and administration add logic and edge cases. | User roles, steps, validations, notifications, exceptions and acceptance scenarios. |
| Integrations | Payment, ERP, CRM, inventory, maps, messaging or identity services depend on external access and behaviour. | Provider, API access, data direction, frequency, failure handling, test environment and owner. |
| Data migration | Volume matters, but inconsistent fields, duplicates, missing media and unclear history often matter more. | Source access, field mapping, clean-up responsibility, reconciliation and archival rules. |
| Quality and release | Supported devices, accessibility depth, security review, performance work and release coordination affect effort. | Test matrix, acceptance criteria, environments, owners, launch plan and warranty boundary. |
| Ongoing operation | Managed hosting, monitoring, maintenance, content support and response expectations continue beyond launch. | Recurring services, exclusions, service hours, escalation and account ownership. |
03 / Content and design
Readiness changes both effort and sequence.
A build can be technically complete and still unable to launch because the words, products, images, approvals or translations are not ready.
Content responsibilities to price or assign
- Content strategy, audience questions, information architecture and a page or content-type inventory.
- Original writing, editing existing material, fact checking, proofing and approval.
- Sinhala, Tamil, English or other language requirements, including who translates and reviews meaning in context.
- Photography, video, illustration, icons, diagrams, licences, releases and file preparation.
- Product, service, team, location, policy, case study or knowledge-base data entry.
- Migration from an old site, including redirects, metadata, files and decisions about obsolete content.
- Ongoing publishing roles, editorial permissions, training and governance after launch.
Design is more than a home-page image
Design effort includes journey mapping, content hierarchy, reusable components, interaction states, mobile and large-screen behaviour, forms, errors, loading and empty states, accessibility and handoff. A heavily templated solution may reduce original design work but can introduce constraints that must be accepted explicitly.
If a proposal says "content included," confirm whether that means page population with finished client material, editing, original writing, product entry, translation, photography or all of those. The same word can describe very different responsibilities.
04 / Workflows, integrations and data
Invisible rules can outweigh visible pages.
Every role, state change, external dependency and recovery path adds analysis, implementation and verification.
A contact form that sends a message is different from a lead workflow that validates eligibility, creates a CRM record, assigns an owner, sends a localized acknowledgement and tracks consent. An online payment button is different from a commerce flow that reconciles orders, stock, refunds, delivery and accounting states.
Integration questions that affect confidence
- Does the external provider offer documented, permitted access for the required operation?
- Are credentials, commercial accounts, onboarding and a safe test environment available before development?
- Which system is the source of truth, and which direction does each field move?
- Is exchange immediate, scheduled or manual, and what volume or service limits apply?
- What happens when data is invalid, delayed, duplicated, rejected or only partly processed?
- Who monitors failures, corrects records and contacts the external provider after launch?
Migration is a data project
Request a sample audit before assuming existing records can move automatically. Estimate clean-up, mapping, media recovery, transformation, test imports and reconciliation. Decide what must be migrated, what can remain in an archive and which old URLs require redirects. Personal or commercially sensitive data also needs an appropriate transfer and access plan.
For local payment, delivery, messaging or business systems, verify current onboarding, supported transaction flows, settlement or billing currency, documentation, test access and ongoing fees directly with each provider. Availability and commercial terms can change; they should not be assumed from an old integration or a marketing page.
05 / Quality and launch
Quality must be defined to be estimated.
"Responsive, fast, secure and SEO-friendly" are useful intentions but weak acceptance criteria.
| Quality area | Clarify | Evidence at handover |
|---|---|---|
| Responsive behaviour | Priority devices, browsers, orientations, zoom and representative content extremes. | Agreed journey checks across the supported matrix. |
| Accessibility | Target standard, keyboard and focus behaviour, labels, errors, contrast, alternatives and assistive-technology review. | Test notes, known limitations and resolved issues for agreed journeys. |
| Performance | Important page types, expected content, representative devices and network context. | Measured results with the test conditions stated, plus an image and content operating guide. |
| Security and privacy | Data collected, user roles, administration protection, updates, logs, retention, backups and incident responsibility. | Configuration and responsibility record without exposing secrets. |
| SEO foundations | Crawlable routes, metadata, canonical rules, structured data, redirects, sitemap and measurement setup. | Technical checks and access handed to the client's controlled accounts. |
| Quality assurance | Who tests content, functions, integrations and real business scenarios; how defects are prioritized. | Acceptance record and a list of known, explicitly accepted limitations. |
| Launch | Domain changes, production accounts, data freeze, rollback, monitoring, communication and final decision owner. | Launch checklist, ownership map and recovery information. |
Search foundations can improve crawlability and understanding, but no website supplier can responsibly guarantee first position for a query. If an estimate promises a rank, ask for the exact work, measurement method, assumptions and limitations rather than accepting the promise as a deliverable.
06 / Beyond the build
Separate one-time and recurring obligations.
A lower initial figure may exclude services, licences or work the business still needs to operate safely.
Costs to list separately
- Domain: registration, renewal, DNS management and the account that legally controls it.
- Hosting and infrastructure: environment, backups, storage, traffic, delivery, monitoring and scaling model.
- Software licences: content systems, plugins, fonts, media, search, analytics or other paid components.
- Transaction and usage services: payment, SMS, email, maps, storage, AI or external APIs whose fees may vary with use.
- Security and maintenance: updates, dependency review, backup checks, monitoring, incident response and compatibility testing.
- Content and growth: publishing, new pages, product entry, experiments, reporting and search-content improvement.
- Support and change: included hours or tasks, response expectations, exclusions and the process for estimating new work.
Currency and tax clarity
A Sri Lankan proposal should state the quotation currency, payment schedule, validity period, whether applicable taxes are included, and how foreign-currency licences or usage services will be billed if their cost changes. Ask for the service provider, renewal interval and account owner for every recurring item.
The organization should understand who controls its domain, hosting, analytics, search tools, payment accounts, source code, repositories and third-party subscriptions. A handover should document access and responsibility without distributing passwords insecurely.
07 / Compare proposals
Normalize the scope before comparing totals.
Two numbers are not comparable when the included work, assumptions, ownership or recurring obligations differ.
| Proposal line | What a clear response should show | Common ambiguity to remove |
|---|---|---|
| Deliverables | Page types, components, journeys, administration, integrations, environments and documentation. | "Complete website" without a route or acceptance inventory. |
| Client inputs | Content, brand files, product data, legal text, access, reviewers and due dates. | Work described as included while depending on unassigned client preparation. |
| Process | Discovery, content, design, build, test, review, training and release stages. | A timeline with no dependency or approval assumptions. |
| Review and change | Review points, included revision boundaries and how new scope is assessed. | "Unlimited changes" without explaining schedule, decision or completion boundaries. |
| Quality | Browser/device matrix, accessibility, performance, security, SEO and acceptance method. | Adjectives without test conditions or evidence. |
| Third parties | Provider, current commercial dependency, allowance, usage model and account owner. | Licences or external fees omitted from the total ownership picture. |
| Handover | Accounts, source, documentation, training, deployment, warranty and support boundary. | Unclear ownership or dependence on one supplier for basic access. |
| Commercial terms | Currency, taxes, payment stages, validity, exclusions and recurring charges. | A headline total without the conditions that produced it. |
If approaches differ, ask each provider to identify why. One may recommend a template-led start while another proposes a custom content system or workflow. The better decision depends on required fit, change, ownership and risk—not automatically the lowest or highest total.
08 / Estimate-ready questions
Give every provider the same useful brief.
Comparable inputs produce more explainable estimates and reveal the decisions that still need discovery.
Business and audience
- What business outcome should change, for which priority audience and why now?
- What are the three most important user journeys from entry to a confirmed outcome?
- Which regions, languages, currencies, policies and accessibility needs are in scope?
Content and design
- What content exists, what must be created, who owns it and when will approved material be ready?
- Which page or content types repeat, and which require distinct layouts or interactions?
- Is an established brand system available, or is brand and visual-direction work part of the project?
Functions, data and systems
- Which forms, transactions, searches, accounts, roles, workflows and administration tasks are required?
- Which external systems must exchange data, and is current documentation and test access available?
- What information must migrate, from where, in what condition and with what reconciliation?
Quality, launch and ownership
- Which devices, browsers, accessibility requirements, privacy constraints and security responsibilities apply?
- Who reviews content, design and functionality, and who makes the final acceptance and launch decision?
- Who will control accounts and maintain hosting, software, content, analytics, integrations and support after release?
- Which one-time and recurring charges should the proposal separate, in which currency and with which assumptions?
Use the website project brief template to assemble these answers in one reusable document.
Hich Web Development
Planning guidance from the organization.
Published and updated .
09 / Continue
Move from a vague price request to a clear brief.
Prepare comparable inputs, then explore the service that matches the required outcome.