Hiring a web studio in the DMV: what's actually worth asking

The DMV market, briefly

Roughly three tiers of web studio operate in the DMV. The large Beltway agencies built around federal contracts, scoped for enterprise work and priced for those budgets. Mid-tier shops with 8-30 employees serving regional businesses. And independents — solo founders or 2-3 person studios — delivering senior work directly. Each tier exists because their respective clients exist; the question is which tier matches the project you actually need.

Five questions worth asking on the discovery call

1. "Who's actually going to write the code?"

Agencies often pitch with their senior team and deliver with juniors. Independent studios pitch and deliver with the same person. Both can work, but the conversion ratio for senior-to-junior delivery matters: if 90% of your project is junior-built, you're paying senior rates for junior output. Ask directly.

2. "Do I own the code, the design files, and the AI prompts?"

If the answer is anything other than "yes, everything, in your repo," that's a vendor-lock arrangement. Some studios keep design files in their Figma, code in their GitHub org, AI prompts in their proprietary system — and your project is held hostage if you ever leave. Independent studios that take craft seriously give you everything. Verify by asking to see the contract clause.

3. "What's your handoff if I want to leave?"

Related to #2 but harder to fake: a good studio can describe the handoff packet in detail because they've done it. A bad studio gets vague ("oh we'd work that out"). Ask. "On day one of a switch, I'd get: this list of repos with admin access, this list of vendor accounts with my email on them, this Figma file, this Stripe / Supabase / Vercel ownership transferred." If the studio can't say that, run.

4. "Show me one project that went wrong."

Every studio with real client history has had at least one project go sideways. The ones that admit it and explain what they learned are the ones you want. The ones that say "all our projects have been smooth" are either lying or new.

5. "What do you NOT do?"

A studio that does "everything" probably does nothing well. The ones worth hiring can articulate their non-services clearly: "we don't do paid ads management," "we don't ship native mobile apps," "we don't take projects with a fixed deadline shorter than X weeks." Sharp positioning is a quality signal.

What to ignore

• Awards from publications you've never heard of (most are pay-to-play).
• Client logos used without context — was it a $5k landing page or a multi-year platform engagement?
• The agency's own website, beyond "does it load fast and not break." Some of the best studios have ugly sites; some terrible ones have beautiful sites.
• Stock case-study format with no specifics. If the case study doesn't name the metrics that moved, the team didn't measure them.
• "Award-winning" badges in the footer — verify what they're for.

Where investment levels land

Pricing varies a lot by scope, complexity, and the specific studio. As rough orientation rather than quotes:

• Marketing websites typically span low five figures (independent practitioners) to mid five figures and up (mid-tier and enterprise agencies), depending on page count, content strategy, and integrations.
• Custom web apps with auth, database, and admin UI usually start in the mid five figures and scale into six figures as scope grows.
• AI integration projects depend heavily on the autonomy model (drafts-only vs. confirm-to-act vs. fully autonomous), the data pipeline, and the guardrails — scoping it correctly matters more than the headline number.
• E-commerce builds on Shopify or similar platforms typically land in the low-to-mid five figures for a properly scoped storefront.
• Workflow automation and internal tools start in the low five figures and grow with the number of integrations and edge cases.
• Care plans / monthly maintenance arrangements vary widely — from a few hundred a month for a small site to mid-to-high four figures for a complex platform.

The actual quote should come from a real scoping conversation, not a public price grid. Anyone willing to quote without one is either guessing or selling a templated product.

Local vs remote

In-person matters for a single discovery call and maybe a milestone review. Everything else happens async — code lives in GitHub, design lives in Figma, communication lives in a portal or a chat. If a studio insists on weekly in-person meetings, they're either old-school agency or padding billable hours. The DMV's commute is bad enough that most local clients prefer async-first delivery once kickoff is done.