Questions to Ask Before Hiring Anyone for Your Website

Hiring someone for your website can be stressful. You might not speak the technical language. You can’t easily judge quality. And horror stories abound of projects gone wrong.

Here’s how to protect yourself and find someone who’ll actually deliver.

Questions to Ask Before Hiring

About Their Work

“Can I see examples of similar projects?”

You want to see websites they’ve actually built, ideally similar to what you need. A portfolio full of corporate sites doesn’t tell you much if you need an e-commerce store.

Look for projects that went live and are still running. Ask if they have references you can contact.

“What will I actually own when this is done?”

This matters more than people realize. Make sure you’ll own:

• The final design files
• All code written for your project
• Your domain name (registered in YOUR name)
• Access to all accounts and passwords

Some developers build on proprietary systems or keep ownership of key assets. Clarify this upfront.

“What platform or technology will you use?”

Understand what you’re getting. Are they building on WordPress? Shopify? A custom solution?

Ask why they’re recommending that platform. Make sure it fits your needs and that you can maintain it afterward (or afford ongoing maintenance).

“Who maintains this after launch?”

Websites need updates, security patches, and occasional fixes. Who handles that?

Some developers include maintenance. Others hand off and move on. Neither is wrong, but know what you’re getting.

About the Process

“What’s the timeline?”

Get specific milestones, not just “about 6 weeks.”

A reasonable timeline might look like:

• Week 1: Discovery and planning
• Week 2-3: Design mockups
• Week 4-5: Development
• Week 6: Testing and launch

Be skeptical of timelines that seem too fast for the scope.

“How many revision rounds are included?”

Unlimited revisions sounds nice but often leads to scope creep. Two or three rounds of revisions is typical.

Understand what counts as a revision and what would be additional work.

“How will we communicate?”

Email? Slack? Weekly calls? Know how you’ll stay in touch and get updates.

Also clarify response times. Same-day? 24 hours? Knowing expectations prevents frustration.

“What do you need from me?”

Good developers will have a clear list: content, images, brand guidelines, login credentials, etc.

If they don’t ask what they need from you, that’s a concern. Projects stall when clients don’t provide necessary materials.

About Cost

“What’s included in this quote?”

Get itemized. A $3,000 quote could mean very different things.

Make sure the quote covers:

• Design
• Development
• Testing
• Revisions
• Launch
• Basic training
• Any third-party costs (hosting, plugins, stock photos)

“What’s NOT included?”

Equally important. Common exclusions:

• Content writing
• Photography
• Ongoing maintenance
• Hosting fees
• Domain registration
• SEO beyond basics

Get these in writing so there are no surprises.

“What happens if the project expands?”

Scope changes happen. Understand how additional work is priced.

Hourly rate for changes? Fixed price for additional features? Know before you need to ask.

Red Flags to Watch For

In Their Pitch

Guaranteed rankings No one can guarantee Google rankings. SEO takes time and has no guarantees. Anyone promising #1 rankings is exaggerating.

Pressure tactics “This price is only good today” or “We’re about to fill up” is sales pressure, not professionalism.

No contract Any legitimate professional uses a contract. If they don’t, walk away.

Won’t share references Experienced developers have happy clients. If they can’t connect you with anyone, that’s concerning.

Vague about process “We’ll figure it out as we go” is not a process. You want someone who knows how they work.

In Their Portfolio

All template sites If every site looks the same, they might just be installing the same template. Not necessarily bad, but know what you’re paying for.

Broken links and errors If their own portfolio has issues, imagine your project.

Sites that are down Projects that no longer exist suggest either unhappy clients or abandoned work.

In Communication

Slow responses during sales If they take a week to reply when trying to win your business, imagine after you’ve paid.

Can’t explain things simply Good developers can translate technical concepts for non-technical clients. If everything sounds like jargon, communication will be hard.

Defensive about questions You’re hiring them. You get to ask questions. If they’re annoyed by reasonable inquiries, that’s a bad sign.

Understanding Quotes

Web development quotes vary wildly. Here’s rough context:

$500-2,000 Basic template site with minimal customization. Good for simple needs. Limited support.

$2,000-5,000 Custom design on established platform. More attention to your specific needs. Reasonable for small business sites.

$5,000-15,000 Significant customization, e-commerce, or complex functionality. Appropriate for growing businesses with specific needs.

$15,000+ Enterprise-level projects, custom applications, or extensive integrations.

Price alone doesn’t indicate quality. A $5,000 project from an experienced developer might be better than a $10,000 project from an agency with overhead.

What Affects Price

• Complexity: More features = more work
• Customization: Template vs custom design
• Experience: Veterans charge more (usually worth it)
• Timeline: Rush jobs cost more
• Ongoing support: Included or separate?
• Location: Rates vary by geography

Get multiple quotes. If one is drastically cheaper, ask why. If one is drastically more expensive, ask what’s included.

Protecting Yourself

Get It In Writing

A contract should include:

• Scope of work (what exactly is being built)
• Timeline with milestones
• Payment terms
• Revision policy
• Ownership of deliverables
• Termination clause
• Liability limitations

Read it. Ask about anything unclear. A good developer won’t mind explaining.

Payment Structure

Avoid paying everything upfront. A typical structure:

• 25-50% deposit to start
• 25-50% at design approval or midpoint
• Final payment at launch

Don’t release final payment until everything works and you have access to all accounts.

Keep Your Own Records

Maintain copies of:

• All contracts and invoices
• Login credentials
• Design files they provide
• Key emails and decisions

If the relationship ends badly, you want to be able to move forward without them.

Own Your Domain

Register your domain in YOUR name, with YOUR email, on YOUR account. Never let a developer register it for you unless it’s clearly transferred to your ownership.

I’ve seen businesses held hostage because a developer owned their domain. Don’t let this happen.

Realistic Timeline Expectations

For a typical small business website:

2-4 weeks: Very simple sites, template-based, minimal content 4-8 weeks: Standard business sites with custom design 8-12 weeks: E-commerce or sites with significant functionality 3-6 months: Complex custom applications

These assume reasonable responsiveness from both sides. Projects stretch when clients take weeks to provide feedback or content.

After You Hire

Stay Involved

Review work at each milestone. Don’t wait until the end to give feedback. Catching issues early is cheaper than fixing them late.

Provide What They Need

When they ask for content, logos, or feedback—respond promptly. You can’t blame delays if you’re the bottleneck.

Document Everything

Keep records of decisions, changes, and approvals. “I thought we agreed on X” is easier to resolve with email evidence.

Plan for After Launch

Before launch, make sure you have:

• All login credentials
• Documentation for how to update content
• Clear understanding of ongoing costs (hosting, maintenance)
• Knowledge of who to contact if something breaks

The project isn’t done at launch. Make sure you’re set up for the long term.

---

Gustavo has worked in web development and digital marketing for 15 years. He writes these guides to help small business owners understand technology without the jargon.