What Should a Business Website Quote Include in Kenya? A Practical Owner Checklist

A website quotation can look tidy and still leave important questions unanswered: what will the site do, what must your team provide, what keeps it running after launch, and who controls the accounts when the work is finished? For a Kenyan business owner comparing proposals, the headline total is useful only when it is attached to a clearly described scope.

Write a short brief first, then ask each provider to price the same pages, customer journey, integrations, support and handover. This checklist shows what to include, how to separate one-time and recurring costs, and what to resolve before approving a project. It does not assume that every business needs the same platform or package.

What a website quote should answer

A useful quote explains the business outcome, included work, exclusions, delivery checks, client responsibilities and costs that continue after launch. A statement-of-work guide from Atlassian describes objectives, scope, deliverables, timelines, responsibilities and budget as core parts of a project brief. You do not need project-management jargon; you do need enough detail for two providers to price the same job.

“A modern website” is an aspiration. “A mobile service site with six named pages, a tested enquiry form, click-to-WhatsApp contact, analytics setup and staff handover” is something a supplier can estimate and you can review.

1. Define the business outcome and main action

Start with the reason for the project. Are you trying to receive qualified enquiries, help customers book, show a service area, take orders, or answer questions before a call? Name the main customer action for launch. The site may support several actions, but the quote should say which journey is essential now and which features can wait.

Describe the customer in practical terms: what they need, which towns or neighbourhoods you serve, and whether they usually arrive from a phone, map listing, social post or referral. Ask how the provider will demonstrate completion. For an enquiry site, test a service page on a phone, submit a test form and confirm the right staff member receives it. For booking or e-commerce, test confirmation and failure paths as well as the happy path. These are acceptance checks, not promises of a particular number of sales.

If reporting is included, ask which events will be measured and who owns the analytics account. A chat opening is not the same as a qualified enquiry or booked job. “Analytics included” could mean only a tracking tag, so ask whether useful events will be configured and tested.

2. Make pages, content and design countable

Request a page list, not just a page count. Home, service, about, contact, booking, product, FAQ, location and blog pages have different content and testing needs. If one template will be reused, say how many entries must be added before handover and who maintains them.

State who supplies the words, photography, logo files, translations, product details and approvals. A quote may include placing images but not their production or licensing; editing content may not include writing it. Clarify whether migration means copying a fixed number of pages or reorganising an existing site. If you need English and Kiswahili, identify the versions and who reviews them.

Ask what “SEO setup” means. It may cover page titles, descriptions, headings and clean URLs, but not keyword research or ongoing content. Ask which pages receive unique metadata and what is excluded. Search visibility depends on many factors, so a build quote should not be treated as a ranking guarantee.

3. Specify mobile, performance and accessibility checks

List the mobile tasks that matter: tapping a phone number, opening WhatsApp with a useful message, reading hours, completing a form with a small keyboard, selecting a date or viewing a product without excessive zooming. Ask which screen widths and browsers will be tested. If customers may have a weak connection, ask how image weight and key pages will be checked instead of assuming “responsive” covers performance.

Ask whether the provider will check keyboard navigation, visible focus, form labels, error messages, colour contrast and control spacing. W3C’s WCAG 2.2 Recommendation gives testable criteria for web content across devices. The quote should name the pages and checks included; a single automated score does not prove full accessibility or legal compliance.

For performance, ask which URLs will be tested, under what device or network conditions, what will be recorded before launch, and who will check for regressions. This makes the work inspectable without promising that a particular score guarantees more enquiries.

4. Name integrations and third-party dependencies

List each system the site must connect to: booking, WhatsApp, a customer relationship manager, email, maps, analytics, e-commerce or M-Pesa. Describe the job each integration must perform. “M-Pesa integration” might mean a payment link, checkout, payment prompt, order update or reconciliation; those are different scopes. For each system, ask who creates and owns the account, who pays its fees, and what happens if the supplier changes its service.

Ask how successful, failed or delayed transactions will appear to customers and staff. For forms, identify where submissions go, who can see them, and how failures are reported. For WhatsApp or chatbots, specify which questions are automated, when a person takes over, and how customers can reach the business without a bot. Separate implementation work from third-party subscription, transaction and messaging charges.

If automation is in scope, use the UniqueTechCamp AI Solutions Desk as a reference for the kind of conversation-led workflow that needs defined data access, human responsibility and measurement. It is not a default add-on; decide whether it belongs in your project only after the customer journey and operating costs are clear.

5. Separate build costs from operating costs

Ask for the first year and renewal years to be shown separately. A project may have one-time discovery, design, development, content or integration work, followed by domain registration, hosting, email, software licences, backups, maintenance or support. State which account owns each recurring service, when it renews, how the renewal price is set, and who receives expiry notices.

For a current Kenyan example, Truehost’s .co.ke domain pricing page lists a first-year offer of Kshs 299.00 for one year and a renewal price of Kshs 1,500.00 for another year. Its separate .CO.KE product page also promotes the offer but displays Ksh 999.00 in its domain table and Kshs 1,000.00 in a nearby pricing note. Confirm the amount shown at checkout and the renewal term before using a provider’s advert in your budget. These are one registrar’s displayed prices checked on 5 October 2026, not a market rate. Compare renewal terms as well as introductory offers, and make sure your business controls the registrar account and DNS access.

Hosting is separate from custom design and development. HostPinnacle’s official hosting page lists a Starter plan at Ksh 4,200 per year, excluding VAT, with 35 GB NVMe SSD storage, a free domain and SSL. This is one provider’s published hosting offer, not a custom site-build quote or a national benchmark. Check renewal price, usage limits, support and backup arrangements before comparing plans.

One local agency’s published packages show why the work included matters. KWETU Marketing Agency’s website pricing lists a Starter package at KES 72,000–132,000 + VAT (one-time project investment), a Growth package at KES 265,000–352,000 + VAT (one-time project investment), and an enterprise package at KES 396,000–572,000 + VAT (one-time project investment). The page describes different page counts, tracking, integrations and support at each tier. These are that provider’s examples, not an average or a price recommendation. Compare deliverables and renewal commitments, not just the headline amount.

Ask whether the quote is VAT-inclusive or exclusive. The Kenya Revenue Authority’s VAT page lists a 16% general rate for taxable goods and services other than zero-rated supplies, and distinguishes exempt supplies. That does not decide the treatment of your particular supplier or project; ask the provider or a qualified tax adviser if unsure.

Use a simple worksheet: build and setup, domain, hosting, content, licences, integrations, maintenance and applicable tax for the first year; then domain renewal, hosting, software or messaging charges, support and maintenance for later years. If a third-party price is unknown, mark it as an assumption or exclusion instead of hiding it inside the project total.

6. Agree milestones, revisions and acceptance

Ask for a delivery sequence with named outputs: discovery notes, sitemap, approved layouts, working build, content entry, testing, launch and handover. Each date should include the dependency behind it, such as your team supplying approved copy. Name who approves each stage and how long feedback may take.

Clarify revision rounds, feedback channels and what counts as a change request. Ask how a change to an approved sitemap affects price or schedule, and require a revised estimate before extra work begins. Before launch, agree checks that a non-technical owner can run: required pages are present, forms reach the right place, contact links work, booking or payment paths pass a test, and a backup is available. A staging link or walkthrough helps your team review the customer experience before launch.

7. Keep accounts, data and handover in scope

Identify who administers the domain, DNS, hosting, content system, analytics, email, payment account and code repository. The business should be able to access essential accounts, recover them if staff change, and transfer them to another provider. Ask what “source files included” means: it could mean design files, source code, a database export, documentation or only the content you supplied.

Make handover specific: account list, secure credential transfer, file and data export, backup and restoration notes, licence details, staff training and a named post-launch contact. If maintenance is included, define tasks, response time, emergency route and what becomes new paid work. “Support included” needs a period and a definition.

If the site collects personal data, ask which fields are collected, where submissions go, who can access them, how long they are kept, and how the business can export or remove them. The ODPC Personal Data Protection Handbook explains principles including transparency, purpose limitation, minimisation, storage limitation, security and accountability. Use it to frame questions for your supplier; seek qualified legal advice for compliance decisions. Do not send passwords in an ordinary project brief.

8. Compare proposals on the same basis

Map every quote to the same list: pages, content, integrations, testing, accessibility, revisions, launch support, hosting, licences, VAT, renewals and handover. Ask providers to mark each item included, excluded, optional or dependent on a third party. A lower quote may be right for a smaller scope; the risk is assuming it covers the same work when it does not.

Before a comparison call, ask: “What can I test at handover?”, “Which accounts will be in my business’s name?”, “What recurring charges start after launch?”, “What triggers a change request?”, and “What must my staff supply or approve?” Record the proposal version and assumptions in writing.

To request comparable bids, send one brief containing your business and service area, the main customer action, required pages and languages, who provides content, mobile tasks, integrations, desired launch window, existing domain or hosting accounts, first-year and renewal cost lines, support period, ownership and handover deliverables.

FAQs

Should a website quote include domain and hosting?

It should say whether each is included, who supplies it, who owns the account, what period the price covers and what renewal costs apply. If the provider buys it, ask how your business receives access and can transfer it.

How do I compare two quotes with different totals?

Align pages, content, integrations, testing, revisions, support and handover first. Then compare first-year and renewal costs separately. Do not treat a lower total as a saving until you know which work is excluded.

Should my business own the website domain?

Ask for the registrar account and renewal notices to be controlled by the business or a named business administrator. Confirm DNS access and the transfer process in writing.

Does “mobile-friendly” mean accessible?

Not necessarily. Ask which keyboard, focus, form-label, contrast and error-recovery checks are included. A mobile layout and accessibility review are related but not interchangeable.

Should the displayed price include VAT?

Ask whether each amount includes VAT and how it will appear on the invoice. KRA distinguishes taxable, zero-rated and exempt supplies, so do not assume identical tax treatment for every supplier or service.

Need this built for your business?

Write the one-page brief and compare the same customer journey, renewal costs and handover in each proposal. Browse the services catalogue , review the Hosting Setup service for the infrastructure portion, or book through the appointments route . Visit the UniqueTechCamp to learn about the company. For conversational automation, contact the AI Solutions Desk . Bring your audience, main action, page list, integrations and handover questions so the discussion starts with your business requirements.