Ask for a scope before a number
A five-page brochure site and a customer portal may both be called a website, but they are different projects. The first helps a visitor understand a service and make contact. The second may need accounts, permissions, payments and support workflows. Compare quotes only after the intended outcome and responsibilities are clear.
For a small service business, begin with three questions: who needs the site, what decision should it help them make, and what should happen after they inquire? Those answers are a better starting point than the number of visual effects.
Separate the estimate into useful parts
Request line items for discovery, design, development, content preparation, integrations and launch. Identify who supplies copy and images, how many revision rounds are included, and what counts as a change in scope. A lower build price can still leave significant work for your team.
- List required pages and reusable page types.
- Specify forms, booking, payments and external systems.
- Name the person responsible for copy, images and approvals.
- Separate essential launch features from later improvements.
Remember the cost of keeping it useful
Hosting, domains, paid tools, content changes and technical maintenance belong in the discussion. Ask which accounts you will own, what happens if you change providers, and whether routine updates are included or billed separately.
Use a simple planning calculation: first-year budget = agreed build scope + recurring services + planned updates. Avoid adding a sales-growth assumption unless you have evidence to support it. A website creates an opportunity to improve a customer journey; it does not guarantee demand.
Compare three scopes for the same business
An illustrative starting scope could be a focused service site with an inquiry form. A second scope could add original photography, several service pages and a content system. A third could connect lead routing, booking and reporting. These are scope examples, not Raytech packages or price promises.
Bring the same written brief to each agency. Ask what is excluded and how success will be checked. When we provide a Raytech estimate, the useful question is whether the proposed work solves your actual problem at a cost you can maintain.
Build a budget you can interrogate
Use a transparent estimate instead of treating a quoted number as a package of unknown work. An illustrative 80-hour project at an assumed $100 per hour has an $8,000 labor allowance. Adding $1,200 of first-year services and a $1,200 contingency produces a $10,400 planning budget. These are arithmetic assumptions, not Raytech rates, a market average or a quote.
Ask each supplier to replace those assumptions with the hours or fixed scope, responsibilities, recurring fees and exclusions in their proposal. A fixed-price project can still be compared this way without requiring an agency to bill by the hour.
| Scope | Work to clarify before a quote | Likely sources of added cost |
|---|---|---|
| Focused service website | Message, page templates, copy, inquiry journey and launch | Original content, photography, migration |
| Growth website | Multiple service journeys, CMS, analytics and conversion work | Content volume, experimentation, CRM integration |
| Custom application | Accounts, permissions, business logic and operational support | Integrations, data migration, security and maintenance |
What should you ask Raytech for?
Send your current site, intended audience, required integrations and the business outcome you need. We can then distinguish the essential launch scope from work that can follow later. Budget choices in our brief help frame that conversation; they are not published packages.
Request a written proposal with deliverables, milestones, approval responsibilities, payment schedule, ownership and support terms. Agree how changes are priced and what a successful launch must demonstrate. The useful comparison is the complete first-year commitment, not just the headline build fee.