Separate pages from functionality
List the information a visitor needs and the actions they should take. Five pages with similar layouts may be simpler than one page with account access, complex forms, and several integrations. Identify those functions before comparing quotes.
For a business in Kathmandu or Bhaktapur, a starting brief might include services, an about page, contact details, and an inquiry form. An NGO may also need program pages and downloadable publications. These are different scopes even if both are described as a company website.
Account for content and editing
Agree who supplies approved text, images, translations, and downloadable files. Content preparation and review are part of the schedule. If staff need to edit the site, specify the content types and publishing permissions required in the CMS.
A landing page estimate should include its form destination and any measurement requirements. CMS development costs depend on the editing and review workflow, migration, and integration with the public site. Ask which of these are included rather than assuming they come with the design.
Match the estimate to the type of website
A brochure-style business website, a conversion-focused landing page, and a publication-heavy NGO website create different work even when their page counts look similar. The table below is a scoping guide, not a price list: it shows which details usually change an estimate.
| Website type | Typical needs | Important cost drivers |
|---|---|---|
| Business or corporate site | Services, company information, inquiry forms, trust content | Distinct page layouts, copy and image readiness, forms, multilingual content |
| Campaign or landing page | One focused offer, a clear action, measurement | Custom interaction, form routing, analytics, campaign variants |
| Publishing or NGO site | Programs, articles, reports, media library | CMS structure, migration volume, filters, editorial roles, document handling |
| Website with application features | Accounts, saved records, payments, dashboards | Permissions, business rules, integrations, security and testing |
Compare the full launch and maintenance scope
Ask for a written breakdown that distinguishes development from recurring services and future updates. A lower initial quote may simply cover fewer responsibilities. Clarify who controls the domain and hosting accounts and how you receive access at handover.
- Page templates, mobile layouts, and design reviews
- Content entry, CMS setup, and staff handover
- Forms, integrations, and submission testing
- Existing URL redirects and launch checks
- Domain, hosting, third-party services, and maintenance
Set a schedule around decisions and dependencies
There is no reliable delivery date until the scope and dependencies are clear. Design approval, content readiness, access to an existing site, and external integrations all affect the schedule. Agree milestones and one person responsible for consolidating feedback.
To request a Kabeli estimate, share the site's purpose, an initial page list, examples of required forms, who will edit it, and any budget or deadline. We can then discuss a first release and identify what can wait.
Prepare a brief that makes quotes comparable
A useful brief does not need to prescribe the technology. Explain the audience, the most important action, and what is wrong with the current situation. Attach a content list or existing sitemap if you have one, and identify any immovable launch date such as an event or campaign.
Ask every provider to return the same categories: discovery, design, development, content entry, testing, deployment, training, and support. Where a category is excluded, record who will do it. This makes a website development quote easier to evaluate and reduces surprises after design has started.
- The primary audience and the action the website should support
- An initial page and content-type list
- Examples of forms, integrations, downloads, or multilingual content
- Existing domain, hosting, analytics, and CMS access
- The decision-maker, reviewers, budget context, and target date