Jedidiah Digital logoJedidiah Digital

Custom Web Development, AI & Automation, Technology Strategy

Services

  • Web Development
  • AI Integration
  • Tech Consulting

Company

  • About
  • Pricing
  • Contact
  • Privacy Policy

Connect

541-255-8118
© 2026 Jedidiah Digital
HomeAbout
PricingResourcesContact
Web DevelopmentMarch 2, 2026

Questions You Should Ask Any Web Agency Before Signing

Business owner in a meeting with a web agency, reviewing questions on a laptop

Most business owners walk into a meeting with a web agency and hear a bunch of promises. Fast turnaround. Beautiful design. "We'll handle everything." Sounds great.

But if you don't know what questions to ask, you can't tell the difference between an agency that actually delivers and one that's really good at selling.

This isn't about tricking anyone or catching them in a lie. It's about showing up informed.

Think of it like buying a used car. A good salesperson will tell you everything that's great about the car. But you still want to pop the hood, check the mileage, and ask about the maintenance history.

Here are the questions that separate the real ones from the rest.

1. "Who owns the code and the website when we're done?"

This one matters more than most people realize.

Some agencies build your site on their own proprietary systems. That means if you ever want to leave, you're starting from scratch. Your site, the thing you paid for, stays with them.

You want to hear that you own everything — the code, the design files, the content, the domain. All of it.

If an agency hesitates on this question, that's a red flag the size of a billboard.

What to listen for:

  • "You own the code, content, and design outright."
  • "The domain and hosting are in your name, not ours."
  • "If you leave, we help you transition everything."

If you hear anything like "we license the platform to you" or "you can’t move the site elsewhere," proceed very carefully.

2. "What happens to my site after it launches?"

A website isn't a brochure you print once and forget about. It needs updates. Security patches. Content changes. Somebody has to keep the lights on.

Ask what post-launch support looks like:

  • Is there a warranty period after launch?
  • Is support included or a separate monthly fee?
  • What’s the process if something breaks?
  • What’s the response time if your site goes down on a Saturday night?

You want specifics, not "we'll be there for you."

Good agencies have a clear plan for this. Bad ones hope you don't ask.

What to listen for:

  • Defined support hours and emergency procedures
  • Clear SLAs (response and resolution times)
  • How they handle updates, backups, and security patches

3. "Can I edit my own content without calling you?"

If every time you need to change a phone number or update a blog post you have to email your agency and wait three days, that's a problem.

You should have access to a content management system (CMS) that lets you make basic edits yourself.

Think of it like renting an apartment where you need to call the landlord to change a lightbulb. That's not a good arrangement for anyone.

Ask to:

  • See the CMS you’ll be using
  • Watch how a simple edit is made
  • Understand what you can change vs. what requires a developer

If the answer involves "just learn a little HTML," keep looking.

What to listen for:

  • "We’ll train you on the CMS before launch."
  • "You can safely edit pages, images, and blog posts without breaking the layout."
  • "We use a well-known CMS, not a custom system only we understand."

4. "What's your approach to SEO?"

This is where a lot of agencies get vague. They'll say "we build with SEO best practices" and leave it at that. That’s not good enough.

You want specifics. For example, do they:

  • Set up proper page titles and meta descriptions?
  • Use clean, crawlable site structure and navigation?
  • Handle redirects correctly when migrating from an old site?
  • Optimize headings, internal links, and image alt text?
  • Consider page speed and Core Web Vitals?
  • Generate and submit XML sitemaps to Google Search Console?

A good agency can walk you through their SEO process without getting defensive. If they can't explain it in plain English, they probably aren't doing much of it.

What to listen for:

  • A clear checklist of on-page SEO tasks
  • How they handle technical SEO basics (URLs, redirects, sitemaps, robots.txt)
  • Whether they distinguish between one-time SEO setup and ongoing SEO campaigns

5. "Where will my site be hosted, and who controls that?"

Hosting is like the plot of land your building sits on.

Some agencies host your site on their own servers, which means they control access. If the relationship ends badly, your site could go dark.

Ask:

  • Where will the site be hosted (which provider)?
  • Who owns the hosting account?
  • Who has the login credentials?
  • Can you move to a different host later if you want to?

The best answer is that you own the hosting account and they manage it for you. The worst answer is "don't worry about it."

What to listen for:

  • "The hosting account is in your name; we’re just administrators."
  • Clear backup and uptime policies
  • How they handle scaling if your traffic grows

6. "What technology are you building this on?"

You don't need to become a developer to ask this. But you should know whether your site is being built on something modern and well-supported, or on a platform that peaked in 2012.

Ask:

  • What CMS or framework are you using?
  • Is it actively maintained and widely used?
  • Could another developer or agency take over this site in the future?
  • Are there any parts of the system that are proprietary to your agency?

A site built on a proprietary or outdated framework is like buying a car where only one mechanic in town knows how to fix it. That gives you zero flexibility down the road.

What to listen for:

  • Use of mainstream, well-supported tools
  • Avoidance of unnecessary lock-in
  • A simple explanation of why they chose that stack for your project

7. "What's a realistic timeline, and what could delay it?"

Every project has a timeline. And every honest agency will tell you that timelines depend on both sides doing their part.

Ask:

  • What’s a realistic delivery window for a project like mine?
  • What are the major milestones (design, development, content, testing, launch)?
  • What typically causes delays?

If they say "nothing, we always deliver on time," that's either a lie or they haven't done enough projects to know better.

The honest answer involves:

  • Content delivery from your side
  • Feedback and approval turnaround
  • Scope changes and new feature requests

A good agency sets expectations up front instead of making promises they can't keep.

What to listen for:

  • A clear project plan with phases
  • How they communicate progress and blockers
  • How they handle changes to scope or priorities

8. "Can I see examples of sites you've built for businesses like mine?"

Portfolio pieces are great, but context matters.

A beautiful e-commerce site doesn't tell you much if you're a local service business. Ask for examples that match your:

  • Industry (or at least a similar one)
  • Business model (e-commerce, lead generation, content-driven, etc.)
  • Size and complexity
  • Goals (more leads, more sales, better branding, etc.)

Better yet, ask if you can talk to a past client. That tells you more than any portfolio ever will.

What to listen for:

  • Case studies with real outcomes (traffic, leads, revenue, conversions)
  • References who are willing to speak candidly
  • Evidence they understand your type of customer and sales process

The real point

None of these questions are gotchas.

Any agency worth hiring will answer all of them without breaking a sweat. They'll probably respect you more for asking.

The agencies that stumble, get defensive, or try to change the subject? Those are the ones that rely on you not knowing what to ask.

Now you do.

[@portabletext/react] Unknown block type "image", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "code", specify a component for it in the `components.types` prop