
A website is one of the few purchases where the consequences of choosing badly show up years later. Not in how it looks — in whether you can update it, whether you own it, and whether moving to someone else means starting over.
These are the questions worth asking before anyone starts.
"Who owns the domain?" It should be you, registered in your name, in an account you control. If a previous provider registered it for you, verify that now rather than during a dispute.
"Whose account is the site hosted in?" Sites built inside an agency's account are functionally hostages. You want the site in an account with your name on it, even if someone else manages it day to day.
"Do I get access to everything?" Domain registrar, hosting, CMS, analytics, and any connected services. You don't have to use those logins. You do have to have them.
"What happens if we stop working together?" Ask before you're in that situation. A clean answer means a professional relationship. A vague one is a warning.
Before hiring a web designer, confirm that your domain is registered in your name, your site is hosted in an account you control, and you receive credentials for everything. Sites built inside a provider's account are difficult and sometimes impossible to take with you.
"Can you show me the editing interface before we finish?" Not describe it — show it, with a real update. This single request predicts whether your site will still be current in two years.
"What can I change, and what requires you?" Text and images should almost always be yours. Layout and structure reasonably require help. Anywhere that line falls, you should know it before launch.
"What happens if I break something?" Good builds constrain what an editor can damage. If the honest answer is that you could destroy a page by editing text, that's a build problem.
"Who writes the content?" This is the most common cause of stalled website projects. If it's you, know that early — content is usually the bottleneck, not design.
"Who supplies photography?" Stock, your existing photos, or a shoot. Each has a different cost and a different result.
"How many pages, exactly?" "A website" is not a scope. A page count is.
"Is SEO setup included, and what does that mean?" Basic technical setup — titles, descriptions, structure, sitemap — should be included. Ongoing SEO work is a separate service. Make sure you both mean the same thing.
"What about ongoing maintenance?" Platforms update, plugins break, things need attention. Know whether that's included, billed hourly, or entirely yours.
"What do you need from me, and when?" Projects stall on client deliverables more often than on production. A designer who names those dependencies upfront has done this before.
"How many rounds of revisions?" And what counts as one.
"What's the realistic timeline?" Then ask what typically causes overruns. Honest answers usually involve content and feedback.
"Can I talk to a client whose site you built two years ago?" Recent references show whether someone delivers. Older references show whether what they delivered held up.
Ask a prospective web designer to demonstrate the editing interface with a real update before the project ends, and ask to speak with a client whose site they built two years ago. Recent references show delivery; older ones show durability.
The platform. Most modern platforms are capable of building a good small business website. The build quality matters far more than the tool.
Portfolio aesthetics alone. A beautiful site that nobody can update, that loads slowly, or that doesn't convert is a failure with good taste.
Price as a lead signal. The relevant comparison is what's included: content, photography, page count, revisions, ongoing support. Cheap quotes usually exclude the expensive parts.
Who should own my website domain?
You should, registered in your name in an account you control. A provider can manage it, but ownership belongs with the business. Domains registered under a provider's name create serious problems if the relationship ends.
What should be included in a web design quote?
Page count, who writes content, who supplies photography, number of revision rounds, basic SEO setup, launch, and what maintenance is or isn't covered. Quotes without these are estimates, not scopes.
Can I edit my own website after it's built?
You should be able to edit text and images at minimum. Ask for a live demonstration of the editing interface before the project ends — not a description of it.
How long does a small business website take?
Typically several weeks to a few months. Content and feedback cycles usually take longer than design and build, which is why the timeline depends heavily on your availability.
What happens to my website if I stop working with my designer?
If you own the domain, control the hosting account, and hold all credentials, nothing — you take it with you. If any of those sit with the provider, it can become complicated. Confirm before starting.
Does the platform my site is built on matter?
Less than most people assume. Build quality, editability, speed, and structure matter far more than the underlying platform for a typical small business site.
Want a straight answer on scope before anything starts? Schedule a free consultation at jpetrous.com | contact@jpetrous.com | 586-563-6634.











You built the email, it looked great in preview, and then someone sent you a screenshot where everything collapsed. Email is the most technically hostile environment in digital design. Here's what actually survives it.
Read More
Pro bono work can build your portfolio and your standing in the community. It can also eat your billable hours and set a precedent you'll have to undo. An honest ledger from someone who just finished a big one.
Read More
They handled my wedding flowers and, years later, a custom corsage for the Daddy-Daughter Dance. A Main Street florist that's also a full gift shop.
Read MoreBefore you go
Call or send a message. Tell me what you're working on and I'll tell you honestly whether I'm the right fit.