Most people hire a web developer once every five or six years. That’s not often enough to
get good at it, and it shows: we regularly inherit sites where the owner paid a fair price,
got something that looked fine, and still ended up stuck.
Usually nothing dishonest happened. The questions that would have surfaced the problem
just never got asked, because nobody tells you what they are.
So here they are. Ask these of us, ask them of whoever else you’re talking to, and compare
the answers. A good developer will be glad you asked — these are the questions that let us
explain what we actually do instead of showing you pictures.
1. “Who owns the site when we’re done?”
Start here, because it’s the one with teeth.
You want to own your domain, your content, your images and the site itself. You want
administrator access to it. And you want to be able to leave.
Some arrangements are built so you can’t. The domain is registered in the developer’s
name. The site is built on a proprietary platform that only they can host. You have an
editor login but not an admin one. None of that is necessarily malicious — plenty of it is
just how a small shop set things up years ago — but the effect is the same. When you want to
move, you can’t, and you discover it at the worst possible moment.
Ask it plainly: if I leave in two years, what do I walk away with? The answer
should be “everything, and we’ll help you move it.”
2. “Is this a custom design or a template?”
Both are legitimate answers. A well-chosen template, properly configured, is a reasonable
way to get a good-looking site for a modest budget, and anyone who sneers at that is
selling you something.
What matters is that you know which one you’re buying, and that the price matches.
Template work priced as custom work is the most common way small businesses overpay.
The follow-up question is more useful than the first one: can you show me two sites
you’ve built that don’t look like each other? A shop that only works from one template
family will hand you a portfolio where everything shares a skeleton. You’ll see it
immediately once you’re looking for it.
For the record: we build custom. We research your market and your competitors before we
design anything, because the point of the exercise is to look like you and not like the
business down the street. But ask us the question anyway. Make everyone answer it.
3. “Can I edit it myself?”
Then: show me.
Not a yes. An actual demonstration of changing a phone number, swapping a photo, adding a
staff member, posting an update. If editing your own site requires a support ticket every
time, you will stop doing it. Everyone does. Within a year your site says you’re open until
5pm when you changed to 6pm, and lists someone who left in the spring.
A content management system you can genuinely operate is worth more than most design
decisions, because it’s the difference between a site that stays current and a site that
quietly becomes wrong.
4. “What happens after launch?”
This is the question that separates a project from a relationship, and it’s the one most
often left vague.
Specifically:
- Who applies updates? WordPress core, plugins and themes all ship
security patches. Someone has to install them, and someone has to check nothing broke. - Who takes backups, and have they ever been restored? A backup nobody
has tested is a hope, not a backup. - How do I reach you, and how fast do you answer? Get a number. Ours is
24 hours as standard for routine updates. Whatever the answer is, you want it stated rather
than implied. - Is there a staging site? Changes should be tested somewhere other than
your live site. If every edit goes straight to production, every edit is a small gamble. - What’s the monthly cost, and what’s in it? Hosting, maintenance and
support are sometimes bundled and sometimes not. Either is fine. Not knowing is not.
A site is not a deliverable you receive once. It’s a thing that has to keep working while
you’re busy running your business.
5. “How will people find this?”
Here’s where you’ll hear the most hand-waving, so listen carefully to how the answer is
framed.
There’s a real distinction between building a site that can be found and
actively marketing it. The first is construction work: clean page structure, proper
headings, fast loading, accessible markup, structured data describing your business, a
sitemap, titles and descriptions written on purpose. That should be included in any build
worth paying for. It’s not an upsell; it’s doing the job properly.
The second is an ongoing discipline — content, local listings, reviews, link building,
reporting. Different skill, different time commitment, different budget.
Be suspicious of anyone who blurs the two, in either direction. A developer who says
“SEO is included” and means only that they installed a plugin has told you nothing. A
developer who says search isn’t their problem at all has built you something structurally
deficient.
We’re deliberately explicit about the line. We build it properly so it can be
found, and our sister studio
PG&J handles the ongoing
marketing side for clients who want it. Your site and hosting stay with us either way — it’s
two studios on one job, not a handoff.
6. “What do you need from me?”
The honest answer involves work on your end, and a developer who pretends otherwise is
setting up the project to stall.
Almost every build that runs late runs late for the same reason: the content didn’t arrive.
Photos, copy, product details, staff bios, the list of services with the actual prices. If
nobody has told you that you’re on the hook for this, the project will sit at 80% for
three months while everyone waits politely.
Ask what’s expected of you, when, and what happens if it’s late. Then ask whether they can
write the copy if you’d rather they did, and what that costs.
7. “Have you worked with a business like mine?”
Not “in my industry,” necessarily — more like at your scale and with your constraints.
A restaurant with a changing menu, a contractor who needs the phone to ring, a retailer
with inventory, a professional practice with compliance requirements: these are genuinely
different builds. So is a seasonal business, which plenty of Gulf Coast businesses are. If
two thirds of your revenue arrives in a few months, the site’s job and your marketing calendar
look nothing like a steady year-round operation’s.
There’s also a practical local question worth asking: what’s the plan if a storm takes
out power for a week? Your site should be the one thing still telling customers what’s
happening — hours, closures, reopening. That means hosting that isn’t sitting in your office,
and someone who can post an update from a phone. Obvious once said. Rarely discussed in the
proposal.
Questions we’d rather you didn’t lead with
Two things people reasonably care about but which turn out to be poor screening questions:
“How much?” — asked first, before scope exists. You’ll get a number, it
will be a guess, and the cheapest guess usually wins. That’s how you end up comparing a
five-page template build against a custom e-commerce site as though they were the same
purchase. Scope first, then price.
“Can you make it look like this?” — pointing at a site you admire. It’s
useful information about your taste and worth sharing, but it’s a weak brief. The site you’re
pointing at was designed for someone else’s customers and someone else’s goals. Better
question: what do you want a visitor to do within thirty seconds of landing here?
What a good answer sounds like
Across all of these, the pattern to listen for is specificity. Not confidence —
specificity. “We handle SEO” is confidence. “We’ll set up your LocalBusiness schema, write
your titles and descriptions, and make sure the site scores well on Core Web Vitals; ongoing
content and link building is a separate engagement” is specificity.
You don’t need to understand every term. You need to hear that the person has done this
before and knows which parts are theirs.
And ask them what they won’t do. A developer with a clear sense of their own edges
is usually the one who finishes.
If you’re in the middle of this decision
We’ve been building and hosting websites in Mobile since 2004, which mostly means we’ve
seen a lot of ways this goes wrong and have opinions about avoiding them. Happy to answer any
of the above about our own work, including the uncomfortable ones.
And if you’re weighing a proposal from someone else and want a second read on it, send it
over. We’ll tell you what we’d ask.