Already have a proposal? Use ARCHV's website quote review to mark unclear costs, or send us a redacted scope.

A website quote may cover design and development but not every asset, account, and service needed to keep the site live. A font, image, plugin, hosting plan, or payment tool can have its own price and terms. Those costs are not automatically improper; the problem is discovering them after the design or build assumes they have been approved.

Ask for two totals

First ask for the project total: what you pay to plan, design, build, test, and launch the agreed site. Then ask for the ongoing annual estimate: hosting, platform fees, domain renewal, paid plugins, subscriptions, support, and any licensed assets that recur. If usage can change the bill, ask what usage level the estimate assumes.

Do not compare a one-time project quote with a subscription quote as if they buy the same thing. A lower build price can be reasonable if ongoing hosting and support are clearly priced. A higher fixed fee can be reasonable if more work is included. The line items make the difference visible.

Check the asset before approving the design

Fonts. Ask whether the proposed typeface is free for the planned website use, already licensed by your business, or requires a new license. Who buys it, who owns the account, and what happens if the relationship ends? Approve a substitute font before paying for a design built around an unaffordable license.

Photos, video, and illustrations. Identify what your business supplies, what the designer creates, and what is bought from a stock library. Confirm permitted website use and whether the license extends to ads, print, or future agencies.

Plugins, templates, and themes. A one-time build may rely on software that renews yearly. Ask which licenses are essential to keep the site working or editable and who receives notices when renewal is due.

Hosting and platform. Separate the hosting account from the design fee. Ask who controls it, what level of service is included, and what migration would involve if you change providers.

Maintenance. Clarify whether updates, backups, security fixes, content edits, and incident response are included, separately contracted, or your responsibility. A short defect-correction period is different from indefinite maintenance.

Make the approval step explicit

A useful proposal lists each third-party item as included, client-supplied, separately quoted, or not needed. If an item is not yet known, set an allowance or require written approval before purchase. Record the price, renewal date, owner, and cancellation effect. Then recheck the schedule when a newly selected asset changes the design.

Run a simple exit-cost check

Ask what happens if you stop paying each recurring line item. Will the site stay live? Will an editor still be able to update pages? Will images or fonts need to be replaced? Could a form or booking tool stop delivering inquiries? These are different outcomes. A provider can explain the technical dependency without promising that a third-party vendor will keep its current price or terms forever.

Request an account inventory before final payment: service name, account owner, billing owner, renewal date, and cancellation or export path. Keep payment methods and administrator access under the appropriate business owner. If the provider’s account holds a license, identify whether the license can be transferred or whether the new provider must buy its own. Do not assume a file downloaded from a stock library can be reused under someone else’s contract.

For a quote comparison, use the same accounting period for both providers and add one-time build cost to the expected service and license cost over that period. This does not predict every future price change; it reveals a difference hidden by comparing only the initial invoice. A public client review mentioning an unexpected font cost is one reported experience, not evidence that a particular provider routinely surprises buyers. The practical safeguard is a written license schedule.

ARCHV's website service page says project proposals should distinguish supplied from commissioned content and disclose hosting, software, licensed assets, and ongoing support. ARCHV's estimate is a planning range; the final project price follows a reviewed scope. Ask for the itemized proposal before committing.

If you want help spotting unclear line items, contact ARCHV or use the quote review.