First decide whether to commission website work
The goal is not simply to outsource work, but to publish a needed site and be able to operate it internally. Choose an approach based on cost and the client's time for copy, review, approval, and operations.
Build in-house
Few pages, sufficient off-the-shelf features, and someone in-house who can build, publish, and maintain the site.
Even if tool fees are low, copy, images, setup, testing, updates, and incident response take time.
Outsource part
Responsibilities can be clearly separated, such as in-house copy with external design and implementation.
Gaps often appear at boundaries, so agree on material formats, handover dates, final reviewers, and integration ownership.
Commission design through operations
Custom features, multiple departments, personal data, migration, and downtime risks need coordinated management.
The client cannot delegate everything: it must decide goals, business rules, accurate copy, approvals, and contract ownership.
When not to rush a quote request
- You have not decided who should do what on the site.
- Internal decision-makers, content owners, and review deadlines are unknown.
- Required pages and features are not separated from optional ones.
- The current owners of the domain, hosting, email, and analytics are unknown.
Summarize requirements on one page before commissioning
A complete detailed specification is not necessary at the outset. But unless each agency receives the same assumptions, you cannot tell whether quote differences reflect the company or scope. List unknowns as items requiring proposals rather than hiding them.
Goals and success criteria
Define business needs such as company information, recruiting, inquiries, bookings, and sales. Use verifiable conditions such as reaching information, receiving inquiries, and staff updating content rather than publication alone.
Readers and main actions
Define key readers, information they need, and their final actions. Request navigation that supports comparison, contact, or applications rather than a structure driven only by internal organization.
Pages, features, and integrations
Separate required and future pages and features such as inquiries, search, booking, payments, membership, multilingual support, maps, and recruitment management. Record external services, contract holders, and data flows.
Copy, images, and migration data
Decide who supplies copy, photos, logos, and product information; if outsourcing, define interview, photography, and proofreading scope. State counts and condition of URLs, articles, images, forms, and redirects to migrate.
Updates, permissions, and maintenance
Decide internal versus agency updates, frequency, user count, and approvals. Separate administrator, editor, and viewer roles and require access removal when staff leave or transfer.
Quality, timing, and constraints
State devices, browsers, accessibility, performance, security, SEO migration, legal review, and desired launch date. If there is a budget cap, ask for proposals covering essential scope and phased release.
Compare website quotes by conditions, not just total price
A broad price range alone does not reveal page count, copy, features, quality, or contract term. This article does not fix a price: obtain individual quotes for the same deliverables and responsibilities. Align tax treatment, payment timing, and units for extra charges.
Initial-cost items
- Research, requirements, information architecture, and project management
- Design, copy, photography, illustrations, and purchased assets
- Templates, CMS, custom features, and integrations
- Data migration, URL changes, redirects, and launch work
- Device, browser, form, accessibility, and security checks
Ongoing post-launch costs
- Domains, hosting, CMS, external services, and paid licenses
- Maintenance, monitoring, backups, updates, and incident response
- Additional copy and images, analytics, improvements, and inquiry handling
- Renewals, minimum terms, cancellation, transfer, and data export
| Comparison item | Conditions to check |
|---|---|
| Deliverables | Page types and template count, features, copy and images, and source and data delivery scope, not just page count |
| Revisions | Definition and submission unit of revisions, changes needing a new quote, and treatment after approval, not just revision count |
| Project management | Meetings, communication, minutes, owners, review deadlines, and delays caused by the client |
| Launch and migration | DNS, email, hosting, old URLs, data, launch attendance, and rollback |
| Maintenance | Covered work, service hours, initial-response targets, monthly work allowance, excess rates, backups, and restoration |
| External contracts | Ownership, initial and renewal fees, minimum term, tax, exchange rates, data after cancellation, and price changes |
Compare website agencies on six criteria
Do not decide from portfolio appearance or search rankings alone. Compare how agencies understand requirements, who builds what, evidence of quality, and post-launch handover. If scoring, set weights first and exclude paid listings and referral fees.

Requirements and proposals
Do questions cover goals, readers, business, and operations? Are there proposals to remove unnecessary features or release in phases?
Team and responsibility
Are owners for sales, management, design, implementation, quality, maintenance, subcontracting, and communication clear?
Relevant experience
Beyond industry, has the team handled similar features, operating models, scale, and constraints? Can it explain its role and post-launch results?
Quality verification
When, by whom, and with what tools will browsers, mobile, forms, accessibility, performance, and security be checked, and how will results be shared?
Operations and handover
Are update procedures, admin rights, contracts, source, data, backups, incident contacts, and transfer terms supplied?
Quote and contract transparency
Are inclusions, exclusions, assumptions, extra rates, payment timing, and cancellation terms explained, with verbal promises documented?
Selection warning signs
For unconditional promises such as guaranteed top rankings, everything included, or immediate completion; unclear deliverables or permissions; excessive contract pressure before a quote; or an unknown contact, do not decide immediately. Confirm the conditions in writing.
Select using the same quote request
Different explanations to each agency prevent comparison. Provide the same one-page requirements, existing site, desired timing, budget approach, and question deadline together; identify unknowns in proposals and quotes.
- 1
Define candidate criteria
Define only essential project conditions such as technology, location or in-person needs, post-launch support, information management, and budget. Do not make company size or fame the goal.
- 2
Share the same materials
Share the same version of goals, readers, pages, features, materials, existing environment, timing, team, and questions. Limit confidential information and choose a sharing method.
- 3
List questions and assumptions
Questions reveal missing requirements. Share answers equally with all candidates and record assumptions, alternatives, and uncertain amounts in a comparison table.
- 4
Hear proposals explained
Before design proposals, ask for explanations of goals, structure, operations, quality, risks, and delivery. Check whether the actual project lead participates.
- 5
Separate evaluation and clarification
Evaluate required-condition fit, proposal quality, team, costs, and terms separately. If a low quote excludes necessary scope, request a revised quote to align conditions.
- 6
Record the decision
Record reasons for selection and rejection, remaining risks, and negotiation items; contract after internal approval. Do not include advertising or referral fees in evaluation.

Checklist to include with a quote request
- Goals, audience, main actions, and success criteria
- Page list, required and future features, and reference URLs
- Owners and status of copy, images, logos, video, and existing data
- Current domain, hosting, email, CMS, and analytics arrangements
- Desired launch date, internal reviewers, and review time
- Quote tax treatment, validity, payment terms, included scope, and extra-work rates
Agree on deliverables, changes, acceptance, and rights before contracting
Connect proposals and quotes to contract documents covering deliverables, changes, acceptance, and post-launch ownership. Legal classification and copyright decisions vary by project; consult a specialist for important matters.
Deliverables and delivery method
Define necessary deliverables by format and deadline, including copy, images, design files, source, settings, data, account inventories, test results, and instructions as well as the public site.
Change management
Distinguish requirement changes, minor revisions, and defects. Agree on request, impact review, quote, approval, and implementation steps; do not leave cost and timing ambiguous through verbal requests.
Acceptance and defect handling
Define acceptance tests, environment, deadline, reviewers, retesting, and how to report issues found after acceptance. Do not rely only on subjective criteria such as matching an impression.
Copyright, licenses, and materials
For deliverables, photos, fonts, themes, plugins, and external materials, check ownership and usage scope, modification, reuse, third-party licenses, and deliverability.
Accounts and contract ownership
Where possible, register domains, hosting, CMS, analytics, search management, and external services under ownership and permissions the client can maintain. Do not hand over only a shared password.
Secrets, personal data, and subcontracting
When handling inquiries or customer data, check access, storage, deletion, incident notification, subcontracting, and oversight. Share only necessary real data with the agency.
Make post-launch operability a delivery condition
Treating launch day as completion can leave the client unable to update, receive inquiries, or track renewals. Include a post-launch verification period and hand over a site the client can operate and transfer using its own permissions.
Immediate post-launch checks
Check key pages, form submission and receipt, email, booking and payment, HTTPS, old URLs, search-blocking settings, analytics, and mobile display, and share incident contacts.
Handover of management information
Receive an inventory of contract ownership, admin URLs, permissions, renewals, licenses, backups, and source and data locations; test the client's own access.
Update and maintenance boundaries
Separate internal copy edits from feature changes requested from the agency. Check exclusions, hours, initial response, restoration, extra fees, and handover on cancellation.
Periodic quality checks
Periodically review content, links, inquiries, permissions, software, backups, performance, and accessibility. Record results and the person who made fixes rather than updating only a date.
Completion checks
- Acceptance testing confirms goals and required functions are met.
- Inquiries and critical functions have been checked in production.
- The client has received contracts in its name and necessary admin access.
- Deliverables, instructions, test results, and contract inventories are retained.
- Maintenance, incident contacts, backups, cancellation, and transfer terms are understood.
Official sources consulted
The following primary sources were checked for contracts, personal data, security, accessibility, SEO, and copyright.
- Japan IPA: model information-system transactions and contracts, second edition (Japanese)
- Japan Personal Information Protection Commission: Act on the Protection of Personal Information guidelines, general rules (Japanese)
- Japan IPA: building secure websites (Japanese)
- Japan Digital Agency: introduction to web accessibility (Japanese)
- Google SEO Starter Guide
- W3C WAI: Plan
- Japan Agency for Cultural Affairs: copyright contract manual (Japanese)
Website commissioning FAQ
What does website development usually cost?
Scope varies greatly with page types, copy and photography, custom features, migration, quality checks, and maintenance, so an unconditional price range is not enough. Give several agencies the same brief and compare initial and ongoing costs, exclusions, and extra-work rates separately.
How many agencies should I ask for quotes?
There is no correct agency count. Limit the list to a number you can brief consistently and whose questions you can answer. Too many candidates can make comparison unreliable if conditions differ.
Is an agency with many projects automatically reliable?
Project count alone is insufficient. Check responsibilities on comparable business functions and operating models, the assigned team, quality checks, and handover. Confidentiality may limit public detail, so ask what can be explained and how.
Does commissioning SEO guarantee high rankings?
Rankings cannot be guaranteed. Google says there is no secret to first place. Besides technical settings, useful content, searchable structure, and ongoing updates matter. Ask about work, evidence, measurement, and improvement rather than guarantees.
Should the same agency maintain the site after launch?
Continuing with the agency is an option, but avoid being unable to move elsewhere. Receive contract ownership, admin access, source, data, backups, instructions, and cancellation and transfer terms; periodically review maintenance scope and cost.
Articles to review before and after commissioning
Align deliverables and responsibilities before comparing company names
Define goals and success criteria and give each candidate the same one-page requirements. Compare not only totals but included work, changes, ongoing costs, contract ownership, acceptance, and handover. The client still owns copy, approval, and business rules; finish with a site the client can operate and transfer using its own permissions.
Editorial policy
Finite Field Editorial Team
Drawing on website development and operations, we distinguish conditions clients can compare themselves from contract and security matters requiring specialist advice. Advertising commissions and individual vendors' sales terms do not change our conclusions.
Consult Finite Field
Discuss website requirements, development, and operations
Goals, required pages, the existing site, desired timing, and internal update arrangements help clarify scope. We can explain where we can assist with requirements, information design, implementation, hosting, launch, and maintenance.
Discuss website commissioning requirementsConsultation does not guarantee availability, timing, outcomes, or a quoted price. We will review the request and explain scope and any fees in advance.
