A businesswoman in an office reviewing a document and laptop while comparing proposals

A website design quotation in Botswana should be more than a total price and a promise to “build a website.” It should explain exactly what will be designed, built, tested, handed over and supported, as well as what will cost extra. That clarity protects your budget, your timeline and ownership of the digital assets your business depends on.

Two quotes can have very different totals because they describe very different projects. Before choosing the cheaper or more expensive option, use this guide to compare scope, technical foundations, integrations and handover terms on the same basis.

Direct Answer: The Essential Inclusions in Every Web Development Quote

A professional website development quote should clearly cover these six areas:

  • Scope and architecture: named pages, page templates, content responsibilities, CMS and required features.
  • Design and user experience: wireframes or mock-ups, responsive layouts, brand inputs and revision limits.
  • Technical foundations: hosting responsibilities, SSL, mobile testing, performance work, basic search setup and launch tasks.
  • Integrations and functionality: forms, WhatsApp, payment flows, booking tools, CRM or email connections, and who supplies access.
  • Ownership and access: domain registrant details, hosting access, CMS administrator access, content, database and any agreed source-code handover.
  • Commercial terms: timeline, payment milestones, change-request rates, warranty period, maintenance options and exclusions.

If a proposal cannot answer these points in writing, it is not yet detailed enough to compare fairly. Ask for clarification before signing rather than assuming an item is included.

Detailed Scope of Work: Pages, Content, and Architecture

Scope is the boundary of the project. A useful quotation names what is being delivered instead of using broad labels such as “five-page website” without context.

A business owner organizing brand assets and notes at a desk for website planning.
Proper content preparation is crucial before starting the website development process.

Start by separating page templates from populated pages. A template is a reusable layout, such as a service page or blog article. A populated page is an actual page built with final text, images and calls to action. One service-page template may support many service pages, but the quote should say how many pages will be loaded and checked.

Item to defineWhat the quotation should say
Pages and templatesNamed pages, number of unique layouts, navigation structure and whether future pages can be added through the CMS.
ContentWho supplies, writes, edits, migrates and uploads copy, product details, PDFs and images.
MediaWhether client photos, licensed stock images or supplied brand assets are used, and who pays for any licences.
CMSThe platform, editor access level, training or handover included, and any paid extensions required.
FeaturesSpecific functions such as a quote form, blog, catalogue, booking request, ecommerce checkout or member area.

For example, “website content included” can mean anything from placing client-supplied text into pages to researching and writing every page. Make the responsibility, approval process and number of pages explicit. The same applies to product uploads, which can become substantial work for an ecommerce catalogue.

Design Deliverables and Revision Allowances

A website is easier to approve when design decisions happen before full development. Ask whether the process includes a sitemap, wireframe, homepage concept or page mock-ups, and identify the approval point that allows development to begin.

Colleagues reviewing wireframes and mock-up designs at a meeting table.
Discussing design deliverables and revision limits ensures smoother project progression.

The quotation should also state how many revision rounds are included at each stage. A revision round is a consolidated set of feedback on an agreed design or build; it is not an unlimited sequence of new directions. Two or three rounds can be a reasonable planning allowance, but the number matters less than defining it clearly.

  • What deliverable will you review first: wireframe, visual mock-up or working staging site?
  • Who on your side has authority to consolidate and approve feedback?
  • How many revision rounds are included for design and content?
  • What counts as a correction versus a new feature or design direction?
  • How will additional work be priced and approved before it starts?

Approval milestones protect both parties. They prevent a project from moving into coding while key decisions about page structure, brand direction or functionality are still unresolved.

Domain, Hosting, and Digital Asset Ownership Rights

Your website is not fully under your control if someone else holds the domain, hosting login or main administrator account. Require the proposal to identify the account holder, access method and handover point for each asset.

For a Botswana domain, ask for the client business or authorised representative to be recorded as the registrant, not an agency employee or developer. NIC Botswana’s registrant and registrar guidance explains that .bw registrations are handled through accredited registrars for the registrant, subject to applicable policy and renewal. New .co.bw registrations are intended for commercial entities; do not assume a new registration directly at the bare .bw level works in the same way.

A good quote should identify:

  • the domain name, registrar and registrant contact details;
  • who pays renewal fees and who receives renewal notices;
  • the hosting provider, account owner and access credentials;
  • SSL certificate setup and renewal responsibility;
  • CMS administrator or super-admin access;
  • ownership or licensing terms for themes, plugins, fonts, images and custom code; and
  • what is transferred after final payment, including website files, database and agreed source code.

A domain registration is renewable service access subject to registry policy, not something to leave unmanaged. Keep renewal contacts current, store credentials securely and confirm the transfer process before a relationship ends.

Search Foundations, Mobile Responsiveness, and Performance

“SEO included” is too vague to evaluate. A launch quotation should distinguish baseline search-friendly build work from ongoing SEO strategy, content production, link earning or ranking work.

At minimum, ask whether the build includes responsive layouts across agreed modern viewports, HTTPS through an SSL certificate, sensible URLs, crawlable navigation, page titles and meta descriptions for agreed pages, image alt text where relevant, redirect handling for a redesign, analytics access and an XML sitemap. Google Search Essentials describe the technical requirements and broader practices that help Google access and understand content. Meeting them does not guarantee crawling, indexing, rankings or leads.

The quote should also say who checks the site before launch and how. “Fast website” is a promise; measurable performance work identifies the pages tested, test conditions, optimisation tasks and exclusions such as heavy third-party scripts. Core Web Vitals provide useful user-experience metrics, but no supplier can responsibly promise one score across every device, connection and future script configuration.

Finally, clarify the sitemap and handover process. An XML sitemap helps search engines discover the canonical URLs you want considered; follow Google’s sitemap guidance when deciding whether to submit it through Search Console. Submission is a discovery aid, not an indexing guarantee.

Forms, WhatsApp, Payment Gateways, and CRM Integrations

For many Botswana service businesses, the website’s main job is to turn visits into enquiries through a form, phone call or WhatsApp conversation. The quotation should identify the exact journey: what a visitor submits, where the notification goes, who responds and whether the lead enters a CRM or email platform.

Specify form fields, spam protection, consent wording supplied by the business where needed, notification email addresses, confirmation messages and testing. For WhatsApp click-to-chat, confirm the number, pre-filled message, tracking requirements and whether the button appears site-wide or only on key pages.

“Payment gateway integration” needs even more detail. A credible scope assigns responsibility for merchant onboarding, credentials, sandbox testing, checkout presentation, callback or webhook handling, payment-status verification and the move from test to live. For example, DPO Pay’s integration workflow shows why token creation, hosted checkout, callbacks and verification cannot be reduced to one vague line item. Gateway approval and available payment methods depend on the merchant account and provider terms.

If a Botswana-focused payment option is under consideration, the scope should also identify who supplies API keys and test access. Bluemoney’s payment API requirements, for example, document API keys, sandbox and live environments, callback URLs and return URLs. This is an implementation reference, not a recommendation of one provider over another.

Common Exclusions: What Most Quotations Do Not Include

Exclusions are not a warning sign by themselves. They are useful when they are visible. Problems start when a business assumes that a once-off build price includes ongoing work or third-party costs indefinitely.

  • Monthly maintenance: software updates, backups, security monitoring, uptime checks and small support tasks after launch.
  • Website copywriting: research, writing, editing, translation and approvals beyond loading supplied text.
  • Photography and video: professional shoots, editing and licensed stock media.
  • Third-party licences: premium plugins, themes, fonts, booking tools, CRM subscriptions, email platforms and gateway fees.
  • Advanced SEO: ongoing content, technical audits, digital PR, local visibility work and reporting beyond basic launch setup.
  • Major custom development: functions discovered later that were not in the agreed requirements.

Ask whether each cost is once-off, annual, monthly or usage-based, and whether it is billed directly by a third party. You can compare website package inclusions and separately priced items, including maintenance options and commonly separate costs, before comparing proposals. Treat this as one provider’s published structure, not a Botswana-wide price benchmark.

Vague Quotation vs Transparent Quotation: How to Spot Red Flags

When proposals look difficult to compare, convert each one into the same checklist. The following contrasts show where a headline price can hide risk.

A business owner with a colleague comparing printed website proposal documents and laptop.
Comparing detailed website proposals helps identify hidden costs and scope differences.
Vague quotation red flagTransparent professional standard
“Professional website design”Lists page templates, populated pages, CMS, required features and content responsibilities.
“Unlimited changes”Defines included revision rounds, approval stages and the rate or process for new requests.
“Domain and hosting included”Names the registrar and host, account holder, renewal costs, access rights and duration included.
“SEO-ready”Names the launch tasks: responsive build, metadata, sitemap, redirects where needed and technical checks.
“Fast and secure”Defines testing approach, SSL, update responsibilities and limits caused by hosting or third-party tools.
“Payment integration”Names the gateway, merchant responsibilities, credentials, test flow, callbacks and status verification.
“Support available”States warranty duration, support channels, response expectations, maintenance scope and fees.
One total with no milestonesShows payment milestones tied to agreed deliverables and a process for delay or change requests.

Do not reject a quote solely because it excludes something. Instead, ask whether the omission is intentional, priced separately and compatible with your launch plan. A lower quote may be appropriate for a smaller scope; it is risky only when the missing scope is unclear.

Example Website Quotation Breakdown: Compare Scope Before Price

Use this illustrative structure to request an itemised website design and development quotation. It does not represent a market average or a fixed package price; it is a practical way to make competing website developer quotes comparable.

Quotation areaExample detail to request
Discovery and planningKick-off session, sitemap, feature list, content inventory and agreed project timeline.
DesignHomepage concept, reusable page layouts, mobile approach, brand assets supplied and revision allowance.
DevelopmentCMS setup, named templates, responsive build, agreed forms and requested integrations.
Content populationNumber of pages or products loaded, who supplies copy and images, and migration from an existing site.
Quality assurance and launchBrowser and device checks, form testing, SSL, backups, redirects if relevant, sitemap and handover.
Handover and supportAdmin access, training or guide, warranty period, maintenance choices and hourly or fixed support rates.

For a simple brochure site, the feature list may be short but the content, ownership and launch checks still need definition. For ecommerce, booking or membership work, add a separate integration section because product data, payment testing, customer emails and operational workflows have more dependencies.

Quotation checklist to copy before you sign

  • I can point to every page, feature and integration included in the price.
  • I know who supplies copy, images, logos, product information and approvals.
  • I know the revision allowance and what happens when requirements change.
  • I know who owns and can access the domain, hosting, CMS, database and agreed code after final payment.
  • I can see all recurring, third-party and excluded costs.
  • I know the launch tests, warranty terms, support route and maintenance cost.
  • I have a written timeline, payment milestones and delay/change process.

Save this checklist with your procurement notes or turn it into a one-page document to send to each shortlisted provider. Their written responses will reveal whether the proposals are genuinely comparable.

Key Questions to Ask a Web Designer Before Signing

  1. Which pages, templates and features are included? Ask for a list, not a broad category.
  2. What do you need from us, and by when? Confirm content, images, product data, brand assets, approvals and account credentials.
  3. Will we see a staging version before launch? Establish where you will review design, content and functionality safely.
  4. How are forms, mobile layouts and key user journeys tested? Request the practical checks, especially for enquiry, booking or payment flows.
  5. Who owns the domain, hosting, website administrator account and data? Ask for the answer to appear in the agreement.
  6. What happens if we request a feature outside the scope? Confirm the approval and pricing process before work begins.
  7. What happens if either side delays the project? Clarify how missing content, late approvals and changed deadlines are handled.
  8. What is covered after launch? Ask about the warranty period, defects versus new work, maintenance scope and support rates.

How Lephutshi Scopes Web Development Projects

At Lephutshi Developers, the useful starting point for a website proposal is not a generic package label; it is the business goal, required customer journey and agreed scope. A transparent proposal should connect milestones to tangible deliverables, from planning and design approval through development, testing, launch and handover.

Before accepting any provider’s quotation, including ours, use the same buyer-protection standard in this guide: confirm responsibilities, access, technical launch work, exclusions and post-launch support in writing. That approach gives your team a clearer basis for approvals and gives the developer a defined brief to deliver against.

Conclusion: Protect Your Online Investment

A website design quotation in Botswana is a project roadmap, not just a price tag. Choose the proposal that makes scope, ownership, testing, exclusions and change control easy to understand, then resolve unclear points before work starts. Clarity is usually more valuable than a low headline figure that leaves essential work undefined.

If you want a proposal built around your actual goals, current setup and required features, request a transparent website quotation from Lephutshi Developers and use the same checklist to review it.

Recommended Reading

FAQ

  1. What should be included in a website quote?
    A website quote should include clear page and feature scope, design and revision rules, technical and search foundations, integrations, asset ownership and access terms, project milestones, exclusions, warranty and support terms.
  2. How much should a full website design cost in Botswana?
    The cost depends on the scope, content workload, design complexity, integrations, ecommerce requirements and post-launch support. Compare itemised deliverables and recurring costs rather than relying on a headline price or an assumed market average.
  3. What do website designers charge for revisions or scope changes?
    It depends on the agreement. A fixed-price quote should state the included revision rounds and explain whether additional work is billed hourly, at a fixed fee or through an approved change request.
  4. Who owns the website after development is completed?
    The agreement should state that, after final payment, the client receives the agreed access and ownership rights to the domain registration, hosting account, CMS access, content, database and any custom code or assets covered by the contract. Third-party licences may remain subject to their own terms.
  5. Does basic SEO in a website quotation guarantee Google rankings?
    No. Basic SEO and technical launch work can help search engines access and understand a site, but they do not guarantee crawling, indexing, rankings, traffic or enquiries.

Your Website Should Bring You Customers — Not Just Sit There

Build My Website
About Lephutshi Developers

About Lephutshi Developers

Lephutshi Developers is a Botswana-based digital marketing and web development agency dedicated to helping businesses attract more customers, enhance online visibility, and boost sales. Our team specializes in strategic SEO, engaging web design, and targeted PPC campaigns—delivering tangible results for your brand. Let us handle your digital challenges so you can focus on what matters most: growing your business.


About Us | Facebook | Twitter | LinkedIn | Google

Get Your FREE Botswana Business Website Planner

Find Out Exactly What Your New Website Should Cost—Before You Spend a Pula.

Enter your email and we’ll send the planner right away

Receive Amazing Deals

Subscribe To Our Newsletter

Get notified on new Deals and Promotions