Quick answer
We've taken over a lot of half-finished, overpriced, or abandoned projects in the Twin Cities. Almost every one started with a bad hiring decision that could've been avoided in a 30-minute call. Here are the 7 questions that filter out the bad fits.
We've taken over a lot of half-finished, overpriced, or abandoned projects in the Twin Cities. Almost every one started with a bad hiring decision that could've been avoided in a 30-minute call. Here are the 7 questions that filter out the bad fits.
1. Will I own the code, the domain, and the hosting account?
If the answer isn't an immediate yes — walk away. You should always own everything. Always.
2. Can you show me 3 live sites you built in the last 12 months?
Old portfolios mean old skills. Live, recent work is the best signal.
3. What's your process for revisions and feedback?
Vague answers here predict missed deadlines. Look for a clear schedule, named milestones, and a single point of contact.
4. How do you handle SEO from day one?
If SEO is an 'add-on later', the foundation will be wrong. Good devs structure SEO into the build itself — semantic HTML, schema, performance, mobile-first.
5. What happens if I want to edit the site myself?
You should be able to update content without calling anyone. If they hard-code text into the codebase, run.
6. Do you support bilingual EN/ES content?
In Minnesota this matters more every year. Even if you don't need it day one, building bilingual-ready avoids a costly rebuild later.
7. What's the total cost — and what's not included?
Get the no list in writing: hosting, email, photography, copywriting, post-launch changes. Surprise invoices kill trust.
Takes less than 60 seconds
Get a Straight Answer to All 7You might also need:
Ready to talk to us?
Book a free consultation — takes less than 60 seconds.