A focused first site or smaller refresh. We establish the message, design, core pages, and technical essentials around the agreed scope.
Pricing
Clear starting points. Scope built around the actual work.
These ranges help you decide whether it is worth a conversation. The final proposal names the pages, features, search work, timeline, revisions, and handoff before anything begins.
Website starting prices
Three common levels of work.
A broader site with a more developed service story, multiple distinct page purposes, and deeper design and search planning.
Custom workflows, integrations, or application-like behavior. I quote the actual requirements instead of pretending every build fits one box.
Hosting, third-party fees, content volume, and any ongoing work are spelled out in the proposal rather than hidden in a label.
Additional work
Useful on its own or alongside a build.
01Existing-site SEOPage structure, technical signals, content priorities, and a plan grounded in the site.02Search Console and analyticsProperty setup or cleanup, meaningful events, and a readable baseline.03Focused site improvementsCopy, page layout, accessibility, speed, or a specific conversion path.04Ongoing careA defined maintenance scope when updates and follow-through are needed.
Add-on prices depend on what already exists and what needs fixing.
What a quote should settle
Know what is included before work starts.
The work
The proposal should identify page count and purpose, copy and design responsibilities, features, integrations, technical SEO, accessibility checks, revisions, and launch testing. If existing URLs are moving, the migration plan belongs here too.
The ownership
It should also name the timeline, dependencies on your materials, hosting and third-party costs, access, source and account handoff, and whether maintenance is included or quoted separately. The starting price becomes useful only when these details are clear.
Launch and handoff
A finished site should be usable after it goes live.
I check the public pages, contact path, redirects where needed, search signals, and measurement against the agreed scope. You should know where the domain, hosting, source, and connected accounts live and how updates will happen. If you want me to keep working on the site after launch, we define that work separately.
Before we start
Enough clarity to decide whether we should talk.
How long will my site take?
That depends on the pages, content, features, and how much of the current site we can keep. I will put a schedule and review points in the proposal before work begins.
What happens after I get in touch?
I look at the site you have or the business you are starting, ask where the current path falls short, and suggest a scope. You can decide from there whether it fits.
Who controls the site after launch?
The proposal names the domain, hosting, source or content system, third-party accounts, and update plan. I want those decisions clear while we are building, not discovered at handoff.
Start with the real problem
Tell me the outcome you want.
I can give you a useful scope only after seeing the site or hearing what the new one has to accomplish.
Tell me about your site You work directly with Trevor.