Two agencies can quote a similar launch price while offering very different handovers. One may put the business in control of the domain, hosting, content, and subscriptions. Another may manage everything in its own account. Either model can work if it fits the buyer, but the operational and exit costs should be visible before signing.
Make a side-by-side asset table
Use the same rows for both proposals: domain registrar, DNS, hosting, CMS, source code or export, design files, copy, images, fonts, plugins, analytics, forms, and integrations. For each, mark the account owner, who pays, what the buyer can edit, what transfers at the end, and any license restriction. Write “unclear” rather than assuming a missing term is included.
Ask when access will be granted. Some providers invite the client at project start; others deliver an export after final payment. The contract should identify that milestone. Do not confuse a live URL with control of the site, or a CMS editor login with ownership of the hosting and domain accounts.
Price the ongoing obligations
List renewal fees for hosting, software, stock media, fonts, and support. Note who receives failure alerts and who handles updates. A low build price may carry a higher monthly operating cost; a managed plan may save staff time. Compare the total arrangement for the period relevant to your business, using actual quote figures rather than a generic industry average.
Check cancellation and transition: notice, final invoice, access, file formats, content export, redirect support, and the date service ends. Ask how long the provider will preserve backups after termination and whether that is included. A platform with limited export can still be a good fit, but the rebuild cost should be understood.
Run a transfer scenario
Ask each agency: “If we move to another provider next year, what exactly would we receive, who would hand it over, and which subscriptions would we need to replace?” A concrete scenario often exposes more than a sentence saying “client owns website.” If portability is critical, request a sample export or documentation of the platform’s limits.
Also ask what training is included and which staff roles can safely make common edits. A handover is not complete for an editor-managed site if the team cannot publish a basic update, unless the agreed model is provider-managed maintenance.
ARCHV’s website service page says ownership, access, files, licenses, and postlaunch support should be set in the proposal. ARCHV’s own exact deliverables are project-specific, and third-party rights do not automatically transfer. Put both offers into the website quote comparison and ask for written answers to unclear rows. A public small-business discussion about domain control shows this is a buyer question; it does not establish that any particular agency withholds domains.
One final question is who will perform the transfer. A promise to “provide access” may leave the business to coordinate export, DNS, forms, and analytics alone. If the offer includes transition assistance, specify its hours, fee, and deliverables. If it does not, budget for a new provider to inspect the handover package and rebuild anything that cannot be transferred.