The price is really paying for decisions
Two websites can have the same number of pages and require completely different amounts of work. A simple service website with supplied copy and one contact form is not the same project as a site that needs strategy, original writing, booking, payments, products, customer intake, multiple locations, or a content migration.
A responsible proposal separates the one-time launch work from the services that continue after launch. That makes it possible to compare offers without confusing a low setup price with a higher long-term obligation—or a high setup price with no support afterward.
- Strategy, structure, and customer-path planning
- Original design versus a lightly edited template
- Copywriting, editing, and content collection
- Forms, booking, payments, products, portals, or integrations
- Domain, DNS, email, analytics, and Search Console setup
- Hosting, security, backups, maintenance, and future updates
What should be written into the agreement
The agreement should name the exact deliverables, payment schedule, customer responsibilities, revision limits, launch requirements, ownership, platform access, ongoing services, and what costs extra. If the proposal only says “professional website,” the customer cannot reliably compare it to another offer.
- Exact page or template scope
- Who writes and approves the content
- What features and integrations are included
- How many revision rounds are included
- Who owns the domain, content, accounts, and final site
- What happens if monthly service ends
A cheaper website can become the expensive option
A low initial price can be reasonable for a very small scope. It becomes expensive when the site cannot be edited, performs poorly on phones, has no clear contact path, hides ownership rules, or requires a new vendor for every basic change.
The better comparison is total cost of ownership: launch price, required monthly charges, update costs, platform fees, replacement risk, and the business lost when customers cannot understand or trust the site.
How RareSons prices the work
RareSons uses written launch payments and defined monthly packages instead of open-ended hourly billing. The public pricing page lists the current package structure, included website scope, support limits, print details, and work that requires a separate fixed-price proposal.
The right starting point depends on what the business already owns and what the website has to accomplish. A visibility review should happen before the final scope is recommended.
- Review the current website and accounts
- Define the customer action the site must support
- Separate launch work from ongoing service
- Document every included deliverable
- Approve fixed-price changes before extra work begins
Related RareSons services
Common questions
Does a small business need a custom website?
It needs a website shaped around the real business, customer, content, and desired action. That can use a reliable platform or framework without forcing every project into a generic template.
Should hosting be included in the price?
The proposal should clearly state whether hosting is included, how long it is included, what maintenance is provided, and what happens if the service ends.
Who should own the domain?
The business should retain documented ownership and recovery access to its domain and core business accounts, with vendors receiving only the access required for their work.