Content and design
The amount of new copy, imagery, content organization, and visual work included rather than supplied by the business.
Before you build
Compare the work behind a website quote.
Two quotes can describe a website and still cover very different work. This guide helps you compare scope, responsibilities, and ongoing costs before deciding what fits your business.
Features and responsibilities matter more than page count.
A handful of pages can be straightforward or involve booking rules, account access, payments, and business-system connections. The cost conversation becomes clearer when those tasks are named.
Functional workflows
Booking, selling, account access, or operational steps that need to work beyond the public page.
Connections and migration
Existing tools, content transfers, public URL changes, and the access or cleanup needed before development.
Review and delivery
How the work is reviewed, what testing is included, and the handover or training needed at launch.
WebOrbit project scope, schedule, fees, and support terms are agreed in a separate written agreement. A general guide is not a project estimate.
Ask what each proposal includes.
If an item is important to your business but missing from a proposal, ask about it before comparing the total. An apparently lower quote may simply cover a smaller set of responsibilities.
| Area | What to clarify |
|---|---|
| Pages and content | Which pages are included? Who writes, supplies, uploads, and approves the content? |
| Design and revisions | What is reviewed at each stage, and how many or which refinements are covered? |
| Features | What does each form, booking, payment, or account flow actually do? |
| Connections | Which tools are connected, and which provider permissions or fees are required? |
| Testing and launch | What devices, key workflows, redirects, and launch tasks are checked? |
| Handover | Which account access, editing instructions, and training are included? |
| Support | What happens after launch, and what is treated as new work? |
| Changes and payment | How are additional requests approved, and how do payment stages relate to the agreed work? |
Separate development from recurring costs.
The build is one cost. Running the site can also involve domain renewal, hosting, email or message delivery, store or booking subscriptions, payment processing, and maintenance. Not every website needs every category.
Ask which accounts are in the business's name, who pays each provider, what renews automatically, and what happens if a service is cancelled. A clear list is more useful than an unexplained monthly total.
- Identify required third-party services and their account owner.
- Separate provider charges from development or maintenance fees.
- Confirm which support and changes are included in an ongoing arrangement.
- Discuss how the business can access or transfer its website if circumstances change.
Reduce scope without breaking the first release.
A smaller first release can be sensible if it still completes the customer's main task. For example, a clear service and inquiry path may be useful before a more complex account workspace is ready.
Deferring a feature should be an explicit decision. Record what is left out, how the business will handle the task in the meantime, and whether adding it later changes the design or integration work.
Keep the essential path
Preserve the information, action, and team follow-up needed for the first release to work.
Defer a complete addition
Plan a later feature as a separate piece of work rather than leaving the first customer journey unfinished.
Bring the constraints into the conversation.
Explain the business goal, essential features, available content, timing, and budget expectations. If a deadline depends on an event or another provider, say so. These details help shape a proposal instead of leaving assumptions hidden.
Ask the provider to explain the approach in terms you understand. You should be able to describe what is being built, what your team must supply, and what happens when the agreed work is finished.
Questions before the next step.
How much does a business website cost?
A useful estimate depends on the pages, content work, design, features, connections, review process, and support required. WebOrbit sets project fees in a separate written agreement after discussing the scope rather than treating every website as the same package.
What costs should I ask about beyond development?
Ask about domain renewal, hosting, relevant platform or provider subscriptions, message delivery, payment processing, and maintenance. Identify which are needed for the project, who controls the accounts, and who pays the charges.
Can we build in phases?
A phased approach can be discussed when the first release still completes the main customer task. Define what is included now, what is deferred, and how the deferred work affects future design or integration decisions.
Let's make it work
Bring a clearer brief to the conversation.
Tell us the goal, the constraints, and what you already have.