Your website usually only gets touched by an outsider when something’s urgent: it’s broken, it’s slow, or you’re finally ready to grow it. That urgency is exactly when people skip the vetting they’d normally do. A few direct questions upfront save you from the most common bad outcomes, whether you’re hiring a freelancer, an agency, or bringing on a full development partner.
The questions that matter aren’t about price. They’re about what happens after they’re done and gone.
Primo Collab
Who actually owns what gets built
“Will I own the code, the theme, and the accounts when this is done?”
Some developers build on accounts they control: hosting, domain registrar logins, plugin licenses, and hand over limited access even after the project ends. Get explicit about full ownership handoff before work starts, not after you’ve paid the final invoice and need something changed.
“Can I get admin access to everything from day one?”
You should have visibility into your own site’s hosting, CMS, and any third-party tool accounts throughout the project, not just at the very end. If someone resists giving you admin access early on, that’s worth asking about directly.
What happens when something breaks
“What’s your process if the site goes down after launch?”
A vague “we’ll take care of it” isn’t a process. Ask for something concrete: response time expectations, whether it’s covered under the original scope or billed separately, and who you actually contact.
“Do you test changes on a staging site before pushing to production?”
Anyone making direct changes to a live site without a staging environment is accepting risk on your behalf that you probably don’t know about. This is one of the clearest signals of how careful someone’s process actually is.
How the relationship actually works day to day
“How do you communicate progress and get my sign-off?”
Some developers disappear for weeks and resurface with a finished, and sometimes wrong, product. Others check in constantly in ways that feel like they’re outsourcing decisions you hired them to make. Ask specifically how and how often you’ll hear from them, and at what points they’ll wait for your approval before proceeding.
“What’s explicitly not included in this quote?”
Scope creep goes both ways. A clear answer here (content writing, stock photography, ongoing maintenance, SEO setup) prevents the awkward mid-project conversation about what counts as “extra.”
“Can I see a site you built that’s still live, and can I talk to that client?”
A portfolio link only shows you the finished front end. A live reference and a real conversation with a past client tells you what the actual working relationship was like, and whether the site is still being maintained well a year later.
Red flags worth taking seriously
| What you hear | What it actually signals |
|---|---|
| “Don’t worry about the technical details” | You’re being kept out of decisions about your own asset |
| “We’ll figure out ownership later” | Ownership terms are being deliberately left vague |
| No mention of backups or staging | No safety net if something goes wrong |
| Pressure to sign before you’ve asked questions | Confidence that scrutiny won’t hold up |
| Can’t name a specific past client to reference | Limited or unverifiable track record |
The mistake to avoid
Most bad website hiring outcomes trace back to skipping ownership and process questions because the price or the portfolio looked good. Price and portfolio tell you about the work someone can produce. Ownership and process questions tell you what happens to you after the invoice is paid, which is usually the part that actually goes wrong.