What to Send for an Accurate Website Estimate

To receive a useful website estimate, send the business goal, primary audience, desired customer action, current website, initial page list, content responsibilities, required functions, integrations, migration needs, ownership expectations, working budget, deadline, and two or three explained references. A concise, specific email is enough to begin.

You do not need to choose a framework, draw every screen, or write a formal request for proposal. The provider needs enough evidence to distinguish a focused lead-generation site from a content, commerce, portal, or multi-location project.

1. State the business result

Complete this sentence: "The new website should help [specific audience] understand [offer or proof] and [primary action]."

Examples include requesting a qualified estimate, booking an appointment, visiting a location, purchasing a defined product, applying for a role, or understanding a complex service before a sales call. "Look modern" is not enough to estimate because it does not identify the work the site must perform.

2. Send the current website and access status

Provide the URL, platform if known, host, domain registrar, and whether the business controls administrator accounts. State what works, what fails, and what must not be lost.

Include analytics or search access if the existing site attracts useful traffic. A redesign estimate should account for content inventory, URLs, redirects, forms, measurement, and migration—not just new page design.

3. List the pages that must exist at launch

A rough page inventory is enough:

• Home.
• Priority service or product pages.
• About, team, trust, or proof.
• Locations or service-area information.
• Case studies, portfolio, menu, resources, or frequently asked questions.
• Contact, estimate, booking, application, or purchase path.
• Required policy pages.

Mark each page as existing, supplied new, needing editing, or needing original writing. Content uncertainty can change the estimate as much as design.

4. Name every function and connected product

List forms, uploads, booking, ecommerce, donations, payments, calculators, directories, maps, search, filters, accounts, portals, languages, and restricted content.

For integrations, provide the actual product and plan: CRM, scheduler, payment processor, email platform, call tracking, accounting, inventory, or another service. "Connect our CRM" is not estimable until the provider knows the data, direction, access, and failure behavior.

5. Clarify content, brand, and proof

State who supplies and approves business facts, writing, logo files, brand rules, photos, videos, reviews, testimonials, licenses, credentials, project examples, claims, privacy language, and regulated content.

Send a sample of the strongest real material. Do not present a fictional demo as client work or ask the developer to invent results. A responsible estimate distinguishes supplied evidence from writing, photography, editing, and professional review.

6. Explain locations and search needs

List the real services, locations, and service area. Include the current business-profile links and any pages or search terms known to produce inquiries.

Do not request hundreds of duplicated city pages. Ask for a structure that supports real service and location information, accurate metadata, internal links, structured data where appropriate, sitemap, redirects, and measurement.

7. Share budget and timing

A budget range tells the provider which outcome to fit. At Vertinus's $49.99 hourly rate, $3,000 represents roughly 60 hours and $5,000 roughly 100 hours.

Give the deadline and its reason. A lease opening, campaign, event, platform shutdown, or seasonal window creates different scheduling risk from a preferred date. Include when content and approval will be available.

8. Name the owner and approver

Identify the person who answers business questions, consolidates feedback, approves content and design, controls accounts, and accepts launch. Several stakeholders can contribute, but one responsible decision path keeps the estimate and schedule credible.

What not to send by ordinary email

Do not send passwords, private keys, customer records, patient information, employee files, payment credentials, production database exports, or confidential documents through an unapproved channel.

Use screenshots, redacted examples, field lists, and approximate counts for the first conversation. Sensitive access and transfer should be planned after the parties agree on scope and safeguards.

A copyable estimate request

1. Business and goal: We provide ___ to ___ in ___. The website should help them ___.
2. Current site: URL ___; platform ___; account control ___; main problems ___.
3. Launch pages: ___.
4. Content: We supply ___; we need help with ___; final approver ___.
5. Functions: Forms, booking, ecommerce, uploads, search, portal, or other behavior ___.
6. Integrations: Product, plan, and data to move ___.
7. Migration and search: Content, URLs, analytics, locations, and important pages ___.
8. Ownership and care: Domain status ___; hosting preference ___; ongoing support ___.
9. Budget and timing: Range ___; desired launch ___; reason ___.
10. References: URLs ___; what is useful about each ___.

What a useful estimate should return

The response should identify pages, components, content assumptions, functions, integrations, migration, redirects, search foundations, accessibility and performance testing, analytics, launch work, ownership, estimated hours, schedule, exclusions, recurring providers, and acceptance.

Vertinus bills only for time actually worked up to the approved estimate. Work added outside the agreed scope is estimated and approved separately; overage for the agreed scope is absorbed by Vertinus.

For the longer planning version, use the website project brief. Compare likely ranges in how much a small-business website costs and confirm asset control with the website ownership checklist.