Website cost follows the amount of content, design work, languages and working features. Compare a written page list before comparing totals. A consultant with one service may use one page; three distinct services may each need their own explanation. A low initial figure says little when renewal costs and delivery files are unspecified.
For a useful pricing review, add an assumptions column beside every line of the proposed scope. For example, five service pages with approved client text is a different assumption from five pages whose subject matter still requires research and writing. The same page count can therefore represent different work. Ask the provider to identify the assumptions that would change the estimate if they proved incorrect.
Also distinguish content volume from visual complexity. Ten photographs placed in an agreed project layout may be a simpler task than two photographs requiring a new interactive presentation. Describe the expected visitor experience and ask for the associated deliverable, instead of using image count as a proxy for design work. Once the assumptions are visible, identify a smaller first release if the initial scope exceeds the budget. Keep the essential service explanation and contact route intact, and move clearly optional material to a separately priced later decision.
Begin with the work, not a price label
A website quote becomes useful when it describes the same problem you are trying to solve. Start with a page inventory: for example, home, services, two individual service descriptions, about and contact. Then write the reason for each page. If two pages answer the same question with nearly identical information, they may be combined. If one page must explain several very different offers, a separate page may improve clarity. This is a content decision before it is a pricing decision.
Count unique pages in the primary language separately from translated versions. In Orvunweb packages, a second language provides counterparts of the agreed pages; it is not an allowance for unrelated new pages. Standard privacy and cookie text placement sits outside the stated content-page allowance, while writing legal advice is not included. These definitions make two proposals easier to compare without inflating or understating the work.
Design complexity also needs a concrete description. A compact introduction with a form is different from a portfolio with several project compositions. Describe how visitors should use the content, which components can share a pattern and where a genuinely different layout is needed. A request for a premium appearance does not by itself explain those decisions.
Separate content, functionality and continued operation
For every text and image, name a supplier. A price that assumes approved copy is ready cannot fairly be compared with one that includes interviewing the owner and drafting all the content. Translation, photography and licensed assets should receive the same treatment. Ask whether the quote includes selecting images, purchasing rights, preparing the files or only placing material supplied by you.
Describe functions as actions with outcomes. A contact form collects and forwards or stores an enquiry. A booking system has additional questions about availability, changes and notifications. An online store adds transaction and order responsibilities. Writing all three as a contact feature hides substantial differences. Orvunweb packages focus on promotional websites; payment, memberships, booking engines and custom integrations require a separately agreed scope.
Next, divide initial creation from recurring operation. The domain must be renewed; business email may have its own subscription; paid services and later maintenance require decisions. Suitable static projects may use free hosting options under the provider’s current limits. That does not make every connected service free. Keep a simple cost register with the item, provider, account owner and renewal date, even when an item currently has no charge.
Compare a realistic pair of briefs
Consider an illustrative accountant who needs one language, five pages and a project enquiry form. Another business needs eight pages in two languages, a blog structure and more varied visual compositions. The second brief contains additional content placement, language checking and page work. The difference can be explained without pretending that all sites have the same production cost.
Orvunweb’s published creation options run from TRY 5,000 to TRY 20,000. These are Turkish-lira build prices, not monthly subscriptions or a currency conversion estimate. The written proposal confirms the selected scope and commercial details. Tax presentation and seller information must be verified before commercial publication; a visitor should not infer an unconfirmed tax treatment from an example.
To make a decision, request a single comparison sheet with included pages, languages, revisions, materials, delivery files and exclusions. Remove requirements you do not need, but retain the information visitors need to make contact confidently. A lower price is useful when it reflects a smaller, sufficient scope that both sides understand.
Compare packages
- Start: TRY 5,000
- Business: TRY 10,000
- Professional: TRY 15,000
- Signature: TRY 20,000
One-time build fee. Domain, email and ongoing maintenance are considered separately. A written proposal confirms the final scope.
Practical checklist
- Count unique pages
- List languages and content owners
- Separate integrations from contact forms
A concrete example: A consultant with one service may use one page; three distinct services may each need their own explanation.
A boundary to keep clear: A low initial figure says little when renewal costs and delivery files are unspecified.
Your next step
Tell Orvunweb about your project
