Every few weeks I talk to a business owner in New York who’s already been burned once — they hired an agency or a freelancer, got a site that looked fine in the demo, and then watched it fall apart six months later in some way nobody warned them about. So before we even talk about our own services, here’s the honest checklist I’d use myself if I were hiring a web development company in NYC today.
Ask to see real, working projects — not just screenshots
A portfolio page full of polished screenshots tells you almost nothing about how a site actually performs. Ask for links to live sites the company has built, and actually click around on a phone, not just a laptop. Load a few pages, submit a test form if you can, check how fast it feels. If an agency is reluctant to share live links and only wants to show you static images or a slide deck, that’s worth noticing — it usually means the finished product doesn’t hold up as well as the pitch.
Understand who actually writes the code
Plenty of NYC “web development” shops are really project managers who outsource the build to a subcontracted team overseas with little day-to-day oversight, which isn’t automatically bad, but you should know it’s happening so you understand who to expect communication from and what timezone overlap looks like for revisions. Ask directly: who will be writing the code, and who do I talk to if something breaks after launch? A vague answer here is itself useful information.
Get a real scope, not a vague package
“Website package — $2,500” with no further detail is a red flag. A company that scopes projects properly will ask about your actual content, your integrations, your timeline, and give you a breakdown of what’s included — number of pages, whether the CMS is easy for you to update yourself, how many rounds of revisions are covered, and what’s explicitly excluded. Vague packages are where scope disputes and surprise invoices come from later, because “that wasn’t in the original scope” becomes a fight nobody wins cleanly.
Ask what happens after launch
This is the question that separates agencies that want a long relationship from ones that want a one-time payment and to move on. Do they offer maintenance plans? What’s their actual response time if something breaks — hours, or “we’ll get to it next week”? Who owns the hosting account and the domain registration — it should always be you, never the agency, because I’ve seen businesses effectively held hostage by a previous developer who kept control of the domain and disappeared or became unresponsive.
Check how they handle SEO expectations
Be skeptical of anyone promising specific rankings or “guaranteed page one on Google.” Nobody can honestly guarantee that, including us — rankings depend on competition, content, backlinks, and factors outside any single developer’s control. A credible company will talk about technical SEO foundations instead: site speed, mobile usability, proper metadata, clean URL structure, and a content strategy, without overpromising positions they can’t actually deliver.
Local NYC considerations matter more than people expect
If most of your customers are local, ask specifically how the company handles local SEO — Google Business Profile optimization, local schema markup, and NAP (name/address/phone) consistency across directories and citations. A generic national agency sometimes treats every client identically regardless of whether they’re a Manhattan retailer competing hyper-locally against five nearby competitors, or a nationwide e-commerce brand where local signals barely matter. That distinction should shape the actual strategy they propose, not just the pricing tier.
Ask about their testing process, not just their design process
A lot of agencies show beautiful mockups and talk at length about design philosophy, but say very little about how they actually test a build before launch. Ask specifically: do they test form submissions end to end, check payment flows with real test transactions, verify the site across different browsers and real devices rather than just a browser’s device-emulation mode? The gap between “looks right on a laptop” and “actually works everywhere a real customer will visit from” is where a lot of post-launch fire drills come from.
Get references you can actually call, not just quotes on a page
Testimonials curated for a website are selected precisely because they’re glowing. Ask for one or two actual client contacts you can call directly and ask pointed questions: did the project finish on time, were there unexpected costs, and — importantly — is the relationship still active, or did it end at launch? An agency confident in its work will connect you without hesitation.
The bottom line
Price matters, but it shouldn’t be the only filter you’re using. The cheapest quote is often cheap because corners get cut somewhere — usually in testing, in post-launch support, or in whether the underlying code is actually maintainable by someone else down the line if you ever need to switch providers. Ask the questions above, compare real answers rather than glossy pitches, and you’ll filter out most of the risk before you ever sign a contract.