How do you write a brief the developer can quote on?
Explain what the business does, who the website is for and what a visitor should be able to do. List the pages you expect and any existing domain, logo, text or photographs. Describe the content you can supply and the content that still needs preparing.
If you need a system rather than a presentation website, describe the process it should support. For example, explain who records a booking and who confirms it. A feature name alone leaves important questions unanswered. Use sample information rather than live customer records.
Share references to explain a visual preference, but say what you like about each one. A moving image, a clear menu and a useful enquiry form are different requirements. Husaini's remote website design page explains the available services and published starting prices.
How do you agree the scope and what is not included?
Ask for a written list of pages, responsibilities and deliverables. Establish whether copy, imagery, extra pages, integrations and ongoing support are included. A design demo illustrates a direction; it does not define everything that will be delivered for your business.
At Husaini, a Normal Website is KSh 10,000 for up to three pages, a mobile-ready layout and a contact form. Animated Website is KSh 25,000 and 3D Motion + Animated UI is KSh 50,000. Other package page counts, content, motion assets, integrations and revisions need agreement in the quote. Compare the published packages using the same brief.
Separate the website build from optional annual plans and any third-party charges. Confirm which plan applies rather than adding alternatives together. Discuss timing against the actual scope and the content available; a price is not a delivery-time guarantee.
How should you review the work in stages?
Agree what you will review and how decisions will be recorded. Begin with page purpose and content, then inspect the layout and working interactions. When giving feedback, identify the page, the element and the result you expected so the developer can act on it.
Review on a phone as well as a desktop. Check that service information is understandable, text is readable and important actions are easy to find. Try the contact path and any agreed forms. Look at the actual page rather than approving a screenshot alone.
Keep a single agreed record of revisions and approvals. A request for another change is different from approving publication. Make the final go-live decision explicit after reviewing the agreed work.
Who owns the domain, hosting and files?
Agree ownership and access in writing before the project starts. Ask who registers the domain, who receives renewal notices and which accounts you will control. Establish what files and administrative access will be handed over and what support continues after launch.
Hosting and maintenance are separate questions. Ask what the selected service covers, who handles renewals and how future edits are requested. Confirm provider charges and any work outside the agreed scope rather than assuming that every update is included.
For a custom system, include software and data ownership in the quotation discussion. Do not assume a general website package describes the terms for a business application. The written scope should cover the actual project you are commissioning.
What payment terms should be confirmed?
Payment arrangements are confirmed in your quote. Ask what is due, when it becomes due and how that relates to the work you will review. Confirm any annual charges and any separately billed third-party subscriptions before proceeding.
Keep the approved quotation and the record of agreed changes together. If the scope changes, ask for the effect on price and delivery to be confirmed before the extra work begins. No particular payment provider or instalment arrangement should be assumed from a website's package list.
What should you ask for at handover?
Use the agreed scope as the checklist. Confirm which pages and interactions were delivered, how the domain is connected, and who holds the relevant account access. Ask how to request later changes and which optional support arrangement applies.
Review the contact details, service information and any time-sensitive offer before publication. Check links and forms again on the finished site. Agree the handover material needed to manage the site or work with a future provider, including any responsibilities that remain yours.
For a broader assessment of a provider's work, read the web designer evaluation checklist. It covers portfolio evidence, mobile layouts, enquiry flow, ownership and support. Use it alongside your own brief rather than treating a polished demo as proof of an agreed deliverable.
Frequently Asked Questions: what should I agree first?
Do I need to travel to Nairobi for a website project?
No. Husaini Tech Solutions handles website and software projects remotely across Kenya. Computer repair requires a visit in Nairobi.
Are the design demos completed client projects?
No. The website demos illustrate visual directions. The portfolio labels them as demos and also shows a RepairTrack web app walkthrough.
Can I assume hosting is included in a package?
No. Read the current offer and your quote. Hosting and maintenance are normally separate optional services, and any promotion has its own stated scope and expiry.