Launch guides · Uncle J
What determines the cost of a company website?
A useful website quote prices a defined job. Start with what visitors need to understand and do, then compare deliverables, content responsibilities and running costs on the same basis.
Choose the job before the page count
A small company introduction may need services, selected work and a contact route. A lead-generation site may also need dedicated service pages, landing pages and conversion measurement. A catalogue needs structured product information. Each choice changes design, content and testing effort.
List the essential visitor questions first: what you offer, who it suits, where you operate, what proves the work and how to start. Then group those answers into useful pages. Ten pages that repeat the same message are not automatically a better scope than five carefully planned ones.
The main factors behind a quote
| Factor | What to clarify |
|---|---|
| Content | Who writes, translates, supplies images and approves each page? |
| Design | Adapted layouts or a bespoke visual system; number of distinct page types. |
| Languages | Arabic right-to-left layout, translation, bilingual navigation and metadata. |
| Functionality | Forms, content editing, search, external systems and automation. |
| Quality checks | Mobile layouts, keyboard use, performance, working links and form delivery. |
| Handover | Account ownership, source or export, editing guidance and support scope. |
Separate launch costs from running costs
Design and development are only part of ownership. Ask about domain renewal, hosting, email, paid tools, maintenance and future content changes. A proposal should say which costs recur, who pays the provider and what happens when support ends.
For an Egypt or Gulf project, confirm the quote currency, billing schedule and whether third-party subscriptions are included. A low headline price is hard to compare if the content, translation or handover is left undefined. Request a written scope before using price as the deciding factor.
Compare two proposals with one brief
- Send the same sitemap, target audience, language requirements and examples to each supplier.
- Ask for named deliverables and a clear list of assumptions and exclusions.
- Confirm revision rounds, acceptance criteria, content deadlines and who signs off.
- Check ownership of the domain, hosting and external accounts, plus ongoing editing access.
- Ask how enquiries will reach you and how launch checks and fixes are handled.
Use relevant work to test the approach
Open portfolio examples on a phone. Can you understand the offer, read the details and find the next action? Our Dar and Alsawah case studies explain discovery and enquiry journeys; BY RAWAN demonstrates a fashion storefront. Use the example closest to your business to discuss scope, rather than asking for a visual copy.
Before requesting a quote, prepare a short business description, audience, core services, existing identity, desired languages and any required integrations. If you have a target launch date or budget range, share it so the first proposal can prioritise what matters.
What search readiness should include
Ask for descriptive page titles, useful text, crawlable links, correct canonical and language URLs, a sitemap and a way to measure visits and enquiries. These are concrete deliverables you can review. Search rankings also depend on the content, competition and signals beyond launch, so separate ongoing search work from the initial build.
Common questions
Can I get a fixed price before a detailed brief?
A supplier can discuss an indicative scope, but a dependable fixed quote needs agreed pages, functionality, languages, content responsibilities and acceptance criteria.
Does a website quote include SEO forever?
Check the scope. Technical launch preparation is different from ongoing content, reporting and search improvement. Each should have explicit deliverables.
How can I reduce the first version’s cost?
Prioritise the core visitor journey, prepare content early and postpone nonessential integrations. Keep the data and page structure suitable for later expansion.